Hi
Yesterday i flashed the Xylon(stable version) rom and francos kernel,also gapps.
When i try to take a photo with a flash the flash is not working,its working just if i tap the screen and then the photo take button.i also tried to turn the torch on and then start the camera but the camera app wont start with a torch on.i wonder if it could be a rom or a kernel bug?
Related
Using TWRP i have wiped everything except internal storage and installed LG-G2-VZW-OTA-VS98012B.zip after this process completed i reboot the device and got a fresh OS in my phone but soon after using i have realized that certain features are not working
1. Screen Rotation
2. Knock ON feature not working (screen goes off from double tap but its not turning back on only by power button)
3. Motion sensor calibration menu crashing (unfortunately settings has stopped)
is there any way to fix?
Hello everyone .. I write because I have a problem with the proximity sensor of my meizu MX4 . I flashed the CM 12.1 and now when I call someone , the screen turns off immediately and to turn it back I have to turn off the phone . I tried with Proximity Fix , but sometimes it works and sometimes it does not . I also downloaded Sensor box and when I go to " Proximity sensor" is shown 0.0 cm , like I was stuck on the phone . I can calibrate the sensor in some way ? I have the cm - 12.1-20151015 - UNOFFICIAL - MX4 even before I had the 028 ... I tried to flash a CM oldest in the hope of solving . Thanks in advance for your response .
You should also try the latest build on this cloud storage account:
https://yadi.sk/d/0FYPeIdSjuR3V
Hello, please i really need help
so tried good lock (Samsung systemUI), after that, the phone become unstable... I uninstalled it and the phone had a lot of fc of systemUI and other apps and random reboots, and sometimes it boot into recovery on its own sometimes into download mode, so i flashed another official firmware and did a factory reset , but no luck , then i flashed a ported Rom (Dr.ketan Rom) now my phone don't do a lot of fc and don't reboot into recovery and download mode on its own , but still having a lote of random reboots and a lot of freezes, any ideas guys? i looked everywhere but nothing
Same problem as you, but it's worst : I tried latest Good Lock 24.0.10 and after uninstalling it, I got a popup saying "SystemUI has stopped working", with black screen and can't do anything else than accessing menu with Lock Key (with reboot, shutdown buttons, etc.) :/
Tried to reflash ROM with ALEXNDR ROM for Note4 but same problem. Any solution ? I'm trying to restore Good Lock latest apk through flashable .zip to see if I can re-use my phone.
hello,
I'm having a problem with my camera. I installed the mod "PIXELFY" or someting like that on lineageos 17 by pig, the phone rebooted and the camera opened during the boot, then bootloop. I tried a data format, but the rom didn't boot at all, and the camera stays open. I reflash the rom, the camera app detects the popup but can't close it...
Any ideas? Thanks.
EDIT : Solved by flashing the stock miui rom
Hello today a screen replacement i ordered in aliexpress arrived and i did change it carefully (i did this process 2 times 1 in my phone and another in a cousin mi a1. No problems).
The thing is... after this i turn on the phone and the screen turns on but only until rom starts to load and then it comes black as if it wasn't turn on. The screen turns on also in fastboot mode but instantly shutdown when entering to recovery mode or normal boot as i said. The phone is working properly the rom loads and there is notification sounds and touch is working too.
If anyone can help me please. The only thing i can thing of is that the screen came with some strange malfunction.
EDIT: I flashed stock rom with flash_all and got the screen and everything working fine. I then tried again to flash a custom rom as i had before and screen failed to turn on again. Then i flashed stock kernel just to try if was it the cause and after this screen worked fine again but i lost wifi and probably there is other issues because of the stock kernel on a custom rom. I don't know if it may be because a different display driver or a kernel setting that may cause this malfunction. Hope someone can help me to solve this as i really want to use a custom rom.