Related
I take no credit for this amazing equalizer. All credits go to @zhuhang and the people from his thread for the convolvers.
If you don't know what V4A is check here for more details.
But basically it's an audiophiles dream that can cause serious hearing loss and such audio enjoyment at the same time!
The Zip has all the files included to enable "neon" support for convolvers, which are also included.
The feedback I've received so far is 100% success.
INSTRUCTIONS:
1) DOWNLOAD THE ZIP
2) FLASH IN RECOVERY (no need to uninstall if you already have viper installed)
3) open the app and you will be prompted to install the drivers. (I always choose the top one, although it does consume more batter, we'll worth it)
The EQ can be either super simple with just the basic adjustments or can get really technical in "expert" mode.
To activate the convolvers hit the 3 dots in the top right and click click the "ui settings" and change it to expert
Current version Download and discussion starts here
UPDATE VERSION 2.4.0.1 Neon Enabled + Convolvers
If using my previous zip version a simple flash of the new zip will update your V4A.
If you are running any version other than the one in my previous zip you will need to follow the steps below to ensure a smooth update to 2.4.0.1.
1) uninstall current driver from Viper by selecting the option is the app or use file manager and delete "libv4a_fx_ics.so" from system/lib/soundfx.
2) wipe data app with application manager or TiBackup
3) uninstall your current V4A
4) Flash to new zip
5) boot up and enjoy
6) hit the thanks button.
old version
Viper4Android neon enabled including convolvers
Thanks to @SammyTRK for confirming it works for this device!
Enjoy!
With permissive enabled kernel, just install v4a as normal app, neon also enable.
Sent from my SM-N920P using XDA-Developers mobile app
Hey everyone, over at The Nexus 5X Forum we tweaked the thermal throttling behavior of the phone. Since The Moto X Pure uses the same SOC, we can also apply this (with a few changes) to this phone.
Update: Please uninstall the old version and reinstall as soon as the new version is online.
Update: Now with a Aroma zip isntaller, see post 2. thanks @tohtorin
I don't own this phone, so I need to rely on some volunteers to test things out.
Of course, you need root and this could potentially damage your phone, so don't crank up the thermals too high. I'm not responsible for any damages, tweak at your own discretion. Even though the phone (probably) has built in overheating protection, be careful.
Naturally, you can also use this to decrease the temps if you think it's too hot, downclock the CPU's, or disable the big cluster alltogether.
One more thing. This will work on the stock kernel. I don't know about other kernels, since they might implement their own thermal tweaks.
First, I'll show you how to actually see the CPU and GPU frequencies. You need the following apps: trepn profiler, stability test and Antutu 3D bench. Trepn profiler can show the frequencies in an overlay, switch to advanced mode and select what you want to see. Don't look at the CPU temperature, it looks crazy hot, but it's irrelevant. The real important temperatures cannot be shown in here.
Stability test is a small app that pushes the CPU so you can quickly see the throttling behavior. Antutu 3D bench is just that, a benchmark for 3D. If you run this a few times and the GPU does not drop it's frequency, than we can confirm that it doesn't throttle.
Let's start with the GPU. It seems that, on this device, the GPU is not throttled at all. It seems strange, since the Nexus 5X's GPU is throttled quite aggressively. If someone could confirm this, that would be nice.
The file that needs to edited is located under /system/etc and is called thermal-engine-clark.conf. You need a root explorer to edit the text and set permissions.
Let's move on to the big cluster (the fast cores): There are two relevant entries for them.
The hotplug temperature determines at what temperature the big cores are shut down.
Code:
[HOTPLUG-CPU5] and [HOTPLUG-CPU4]
thresholds [B][COLOR="Blue"]44[/COLOR][/B]000 and [COLOR="blue"][B]47[/B][/COLOR]000
thresholds_clr [COLOR="blue"][B]42[/B][/COLOR]000 and [B][COLOR="blue"]45[/COLOR][/B]000
The blue numbers represent the temperature at which the core is shut down. Thresholds means when it is shut off, thresholds_clr when it goes back online. Keep at least 2°C between them.
Next is the throttling behavior. Both cores' throttling is determined by this setting:
Code:
[MONITOR-QUIET-1]
thresholds [B][COLOR="blue"]44[/COLOR][/B]000 [COLOR="blue"][B]45[/B][/COLOR]000 [COLOR="blue"][B]46[/B][/COLOR]000
thresholds_clr [B][COLOR="blue"]42[/COLOR][/B]000 [COLOR="blue"][B]43[/B][/COLOR]000 [COLOR="blue"][B]45[/B][/COLOR]000
action_info [B][COLOR="SeaGreen"]1632[/COLOR][/B]000 [COLOR="seagreen"][B]1248[/B][/COLOR]000 [COLOR="seagreen"][B]960[/B][/COLOR]000
Again, the blue numbers show the temperature, and thresholds means when it clocks down, thresholds_clr when it increases the clock. Keep at least 1°C between them. The green numbers show the clock speed. That means @44°C the big cores' frequencies wil be decreased to 1.632 GHz (down from 1.824 GHz) and so forth.
Now to the little cores. Only one of them is shut off at a certain temperature:
Code:
[HOTPLUG-CPU2]
thresholds [B][COLOR="Blue"]48[/COLOR][/B]000
thresholds_clr [B][COLOR="Blue"]45[/COLOR][/B]000
The throttling behavior:
Code:
[MONITOR-QUIET-0]
thresholds [B][COLOR="Blue"]46[/COLOR][/B]000 [B][COLOR="blue"]48[/COLOR][/B]000
thresholds_clr [COLOR="blue"][B]44[/B][/COLOR]000 [B][COLOR="blue"]46[/COLOR][/B]000
action_info [COLOR="SeaGreen"][B]1248[/B][/COLOR]000 [COLOR="seagreen"][B]960[/B][/COLOR]000
Profiles and Installation
I created some profiles that you can place and overwrite in your system/etc folder (rename them to thermal-engine-clark.conf). Set permissions to rw- r-- r-- and reboot
Update: thanks @tohtorin for a flashable zip!
Update: Please uninstall the old version and reinstall as soon as the new version is online. Sorry for the inconvenience.
The new installer 1.2 and uninstaller 0.2 are online. I also attached the old 0.1 uninstaller in case someone still needs it. The magisk uninstaller didn't change.
Code:
INSTALLATION:
1. Download installer zip
2. Only IF using magisk, download magisk module for moto x as well
3. Reboot to custom recovery
4. Only IF using magisk (requires magisk v6 or higher) flash thermal tweaking magisk module
5. Flash installer zip
6. Select proper installation method:
- Systemless for SuperSU systemless install (requires SuperSU v2.76 or higher)
- Magisk for magisk install (requires magisk v6 or higher)
- System for classic system install (writes directly to system partition and might trigger dm-verity, breaks OTAs)
7. Select profile to be installed (uses stock by default)
8. Enjoy your snappier Moto X
UNINSTALLATION (Only with systemless or magisk):
1. Download uninstaller zip IF using magisk then download uninstaller for magisk
2. Reboot to recovery
3. Flash uninstaller zip
4. Reboot back to stock thermal settings
If using system mode just flash stock settings with installer to get back to stock
Light profile:
Increase all blue temperatures by 2. This should be almost risk free.
Medium:
4. This will make your phone noticably warmer.
Heavy:
6. Should be safe, but that's just an estimate.
Insane:
8. That is hot. Would not recommend it.
I'll make an installer for this today. It supports supersu systemless, magisk and normal system install.
Stay tuned.
So what about this file
“/system/bin/thermal engine”?
lknnnn said:
So what about this file
“/system/bin/thermal engine”?
Click to expand...
Click to collapse
No. Thats the engine binary itself. Config file is located at /system/etc/thermal-engine-8992.conf
---------- Post added at 14:52 ---------- Previous post was at 14:39 ----------
NOTE: I do not own this device so there might (and probably will) be bugs around. Just report them to me with recovery log if possible.
AROMA installer ported from Nexus 5x
Changelog:
v1.1
* Fixed few typos
v1.0
* Initial release
* Ported from Nexus 5x
* Support magisk, system and systemless installations
INSTALLATION:
1. Download installer zip
2. Only IF using magisk, download magisk module for moto x as well
3. Reboot to custom recovery
4. Only IF using magisk (requires magisk v6 or higher) flash thermal tweaking magisk module
5. Flash installer zip
6. Select proper installation method:
- Systemless for SuperSU systemless install (requires SuperSU v2.76 or higher)
- Magisk for magisk install (requires magisk v6 or higher)
- System for classic system install (writes directly to system partition and might trigger dm-verity, breaks OTAs)
7. Select profile to be installed (uses stock by default)
8. Enjoy your snappier Moto X
UNINSTALLATION (Only with systemless or magisk):
1. Download uninstaller zip IF using magisk then download uninstaller for magisk
2. Reboot to recovery
3. Flash uninstaller zip
4. Reboot back to stock thermal settings
If using system mode just flash stock settings with installer to get back to stock
Download primarily from OP attachments, but here is direct secondary links:
Installer:
http://drg.fi/misc/thermal_tweaking_systemless_motox_v1.1.zip
Magisk module:
http://drg.fi/misc/thermaltweaking_magisk_motox.zip
Uninstaller (which is same for N5X and motox):
http://drg.fi/misc/thermal_tweaking_uninstaller_v0.1.zip
Uninstaller for magisk:
http://drg.fi/misc/thermal_tweaking_magisk_uninstaller_v0.1.zip
@Razorless you can update OP accordingly
Enjoy!
got it.thanks
Fixed few typos from installer so do not care if old one says in recovery "Selected profile: Normal" even tho you selected different. Its just a typo and it is fixed now.
Updated installer:
http://drg.fi/misc/thermal_tweaking_systemless_motox_v1.1.zip
Will test as soon as I get the time.. The file is of a different file name btw
ffonegod said:
Will test as soon as I get the time.. The file is of a different file name btw
Click to expand...
Click to collapse
Do you mean this is the only engine you see in system/etc after installing? When using the systemless installation, it can occur that certain file managers no longer "see" the thermal-engine-8992. This is because the system gets the information from a differernt file. Nothing to worry about.
Razorless said:
Do you mean this is the only engine you see in system/etc after installing? When using the systemless installation, it can occur that certain file managers no longer "see" the thermal-engine-8992. This is because the system gets the information from a differernt file. Nothing to worry about.
Click to expand...
Click to collapse
that's the stock engine file name actually before installing..
@Razorless I think we need to change those profile file names since I think moto x reads that clark file instead of 8992 so flashing our installer does not affect thermal engine?
tohtorin said:
@Razorless I think we need to change those profile file names since I think moto x reads that clark file instead of 8992 so flashing our installer does not affect thermal engine?
Click to expand...
Click to collapse
That's my point.. Clark has a different file name engine so flashing the "8992" won't make a difference.. It wouldnt overwrite the stock file you would just have 2 file engines installed
ffonegod said:
That's my point.. Clark has a different file name engine so flashing the "8992" won't make a difference.. It wouldnt overwrite the stock file you would just have 2 file engines installed
Click to expand...
Click to collapse
Thermal engine uses different config file so yes you are right it does not even try to load different one. I can make a changes to installer when razorless confirms this.
N5X and LG G4 has 8992 conf file, dont know about other 808 SoC devices.
tohtorin said:
Thermal engine uses different config file so yes you are right it does not even try to load different one. I can make a changes to installer when razorless confirms this.
N5X and LG G4 has 8992 conf file, dont know about other 808 SoC devices.
Click to expand...
Click to collapse
To verify that, someone needs to upload all thermal-engine files present on a stock Moto X so we can take a look at this.
I know the LG G4 has two thermal engines, but both the G4 and 5X read the 8992 for throttling/hotplugging. The thermal engine I found somewhere on the Moto forum was only named "Moto default", so I didn't know it's original file name. I just assumed it was the same as on the G4 and 5X.
Razorless said:
To verify that, someone needs to upload all thermal-engine files present on a stock Moto X so we can take a look at this.
I know the LG G4 has two thermal engines, but both the G4 and 5X read the 8992 for throttling/hotplugging. The thermal engine I found somewhere on the Moto forum was only named "Moto default", so I didn't know it's original file name. I just assumed it was the same as on the G4 and 5X.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=3775249&d=1465303814.. That's the moto default file u mentioned
Found it.. This is the engine on my device presently
ffonegod said:
Found it.. This is the engine on my device presently
Click to expand...
Click to collapse
Thanks, this confirms that the name of the engines need to be changed.
So everyone please uninstall the thermal tweaks and reinstall as soon as the new zip is ready. Or download the new profiles from post two and overwrite.
That sounds interesting but what are the expected benefits?
AROMA installer updated:
Changelog:
Systemless installer v1.2
* Fixed thermal engine config filename
Magisk module v0.2
* Fixed config filename
Now Moto X has its own uninstaller (the same with N5X does not work anymore):
Uninstaller v0.2
* Fixed config file name
Download from here:
Installer:
http://drg.fi/misc/thermal_tweaking_systemless_motox_v1.2.zip
Uninstaller:
http://drg.fi/misc/thermal_tweaking_uninstaller_motox_v0.2.zip
Magisk module:
http://drg.fi/misc/thermaltweaking_magisk_v0.2_motox.zip
@Razorless update OP accordingly
Enjoy!
tohtorin said:
AROMA installer updated: Enjoy!
Click to expand...
Click to collapse
Thanks, post #2 has been updated
DekkerP6 said:
That sounds interesting but what are the expected benefits?
Click to expand...
Click to collapse
The phone will not throttle as much under heavy load with a tweaked thermal-engine, but it will become warmer.
Welcome to the official thread for Intex Cloud Tread.
You can discuss anything related to the phone here. (All links are Google Drive and XDA)
Make: INTEX
Model: Cloud Tread
Stock ROM: Android 5.1
Kernel: 3.10.72 (Remember this while looking for ROMs to port)
SOC: MT6591 (The same as MT6592, so you can easily port ROMs)
RECOVERY
Type: TWRP
Version: 3.2.1 EXPERIMENTAL
Kernel: 3.10.72
Supports: MT6591/MT6592
Download (Note: Old backups doesn't' work with this one.)
*Might have a couple of bugs (CPU Temperature doesn't work, ADB Backup doesn't work), but works for backups and restores and flashing and mounting and ADB Sideloads. This is an experimental build. Use with caution.
Type: TWRP
Version: 3.1.0
Kernel: 3.10.72
Supports: MT6591/MT6592
Download New Fixed Version Download (Note: Old backups doesn't' work with this one.)
OLD Version (This was a half-assed port from Excite Prime that Identifies device as Excite Prime and has a lot of other bugs)
Download OLD Version
Instructions:
1. Download and install SP Flash Tools
2. Start it and go to Download tab.
3. Now, in the scatter loading file box open the SCATTER Text you downloaded. (Link below)
4. Make sure the drop down box is selected at Download Only.
5. Untick all boxes except recovery and double click on the location part of the recovery row.
*DON'T PLUG YOUR PHONE IN NOW*
6. Select the recovery you downloaded from here and click the Download button.
7. Now turn the phone off or remove its battery and plug it in.
The necessary drivers should install and wait for a few seconds until a green tick or circle comes on the screen.
There, one custom recovery for INTEX Cloud Tread has been flashed.
SCATTER FILE - Download (You will need it to use with SP Flash Tool)
If you want the STOCK RECOVERY download it from here.
ROOT
Type: SuperSU
Download
Instructions:
1. Copy the file to your SD Card.
2. Press Volume Up+Power to boot into recovery when the phone is off.
3. There go to Install > Select Storage > MicroSD > SuperSU.zip.
4. Un-check Reboot Automatically. (This may clear the dalvik-cache which is recommended but not necessary and might take some time to boot up the first time.)
5. Then Swipe to flash and reboot.
Congratulations! You are now rooted without the annoying KingUser.
XPOSED
Installer: v89 sdk 22
Download
Uninstaller: Download
Instructions:
Flash XPOSED using the same method used to flash SuperSU above.
After flashing Clear Dalvik-cache (Option is on the same screen) and boot into android and install below APK to manage XPOSED
XPOSED APK v3.1.5
Uninstallation Instructions are also the same.
STOCK ROM - Download
Flash with SP Flash Tools.
After flashing stock ROM from the above link, untick all the boxes and tick only the boot image section.
Now download and select this boot image and flash.
This is because the boot image included in the above linked ROM has screen flickering issues.
Intex Cloud Tread Battery and Performance Optimization
First download and flash this "IntexDebloat.zip" file.
It will remove the bloatware that came with the phone. (User uninstallable apps are not included)
Intex Keypad (Which when automatically updates to Mox Keypad is a privacy nightmare) is also removed. Use Gboard or the stock AOSP keyboard in the phone.
Now make sure you are rooted and have xposed installed.
Install these below apps from playstore or apkmirror or from anywhere
1. Greenify
2. Kernel Adiutor
3. L Speed
4. Busybox
5. Powernap 0.7a (optional) (and don't download the newer versions or update from play store)
After installing all of the above follow these tutorials in order.
#BusyBox - Preparing the phone
Open busybox, grant SuperUser permissions and install it. Now you can uninstall the app if you don't need it.
#Kernel Adiutor - Custom Governor Tunings
Disabling MTK Performance Service
This is one of those situations where a good idea is implemented in a not so good way. Performance service can provide you good performance at a very dear cost of battery life and it can also override or worse play along and consume more power with the below tweaks. So you should disable it before attempting these.
Open Kernel Adiutor, grant su permissions and in the sidebar goto build prop tab
There search for ro.mtk_perfservice_support
Change its value from 1 to 0.
Now we are going to tune the Governor.
Believe me when I say this I've been tuning this phone for over two years now with 100s of different configurations and these are the two best configurations for a balance between power consumption and performance.
Option one: Hotplug with rush function and fast sampling rate (My favorite)
Open Kernel Adiutor > CPU tab.
Make sure the governor is set to Hotplug.
Now change the following Governor tunables;
Code:
cpu_down_avg_times=20
cpu_down_differential=1
cpu_input_boost_enable=0
cpu_rush_boost_enable=1
cpu_rush_threshold=98
down_differential=5
sampling_rate=30000
up_threshold=99
This should give you good performance while maintaining good battery life
Option 2: Hotplug with no rush and high sampling rate (This is also good for battery life but a bit low on performance)
Code:
cpu_down_avg_times=20
cpu_down_threshold=20
cpu_input_boost_enable=0
cpu_rush_boost_enable=0
cpu_up_threshold=90
down_differential=5
sampling_rate=73000
up_threshold=97
No matter what you choose your battery life is hugely dependent on what you choose to do with your device. I usually get 5h of *continuous* SOT on auto brightness with these settings on WiFi and browsing. YMMV.
Some people might suggest setting
ignore_nice_load=1 for more battey life as well. But this phone kinda categorizes everything as nice processes and will only run on 1-2 cores @728MHz if you enable that without MTK Performance Service. It did got me more than 7h SOT but it was basically unusable.
Make sure you enable apply on boot on each page you change to make it apply on each boot!
Now go to I/O Scheduler tab.
There change scheduler to noop for internal storage and sd card if you have one.
Also goto settings and change the apply on boot delay to instant.
#LSpeed, Paget96's masterpiece!
Open L Speed, finish the tutorial without enabling anything and do as follows
Sidebar > Main section
Disable Debugging: Enabled
Window Animation Scale: 0.5x
Transition Animation Scale: 0.5x
(Don't change animator duration scale as it will mess up every animations in the device)
CPU Tuner
Don't enable anything in here, we already tuned our governor with our own values in Kernel Adiutor.
Battery
Battery Improvement: Enabled
I/O Tweaks
SD Tweak: Enabled (If you have a SD Card)
I/O Boost: Enabled
Partition Remount: Enabled
Disable I/O stats: Enabled
Don't enable scheduler tuner as we choose noop in kernel adiutor which can't be tuned!
RAM Manager
You will be tempted to change a lot of things here but don't. It will only make it worse. Just change the below settings
Virtual Memory Tweaks: Battery
Cache Reclaiming: 50%
OOM Killer: Enabled
OOM Dump Tasks: Disabled
Also you can do a fstrim as well if you would like to. No probs.
Now go to settings and chage the apply on boot delay to instant.
#Greenify
Install greenify, enable the module in xposed installer and restart. After boot, make sure you wait till L Speed and Kernel Adiutor apply their settings.
Now open greenify, goto its settings, xposed based features and enable the below
Wakeup timer coalescing
Telephony Wakeup
Greenifying System apps
Now go back, select add apps and on the top right corner, select the three dot button and choose Show All.
Now add every app in the phone to greenify. (Don't worry greenify only hibernates app that consumes battery, those who don't consume battery in the background will be shown as background free.)
Don't add the following apps:
Bluetooth
MTK NLP Service
Phone
Phone (System)
Google play Services
Google Play Services (Persistent)
Voicecommand
Download manager
Calendar storage
Play store
Google account manager
com.mediatek.voiceextension
Google backup transport
Google calendar sync
Google contacts sync
Kernel Adiutor
L Speed
Prevent Pocket Dials
Click to expand...
Click to collapse
^These will start again and will consume more battery if you hibernate them.
#Power Nap (Optional)
Only install v0.7a (link above).
It's the basic stuff. Install, enable in xposed installer, open, enable the first option, add L Speed and Kernel Adiutor to it's whitelist. And reboot.
And that's it! Make sure you add any new app you install to greenify. Some say you don't need to hibernate everything, only the rogue apps. But Greenify itself can decide whether it should hibernate an app or not. So that's fine.
This took me a long time to write and more importantly this took me two years of experimentations to find. (Especially the governor tunings). Hope you guys enjoy it.
In addition to this I also recommend using Nova Launcher as the stock launcher is basically adware and follow the usual "don't install every crap-booster-cleaner-app you see" advice to maintain your device.
Device not revealed.
When I start MTK Droid tool, it says,"The device isn't revealed. Connect or reconnect a cable." I waited for like half an hour still the issue persists.
MTK Droid doesn't work that easily with phones newer than KitKat because of an incompatible adb. The solution is to manually replace the adb while MTK Droid Tools is running to make it work.
You can use this script I made that will automate the process and saves you the hassle.
https://forum.xda-developers.com/android/general/fix-impossible-to-start-adb-error-t3582571
Remember: Keep the phone connected with USB Debugging enabled before using the above script.
If it fails, try again it will work. :good:
Ritesh Sachan said:
When I start MTK Droid tool, it says,"The device isn't revealed. Connect or reconnect a cable." I waited for like half an hour still the issue persists.
Click to expand...
Click to collapse
Bump! :highfive:
Yes it did work, but on running mtk droid tools the icon on the bottom left corner shows yellow colour. So to fix that I clicked on the ROOT option next to the ADB Terminal option. I granted the access through my phone. Few seconds later the icon turns green for few milliseconds and it quickly turns into red colour saying "CONNECTION LOST." Even though my device was connected with USB Debugging ON. HELP ME.
You cant use MTKDroid to root the phone. Try with TWRP and SuperSu.zip
Now even after rooting MTKDroid will report that the phone is not rooted.
That's another security feature of Android. The adbd interface will work on non root mode even after rooting. You have to install adbd insecure apk (paid on google play, but available for free here on its XDA thread) by chainfire to change it to root mode.
Link to adbd - https://forum.xda-developers.com/showthread.php?t=1687590
Adithya FRK said:
Welcome to the official thread for Intex Cloud Tread.
You can discuss anything related to the phone here. (All links are Google Drive and XDA)
Make: INTEX
Model: Cloud Tread
Stock ROM: Android 5.1
Kernel: 3.10.72 (Remember this while looking for ROMs to port)
SOC: MT6591 (The same as MT6592, so you can easily port ROMs)
RECOVERY
Type: TWRP
Version: 3.1.0
Kernel: 3.10.72
Supports: MT6591/MT6592
Download
Instructions:
1. Download and install SP Flash Tools
2. Start it and go to Download tab.
3. Now, in the scatter loading file box open the SCATTER Text you downloaded. (Link below)
4. Make sure the drop down box is selected at Download Only.
5. Untick all boxes except recovery and double click on the location part of the recovery row.
*DON'T PLUG YOUR PHONE IN NOW*
6. Select the recovery you downloaded from here and click the Download button.
7. Now turn the phone off or remove its battery and plug it in.
The necessary drivers should install and wait for a few seconds until a green tick or circle comes on the screen.
There, one custom recovery for INTEX Cloud Tread has been flashed.
SCATTER FILE - Download (You will need it to use with SP Flash Tool)
If you want the STOCK RECOVERY download it from here.
ROOT
Type: SuperSU
Download
Instructions:
1. Copy the file to your SD Card.
2. Press Volume Up+Power to boot into recovery when the phone is off.
3. There go to Install > Select Storage > MicroSD > SuperSU.zip.
4. Un-check Reboot Automatically. (This may clear the dalvik-cache which is recommended but not necessary and might take some time to boot up the first time.)
5. Then Swipe to flash and reboot.
Congratulations! You are now rooted without the annoying KingUser.
XPOSED
Installer: v87 sdk 22
Download
Uninstaller: Download
Instructions:
Flash XPOSED using the same method used to flash SuperSU above.
After flashing Clear Dalvik-cache (Option is on the same screen) and boot into android and install below APK to manage XPOSED
XPOSED APK v3.1.1
Uninstallation Instructions are also the same.
Recommended and tested Mods:
Ultimate Performance MOD by sohamsen (Tweaks - Flashable with TWRP)
BootManager (XPOSED Module)
GravityBox [LP] (XPOSED Module) (Requires dalvik-cache to be cleared after changing settings to avoid SystemUI crash)
Zeus Contextual Expanded Status Header (XPOSED Module)(Requires dalvik-cache to be cleared after changing settings to avoid SystemUI crash.
Android O (Oreo) Boot Animation by -CALIBAN666-
I made a flashable ZIP here. In case you want the stock animation back, flash this.
If you did encounter a SystemUI crash after enabling some XPOSED module you can boot into twrp and Deleting the folder 'conf' from /data/dev.robv.android.xposed.installer to disable the XPOSED modules without uninstalling it altogether.
Thanks: rovo89 for XPOSED for Lollipop.
If this guide has been helpful for you, please hit thanks.
Click to expand...
Click to collapse
Awesome work Adithya ..have been looking for custom recovery for quiet long....and your twrp worked like a charm..Thankyou....just need to point u out that supersu link is not working....keep-up the good work,will be looking forward for new custom roms for intex cloud tread from u.
jackquest said:
Awesome work Adithya ..have been looking for custom recovery for quiet long....and your twrp worked like a charm..Thankyou....just need to point u out that supersu link is not working....keep-up the good work,will be looking forward for new custom roms for intex cloud tread from u.
Click to expand...
Click to collapse
Thanks for pointing that out. I will fix it as soon as possible. Also updated some extra info about the tweaks.
i have used this boot animation (Android O (Oreo) Boot Animation by -CALIBAN666- ) ....its working perfect...thanks ... if possible upload stock rom to flash with sp flash tools(in case if phone brick) . i have tried mtk tools to backup and your zip" [FIX] 'It is impossible to start ADB' or 'Phone not revealed' error in MTKDROID Tools" ... no success ...cannot get root in mtk tools though my phone is rooted.
That is a safety measure. Install adbd insecure to enable root interface.
jackquest said:
i have used this boot animation (Android O (Oreo) Boot Animation by -CALIBAN666- ) ....its working perfect...thanks ... if possible upload stock rom to flash with sp flash tools(in case if phone brick) . i have tried mtk tools to backup and your zip" [FIX] 'It is impossible to start ADB' or 'Phone not revealed' error in MTKDROID Tools" ... no success ...cannot get root in mtk tools though my phone is rooted.
Click to expand...
Click to collapse
Stock ROM link added.
Adithya FRK said:
That is a safety measure. Install adbd insecure to enable root interface.
Click to expand...
Click to collapse
after install [2014.11.10][ROOT] adbd Insecure v2.00 i got root access on mtk tools though weird its not showing my imei numbers its button is gray...block map create scatter is gray
when i hit backup its trying to store preloader and other files on phone then error no space on phone ...only 1 file on comuputer backup its system...any way i got that repair mobile stock rom before its posted ,was not sure if its tested and safe to flash if needed
Before doing anything, please do a readback using SP Flash Tools. The scatter file is in the #1 post.
EDIT: MTKDroid never worked for me too, apart from making the scatter file.
Adithya FRK said:
Before doing anything, please do a readback using SP Flash Tools. The scatter file is in the #1 post.
EDIT: MTKDroid never worked for me too, apart from making the scatter file.
Click to expand...
Click to collapse
Thanks for the advice ,got my readback using sp tools.
Just a suggestion, TWRP is extremely good with backups. If you just want the stock ROM, goto TWRP>Backup>Tick all except data and cache. The backup size should be around 1.6 GB.
Note: SuperSU and Boot animation are in the system partition so that will also be in the backup.
Adithya can u edit EBR files ..in our phone EBR 1 is too small ....i know the method ..though not a geek to do it.
hope this link will help u even getting new roms to intex cloud tread ....... http://www.droidgyan.com/development/
jackquest said:
Adithya can u edit EBR files ..in our phone EBR 1 is too small ....i know the method ..though not a geek to do it.
Click to expand...
Click to collapse
To be fair, I am not really a geek myself. I did this because I was so desperate to get a recovery.
The EBR records doesn't seem to be too small (I got 171 apps installed) and still says I can have more.
You should try SD Maid Pro it really is a great app to clean the remains if you are rooted, you might get more space that way.
Still, it's good to learn something new and might be useful in the future if you could share how to modify the partition size.
EDIT: I can't really work on my phone now. It's kind of my day to day phone.
just go to the link http://www.droidgyan.com/development/ everything /lots of information for MTK chipset.
Updated.
Warnings about powersave governor added. (Post #2)
Next post will be about saving battery without radically affecting performance using SetCPU.
This is a small magisk Module which will update gpu drivers for any android device having adreno 630 GPU specially snapdragon 845 devices comes with adreno630 gpu. Below is the list of SD845 devices with adreno 630 gpu where this module should work.
What are benifits of udating GPU drivers?
What benefits would updating your GPU more frequently have? Likely, you'd see more patches to rectify issues like game crashes, optimization for performance on new titles, and potentially support for new features.
https://mobile.phonebunch.com/phone-filter/gpu/adreno-630/page/1/
Requirements :
1)device with adreno 630 gpu
1) Rooted and magisk installed
Procedure :
1)First download AIDA64 apk. Install and open go to display there if you see GPU drivers version less than 4.15(415) then you can use this module.
But anything greater than that then you need not to update drivers.
2)serch for adreno 630 drivers under download section in magisk app. Download module, install and reboot.
https://play.google.com/store/apps/details?id=com.finalwire.aida64
To manually install module download from below link(as per your android version android 9 and android 10 have different modules)
https://github.com/Magisk-Modules-Repo/adreno-630-gpu-driver/releases
3) after installation reboot device and go to AIDA64 app see whether your GPU version changed to 4. 15(415)
Thats it guys enjoy new drivers
Here is small video tutorial if you wnat preview
https://youtu.be/4v-zW-KOeDk
Some Custom OS Like Lineage OS, Evolution X, etc. have a common problem - Error in Single Reception.
To fix Follow the following Steps -
DISCLAIMER - I am not responsible if any damage occurs.
1) Flash Magisk Root Manager.
2)Open Magisk Manager and Download and Install given Modules
- Riru (Riru - Core)
- Riru - EdXposed
**REBOOT**
3)Open EdXposed Manager (You will be redirected to Github to download the latest apk), Go to Modules and Enable EdXposed Manager.
**REBOOT**
4)Open EdXposed Manager, Go to Downloads, and Search LTE Mobile Signal Fix.
5) Download, Install and Activate the module in Modules Menu
**REBOOT**
And that's it.
NOTE -> This Method Currently works on Android 9.
**Android 10 Coming Soon**
Youtube Channel - https://www.youtube.com/channel/UCfgOffADDHCh7dOxUeB4NRQ
Video to install EdXposed - https://youtu.be/MezpjCoDRVQ