Good evening all.. Just looking for some help if possible. I absolutely love Remix OS and I am really enjoying it so far. I have a dell inspirion 3000 11 inch 2 in 1 laptop. Everything works like a champ and its super smooth. I've installed to my hard drive with a window 10 dual boot. My issue is this: It will randomly just freeze, no matter what I am doing. browsing the web, looking at settings, watching a video, etc. It just freezes and then i have to hold the power button down to reboot. (is there a shortcut key or something to try to kill a task or is the power button the only option?) does anyone else have this issue? I've tried the latest update and that seemed to make it worse, so i downgraded but it still happens from time to time.
Any help or advice would be wonderful.
If you're using a Nvidia GPU, it's most probably a nouveau driver issue that will be fixed in the next kernel update.. Most probably in the next 1-2 updates.
@Dieseltown it's hard to say what causes the freeze, but we can try to find out:
1. You can go to Settings > Experimental Features > Enable ALT-F1 terminal console
2. When the freeze happens, press ALT-F1.
If it successfully switches to console then go to step 3. if not go to step 6.
3. Enter
Code:
logcat
and take a picture showing the output (it will take some time before it reaches the end of the log)
Instead of that you can press CTRL+C to terminate logcat and then request the logcat to be saved in a file by entering:
Code:
logcat > /sdcard/logcat.txt
Wait some time - 1 minute should be enough. Then press CTRL-C again.
4. Enter reboot -p (not just reboot because this tends to fail more).
5. Start the PC again go to your personal data directory and send us the logcat.
6. If the above isn't possible, then do step 3. right after bootup, but only do the save to file part. Don't press ctrl-c after requesting logcat file - press ALT-F7 instead to switch back to GUI and use your device until it freezes. The logcat will be saved through all device uptime.
Then reboot and get the logcat file uploaded.
Sent from mobile
Vioner said:
@Dieseltown it's hard to say what causes the freeze, but we can try to find out:
1. You can go to Settings > Experimental Features > Enable ALT-F1 terminal console
2. When the freeze happens, press ALT-F1.
If it successfully switches to console then go to step 3. if not go to step 6.
3. Enter
Code:
logcat
and take a picture showing the output (it will take some time before it reaches the end of the log)
Instead of that you can press CTRL+C to terminate logcat and then request the logcat to be saved in a file by entering:
Code:
logcat > /sdcard/logcat.txt
Wait some time - 1 minute should be enough. Then press CTRL-C again.
4. Enter reboot -p (not just reboot because this tends to fail more).
5. Start the PC again go to your personal data directory and send us the logcat.
6. If the above isn't possible, then do step 3. right after bootup, but only do the save to file part. Don't press ctrl-c after requesting logcat file - press ALT-F7 instead to switch back to GUI and use your device until it freezes. The logcat will be saved through all device uptime.
Then reboot and get the logcat file uploaded.
Sent from mobile
Click to expand...
Click to collapse
I had the freezing issue (because of nouveau) before and the problem is that all the system freezes that ALT+F1 doesn't work anymore
@modaifallah please read my signature
Back to the thread: His GPU is intel.
Sent from mobile
Thanks for your help so far.. I actually reinstalled the newest, from the torrent instead of OTA. No issues as of yet, but will try your guide when and if I do, then will follow up.
Downgrade to Remix OS 3.0.102 and freezing problem is gone, and az screen recorder is working fine to. Gpu driver on latest mesa Remix OS is buggy
Related
If you are experiencing a few seconds delay from when you push the power button to seeing the lock screen this will fix the issue on Cognition ROM. I have not tested on stock, but of your experiencing three same delay this should fix
It as well. Please post back If you applied to stock and it fixes the issue.
Do a nand backup before you use this. It's very unlikely that you will encounter issues, but better safe than sorry.
http://forum.xda-developers.com/showthread.php?t=991276
[Script][U9 Beta 6.2.2!] THE SuperCharger! The ONLY Android MEMORY FIXER! 3G & KAK!
Quick run down on how to use this:
Download script manager from the market.
Download this script which can be found in the thread above.
http://db.tt/SowitehP
Open script manager and goto the place you downloaded the V6_SuperCharger_for_Android-update9_beta_6.2.2.sh file and select it.
A dialog box will pop up check run as root then click run. It will warn you that your busy box is higher than 1.82 ignore this.
Now tap screen to bring up keyboard type 1 and hit enter to enable fast scrolling.
Let it load up until it asks for you to enter 1-26. Type 11 this will apply oom fixes and htk launcher and hit enter. It will ask you about writing to build.prop enter Y for yes and hit enter. Let it run its course until you get to the menu again.
Type 9 hit enter this will set recommended minfrees for our phone let it run its course and when you're at the menu again
Type 25 hit enter this will reboot your phone.
All done! Enjoy!
pls help my phone is rooted n sometime my phone switch off without any notification is there any problem
attaripatel said:
pls help my phone is rooted n sometime my phone switch off without any notification is there any problem
Click to expand...
Click to collapse
You should try to wipe cache and Dalvik cache in recovery.
If the issue persists, try to re-flash the kernel.
If that does not help, try to flash the whole ROM again.
If that does not help either, it could be a "bad" app.
Maybe you can get a hint to the cause of the shut down/restart in the last_kmsg file.
You can grab the last kmsg (kmsg = Kernel Message / the kernel log buffer)?
If you haven't rebooted since the crash, grab a terminal editor and enter the following:
Code:
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg
Kmsg is continuously overwritten, so you need to extract last kmsg as soon as the issue/crash occurs.
Crash => reboot with long press Power button => grab last kmsg.
Just have a look at the last_kmsg.txt file and you may recognize what was going on shortly before the crash.
If the phone crashes next time:
1. Reboot the phone with long press power button.
2. As soon as the phone is up, start Terminal Editor app (e.g. Terminal Emulator from Play store).
3. Type the code from above. That will grab the last kernel message and saves it into "/mnt/sdcard/last_kmsg".
4. Open/read/copy last_kmsg examine yourself and/or post here again and ask for help.
Good luck !
very difficult to understand
It_ler said:
You should try to wipe cache and Dalvik cache in recovery.
If the issue persists, try to re-flash the kernel.
If that does not help, try to flash the whole ROM again.
If that does not help either, it could be a "bad" app.
Maybe you can get a hint to the cause of the shut down/restart in the last_kmsg file.
You can grab the last kmsg (kmsg = Kernel Message / the kernel log buffer)?
If you haven't rebooted since the crash, grab a terminal editor and enter the following:
Code:
su
cat /proc/last_kmsg > /mnt/sdcard/last_kmsg
Kmsg is continuously overwritten, so you need to extract last kmsg as soon as the issue/crash occurs.
Crash => reboot with long press Power button => grab last kmsg.
Just have a look at the last_kmsg.txt file and you may recognize what was going on shortly before the crash.
If the phone crashes next time:
1. Reboot the phone with long press power button.
2. As soon as the phone is up, start Terminal Editor app (e.g. Terminal Emulator from Play store).
3. Type the code from above. That will grab the last kernel message and saves it into "/mnt/sdcard/last_kmsg".
4. Open/read/copy last_kmsg examine yourself and/or post here again and ask for help.
Good luck !
Click to expand...
Click to collapse
very difficult tounderstand pls give me sugestion what i can dosimply to avoid this
So,
SGS users, here is my another thread, for guys, who want to help devs of our sgs community.
Devs asking you to get a logcat and give?? Yes it helps a lot for devs if you give logcat to solve problem. So dont wait till devs ask you to get a logcat! Just give them a logcat when you tell them this/that doesnt work. This way theirs and yours time will be saved and unnecessary posts will be avoided.
Now i will give you simple steps to do it. There are two main ways to do a logcat, 1. within android device, and 2. through adb using PC.WITHIN ANDROID DEVICE METHOD:
1. Logcat within android device can be done in one of two ways, through a Logcat app: Difficulty --> Very Easy
Here are two good apps: aLogcat or Catlog
Both of these programs can dump their logs to a text file, which is very useful for debugging. Or, you can do it in terminal emulator (same rules as running through adb(see below))
2. Through Terminal method: Difficulty --> Almost Easy
Install Android Terminal Emulator app from Play Store..
Open terminal app you just installed..
Enter these commands:
After every command press ENTER/SUBMIT button
Code:
su
then accept the superuser popup message[it comes only first time if you select checkbox "remember the choice"]
Code:
logcat -v long > /sdcard/test.log
Or use this command:
The -v long puts the text in a nice format that is more easily readable. The *:W will search for all warnings, errors, and fatals, while the *:S will silence everything else.
So essentially, u will have a .txt file that has a log of all warnings and up, nothing else, and it'll look pretty too!
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
now press home button to minimize the terminal..
and do the task which is giving problems/ whichever task log you need to give to dev..
then drag the notification bar..
select terminal app in it..
now press and hold "Volume down button" and touch c button on keyboard.
This will stop the command..
now use this command twice
Code:
exit
Now app will get closed. go to sdcard to find test.log file.. upload it to here so that dev can access it..
Thank you for reading it with patience hope you can get logcat now..
Note: if you are stuck in boot and want to take logcat.. READ LOGCAT FROM ADB METHOD BELOW.. the above one is simple method for these tasks for eg.. if you are having some force close of app/lag etc.. then after entering second command press enter and then use home button to minimize terminal.. dont worry it will take log.. now open that app and once it gives force close then click on it and then open terminal again and press volume down button + c to terminate command.. then use exit command two times... done.. now go to sdcard and find a.txt file
From PC[i.e, ADB] LOGCAT METHOD :Difficulty --> Medium
There is an advantage here. As doing this way, you can start using logcat when your device boots. There are 2 ways here again..
PREPARATION:
In your android device, go to settings --> applications --> development -->
Check USB Debugging
Make sure your device driver is already installed otherwise install kies software which will install drivers too.. Get kies from This LINK
You need to download this ADB.zip file i made to your system.. Download link
Extract the ADB.zip file from any applications like IZarc/7Zip/winzip/winrar.
ADB USAGE INSTRUCTIONS:
Then go to Android folder.. inside that you should find 3 files.. Now open a command prompt or terminal in that path..(wherever you extracted it.. use cd command)
Then inside that path.. type
Code:
adb logcat > filename.txt
Or
Code:
logcat -v long > /sdcard/test.log
Or
Code:
logcat -v long *:W*:S > /sdcard/filename.txt
Now perform tasks in android device of which you need to give logcat for the devs. Then use CTRL+C to end the command.
Now find the filename.txt inside the Android folder which has logcat. Upload this file and give link to dev..
The full list of options that can be used with logcat command is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the *:W with any other letter from above to get more info.
CREDITS
CRESITS ;
I) @Niku-Droid
II)www.google.com
III) XDA Threads, as this information is taken up from threads of XDA only
Oh! I missed someone, Send me a PM
hmn nice thread
most guides are user friendlyy if the ppl read a few sentences
just like all other threads the self aclaimed noobs will just ignore this thread and when asked for logcats theyll just post how to take logcat when they can just type that up at google or had read here
also im not able to take logcat at boot can u post up how to do that
Sent from my GT-S5282 using Tapatalk
T3snake said:
hmn nice thread
most guides are user friendlyy if the ppl read a few sentences
just like all other threads the self aclaimed noobs will just ignore this thread and when asked for logcats theyll just post how to take logcat when they can just type that up at google or had read here
also im not able to take logcat at boot can u post up how to do that
Sent from my GT-S5282 using Tapatalk
Click to expand...
Click to collapse
hmm... dont worry bro, we will give them link to this thread when they ask this silly question n hv u tried taking logcat using adb, i m sure that it can take logcat as soon as device is booted
Niku-Droid said:
hmm... dont worry bro, we will give them link to this thread when they ask this silly question n hv u tried taking logcat using adb, i m sure that it can take logcat as soon as device is booted
Click to expand...
Click to collapse
of course i used adb
i want to take logcat while star is booting
but device doesnt show in adb until the booting is complete
When the projection function is turned on, the phone will reboot.
Sorry, I am a Taiwanese, so my English is not very good. I hope you can understand.
My whyre will restart whenever the projection function is turned on. This problem is very annoying because I use it often.
I hope that ArrowOS can be more perfect in Chinese culture, otherwise it will be difficult for my newbie, and how do you solve the 4G signal problem?
I use a lot of OS, but their 4G can't work, which makes me very troubled. As a geek, I want to learn how to deal with this.
The system you made is really great, I like it very much, I hope you will surpass PE.
how can solve no internet problem?
how can solve no internet problem?
Network problem on moto g4 plus of version Arrow Os 9
Doesn't access network problem while installed
The connection to my smartwatch dosnt work.
the bug that I found for the moment was that it does not allow changing the file transfer mode when connecting the usb cable to the computer
Niku-Droid said:
Кодlogcat -v long > /sdcard/test.log
Click to expand...
Click to collapse
Although I've made fundamental protection in the Xposed module of Greenify (especially in 2.6 beta 10), some of you are still experiencing bootloop if experimental Xposed-based features are activated.
It's really hard to dig these issue without logcat since Android devices and ROMs are highly diverse (fragmented). But logcat in the bootloop case is understandable harder to capture than regular crash issues.
If you are one of the bootloop victims, and would like to help me on this issue. Please follow this instructions to capture a proper logcat for the bootloop issue:
1. Download and install ADB tool, either as standalone package or from the Android SDK.
2. Connect your device with a PC or laptop with USB cable.
3. Enable developer options on your device. (this must be done before the bootloop happens)
4. Test logcat capturing by typing this command in shell (or command prompt): "adb logcat -v time -d" (without quote marks), if you see plenty of log scrolling through the screen and finished, it's ready.
5. Trigger the bootloop, then after the device reboot, type this command in shell: "adb logcat -v time > logcat.txt", if you read "waiting for device" and the command continues running, that's OK.
6. Wait until the last command to finish and return to the shell, then you will get a "logcat.txt" file in the current path (usually the root path of your user home / folder). Send it to me via email (or pastebin.com).
If the command does not finish in a long time, just press "Ctrl + C" to end it, and send me the logcat.txt if it's not empty.
Thanks very much for your effort to help diagnosing this issue.
I had some severe boot loops on a CM12 device last night, I think it was just soft reboots not hard (no way to confirm it, sorry). It was running in root mode. I think a play store update cured that one. The SuperSU logs confirmed it was the item requesting access just before soft reboot.
I also had severe soft boot loops on my Moto X OTA 4.4.4, running in boost mode. Updating from play store (to 2.6.1), or disabling the xposed module auth for Greenify would not fix it. Only blocking SuperSU access fixed it. I just verified that granting SU back again to Greenify immediately causes soft boot loop.
Unfortunately, the effected device is a work unit with sensitive information, so I cannot post anything. I can try limited requests if you have any.
Waking a hibernated system app (Spotlight Player) caused a soft reboot, but it appears its working properly now going back into hib and back.
Tested On XT1526 from the stock 5.1.1 firmware surnia. PLEASE check your settings->about phone and look to make sure the model is surnia before going forward! Please reply in the comments if you were able to get this to work on another model other than the XT1526!
So you have the Moto E Gen 2. You may have even got this phone specifically to play the game that's sweeping the world, 'Pokemon Go'. You felt great having installed the APK like a true hacker, you went to play and......oh no. What's this? The phone takes ages to boot up? Restarts all the time while trying to log into your account? Or you FINALLY get far enough into the load that the game starts (or gets close to it) and the phone gets soo hot in your hands it's unbearable and the game begins to **** out? Perhaps it runs terribly from the get go?!
This. Guide. is. For. You.
This guide will help you to set up your Moto E Gen 2 to run perfectly with the game! It will also cause your phone to run almost 3x faster, and have the battery last almost 2.5x longer! I would recommend this guide to ANY person using the Moto E. I have NOT tested this guide with the Gen 1 or any other phone.
I do not take ANY responsibility if your phone ****s out on you in any way, shape or form. Messing with your phone's system like this can ALWAYS cause issues if you don't take your time and know a bit of what you are doing. Or, if you are new to this and daring, I have constructed this guide to be extremely easy to follow. As long as you follow step by step, you should be goldeen...erm...golden! If not, it's not on me. Your fault !
If you encounter a step you have previously done, go to the next one! This guide is step-by-step for someone with a stock Moto E (2015)!
Step One: Unlock The Bootloader
So the first thing we need to do on this journey is unlock our bootloader!
1. Back up ALL of your data! Do it. Or if this fails, you will be SOL.
2. Download the Android SDK or get the Minimal Version (this is what I did)
3. When you install the SDK, install it to your desktop (during installation it will ask you for location. Make a new folder on your desktop called SDK and install it there for easy access).
3. You will want to install the drivers for your phone so you don't have problems connecting from your computer to your phone! Download them HERE.
4. Now we need to get into fastboot. To achieve this there are a few things we need to do.
-With your device powered on, go to your Settings->About Phone and click on the 'Build Number' 7 times to enable Developer mode!
-Go into your settings->developer options and enable 'USB Debugging'
-While in Developer Options, make sure 'OEM unlocking' is ENABLED.
-Open the directory on your desktop where you installed ADB. You should see some programs such as 'fastboot' and 'adb' in there. Should NOT be an empty folder containing another folder!
5. Once you are in the directory of your ADB on your computer, and you have done all steps above, hold down the SHIFT KEY and RIGHT CLICK inside the ADB folder containing your 'fastboot' and 'adb' programs. Choose the option that says 'Open Command Window Here'.
6. Once the command window opens, connect your phone (while powered on) to your PC.
7. In the command window, enter the following command to make sure your device is connected: 'fastboot devices' Now, enter the following command: 'fastboot reboot bootloader'
8. When your phone restarts, you will be in the bootloader screen. Once here, enter the following string into your command window: 'fastboot oem get_unlock_data'
9. You will get a nice long string of text. Copy it by right clicking on it->Mark->then mark the string of text by holding the shift key. Ctrl+C to copy it.
10. Open a Notepad and copy the string into it by pressing Ctrl+V. Make the string of text ALL ONE LINE by deleting the spaces.
11. Head over to the Motorola site HERE and log in using your google+ account.
12. Scroll to the bottom of the page, and in step 6 paste your string code from your notepad (step 10) into the blank box. Click on the 'Can My Device Be Unlocked' link. There should be a new button that comes up that says 'Request Unlock Key'. You will be emailed your unlock key after clicking the 'I Agree' prompt!
13. Go into your email, and open up the new one that contains your unlock key. Copy the 20 character string that is your unlock key.
14. Back in your command window, enter the following command again: 'fastboot devices' to ensure your device is still connected. Your device should STILL be in your bootloader screen. If so, and you see your device in the command prompt, enter the following command: 'fastboot oem unlock YOUR_UNLOCK_CODE'
15. After a while, you should get a 'Bootloader Unlocked' notification on your phone.
If so, you're done with this step! On to the next one . KEEP YOUR CMD WINDOW OPEN FOR ADB
Step Two: Rooting Your Phone and Installing TWRP
1. Turn your phone back on like normal. Connect your phone to the computer so you can see into the storage (should be under My Computer->Your Device).
2. Download the following files. TWRP Recovery and SuperSU.
3.Take your 'recovery.img' and move it to the folder with your ADB and Fastboot (on your desktop). Make SURE it is in the same folder with the adb and fastboot programs and is named 'recovery.img'.
4. Take your 'SuperSu' zip file you downloaded (DON'T UNZIP IT) and move it to your phones SD card (preferred) or Internal Storage.
5. Once your recovery image is in the ADB folder and the SuperSU zip file is on your phone's storage, type the following command: 'adb reboot bootloader'
6. Your phone will reboot into the, now familiar, bootloader screen! For this tutorial, we are actually going to flash TWRP onto the phone so it is the phone's default recovery program. To do this, while in the bootloader screen on your phone, type the following command into your command console on your computer: 'fastboot flash recovery recovery.img'
7. Once it is done and successful, enter the following command into your CMD console to make sure TWRP in installed on your phone: 'fastboot reboot bootloader'. On your phone, use the Volume+ and Volume- keys to navigate to the 'Recovery' option. Press the Power key when it is highlighted!
8. Once you are in your TWRP, press the 'install' button. Navigate to the storage folder on your phone that contains the SuperSU zip file you moved from your computer onto your phone in step #4. When you see it, click on it and use the slider to flash it onto your phone. Once it is done, (as you should ALWAYS do after a flash), click the 'Wipe cache/dalvik' button and do the 'Swipe to Wipe'. Once done, click the 'Reboot System' button!
Step Three: Now your phone is rooted and has TWRP installed! It is time we install Cyanogenmod CM13!
1. Go HERE and download the 'Latest Nightly' rom at the top of the page. It will download a .zip file to your computer. Then go HERE, select ARM->6.0->Stock and hit the green download button (it's pretty big). Once both are downloaded, boot up your phone (if not already done) and connect it to your computer. Move both these .zip files to your phone's SD card (recommended) or internal storage.
2. Boot into recovery after the transfer is complete by holding the Power+Volume Down buttons. When the screen turns black, let go of the power button and continue to hold Volume Down.
3. Once in the bootloader, use the Volume+/Volume- buttons to navigate to the Recovery option. Hit the power button when it is selected.
4. Once in TWRP recovery go to install. Navigate to where you just transferred the two .zip files you just downloaded ONLY TO MAKE SURE THEY ARE THERE ALONG WITH THE SUPERSU .zip FILE YOU DOWNLOADED EARLIER. If it isn't, figure out why and correct it! If it is, continue (DO NOT INSTALL EITHER LOL)
5. Go to the 'Wipe' option on the homescreen of TWRP. REMEMBER TO HAVE BACKED UP ALL YOUR DATA BY THIS POINT. Move the slider to complete the wipe.
6. NOW we can install the rom! Go back to 'Install' on the homescreen of TWRP. Navigate back to the .zip file of the Nightly Build rom again (NOT THE GAPPS), and select it! Once selected, move the slider to flash Cyanogenmod CM13 to your phone. WE WILL NOT BE INSTALLING THE GAPPS YET. YOU WILL FIND OUT WHY SHORTLY.
7. Once it is done, hit the 'Wipe cache/dalvik' button. Once completed, go ahead and reboot the system! The first boot will take awhile to set everything up. Have patience!
8. Once everything installs, you will be at the setup screen. As you go through the setup screen, something weird will eventually happen...you won't be able to hit the 'Next Button'. The only thing that will happen is when you hit 'next' your phone will bring the system tray down from the top. It took me AGES to figure this out people...but NOT installing the GAPPS at the start is literally the only way to get past this (with GAPPS installed, it takes too long to proceed through setup and you will keep getting killed by the drop down screen). Get through it in step 9!
9. Once you get to the point in setup that the dropscreen comes down, position your right thumb so its hovering above the 'Next Button' and DON'T MOVE IT. Using your left hand, hold the power button until you see an option to 'Restart' the phone. Do it. And from the moment your phone restarts, RAPID TAP (and I mean it, tap as fast as your thumb will allow you) WITH YOUR RIGHT THUMB WHERE THE 'NEXT' BUTTON WILL BE. Do NOT stop until you have successfully got through the setup process and are on the android's home screen! At this point, you MAY have an issue hitting the middle gray button at the bottom of your phone (next to messages and chrome icons) without it bringing down the stupid drop screen. To fix this, once again position your thumb on the gray button that sends you to your apps and hover it there. Restart the phone again, and rapid tap where this gray button will appear upon boot. Once booted and you have successfully clicked the button, the error goes away! You can navigate your phone normally and reset it without the problem coming back! (if it does, simply repeat this past step to get rid of it).
10. NOW we can reboot back into the bootloader by holding the Power/Volume- keys. Once in the bootloader, navigate with the Volume+/Volume- keys to the recovery option, and hit the power button to boot up TWRP.
11. Once in TWRP, click the 'install' button. Navigate to where your GAPPS .zip file is (the one you just downloaded along with the nightly rom), click on it, and move the slider to flash it. Once it finishes, make sure to wipe the Cache/Dalvik. Do not reboot yet!
12. Navigate back to the 'Install' button of TWRP, and find your SuperSU .zip you installed earlier. Install it again for safe measures and wipe the Cache/Dalvik once it is done!
13. Boom. Restart the phone and you now have working CM13 6.0 on your Moto E 2015 Device! Now the moment you have all been waiting for, POKEMON GO !
Step 4: How to make Pokemon Go run GREAT
1. Once booted up, go to your system->about phone. Click on the 'Build Number' 7 times to unlock developer mode.
2. Go to your system->Developer options and make the following changes
-Advanced Reboot->ON
-Root Access->APPS and ADB
-Select USB Configuration->MTP (Media Transfer Protocol)
-Window Animation Scale-> changed to 0.5x
-Transition Animation Scale-> changed to 0.5x
-Animator Duration Scale-> changed to 0.5x
-Don't Keep Activities-> Turn ON
-Background Processes limit-> Change to 'At most 1 process'
3. Now, head to your system->Apps settings. Force Stop and Disable the following (unless you actually use it...)
-Cloud Print
-Docs
-Drive
-Fit
-Gmail (unless you use it, using chrome browser to access it is better option to keep phone running fast)
-Google Play Books
-Google Play Games
-Google Play Movies & Tv
-Google Play Music
-Google Play Newsstand
-Google+
-Hangouts
-Keep
-News & Weather
-Screen Recorder
-Sheets
-Slides
-Youtube
4. Go to your settings->security and enable 'Unknown Sources'
5. Go to settings->memory and hit 'Apps Started on Boot' and make the following changes
-Photos: deselect 'keep awake' and 'start at boot'
-Keep: deselect 'keep awake' and 'start at boot'
-Hangouts: deselect 'keep awake' and 'start at boot'
-Camera: deselect 'keep awake'
-Gmail: deselect 'keep awake' and 'start at boot'
-Exchange Services: deselect 'start at boot'
-Media Storage: deselect 'keep awake' and 'start at boot'
-Download Manager: deselect 'keep awake' and 'start at boot'
-CM Updater: deselect 'keep awake' and 'start at boot'
-Talk Back: deselect 'keep awake' and 'start at boot'
-YouTube: deselect 'keep awake' and 'start at boot'
-Google Play Movies & TV: deselect 'keep awake' and 'start at boot'
-Fit: deselect 'keep awake' and 'start at boot'
-Google Play Music: deselect 'keep awake' and 'start at boot'
6. Reboot the system! (hit the power button and hit reboot->reboot)
7. Go into the google play store, and login using your normal account settings.
8. Once logged in, download 'Kernel Adiutor (ROOT)' and open it up. Allow it to use root access (screen will pop up be looking for it).
9. Once opened, hit the tray button to the left of 'Kernel Information' (the three lines) and go to CPU. Slide the 'Apply On Boot' bar to the right to enable. Set your 'CPU Maximum Frequency' to '1209MHz' and 'CPU Minimum Frequency' to '400MHz'. Then, change the CPU Governor to 'Performance'.
10. Now that your phone is running faster than ever, go to chrome on your phone and google search 'Pokemon Go APK'. I used the 'APKPURE Pokemon Go APK 0.31.0' from m.apkpure.com. Your phone might glitch a tiny bit (it did for me the first time) and do a soft reboot. It's fine! Re-open chrome and hit the 'Download APK 59.9MB) bar beneath 'Verification Passed' and it will start downloading. Once it is done, open your 'File Manager' and go to the 'Internal Storage' then go to 'Download'. Click on the 'Pokemon Go' icon and allow it to install!
11. Start up the app, and MAKE SURE you only have ONE google email on the device. Let the game load, and set everything normally. When it asks you to login (if you use the google account one) right after you hit the google account, click on the screen in the middle rapidly. It SHOULD keep the game from re-setting. If the game does reset, don't fret. Restart it and try again. Once you get past this point? You phone should be running the game 2x if not 3x better than before! The final step is once the game is loaded, click on your pokeball icon and go to settings. Turn on battery saver mode!
Boom Bada Bing! Your phone should not only load the game ridiculously fast now, your battery life will be extended 2x-5x and the game will run at a steady rate keeping your CPU cooler than ever before!
This guide is compiled based on the struggles I faced getting the game to work properly. I got the phone from my wife while I wait and wait and wait for Pokemon Go to POSSIBLY come to my Windows Phone 1020 lol. When she gave it to me, it ran terribly and would overheat after 20 minutes of play in the sun. These are the ways I got the phone to run soo smoothly that now she ALMOST wants the phone back haha!
Any errors you see? Any fixes not mentioned? Give some feedback in the comments below!
Any reason for using stock gapps? You seem to disable most of the gapps anyway so perhaps it may be good to just go with nano or pico?
I put it in there in case someone wanted to use one of the stock gapps in the future.
Dude.... I already have CM 14 since a month....and I simply downloaded the app and followed the steps as you said..... Pokemon Go's still not working
RayShah_N said:
Dude.... I already have CM 14 since a month....and I simply downloaded the app and followed the steps as you said..... Pokemon Go's still not working
Click to expand...
Click to collapse
What error are you getting?
shaktiman01 said:
What error are you getting?
Click to expand...
Click to collapse
Unable to authenticate. Please try again
RayShah_N said:
Unable to authenticate. Please try again
Click to expand...
Click to collapse
That's due to Pokemon go now don't run on rooted phones.
For this you have to delete su files from following directory :
/System/bin
/System/xbin
Give it a try.... But you'll lose root access