Hey Guys, i flashed a custom ROM on the device, how ever, the phone wont charge up to more than 92%.
I googled it but never found a cause nor a solution (even though on Xiaomi forum some ppl faced it).
Any ideas on the cause and possible solution??
Yeah, it is a battery calliberation issue at best. Most of the redmi 4 users faced it (atleast i did). Just use any battery calliberation app from play store or if using twrp just head to recovery and delete files batterystats.bin & batterystatsdaily.xml from data/system folder via twrp file manager and reboot. See if the issue is resolved.
Related
yesterday, I pluged in my charger and started browsing.
at one moment phone freezed, purple led flashed and phone rebooted
after that a lot of apps I had installed are missing. among them are gmail, google search widget, play store, titanium backup, some office from market (can't remember which) ...
and one widget I use can't be loaded on startup but if I remove it and add again it works.
I tried all I can think off except factory reset.
I tried deleting cache, dalvik cache, switched app2sd off (which were on, although I remember leaving it off), fixed permissions from recovery ...
I even reinstalled kernel and ROM and gapps, but no change at all which is really strange.
I use MiniCM7-2.2.0 ROM and 2.6.29.6-nAa-11 kernel
SD card is working, I can browse files and swap is working.
It also seems that rebooting doesn't work well. Sometimes, I choose reboot but it doesn't boot up until I pull out battery and press power button.
I'm not sure if this is connected because I didn't reboot much phone with this kernel and ROM
Any ideas before I wipe data?
Overclocked ?
Sent from my E15i using XDA
Apps2sd that's why ur apps r gone. Full wipe and reflash rom. Reboot issue can be fixed with latest flashtool reflash kernel with that. Worked for me no reboot problems no more
Hit thanx if I helped
Sent from my E15i using XDA
thank you for fast replies
phone is not overclocked.
I also guess it has something to do with app2SD
but I do not use it.
when I installed ROM I wanted to use Link2SD but it couldn't work because of build in App2SD.
I tried that App2SD but I couldn't control which apps to move, I even didn't exactly understood how it works, so I gave up of it.
Everything worked until yesterday.
and I only browsed internet when this happened. what could go wrong?
Is there a way to fix this before I wipe the whole thing?
I would like to make some backups and for that I need missing apps.
thank you
Oh,
and the strangest thing to me is that even after I reflash gapps, I don't have any google apps (at least which I use) except google talk
Try this:
Root again your phone with SuperOneClick.
Go to Settings >CM Settings >Performance >a2sd, and deactivate it. Then, activate it again.
Reboot.
Hopefully... it will fix your problem (worked for me ).
any particular version of superoneclick I should use? I tried one I have (which I used to root my phone a long time ago) and it fails to root it.
but why do you think I should root again? This is custom room and it is already rooted.
I tried turning on and off app2sd but there's no change, except some files are in one case in sd-ext directory and in other arent. but that are not missing apps :-(
Use the newest version, it will work. If not... use any method to root your phone again and follow the above guide (YES, I know that your ROM is rooted, just do it).
Why you should root again? Well, I already had that problem and all root apps were having problems (I dunno if you are having problems too, try it), so I rooted again my phone and all the problems were solved.
I repeated this with superoneclick 2.3.3 but no difference.
I had to full wipe the phone.
thanks all for suggestions.
EDIT: just to be clear, it did root this time, but no difference about this apps.
Hi i'm a noob (ex-apple fanboy) i just got my first android device 2 weeks ago and cuz i wanted to run obb files for games on my external sd i rooted my device.then i flashed xposed to my phone using twrm recovery and installed xposed and the obb to sd module.Finally got it to work after much frustration until something strange happened.I went to sleep with my device at about 50 or 60% battery level and when i woke up my phone was dead.I was shocked.anyways luckily i did a backup before flashing xposed and am now currently restoring the backup.Cn xposed be the culprit here? this has never happened until i flashed xposed.I also noticed that my battery was really going down fast and when i checked power settings android system was using up 100% battery .Sense home too was using up a lot and ive never seen this happen before until now.Please advice me.I use an unlocked HTC One M8 with a Stock rom and TWRM recovery on lollipop 5.0.1
Which modules do.you have and download a wakelock detector to see what's keeping your phone awake
Lol
nemofbaby2010 said:
Which modules do.you have and download a wakelock detector to see what's keeping your phone awake
Click to expand...
Click to collapse
i i only had single module installed.the obb on sd module.anyways i did a restore from my NANDroid backup and my phone is back to normal .lost about 3% overnight.Is there an issue with xposed on lollipop 5.0.1 or the module itself.cuz i deactivated the module and rebooted but my phone was still draining quivkly until i decided to restore.now I dont have xposed on my phone anymore .
i really have to try almost all Module (whose work on my device) but nothing about Battery Drain.....
Hesham Sleem said:
i really have to try almost all Module (whose work on my device) but nothing about Battery Drain.....
Click to expand...
Click to collapse
i'll try to flash xposed to my phone again and not install the obb on sd module maybe its the culprit.i wish someone would advise me tho
There shouldn't be any batt drain due to Xposed. DO CLEANUP and CLEAR your Download/Photos/Pictures folder.. Any sideloaded apk from 3rd websites do WAKE Play services + Play store and they'll start upload the apk for verification without your knowledge..
remiavan said:
Hi i'm a noob (ex-apple fanboy) i just got my first android device 2 weeks ago and cuz i wanted to run obb files for games on my external sd i rooted my device.then i flashed xposed to my phone using twrm recovery and installed xposed and the obb to sd module.Finally got it to work after much frustration until something strange happened.I went to sleep with my device at about 50 or 60% battery level and when i woke up my phone was dead.I was shocked.anyways luckily i did a backup before flashing xposed and am now currently restoring the backup.Cn xposed be the culprit here? this has never happened until i flashed xposed.I also noticed that my battery was really going down fast and when i checked power settings android system was using up 100% battery .Sense home too was using up a lot and ive never seen this happen before until now.Please advice me.I use an unlocked HTC One M8 with a Stock rom and TWRM recovery on lollipop 5.0.1
Click to expand...
Click to collapse
Hey man, I've battery drain too.. I've got LG G3.. And I've only one module installed (lte/4G switch.. Very easy!!)
Imho is because is an alpha version..
I rooted my HTC one. And now weird stuff is happeningt that has never happened before when I was unrooted. 1 , the battery seems to have a problem. It goes from 67%to 66%normally. I'll use an app like Facebooko r YouTube, and http be at 78% and more recently 100%. Weird. Also when I install an app from Google play or download the all file, it said successfullyi installed but it doesn't show up in the app drawer until I reboot, and if I click on it to open it , it tells me it has stopped. And when I have to update an app it takes forever. I mean I've been updating 6 apps forbtwp days now. And it hasn'tprogressedp passed the "installing" step. And my phone is always really warm. But not hot. Please help
Well, what i would do in your case is to reboot into TWRP or any other custom Recovery you have, and do a factory reset to the phone.
And if that wouldn't work i would flash the respective STOCK ROM for my phone.
it sounds drastic but i dont really know what else you can do.
Since Magisk 11 released and even now with 12, rebooting feels like a roll of the dice between flashing something or installing a module. I don't have any real development experience, but had tried building a module or two and troubleshooting another in the past few weeks, which resulted in eventually booting to the error SystemUI has stopped... This has happened several times in a day even. Now today, I push the April security update, install Magisk 12, and slowly start piecing my setup together 1 by one to make sure everything works properly. Then suddenly another SystemUI has stopped error... Only way to fix it is to restore from TWRP or factory reset. A timely process. Flashing zips in TWRP in the past hasn't resulted in this for me ever... That's going back to the Donut days on my Samsung Moment, LG Optimus, HTC One M7, and now my Nexus 6. I really want to love Magisk, but its very frustrating to get so far then to have to restore and start again.
Is it something I'm doing wrong? Is there a better way to resolve this when it occurs? Is there a way to avoid this error? Is this even a Magisk issue and the fact it hasn't happened before is a matter of luck? I don't even know what's causing it...
Use MagiskMount to mount magisk.img to /magisk and delete the installed module
duxishere said:
Use MagiskMount to mount magisk.img to /magisk and delete the installed module
Click to expand...
Click to collapse
Yes, I do that. That's not even the problem. It's when I finally boot after installing something or removing a module, SystemUI stops and I can't do anything.
Hm... I did notice this issue a couple of times on my Nexus 6 as well. It did happen a few times when installing modules that weren't quite compatible or otherwise had issues (I was experimenting and it was never quite reproducible), but mainly when trying to do a TWRP backup or restore (completely reproducible, 100% of the times). I figured it was my device acting up and never really connected it with Magisk.
I'm going to do some further testing...
gk1984 said:
Yes, I do that. That's not even the problem. It's when I finally boot after installing something or removing a module, SystemUI stops and I can't do anything.
Click to expand...
Click to collapse
Exactly my problem too. Im using redmi note 3 with lineage os and rr. The problem sam like this. Please tag me if you find the solution.
batmi said:
Exactly my problem too. Im using redmi note 3 with lineage os and rr. The problem sam like this. Please tag me if you find the solution.
Click to expand...
Click to collapse
I concluded it's a module I was using. Actually, the module I tried writing myself. Stopped using, no more issues. Well, at least not yet.
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Bassem AbdullMonem said:
Hi guys..
I have recently rooted (supersu) my j7 prime g610f (7.0) after installing dm-veriry pypass and twrp and then flashed xpoosed framework and tried aome moudles out and everything seemed to be fine .
Untill i rebooted to activate a moudle and i found that the lock screen doesnt want to unlock although the pin is right( just stands still for 2 seconds and then screen turns off and i repeated the process and same thing ) ..
I managed to unlock my phone through the website and tried other lock methods and i found that every method isn't responding aswell !
I then disabled all the models and denies all root access apps and rebooted and same thing happens.
I really need some help as i cant leave my phone unlocked.
Thx.
Click to expand...
Click to collapse
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
bogarty said:
1) Easiest way is to wipe and restore a backup in TWRP from when your device was working properly if you've hopefully already made one.
2) Another option is to boot into TWRP and go into file manager and delete the folders of the Xposed Modules you installed that you think might be causing the problem(in "/data/app/", "/data/data/, etc)". Then reboot and see if that fixed the problem. You have to be very careful when installing Xposed mods, especially when they're meant to tweak the system in some way, that they are actually meant for your device, particularly with Samsung Touchwiz devices that have heavily modded software.
3) Make sure that you're using the correct Xposed version for Samsung too, as this can cause problems with properly booting up the device.
4) Last case scenario you might want to consider wiping and reflashing your rom. Then at least you can make sure your touchscreen digitizer still works and can redo everything one at a time to see what's causing the problem.
I hope one of these suggestions helps.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Bassem AbdullMonem said:
Unfortunately i dont hace a backup but i noticed something that the problem is a delay in responding to my pin , and i notice that the cpu usage goes 3% to 35% when i unlock my phone usinv the pin ... i managed to unlock it by entering the pin and tapping in the screen few times to keep it lit and prevent it from sleeping .. any ideas foe that delay or cpu usage ?
Click to expand...
Click to collapse
Truthfully, your best bet while you have your device up and running is to backup all your apps and data with something like Titanium Backup or even sync them with the Samsung Cloud. The cloud reinstalls everything and sets your device configuration back to the way it was. Then, if you have a custom rom installed, wipe it in TWRP and reinstall it. If you're running stock, then don't wipe. Just go to the Sammobile website, download the latest firmware for your specific device and reflash it to the device with Odin. This generally fixes all system problems with a device, while preserving your app data.
Alternately, you can also try searching XDA for kernels that are made for your device that have a higher performance and try installing one of those to see if anything improves. As far as the screen going off early too, you can always check in "Settings/Display/Screen Timeout" to see what it's set for and change it to the max screen on time. It really sounds like you may have broke something system wise with Xposed or an Xposed module though, which is very easy to do, so I would really recommend starting over fresh. If you're on stock especially, as you really have nothing(data wise) to lose.
Sent from my SM-N920T using Tapatalk