hi guys,
my problem is a little difficult to describe.
After flashing a custom ROM (RR, CM, Vanir, Slim, LiquidSmooth...) KitKat or Lollipop , everything seems to work normal, but after unlocking display the brightness is about 5-10%, It is very difficult to see something on the display. The only way is to reboot into recovery and restore a nandroid.
This issue appears with installed mods just like xposed modules and other stuff, BUT it also appears without them (completely fresh install - ROM and GAPPS).
Curiously no problem with stock ROMs like KitSlim, Dstriker, PrivacyGuard and RockZ1K.
This is very ANNOYING!
Anybody the same issue or an idea how to solve it???
Thx for your help.
Related
Hi Guys,
I have this strange problem of not able to Initialize Whatsapp application on any AOSP roms.. i have tried many AOSP roms but issue remains same..
however same whatsapp works fine on any AOKP roms..
- Once i tried chaning the Radio somehow it worked.. but after that i flashed a different AOSP rom and it hasnt worked since then..
- I have tried all possible ways of flashing these, super wipe, factory reset... almost everything
- sometimes even USB tethering doesnt work on AOSP roms...
any idea what might me the issue, pls help.
Before the official v20b update came out, I was installing 5.0.2 AOSP based ROMS without issues. Used The Pagel's TWRP method to upgrade from 10r to 20b with no issues. AOSP ROMS based on 5.0.2 didn't give me issues at that point either. As soon as 5.1 ROMS came out, I started getting an error where the phone would go dead on me until I did a battery pull. It happened on BlissPop once and it increased on Candy5. Thinking it was a CM bug, I went back to my nandroid backup of 20b and now it is happening there too!
On the AOSP ROMs it's happened when the phone goes to sleep, if I try to update AdAway or the internal ROM's Ad Blocker, or simply when installing some CM themes. On v20b, it happened when I tried to reboot after updating my hosts file using AdAway.
On AOSP based ROMs, it does this randomly, and more with some ROMs than others. This will happen whether I use the kernel that came with the ROM or 777kernel, only script I use is the Android Cid camera script for AOSP based Roms. With stock v20b, I use the oversharpening script and textdroider to adjust the DPI. That's it.
When it happens, the phone just shuts off and the screen is completely unresponsive and the hard buttons do not work. Not even pressing power+down button does anything.
I need your help guys. Thanks for your replies!
Same problem here on 5.1 roms. I haven't tried rolling back yet. Came from Kitkat.
Hi everyone,
i have a problem with my rooted LG G3 855. After flashing Cloudy 2.5 i want go back to a cm based rom. After installing any CM based rom, my phone messed up. The "Uprade in Progress" message appears. After that my phone reboots and the initializing progess begin again. Anybody else faces this problem? Any solutions? I tried different roms. Nothing works. Only backups of older roms seems to be stable. Dont know what happened. I always did a clean install.
Hello there all!
I've been having this issue for a long time.
I've been using the SuperZen ROM, Custom Project T Kernel and official L Speed Mod. Sometimes I got stuck during the device's bootanimation (until this occurred really often). I tried going back to stock kernel and everything went okay, but didn't have the enough time to test some consecutive reboots/power-ons as I did flash my phone again. The issue occured ONCE without the custom kernel, but then reinstalled Prohect T and L Speed Mod.
I am now running Prism Barebone with Project T and L Speed Mod. The issue occurs very often I tried removing L Speed Mod via Emergency_Uninstaller (provided or L Speed official page)...but the issue's still there. I may try a new fresh install by only adding the custom kernel this time, but I did want to ask if anyone experiences this issue as well? I am not sure if it is a hardware issue. Everything was okay with the stock ROM (the actual stock). Please note that my phone was in service ONCE for a screen replacement. I hope that nothing bad happened during that time..
Thank you for any response!
i have strange issue, i'm not sure it's from last update, when i back to pe2 stock with odin and then install twrp, after i installed many custom roms i had a common issue that never happen before, with every custom rom when someone call me mu N4 don't ring and answer automaticly, and those roms works before without this problem, any idea???
i tried with official bases and custom roms, same issue
installing cm12.1, cm13, aosp always same bug
please, if someone know how to fix that i'll be gratefull