-# FAQ -## Here you can find the most common questions and their respective answer. Simple as that. READ THEM.
-A - Once you have installed the app, just open it and click on "Install Core Mod", the app will create the Core Mod needed for your device (this might take a while, from 5 to 30 minutes) and then will reboot the phone to flash it. When the phone has rebooted, open the app: If the message says "Service Bound" you're all set!
-A - From within the app, just switch to the "Wakelock" tab. Here every wakelock recorded since the first boot with the core mod installed, so give it at least 2/3 days of normal use before blocking anything. Click on the wakelock you want to block, press the "Block" button and then set for how long is the wakelock gonna be blocked!
-A - We suggest to check out this guide on XDA (https://goo.gl/PFAPJ2) to fully understand what it means to block a wakelocks and how it affects your system.
-A - Ok, but we don't take any responsibilities if the phone bricks or your ROM explodes. You are totally free to change the blocking time value to make it as you please but, again, we don't take any responsibilities. You can find the list here: https://goo.gl/xAE8ny Remember: if you don't find one of the wakelocks, just check in later. If you still don't find it, don't worry at all! Side note: the search button is not case-sensitive.
-A - If it is part of the list linked above, you're good to go! If not, we can't assure a thing, but if you find any safe-to-block wakelock let us know!
-A - Do not ask for an ETA. We do this for free, without any ads in the app nor donation packages, we don't even put a price on our app. We all have jobs, university and a private life to manage, we don't have superpowers, so managing all of this takes time. Our free time is pretty short, but we usually put at least half of it on the developing of the app. Be patient and do not harass the team nor the telegram group.
-A - Everything is done by user input, the app by itself (even with the core mod installed) doesn't do anything but reading which wakelock the system is calling. Unless you blocked something we didn't suggest you do to this problem and our app are totally unrelated.
-A - By itself, the app doesn't do anything even with the core mod installed. Keep WakeBlock whitelisted in every hybernation app (like greenify) but the basic Android Optimization. If the battery drain has increased, double check what you blocked, that might be the reason!
-A - It's a known bug. Check if the app kept all permission (Both root privileges and Storage permission) and simply reboot your phone. It will magically start to see it again! SIDE NOTE: you don't need to reinstall the Core Mod every time you update the app!
-A - First of all, we are sad that you want to leave us. If you didn't install the Core Mod, or it failed in any way, you just need to delete the app and everything is gone! If you did install successfully the Core Mod, check the WakeBlock backup folder (/sdcard/WakeBlock/Backups). You will find a bunch of different folders with different dates and times. Pick the most recent one and look inside. Here, you will have one of two cases:
-CASE 1: FILES = services.odex & and services.vdex | ODEXED ROM -In this case, boot into your custom recovery of choice (TWRP for example, you can't do it from a root explorer) and mount your /system partition. Now check both /system/framework/oat/arm and /system/framework/oat/arm64 for a service.odex and a service.vdex. Here, COPY (and DO NOT MOVE) the files from the backup and paste them to replace the files in your system (one of the two folders above). Now delete the app and you're now WakeBlock-free!
-CASE 2: FILE = services.jar | DEODEXED ROM -In this case, boot into your custom recovery of choice (TWRP for example, you can't do it from a root explorer) and mount your /system partition. Here, COPY (and DO NOT MOVE) the file from the backup and paste it to replace the file in your system (in this case /system/framework). Now delete the app and you're now WakeBlock-free!
-A - It works. We tested it (and we keep testing it) many times before committing an update! Double check permissons and give it a reboot, usually fixes most of the "doesn't work" problems.
-A - First of all, check on the telegram group (https://t.me/wakeblock) if anyone else had your problem, both by first searching and then asking directly. If no one can help you on the spot, send a ticket on the @WakeBlockSupportBot. It will ask for a logcat, so make sure you make one while you encounter the problem. DO NOT CONTACT ANYONE OF THE TEAM UNLESS EXPLICITLY ASKED TO.
-A - First of all, make sure that you have the needed Platform Tools (https://goo.gl/2rgkLY). Due to the fact that the app reboots, it's better if you take it with a pc rathern than with an app. Plug the phone into your PC, you start the cmd.exe as administrator (or, if you use Linux, you need to open the terminal with root privileges) and run the command "adb shell", now the console will show the internal console of the phone. From there, run "su", a prompt will appear to your phone to ask for root permission. Approve it, then run "cd /sdcard/Download". Afterwards, run "logcat >> log.txt" (Nothing will appear on screen because it's redirecting every output to the log file). Now start the patch. When it gives the error (or after it reboots), close the app, click "Ctrl + C" to stop the logcat. Then, from the phone, send us the log.txt (you will find it in your Download folder).
-## TO-DO LIST | -- Alarms. Yeah. -- Fixing problems related to some Samsung devices and Pixel devices -- Import/Export system for the blocked Wakelock -- Inserting the FAQ and the suggested wakelock-to-block list into the actual app -- Adding the feature to change the block time without unblocking the wakelock -- Various fixes and improvements