I ran CRDroid 7.x on this phone for a while and got quite used to having a charger connect / disconnect vibration (and sound) which lets me know i accidently pulled out the cable or didn't put it in all the way.
Now, I had some issues with CRDroid and some apps not playing nice plus my auto brightness was flickering very bad so I decided to just go back to stock for the time being.
So, I MSMTool / Unbricktool / EDL installed the EU 11.0.3.3 ROM, updated it to 11.0.4.4 through OTA, OEM Unlock again, rooted it with Blu_Spark R87 kernel (which I used on CRDroid as well, it supports both custom and OOS) and set everything up again. However, I noticed that in the settings for sound and vibration and also battery settings I cannot find a single option allowing me to turn on the charger notifications.. Does that not exist in OOS or something?
Related
Hey,
i just woke up yesterday (2017-08-17) without my phone ringing my alarm. It did not respond at all (power button,...) When i did reboot it there didn't seem to be a problem.
I was running official LOS (build 2017-08-03) with the latest bueffla kernel back then.
The phone was connected to a charger to charge it over night.
I installed the latest LOS build (2017-08-17) in the evening without reinstalling bueffla kernel (to check if this problem was kernel related).
When i woke up this morning (2017-08-18) the phone did not respond again.
I tried to call the phone but it was not connected to the network.
Did anybody have the same problem related?
I've attached the console-ramoops-0 file but there much garbage in there. I did reboot the phone at ~6:10 - 6:20 (i'm not sure about the exact time)
This post is more informational if anyone get the same problem with huawei p8 lite.
Today i have plugged my phone to charger, power it on and realized that after an hour battery is still at 3%. After reboot nothing changed. I want to mention that battery is not broken and its phone issue, it can happen on every p8 lite phone. Ok, phone plugged, showing charging but starts to loose % till 0. After that i have long fight to solve problem with charging. On some site i read that powering up and plugging at huawei logo at good moment fix it and ppl agreed with it, but i cant get the timing and have issues to even power up phone. Here's what i do:
I tried to boot in recovery (have stock rom, and twrp) and phone was at 3% not charging still. I go as far as i can to advanced>file manager opened data folder and simply delete batterystats file (only way to wipe battery status through twrp) and it works as charm. Hope that you wont get that problem but if you had it try wiping batterystats, or try your timing with mentioned above metod: https://www.ifixit.com/Answers/View/265933/Why+my+phone+doesnt+charge#answer343508
additional info:
-stock rom android 6.0
-flashed xposed, dolby atmos & camera tweaks
-twrp 3.0.2-0
-orginal charger
Hello,
I was using my Zenfone 3 (in the back of the device is written ZE520KL) normally: Stock ROM, no Root, Never touched the bootloader (It means that I DID NOT installed Custom ROM nor Unlocked the bootloader nor rooted it). Then suddenly the brightness of the device went crazy. I mean, when I boot de device every thing works fines, but when the screen locks up when I unlock it or wake it up the brightness is lower than the lowest brightness configuration possible.
To try to fix it I:
- Change the brightness in the Android - NO success
- Turn off the automatic brightness adjustment - NO success
- Reseted it to Factory settings - NO success
- Flashed a older version of the android using the script from the package downloaded, i think they call it AFT(Actually, here comes something weird: If I try to flash it with the ZE520KL version of the ROM it does not flashes it, I had to use the ZE552KL version to get the flash working) - NO success
- Unlocked bootloader (Installed the TWRP 3.2.3 and the weird thing is that the extreme low brightness problem that I was facing in the Android when the screen wakes up is present in the TWRP. And the worst part is, it happens from boot into it. I even tried to change the settings and set the brightness to the maximum value in the TWRP's settings and nothing changed) - NO success
As I did not have success with anything, I locked the bootloader and flashed the stock image of Android again.
What really bugs me is that if I restart my device by holding the power button for some seconds, the display starts correctly, the auto-brightness works correctly and the brightness settings works just fine.
Could anyone please help me?
Thank you in advance
Freeny
Hello,
I have installed LineageOS 16.0 with Extras and OpenGApps 9.0 Super via TWRP on my phone SM-910C. There is no problem at all I found except it is not charging while its turned off. Its perfectly charging when turned ON. While I connect the charger when it turns OFF, it show's the empty battery once. But then turns off the screen and hanged up. No power button work then and not showing battery if I remove and connect the charger again. Then I have to remove and then insert the battery to turn it ON.
Please help me what should I do now? What if some time I drained all battery?
Sorry for my English.
Update: Rooted with Odin.
firdosi said:
Hello,
I have installed LineageOS 16.0 with Extras and OpenGApps 9.0 Super via TWRP on my phone SM-910C. There is no problem at all I found except it is not charging while its turned off. Its perfectly charging when turned ON. While I connect the charger when it turns OFF, it show's the empty battery once. But then turns off the screen and hanged up. No power button work then and not showing battery if I remove and connect the charger again. Then I have to remove and then insert the battery to turn it ON.
Please help me what should I do now? What if some time I drained all battery?
Sorry for my English.
Update: Rooted with Odin.
Click to expand...
Click to collapse
We know this - it's a bug.
Charge your battery when it's at 15%-10% or whenever you like so that it will not die.
The developer is aware and he will work on it when he has time.
So you either stay with it as it is or go back to stock/other custom rom which does not have this bug.
You should've not open a thread here but write on the existing Exynos dedicated one.
w41ru5 said:
We know this - it's a bug.
Charge your battery when it's at 15%-10% or whenever you like so that it will not die.
The developer is aware and he will work on it when he has time.
So you either stay with it as it is or go back to stock/other custom rom which does not have this bug.
You should've not open a thread here but write on the existing Exynos dedicated one.
Click to expand...
Click to collapse
OK. Thank you so much for replying. Can you please tell me any stable Android 7+ version of custom OS for my mobile SM-N910C. It should not have any bugs, encrypting and charging should work perfectly.
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
spencetj said:
I have an S5 with stock Samsung ROM which I rooted some years ago with Magisk and TWRP recovery. For the last few years it has only been used as an alarm clock and I have forgotten how I set it all up in the first place, in fact I had forgotten that I ever rooted it. Up until now it has been working fine but I wanted to give it to my 9 year old daughter to use, so I did a factory reset on it through the normal Android menu. After that the phone works but will only charge in Recovery, not when its off or when its booted normally. Same cable and charger that I have been using up until now and I also tried others but didn't make any difference.
When the phone is off and I plug in the charger,it vibrates, the battery symbol comes up for a second and it displays the message "set warranty bit: kernel" then the screen goes off. The charging LED does not come on. Then after about 10 sec it does the same thing again: vibrate, battery symbol, message, screen off and just keeps going round that loop but never charges. When the phone is booted in normal mode it doesn't seem to detect the charger at all, nothing happens. In Recovery it charges perfectly but its a bit inconvenient!
I tried restoring the last TWRP backup that I had which seemed to contain all the partitions but it hasn't made any difference to the charging problem. It seems the phone has power and CAN charge but is deciding not to. Any ideas please how I can get it back into operation?
Model: SM-G901F
Android 6.0.1
Kernel 3.10.40-9709634
Build MMB29M.G901FXXU1CRH1
Magisk 19.3
Magisk Manager 7.3.4
Magisk version is old but I have not attempted to update it yet in case that makes the situation worse.
Click to expand...
Click to collapse
Never mind, I got it working with a different charger. Very strange. The first charger works fine with my Huawei P20, maybe too high power for the S5? Although I thought the device only draws the power it needs even if the charger is capable of more.