Related
So, this doubles as a root kernel (might as well keep the scripts in there since I already made 'em!), custom boot animations (/system/media/sanim.zip), init.d support.
Max speed is 1.94GHz. Max speed I've benchmarked stable at is 1.83GHz. Reboots at higher.. YMMV with voltage adjustments etc.
Stock speed on this kernel is 1566MHz, I have removed a lot of scaling overrides that Samsung added, so this should be a bit smoother than the stock kernel without OCing more than the slight default.
GPU is also OC'ed from 3d speed 266 -> 300 and 2d speed 200 -> 266.
I will be releasing a GUI soon with more advanced tweaking options for the kernel (it is compatible with existing tools like system tuner, fauxclock, setcpu, etc.)
Version 0.2 CWM Zip: http://m-s-j.net/dagnarf/cwm-sgh-i717-dagkernel-oc-v0.2.zip
Version 0.2 CWM Zip (with KALLSYMS + KALLSYMS_ALL for debugging) http://m-s-j.net/dagnarf/cwm-sgh-i717-dagkernel-oc-v0.2-kallsyms.zip
Version 0.2 CWM Zip (No root script, su, busybox in ramdisk) http://m-s-j.net/dagnarf/cwm-sgh-i717-dagkernel-oc-v0.2-nosubusybox.zip
New stuffs:
* BLN Support (Use BLN Control from market)
* XZ Compression
* CFQ Scheduler
* New CPUFreq governors: smartassv2, lagfree
Code:
CWM Zip 0.1 [url=http://m-s-j.net/dagnarf/cwm-sgh-i717-dagkernel-oc.zip]Available here[/url]
Odin Tar 0.1 [url=http://m-s-j.net/dagnarf/pda-overclocked-dagkernel-v01.tar]here[/url]
Modified libraries 0.1 [url=http://m-s-j.net/dagnarf/modded-libs.tar.gz]here[/url].
Stock CWM zip (Stock Kernel and Libraries) Available here
CWM Flashing Instructions:
CWM Install Instructions said:
1.) Install CWM from http://forum.xda-developers.com/showthread.php?t=1517134
2.) Copy the cwm zip to your /sdcard/
2.) Reboot into CWM either by issuing "adb reboot recovery" from command line, or loading ROM Manager app and choosing "Reboot into recovery", or by powering the device off and holding vol up+vol down and powering on.
3.) From CWM, choose "install zip from internal sd card" then navigate to the cwm zip you copied in, select it
4.) Select "reboot system"
Click to expand...
Click to collapse
Souce code available at: https://github.com/dagnarf/sgh-i717-dagkernel
Don't forget the donate link in my sig if you find this useful
Excellent work as always!
Sent from my SGH-I717R using XDA App
You're on a roll. Thanks so much for your work!
wow so fast!
Da_G said:
So, this doubles as a root kernel (might as well keep the scripts in there since I already made 'em!)
Max speed is 1.94GHz. Max speed I've benchmarked stable at is 1.83GHz. Reboots at higher.. YMMV with voltage adjustments etc.
Stock speed on this kernel is 1566MHz, I have removed a lot of scaling overrides that Samsung added, so this should be a bit smoother than the stock kernel without OCing more than the slight default.
GPU is also OC'ed from 3d speed 266 -> 300 and 2d speed 200 -> 266.
I will be releasing a GUI soon with more advanced tweaking options for the kernel (it is compatible with existing tools like system tuner, fauxclock, setcpu, etc.)
You can find the Odin tar here, follow the flashing directions from my Root kernel here
You will need modified libraries to take full advantage of this kernel as they override speeds at times, you can find these here.
You'll have to push them over adb for now after flashing the kernel, when CWM is up I will make a CWM zip for it.
From the directory with adb and the three .so files:
Code:
adb remount
adb push libhardware_legacy.so /system/lib/
adb push librpc.so /system/lib/
adb push libandroid_runtime.so /system/lib/
adb shell chmod 0644 /system/lib/libhardware_legacy.so
adb shell chmod 0644 /system/lib/librpc.so
adb shell chmod 0644 /system/lib/libandroid_runtime.so
adb reboot
Souce code available at: https://github.com/dagnarf/sgh-i717-dagkernel
Click to expand...
Click to collapse
straight fire... phone's not even officially released and everything needed for awesomeness is available.
Da_G said:
You will need modified libraries to take full advantage of this kernel as they override speeds at times, you can find these here.
You'll have to push them over adb for now after flashing the kernel, when CWM is up I will make a CWM zip for it.
From the directory with adb and the three .so files:
Click to expand...
Click to collapse
are the .so files located in the boot.img file? Or am I missing them somewhere in the .tar file?
Thanks for all your hard work.
You are a beast man.
I havent aquired a note yet but i am curios...CIQ present? it is one of the things I failed to check for when I had one in hand
Sent from my SGH-T989 using XDA App
00mred00 said:
You are a beast man.
I havent aquired a note yet but i am curios...CIQ present? it is one of the things I failed to check for when I had one in hand
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Doesn't look like it.
Da_G said:
Don't forget the donate link in my sig if you find this useful
Click to expand...
Click to collapse
I actually haven't found this useful as I have to wait until the morning to get my phone at bestbuy but I have faith. Hopefully this gets you some more gogo juice. Thank you for your dedication!
69360830PL846881R
AllTheWay said:
are the .so files located in the boot.img file? Or am I missing them somewhere in the .tar file?
Thanks for all your hard work.
Click to expand...
Click to collapse
http://m-s-j.net/dagnarf/modded-libs.tar.gz
breakingspell said:
http://m-s-j.net/dagnarf/modded-libs.tar.gz
Click to expand...
Click to collapse
Thank you sir.
Flashed, libs pushed, and ready to roll! Woot woot! I'm so glad that i got my phone a day before most everyone else, muahahaha!
EDIT: HOLY CRAP ON A STICK. I laugh at the Engadget review that told us the Quadrant score was lower than the International model. This was at 1.83ghz, performance scaling.
I use on-demand governor, also 1.83Ghz. Hope this doesnt rape battery. Would be nice to have some static undervolting or even better - HAVS. SBC for the battery could be awesome too (am I getting greedy? lol)
How is your Quads 3900...
Posted using AT&T Samsung Galaxy Note
No love for roger's ??
Sent from my GT-I9000 using xda premium
Also no Undervolting shows on this kernel take it as its not enabled yet?
Posted using AT&T Samsung Galaxy Note
How nice, these scores are the same or better than int version most with custom roms and kernal. Good job man
Sent from my INFUSE powered by ZEUS
Nobody out there with some Rogers talent lol
So nice to see high scores with just minor adjustments. I get near 4k on quadrant now.
Seems like it charges a little quicker or is it my imagination?
Sent from my GT-I9100 using xda premium
Welcome to LunarTools
Download standalone: Link
Can find older versions here along with some other rom mods: Link
Download compatibility test script: Link
Link to script source
Link to app source
Q: What is this?
Breif explanation of LunarCmdline & LunarMenu:
LunarCmdLine: It's intended use is for getting rid of the need of a cpu control app. This script allows the end user to change kernel defaults as a boot.img for either immediate flashing or saving for later on a storage option. Can only be implemented if your kernel supports showp1984's command line options.
LunarInitd: Same as Cmdline but more universal to any kernel when paired with init.d supported roms. Be aware, even though this may be safer it may also not be quite as stable as Cmdline.
LunarMenu: This coincides with the boot.img's created from invoking LunarCmdline. It lists the boot.img's created that are found on internal storage in lunar directory. Also has the ability to flash a recovery for you. Also those rom dev's who wish to implement it later you will be able to switch your boot.img using this script.
Think of them as my implementation of TWRP's Dumlock option that works with with every recovery. AS WELL -DO NOT SET A HOTPLUG GOVERNOR WITH CMDLINE! This *might* result in a softbrick only recoverable by reflashing your rom's boot.img.
Q: Oh neat ok, ..... but how do I run them?
Using a terminal emulator app, allow superuser permissions (su then enter), then invoke either script (menu then enter or cmdline then enter).
Q: There was mention earlier about recoveries or switching boot.img's, how do I use that feature?
Place the recovery you wish to flash in the lunar folder on internal storage(Sense)/external (AOSP) in this name format "recovery<name><version of recovery>.img". You will also be prompted if you wish to create a recovery backup if you wish to use the feature. Examples: recovery_CWMTouch6.0.3.1.img or boot_Rage2.5.img
Q: Would I be able to use this with other boot.img's/kernels?
Currently, if your rom dev supports the feature.
Q: Do you plan to support XxYzZ feature?
Post some feedback. I might consider it.
Q: I have a question not listed here, what information would you need if I had an issue?
Filename of the latest boot/recovery you intended to flash & of course your patience while we work on the issue at hand.
Q: I'm a kernel/rom dev, can I use these for HTC xYzzYx device in my android project ?
This is freely distributed for use, all I ask is if you do use it refer back to this thread. If assistance is needed please PM me or post in thread. You may need to modify some values in cmdline.sh for proper implementation and will need abootimg & unzip in system/bin as part of busybox/toolbox.
Known Bugs:
If flashing a recovery, remember to rename your recovery_backup.img to proper format (recovery<name><version>.img). If you don't and attempt to flash it using the same backup filename, you will just be reflashing your current recovery. No longer a bug
Remember to reboot to recovery if it doesn't automatically.
To do or possibly implement:
zImage flashing similar to AnyKernel. Done!
Known Compatible Devices:
HTC Rezound
Credits @d.kozzer - Without your knowledge & assistance the GUI wouldn't exist
PS: REMEMBER THIS IS ALL AT YOUR OWN RISK AND PURE BETA!!!! YOU CAN POTENTIALLY SOFTBRICK BUT CAN ALSO EASILY RESTORE FROM THAT SOFTBRICK!
A quick how-to from a good friend that's been using this since release candidates:
kcirtap420 said:
Here's a quick rundown of what I came up:
LunarTools(menu only currently) Options Explained
NOTE: If you are prompted to reboot or it fails to auto-reboot please do so
and follow instruction.(auto-reboot doesn't work with sense roms)
Option 1 will give you the ability to flash saved boot.img configurations from the cmdline feature or apply those same settings via init.d , eliminating the need for a cpu or kernel modifing app.
Once selected to will be prompted to choose which boot configuration to flash/appl. If command line, reboot to recovery (auto wipes cache and dalvik) for settings to apply. If init.d a simple reboot will do.
Option 2 has the ability to flash a recovery for you, and also backup your current one!
To do this you must first place a recovery image in the lunar folder, rename it to look like this recovery"name""version" enter recovery name and version without quotes.
Once selected it will ask which recovery to flash(if it's not there make sure it's named correctly and in the lunar folder!)
It will then ask you if you would like to backup your current recovery.(this will be in the lunar folder ready to
go!) Enjoy your new recovery once it's completed! No reboot needed.
Option 3 can be used for a couple things, you can update your kernel, or flash a whole new one!
To flash a new one place kernel zip in the lunar folder. If you would like to update your current kernel, place the zimage from a kernel zip in the lunar folder.
Select either file from the list, Once it's done reboot to recovery if not done automatically ( auto wipes cache and dalvik)
Option 4 is the answer for S-on users and boot.img's, REJOICE!! This option will flash a boot.img from a ROM zip!
To do this first place the ROM zip inside the lunar folder and select it, it will continue to flash the boot.img. Once it's done
reboot to recovery and go about usual ROM flashing habits such as perform factory reset and wipe system, then install your ROM and reboot!
Enjoy your new ROM flashed without fastboot commands!
Click to expand...
Click to collapse
Please try to take any questions/bugs to this thread
http://forum.xda-developers.com/showthread.php?p=41634758
or here
http://themikmik.com/showthread.php?16096-LunarTools-ChitChat-amp-Bugs-Thread
For now, the source that's on git is for AOSP roms(place boot.img's on sdcard/lunar). Bare with me while working on getting insecured boots for AOSP to get the scripting to work properly.
Snuzzo said:
For now, the source that's on git is for AOSP roms(place boot.img's on sdcard/lunar). Bare with me while working on getting insecured boots for AOSP to get the scripting to work properly.
Click to expand...
Click to collapse
wow wait for this to be stable. cheers!
Watching
sexy
lookin sexy!
First bug found
Problem
When choosing recovery_backup<DATE>.img and today's date is the same recovery doent seem to flash.
Solution
Rename recovery_backup<DATE>.img to a proper filename. recovery_<name><version>.img and flash the file under the new filename.
Just a small bug found which I will be rectifying very VERY soon.
Nearing release as standalone flashables.
https://github.com/Snuzzo/LunarTools/commit/9bd3b14b2f6a23172da957ae893fea9f5bb0f766
For those who have been following this; do you see anything that you would like implemented?
Standalone flashables posted in the OP for download.
OK so far heroes what i got in a new menu addition...
Pulls boot.img from zip
Flashes it
Creates a recovery script which right now only flashes the zip you chose
Then auto reboots.
May need some assistance with this as it needs to wipe data cache. I probably could do this with a rm command prior to auto reboot.
Thoughts?
Sent from my Nexus 7 using Tapatalk HD
Snuzzo said:
OK so far heroes what i got in a new menu addition...
Pulls boot.img from zip
Flashes it
Creates a recovery script which right now only flashes the zip you chose
Then auto reboots.
May need some assistance with this as it needs to wipe data cache. I probably could do this with a rm command prior to auto reboot.
Thoughts?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I like the idea of it just auto booting into recovery only after flashing boot.img
Edit: or maybe have the script prompt if you want to reboot
Sent from my ADR6425LVW using xda premium
Bug: mismatched boot and rom in a backup
Solution: before using the 4th option to flash a boot.img from zip run your optional nandroid prior.
Sent from my Nexus 7 using Tapatalk HD
Test builds sent out as extensions to busybox placed in /system/bin.
So far that has been working nicely. If those testers find any softbricks today I won't be releasing.
Next to do:
write a how to even though the menus are rather straight forward.
Add implementation of auto reboot to recovery to finish flashing a zImage from a zip.
Further reduce bootsize buffer for compression of output boot.imgs.
Finalize LunarCmdline.
Write a script to test compliance.
Sent from my ADR6425LVW using Tapatalk 2
Updated OP with a v1 release. Still has some work but 99% of it is completed.
Next to do:
write a how to even though the menus are rather straight forward.
Add implementation of auto reboot to recovery to finish flashing a zImage from a zip. Done
Further reduce bootsize buffer for compression of output boot.imgs. Done
Finalize LunarCmdline.
Write a script to test compliance of other devices.
Footnotes:
1st menu option- Not completely implemented yet. Could be used if wishing to restore a backup from Amon RA/CWM, I have further plans for it
3rd menu option- Use zImage from zip if fresh flashing. Use straight zImage if updating/downdating.
DO NOT PUT INVALID CHARACTERS IN ANY REQUESTED INPUTS! This could lead to unwanted results. Please PLEASE ask questions, don't let curiosity get the best of you.
Sent from my ADR6425LVW using Tapatalk 2
Had to re-upload a fixed AOSP/SDCARD zip. It was attempting to source a file from sdcard2.
http://www.androidfilehost.com/?fid=13858035414129967316
Major thanks, this is a really simple way to make use of cmdline features. :thumbup:
Sent from my ADR6425LVW using xda premium
ezpz
Gotta say this is a very handy tool to have around. I've flashed a bunch of different roms/boot.img/zimage and its pretty simple, especially after doing it at least once.
would this finally be an app to make it noob friendly
Sent from my MIUIFIED using xda premium
live2die said:
would this finally be an app to make it noob friendly
Sent from my MIUIFIED using xda premium
Click to expand...
Click to collapse
A walk thru is in the works but its pretty straight forward
Sent from my ADR6425LVW using xda premium
Still got some minor kinks to work. Mainly on the Sense portion. Some of the ported roms are being a pain. The cmdline script runs beatifully. If you're s-off, mainly going to be interested in menu options 1 & 3. Both scripts work brilliantly with s-on and s-off alike without using fastboot.
Next to do:
write a how to even though the menus are rather straight forward.
Clean up some of the script to make it more efficient.
Create a boot.img to command line bootimg.cfg converter.
Add implementation of auto reboot to recovery to finish flashing a zImage from a zip. Done
Further reduce bootsize buffer for compression of output boot.imgs. Done
Finalize LunarCmdline. Done
Write a script to test compliance of other devices. Done
PLEASE READ NEW FLASHING INSTRUCTIONS
Disclaimer:
I am not responsible for any bricks. By flashing this you understand that no one involved with the making of this Rom is responsible for a brick. However, if two nations go to war, that's okay, because they will destroy themselves and their people will worship me, THE BUTTAHLORD OF BUTTERNOOBIA!!!
I mean uhh... No, very bad thing, no countries should not go to war *cough* destroy yourselves *cough*
PLEASE READ ENTIRE THREAD BEFORE FLASHING, D/Ls and Changelog in 2nd Post
Okay past the joking, this is a stock, rooted KitKat ROM for the ZTE ZMAX. The deodexed version would not boot, so this is odexed. However, this version is free of any King Related apps and I've also removed the little bit of crapware in the device.
FEATURES:
Removal of All King Related Apps
Pre-Rooted
Clear of Bloatware
Added Xposed
Added SuperSU
Removed crappy ZTE/Metro/TMO apps
Overall Clean experience
HOW TO FLASH (NEW INSTRUCTIONS):
1. Place ZIP on SD Card
2. Reboot Into TWRP
3. NANDROID (DO NOT SKIP THIS FOR YOUR SAKE)
4. Don't factory reset the normal way, go to wipe > advanced wipe and click "dalvik cache", "data", "cache" and "system". If you don't, you run the risk of getting an updater-script error (not from the zip, it's a bug in some TWRP builds).
5. New Step: Reboot recovery (in the recovery menu). It will ask if you want to install su, press do not install.
5. Flash the ROM
6. Reboot and rep Butternoob!
BUGS:
Free and clear, you tell me!
ADDITIONAL INFORMATION:
Butternoob has been confirmed to work on all variants of the ZTE ZMAX by at least two people on each variant. THIS IS NOT SUPERBUTTER! For those that don't know, Superbutter will be a heavily modified custom rom. Butternoob was designed to be a stock, clean experience with solid performance. I may add tweaks, but you won't find a lot beyond the stock experience.
CREDITS:
-XDA User Mazer.One for the Bootanimation. I made some edits to his and don't take credit for the original work.
-JCase for helping us get root
-Hroark13 for helping me fix the wifi issue in the updater-script
-ZTE Because I have to... They are banished from ButterNoobia though...
-Masterchief87 for the 4.4.4 base and boot.img
ENJOY, REPORT BUGS, FEEL FREE TO USE AS A BASE AND GIVE PROPER CREDITS!
People have asked what my PayPal email is for donations, it is [email protected] . Never required but always appreciated, I'll give 100% regardless
Changelog:
V2:
-Updated to Android 4.4.4 base
-Band 12 Ready
-Replaced Google Launcher with Apex
--Advice on Apex: Go into menu > apex settings > drawer settings > drawer animation > circle to enable Lollipop-style animation for the drawer opening!
-Fixed SuperUser (All binaries updated)
-Fixed Gapps Force Closes
- New Wallpaper, taste of the SuperButter
-All bugs are squashed
V1:
-Initial Release
-Android 4.4.2
-Removed T-Mobile Apps
-Removed ZTE Apps (i.e. music, file manager, etc.)
DOWNLOAD:
BUTTERNOOB Stock 4.4.4 v2.0
md5: E44F1F84B47D3C4401DA522D0A7494F5
BUTTERNOOB Stock 4.4.2 v1.0
md5: 092cee0504d07fa4decde02d2206a2b7
Mine again
Cricket Zte Z987
Will this work on Cricket ZTE Z987 model
How to enable VOLTE on this rom?
work
will this work on ZMAXX Z958 ?
kas hif said:
will this work on zmaxx z958 ?
Click to expand...
Click to collapse
no. Don't try it. Unless you want to buy another phone.
Having an odd issue with LTE. When I call with LTE enabled, it tries to force the call through VOLTE, rather than handing off to a 4g (or whatever) local band. The call, of course, fails with no audio in or out; is this a known issue, is there a workaround, do I need to re-flash, or is this something weird that nobody's heard about before?
Does this work on Grand X Max + Z987?
Sent from my Z987 using Xparent Blue Tapatalk 2
Zmax Z970 RamDisk Boot.img packing problem
Hi,
Im attempting to repack the ram-disk image for my boot img on my ZTE Zmax z970 running the BN 2.0-oxed ROM. I was trying to use gzip with mkbootimg and it is not working, im assuming due to the fact that my newly repacked ram-disk cpio compressed file was not the same size as the original making the phone fail to boot when the boot.img was sent back to the boot block. My pc is running Ubuntu 14.04-32 bit. I know that the unpack-bootimg and mkbootimg scripts are working correctly because when i repack an unchanged boot.img-ramdisk.cpio.gz file (unpack the img and recreate the boot.img file) and re-upload it to the boot block, the phone boots correctly so I know that my procedures outside of the ram-disk cpio file are correct. My question is, How can I find out how much padding i need on the ram-disk file, where the padding should go, and how to apply the padding to get the file the correct size so that it will work as intended? Any help you can give me would be greatly appreciated.
P.S. I only unpackaged the boot image to change one entry in the ramdisk to the default.prop file. If there is a way to open the compressed cpio file with an archive manager and could update the file once i make my change. that would work as well. I can open the gz file with the archive manager but can not open the cpio folder contained inside.
Thanks,
Much appreciation.....f20062e
I followed your directions. Surprisingly it was super easy! Thanks!!!!!
Does this work on 6.0.1 Zmax Pro Tmobile?
link
Need link to root the z981 and link for twrp to install the recovery image. Thanks all for the hard work this excellent community pours out on a daily basis!
Hi there! I just got this flashed, and I need to know if it's safe to do an OTA update over your ROM.
Thanks a ton!
ZTE 982
Hi there good morning I have a big question, I have the ZTE z982 from MetroPCS I went ahead and rooted and installed TWRP on it. Now I was having some issues trying to flash a custom rom Slimrom to be exact (https://forum.xda-developers.com/zte-zmax/development/slimrom-5-0-2-t3161888) but I kept getting errors about legacy property? So something along those lines. Well I then read somewhere that it could be because of TWRP being outdated. I took it upon myself to look and find an .IMG witch I then flashed and now am stuck with a sorta bootloop flashes on but the screen goes black. Any suggestions? I would really appreciate it.
how did you get past fastboot. my z982 cant find device there?
soLo1Blue said:
Hi there good morning I have a big question, I have the ZTE z982 from MetroPCS I went ahead and rooted and installed TWRP on it. Now I was having some issues trying to flash a custom rom Slimrom to be exact (https://forum.xda-developers.com/zte-zmax/development/slimrom-5-0-2-t3161888) but I kept getting errors about legacy property? So something along those lines. Well I then read somewhere that it could be because of TWRP being outdated. I took it upon myself to look and find an .IMG witch I then flashed and now am stuck with a sorta bootloop flashes on but the screen goes black. Any suggestions? I would really appreciate it.
Click to expand...
Click to collapse
No matter what I do I cannot get this vile little phone to root. It is located in adb but fastboot just isnt there or doesnt' want to find it. I have tried every dang driver you can think of and still nothing in fastboot. I must know its driving me crazy. I have got to where i absolutely hate this phone!
works on z981 ??
I read the OP of A.R.I.S.E. several times, and honestly, I didn't understand it properly. And plus, I have also seen a lot of Onyx users reporting that the installation freezes in recovery. Can someone please guide me through the entire process? Thanks in advance!
meraj99 said:
I read the OP of A.R.I.S.E. several times, and honestly, I didn't understand it properly. And plus, I have also seen a lot of Onyx users reporting that the installation freezes in recovery. Can someone please guide me through the entire process? Thanks in advance!
Click to expand...
Click to collapse
I hope you are aware of flashing custom recovery and rooting your phone. Once you did that it is easy to install it.
1. Download arise from official thread. (am using magnum opus version) Make sure you download non auroma version.
2. For starters inside zip there will be a folder called our modules. Copy any of the arise_customize.prop file from that and paste it in in internal storage root directory.
3. flash the ARISE zip from recovery and you are good to go.
4. Read arise_customize.prop file for further info of adding and removing modules.
micoeyes said:
I hope you are aware of flashing custom recovery and rooting your phone. Once you did that it is easy to install it.
1. Download arise from official thread. (am using magnum opus version) Make sure you download non auroma version.
2. For starters inside zip there will be a folder called our modules. Copy any of the arise_customize.prop file from that and paste it in in internal storage root directory.
3. flash the ARISE zip from recovery and you are good to go.
4. Read arise_customize.prop file for further info of adding and removing modules.
Click to expand...
Click to collapse
which effect do you prefer?
meraj99 said:
which effect do you prefer?
Click to expand...
Click to collapse
I prefer Dolby Atmos with Dirac. Viper with ground zero preset (with my customization) nothing else. For speaker mode I use Atmos with movie preset no Viper n Dirac.
We are going to use 'Dirac' sound module extracted from OPPO smartphones by ARISE team to increase sound of any device.
We will install Dirac using 'ARISE sound system zip'
REQUIREMENTS-
*ROOT ACCESS
*Custom Recovery (TWRP RECOMMENDED)
INSTRUCTIONS-
1. Download ARISE SOUND SYSTEM ZIP and arise_customize.prop from links given below.
2. Now move "arise_customize.prop" to your internal storage.
* - optional steps - If you just want "loud sound", skip these
*If you want additional sound mods like viper4android Dolby etc, you need to open "arise_customize.prop" and write true in front of whatever MOD you want.
*I advice "mediatek" users "not to use ice mods" as it sometimes stops other modules like Viper4android and Dolby
3. Now boot your device into recovery mode (TWRP RECOMMENDED)
You don't need to wipe "anything"
Just "dirty flash" it
4. Flash the ARISE Zip
If you want to uninstall any module just scroll down and set "uninstall_module" value to "true" and flash the zip again
DOWNLOADS-
ARISE ZIP
arise_customize.prop
VIDEO TUTORIAL-
https://www.youtube.com/watch?v=iTwXjXXv6vA&t=51s
is this work on any droid version? eg: kk maybe?
majorfifth said:
is this work on any droid version? eg: kk maybe?
Click to expand...
Click to collapse
I don't see any reason why it shouldn't !
Most probably yes ,
No harm in trying
blacklisted.rock said:
I don't see any reason why it shouldn't !
Most probably yes ,
No harm in trying
Click to expand...
Click to collapse
btw, i have no luck on ridon os, dirac just stopped, yet with rr.
better trying than never
Updater process ended with error 1
amol.ml14 said:
Updater process ended with error 1
Click to expand...
Click to collapse
copy arise.customize.prop to internel directory
Same problem
majorfifth said:
btw, i have no luck on ridon os, dirac just stopped, yet with rr.
better trying than never
Click to expand...
Click to collapse
Same problem for me. Did you found solution how to increase sound on Ridon OS?