-
Notifications
You must be signed in to change notification settings - Fork 7
Help page
- GPS / Radio
- Random Power off or reboots?
- Bootloop to TWRP after a Factory Reset
- Pictures access, view, sharing or related problem
- USB OTG player
- VVM for custom ROM XT1254 only
- Bug reports
Changing/Updating the ROM may cause GPS lock problem, this also help in situations that the device after a boot up doesn't have a radio or show a missing SIM card.
option 1) For GPS only problem Install GPS Status & Toolbox, open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) For GPS and others Radio problem If the above doesn't help you can try to erase all the radio status Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar. To erase the radio status is very simple just flash this zip Clean_modem_status.zip via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% if charge as low you let it get worse yours battery will be over time.
2) Check the boot reason prop "ro.boot.bootreason" if it is like the example bellow set to power_key_press the device didn't reboot it sled power off.
[ro.boot.bootreason]: [power_key_press]
Check the prop using : Kernel Audiutor app > logs section > search in a log > mark getprop > search key word "reason".
If the Random power off are related to battery, BCL can help mitigate the problem.
BCL can be controlled via BHB27 kernel adiutor Power and battery section. Lowering the BCL Max frequency or Making the number of hot unplugged core higher will help to mitigate the CPU power. But if the problem persist is necessary to change the BCL low and high voltage threshold to higher values to make BCL to start sooner, the recommendation is to set they to 3700mV (Low) and 4000mV(High) and if the problem is resolved after that, the device stops randomly power it self off, lower the values 100mv it until you find a perfect value, or if the problem persist make the values 100mV higher.
Is also recommended to set the battery "Automatic power saver" from default 15% to a higher value, with is today max at 25%
If the device did just reboot just share a log as recommended on the bottom of this help.
This is a Nougat and newer OS problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions, as it's using the Marshmallow recipe) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda. TWRP xda thread Click Here
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example. You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
This is a Nougat and newer OS issue, to play anything from a USB OTG device is needed proper permission, that is not simple can't be just given, as the app must request it before it can be given, so to play anything from a USB driver you need to find a proper app, this is a sample of one that works JS USB OTG
This is for custom ROM only, VVM app (VVM may only be accessible via play with this link VVM, but VVM may not work perfectly with custom ROM, google has it on version is free and seems to work 100% Google voice, the in the ROM phone app also has a dedicated option for voice calls.
Are always welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix. Always post a bug on the ROM thread you are using All threads link here with a mention writing @fgl27 on the top of post and attaching a log .zip generated by the app BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP, even after a random reboot share a log generate the log as soon the device finishes boot up.