Hey I'm getting some unusual battery drain all of a sudden. Yesterday I had pretty intense use and lost 50% over 6 hours or so. Today I've had much less use and lost 40% in 2 hours.
Also this morning, I got the notification that 34.3.A.0.206 is available. Is it possibly that notification, or maybe something else causing the issue. I haven't installed anything new, but I did update apps in the play store. The battery usage says it's the Android System doing it though.
Did some digging, and it looks like pm-service and logd are running crazy, burning battery and CPU cycles. I'm having trouble finding out what pm-service is, but it may be power management or peripheral management. I can't find settings for logd levels, and I haven't checked my log at yet to see what it's writing.
dmesg shows countless entries of
IPC_RTR: msm_ipc_router_bind: pm-service Do not have permissions
But I can't figure out how to fix it or what it is. Any ideas?
it your phone getting hot?
some services my glitch and get stuck on ram and drain battery
install a ram and cache cleaner app and restart your phone multiple times, i hope you will fix it
Kianush said:
it your phone getting hot?
some services my glitch and get stuck on ram and drain battery
install a ram and cache cleaner app and restart your phone multiple times, i hope you will fix it
Click to expand...
Click to collapse
It is, and I think it's because pm-service was stuck in an error loop, and logd was tracking it, between the two using 40-50% of my CPU non-stop. I'm fiddling with restoring old system backups to see if I can fix it. It may be related to a botched magisk 12->13.1 upgrade, or a failed OTA update.
voilsb said:
It is, and I think it's because pm-service was stuck in an error loop, and logd was tracking it, between the two using 40-50% of my CPU non-stop. I'm fiddling with restoring old system backups to see if I can fix it. It may be related to a botched magisk 12->13.1 upgrade, or a failed OTA update.
Click to expand...
Click to collapse
yeah it might be
also most of the times a corrupt media file makes media storage getting stuck and phone getting hot...so you might wanna check that before restoring everything
I think it's related to this (https://forum.xda-developers.com/oneplus-3/help/ob-9-qmifw-log-spam-t3521248) because it happened after I restored a backup in twrp. I'm currently dirty flashing my firmware in flashtool
Dirty flash seems to have fixed it. Perhaps the problem is in how TWRP does backup restores.
voilsb said:
Dirty flash seems to have fixed it. Perhaps the problem is in how TWRP does backup restores.
Click to expand...
Click to collapse
I'm not allowed to give anymore 'thanks' today, so I will do it manually! Thanks for sharing this help, I noticed this problem too, but had no idea how to fix
qvmuhuuxz said:
I'm not allowed to give anymore 'thanks' today, so I will do it manually! Thanks for sharing this help, I noticed this problem too, but had no idea how to fix
Click to expand...
Click to collapse
That's exactly why I was walk thru my steps, even if I'm not getting replies. Just in case someone else has the same problems.
BTW, my logcat showed the same error spamming as that thread, which led me to try that fix.
E/QMI_FW (634): xport_reg Failed for service_id=0x35 version=0x1001 on 10
Sent from my SM-T700 using Tapatalk
voilsb said:
That's exactly why I was walk thru my steps, even if I'm not getting replies. Just in case someone else has the same problems.
BTW, my logcat showed the same error spamming as that thread, which led me to try that fix.
E/QMI_FW (634): xport_reg Failed for service_id=0x35 version=0x1001 on 10
Sent from my SM-T700 using Tapatalk
Click to expand...
Click to collapse
Now that we have a TWRP that supports nougat's decryption, I can encrypt.
But can we still dirtyflash if we are encrypted?
I see this, so I think it's possible - https://www.reddit.com/r/Nexus5/comments/2zdtqo/dirty_flashing_with_encryption/
"Disable screenlock. Set it to none. Device will still be encrypted, just the password will be set to default which enables the dirty flash to work. When everything is updated. Set a screenlock password again."
Related
Hi,
My N910F has recently been acting weirdly. It either randomly reboots itself, or just freezes for several seconds when switching screens or scrolling/tapping buttons. This started a couple of weeks ago on stock 5.0.1 (this version, I think) running Emotion kernel. This was running fine for a while; I didn't flash any new mods during this time, although I did switch between AEL kernel and Emotion once or twice without much success.
Thinking it was just one of those situations that called for a clean slate; I backed up my important stuff, booted into TWRP to wipe all partitions, then flashed stock 5.1.1 via Odin (this version, which I'm currently running). But even before I rooted it once again the phone was displaying the same aforementioned symptoms, both during and after going through the built-in setup wizard. This behaviour continued after flashing TWRP and AEL kernel v8.2, which I'm currently on at the moment. If it makes any difference I've also noticed that the lower my battery level, the more often it reboots itself. The battery level also "yo-yos" sometimes, usually at lower levels.
I've uploaded the relevant logs as advised elsewhere for anyone who can decipher them, as I otherwise don't know what to look for. This includes my last three kmsg dumpstate logs (just in case it's a slightly different cause each time), as well as my logcat and dmesg files (whatever they are lol) which I got using the SysLog app.
Any help would be appreciated, and if you need any more info please let me know.
Thanks .
*bump*
I have the same problem. Help would be highly appreciated. : )
*bump*
[UPDATE]: Once or twice when it's crashed as above, it would try and boot again but then reboot into download mode with the following text at the top of the screen above all the other info:
Code:
Could not do normal boot.
ddi: mmc_read failed
If I then pull the battery and turn it on again, it boots up as normal (at least until the next crash). Is this something that can be fixed with a fresh flash in Odin (or some other method), or is my phone on the way to its death?
Got the same issue + loses Wifi password after random reboot. Sent the phone back to the operator I bought it from 1 week ago and they did a repair. They replaced the USB-flex, did a firmware upgrade(?? ..was already updated to latest) and sent it back. I got it this morning and at first the phone now works fine and no more "mmc_read fail". But after some time the random reboots started again. Not so often now but still 4 times over the day and twice the wifi-password is lost and I had to retype it. Now I'm on the fence and just waiting for the first mmc_read fail" to happen before I complain and send it back for a second repair. I can not imagine this beeing beeing other than a hardware fail coming from a weak spot on the phone. I got the impression many people has the same issue and it really comes to life after upgrading to 5.1.1.
I also think the problem at the service shop ist that they just do a quick system test on a clean wiped phone and can't find the issue and think the phone is fine. After reinstalling my 200 apps and setting up my phone all over again, the workload causes the issue to reappear and I now have to ask the service shop for a deeper check. They accepted this as a warranty fix all though my phone has a knox trip (0-1)x4...
I've also faced random reboots on Lollipop. How i solved that? Simple. I downgraded to Kitkat. Lollipop still having lots of battery drains and bugs even on 5.1.1
[UPDATE]
I've decided to go through my network provider to get a replacement sent out to me, which they were happy to do after going through their line of questioning over the phone ("have you tried turning it off and on again", "did you try taking out your memory card and see if that helped", "did you try doing a factory reset", etc). They say it will get here tomorrow so fingers crossed for the replacement.
The ddi mmc_read fail has not reappeared yet..
It's strange.. Lately the random reboots are not wiping my wifi passwords anymore, but now after every random reboot the multiwindow is enabled and I've got to untick it in quick settings..
Latest: It seems that the random reboot may come from heavy account sync workload. I did have 5 Google accounts syncing on my phone + 6 excange accounts and when i disabled syncing alltogether the phone ran a lot smoother and the reboots stoped. So i deleted all Google accounts except my main account and for now thing seems to be fairly stable. I've also uninstalled all for me unimportant 3'rd party apps, reducing 3'rd party app count from aprx 200 to 150..
If things develop further I'll come back with more
Sent from my ****in' phone!
Thanks fot starting this thread Jointfcfan...i am using 910P and have same issue of your post 1 and 4!!!!
Loosing hope on Samsung, it is really frustrating...
Tried cleaning cash, dalvic, reboots, on latest 5.1.1 k version...frozen all not neede games and apps ...only 1 google and 1 exchange account no auto sync
At next stage while rebooting it sometime going an error stating kernel panic and i have to pull battery to restart
Replacing USB-flex board at service shop has cured the "ddi. mmc_read fail" boot issue for good.
So to me it seems that when many people experiences this, the USB-flex board may have a built in design flaw making it a weak spot on the Note 4.
Also I found that the phone works A LOT smoother if using Nova launcher instead of TW. Random reboot count is way down and phone works almost normally. Still some lag, mostly when unlocking screen, but reboots happens only 2-3 times a day now. Still random rebooting enables "multi window" option every time..
I've also rooted the phone now using CF-autoroot. I've flashed Philz CWM recovery and using it to install Wanam Xposed. So now I can run Greenify properly in Xposed mode and automaticly hibernate apps including system apps..
NB! Be aware, flashing root and custom recovery trips Knox counter 0x1 permanently and MAY void warranty
I have also mailed my operator asking them to take in the phone a second time for check/repair, alt. replacing the phone. I guess when they did system check 1st. time without issues after replacing the USB-flex, it was done when phone was reset to factory and under no significant workload.
Sent from my ****in' phone!
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
gjkrisa said:
You can set the phone to back up without wifi if you are good with that I've had my phone since December I have not had that happen odd.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
And how would you do that? Can't seem to find any way to do that...
In Google photos there is in settings also drive after that I believe the rest of settings will back up w/o wifi I know photos will
Sent from my Nexus 6P using Tapatalk
Dytoonn said:
This is the second time I get this message. First time was on stock Android 7.0. next time, ~2 weeks later on stock Android 7.1.1. To revive my phone I had to perform a factory reset twice.
What causes this message? Is it software or hardware related? I assumed the former, but the fact that it happened twice after a reset and on a new version made me wonder...
I'm heading to a country without 3G coverage and barely any WiFi, so if this happens then, I'm screwed on 2 levels: -Loss of pictures, due to not able to back-up -Not able to reset, since that requires WiFi.
Anyone else who had this issue? Any recommendations, RMA?
Full error message: "Decryption unsuccessful" The password that you entered is correct but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account"
Thx.
Click to expand...
Click to collapse
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
rchtk said:
Did you experience any random reboots?
When you say stock you confirm that it's full stock (no root and running google's kernel) ?
Click to expand...
Click to collapse
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Dytoonn said:
Never had any troubles with random reboots.
My phone froze, got unresponsive. I had to restart, and when it tried to boot I got this message. This happened twice.
No root, standard kernel. Bootloader not even unlocked.
Click to expand...
Click to collapse
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
rchtk said:
That's it. Storage corruption and the decryption unsuccessful is a consequence of your problem.
Sorry but that looks like a defective device.
ram/emmc/power, it's hard to find without root/twrp. Unless an update got wrong but I don't think that would show these symptoms.
First, I would also raise a PR on google to see what they suggest: https://source.android.com/source/report-bugs.html
You really need to backup your data and have a backup phone in case the following gets you a brick..
I'd actually try flashing factory images (you won't be able to flash recovery image but others yes ). Make sure to record the messages returned on your PC to see if something went wrong. The update process is a bit dumb, it goes on even if errors are encountered so even if it finishes it doesn't mean much.
Once the device is flashed, if it boots, you could try filling your data partition by moving big files using usb transfer. When its full, reboot and see what's happening.
If you are short on time, prepare the RMA process...
edit: oh btw, I'm sure people would be interested to get the information displayed in bootloader mode (power on the phone by pressing volume down)
Click to expand...
Click to collapse
Thanks for your reply.
I sent it for an RMA, so unfortunately not able to do what you described. Couldn't chance it getting this error message when abroad.
Curious though if they will grant an RMA, nothing much is looking wrong at the moment. Hope they will, because else I'm screwed.
If they don't, though, I'll see if I can get the information displayed in bootloader mode.
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
rwj5279955 said:
I'm having the same issue.
Same message, only I'm BL unlocked, rooted and twrp.
It happened twice. Once on 7.1 DP1, and again on DP2.
Once I get into recovery, the system is encrypted, and I can't do a thing.
I'm going to try and back up to a flash drive, and try to mount that in twrp if it happens again.
Click to expand...
Click to collapse
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
rchtk said:
Recent Twrp now supports full disk encryption so you should be able to see your files? And even do a backup from there. Take twrp 3.0.2-3
Click to expand...
Click to collapse
Strange, that's exactly the version I'm using.
rwj5279955 said:
Strange, that's exactly the version I'm using.
Click to expand...
Click to collapse
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
rchtk said:
Weird. I don't have twrp so I can't check but you should see your data. Maybe the partition needs to be mounted (I think it is by default though). No /data/media ? /sdcard is the same but as a virtualized FAT file system to be able to be access from Windows. Could be that /sdcard is empty in twrp but /data/media shouldn't.
Click to expand...
Click to collapse
I'll have to look if it happens again.
I only remember trying to access /sdcard. Empty
https://twrp.me/faq/datamedia.html
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Joeykatie said:
Same issue , rooted and twrp noto e4 plus , any help ? Idk what's is going on
Click to expand...
Click to collapse
If I understand this thread flash custom kernel like ElementalX to unencrypt your device.
Hello people of the world,
after reading a lot of posts here I still can't fix my phone's issues, so I need to post. Bear with me...
I have an N910F which was entirely stock and functioning without problems. Two days ago I accepted the official update. After that, the phone regularly lost connection to the mobile net, froze, and restarted. It would work for a short while until it froze and restarted again and again. When I tried to use the camera, the live picture was completely distorted. The phone crashed and has then gone into a bootloop.
I pulled the battery, did a recovery start and wiped the cache. No difference. Factory recovery next, no difference.
I have since tried several stock and custom firmwares, always taking care to follow instructions and use the correct bootloaders, modems, etc. TWRP is working.
When I flash a stock firmware, it will go into a bootloop. With any custom ROM, it will crash during startup (logo) and switch off.
Any help would be greatly appreciated!
Protect the eMMC?
So, after more reading I began to suspect that the eMMC had moved on to the valhalla of electronics. Sent my phone to service where my suspicion was confirmed. Luckily, they were able to replace the chip without having to put in a new board.
Is there any way to prevent this kind of failure again, or at least make it less likely?
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
nicholes said:
Yes this is a known issue after latest update you could you install only one application called wakelock so that your phone doesn't reboot and CPU keeps awake
Click to expand...
Click to collapse
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
tullian said:
Thanks! I had read about that.
Got my phone back from service today, they had flashed stock 5.0.1. After checking that it worked I flashed RR 5.8.4 and installed Wake Lock Powermanager. I searched for a comprehensive tutorial on what the settings do and which to use. Right now I set it to PARTIAL_WAKE_LOCK (4) but I'd like to read more about it. Any tips on that?
Click to expand...
Click to collapse
installing power wakelock and setting up on partial wake lock is enough.if you get trouble in starting your phone remove its battery and put your phone in refrigerator for five min.and try to start your phone.this problem also related and happens after the latest update
Hi
Firstly, thanks for taking the time to read this
I am stock ROM and RECOVERY.
Problem
For the past few weeks my phone has been freezing and rebooting (or sometimes after a minute I'm forced to restart manually)
This happens at different times, different battery percentages, apps, and even just locked in my pocket. With lots of app and even minimal apps installed.
I have reinstalled rom and rec twice now - all official. And wiped all options at least twice.
I really am at my wit's end now (https://dictionary.cambridge.org/dictionary/english/at-your-wits-end)
Again, thanks for reading.
Any advice would be great, I'm confident doing any software changes necessary.
Regards,
Josh
Vitamin--X said:
Hi
Firstly, thanks for taking the time to read this
I am stock ROM and RECOVERY.
Problem
For the past few weeks my phone has been freezing and rebooting (or sometimes after a minute I'm forced to restart manually)
This happens at different times, different battery percentages, apps, and even just locked in my pocket. With lots of app and even minimal apps installed.
I have reinstalled rom and rec twice now - all official. And wiped all options at least twice.
I really am at my wit's end now (https://dictionary.cambridge.org/dictionary/english/at-your-wits-end)
Again, thanks for reading.
Any advice would be great, I'm confident doing any software changes necessary.
Regards,
Josh
Click to expand...
Click to collapse
Do you have root to pull out these files from within that directory sys/fs/pstore
They'll might help to identify the random reboot issue. Pull them out after the random reboot happens. It's a log of what forced the reboot.
cutomer bringed few weeks ago op5 with same issue. had to fully reflash with ufs repartition, restored imei by box (was wiped out by repartition, twrp backup didn't worked). pretty common issue after 8.0 update.
strongst said:
Do you have root to pull out these files from within that directory sys/fs/pstore
They'll might help to identify the random reboot issue. Pull them out after the random reboot happens. It's a log of what forced the reboot.
Click to expand...
Click to collapse
No root, unfortunately . What about OEM logs or bug capturing
Hello everyone,
I have random soft reboots on my LG G6 Europe variant.
Bootloader is unlocked and custom Rom Fulmics Rom 4.2 is installed.
Does anybody experiencing the same problem?
The reboots happens after some days randomly....
Thx and regards
it is necessary to speak about it in the dedicated subject, more chances to cross someone in the same situation or who can help you
aking007 said:
Hello everyone,
I have random soft reboots on my LG G6 Europe variant.
Bootloader is unlocked and custom Rom Fulmics Rom 4.2 is installed.
Does anybody experiencing the same problem?
The reboots happens after some days randomly....
Thx and regards
Click to expand...
Click to collapse
Had the same problem on stock ROM, but the last update with january security patch fixed it.
Maybe a factory reset fixes the issue?
Krysdyan said:
Had the same problem on stock ROM, but the last update with january security patch fixed it.
Maybe a factory reset fixes the issue?
Click to expand...
Click to collapse
I did make a clean install through TRWP. WIPED cache and dalvik cache. deleted internal data and system data.
I had random soft reboots before I was on fulmics Rom as well. so I think it's not specific to this Rom....
how many times did your device rebooted?
aking007 said:
I did make a clean install through TRWP. WIPED cache and dalvik cache. deleted internal data and system data.
I had random soft reboots before I was on fulmics Rom as well. so I think it's not specific to this Rom....
how many times did your device rebooted?
Click to expand...
Click to collapse
On which base is Fulmics yet?
The reboots happened once a week, or sometimes even twice a day.
I had this happen on stock. After much reading of logcat output I was able to determine some kind of system table was getting exhausted. Proceeding on the theory that some app must be misbehaving to cause this, I disabled or uninstalled as many apps as I reasonably could, concentrating on what I could remember having installed or updated recently, and the reboots went away (I am paying close attention as I gradually re-enable or re-install stuff but haven't found a definitive culprit yet).
jdock said:
I had this happen on stock. After much reading of logcat output I was able to determine some kind of system table was getting exhausted. Proceeding on the theory that some app must be misbehaving to cause this, I disabled or uninstalled as many apps as I reasonably could, concentrating on what I could remember having installed or updated recently, and the reboots went away (I am paying close attention as I gradually re-enable or re-install stuff but haven't found a definitive culprit yet).
Click to expand...
Click to collapse
I had the same thoughts.....cause the issue is not taking place continously.... so I don't think it is ha hardware issue.... still couldn't find the app which may lead to a random soft reboot