Related
SUPREME Mods v1.5
For CM9/ICS!
FEATURES:
Code:
-wifi speed increases
-changed bluetooth name to "Touchpad"
-increased quality of photos and videos
-added initial dalvik heapsize for better start up
-changed the wifi scan interval to 180 (save battery when not connected to wifi)
-kernel tweaks for less debugging/more RAM
-higher events per second for the window manager (smoother scrolling)
-overall performance boost and responsiveness increase with higher cache values
-disable sending usage data (not sure if functional but it was a property listed in the documentation)
-deeper sleep during the night hours for better battery life
-disables error checking
-faster media streaming
-changed device info to that of a SGH-T989 from Samsung so most Gameloft games are compatible to download the SD files
-270 degree rotation
-uses image dithering for faster performance
-keeps launcher in memory for faster launcher performance
-better battery management in terms of percentage and associated kernel actions
-better sqlite management for apps
-better sqlite management for apps
-faster app switching between google apps
-defragmentation of database files
-cleaner of temporary files at bootup that are no longer in use
If you want support, either post here or ask me on twitter: http://twitter.com/rohanXm
COMPATABILITY: Tested on Cyanogenmod Alpha 2 and the CM9 nightlies, may/may not work on other ROMs!
If you install this with ROMs other than CM9, then you will see many side effects in the Settings app, such as it displaying you are running CM9 when really you are running some other ROM. The build.prop is built off of the latest official nightly, 20120404.
DOWNLOAD:
Choose the DPI you want and download the respective one!
160 DPI: supreme-rohan-v1.5-160dpi.zip
120 DPI: supreme-rohan-v1.5-120dpi.zip
If you don't know what DPI is, download the 160 DPI version.
DOWNLOAD IS HERE: http://goo-inside.me/devs/rohan/tenderloin/SUPREME Mods
Current version is v1.5
Click to expand...
Click to collapse
INSTRUCTIONS
WARNING: Make a nandroid backup before downloading this!
If something goes wrong (even though it has been tested numerous times) its always good to have a backup! I am not responsible for anything that happens to your device as a result of this!
1. Download the .zip from goo-inside.me linked below
2. Reboot into ClockworkMod
3. Install zip from SD Card -> Browse for zip you just downloaded
4. Wipe Dalvik cache (in advanced menu)
4. Reboot
5. Heres the decision point: you can either end here, or you can continue on to install the V6 ICS Supercharger script. The process is a little bit involved, so if you don't want to continue, you don't have to. I reccomend you do continue though, as the Supercharger script makes a very big difference in terms of speed! For those of you who choose not to continue, thanks for installing the SUPREME Modpack! Enjoy your Touchpad! For those that want the ICS Supercharger too, continue below!
=======================================================
6. Download the latest Supercharger script from this post: http://forum.xda-developers.com/showthread.php?t=991276 to your /Download folder (the file is called "V6_SuperCharger_for_Android-update8.sh.txt") (Note: the name might change if a new release of the script comes out)
7. Continuing to install the supercharger script... open up a file manager and rename the file to get rid of the .txt extension (so that it becomes a .sh extension)
8. Open up the app called Terminal Emulator on your Touchpad. If its not already installed (it should have come with CM9) then just install it from the market.
7. In the Terminal, type the following.
Code:
su
Then accept the Superuser request that opens up.
8. Then type:
Code:
sh /Download/V6_SuperCharger_for_Android-update8.sh
(Note: the name might change if a new release of the script comes out)
9. The screen will display some text as the script loads up. Be patient and wait.
10. After loading, it will come to a thing where it detects what launcher you are running. Press the enter key to confirm your launcher.
11. The script will do some more stuff and then ask for what type of scrolling you want. Type in "1" without quotes to confirm you want fast scrolling to make the install process quicker and then press enter.
12. It will do some more stuff and then ask about integration. Type "y" without quotes confirming you want integration and then press enter.
13. It will do some more stuff and then ask about animations. Type "y" without quotes confirming you want to disable the animation and then press enter.
14. It will do some more stuff and then ask about what type of Supercharger you want. Type "9" without quotes confirming you want the highest and most aggressive tweaks (they work the best for the Touchpad) and then press enter.
15. The script will finish up and then ask if you want to super clean your system. Type "y" without quotes and then press enter. Your system will reboot.
16. Go to this link: http://android.mimic.ca/
17. Upload your services.jar file from the /system/framework/ directory
18. Patch the file using the online patcher
19. Download the CWM file it gives you (the .zip). Don't worry about what it says about being for Nexus S.
20. Reboot to recovery and flash the CWM file it just gave you.
Congrats, you have the SUPREME Modpack and the ICS Supercharger scripts installed! Reboot normally and enjoy!
To update, just follow the same instructions as the install directions! You will also need to install every time you install a new ROM.
Click to expand...
Click to collapse
Changelog:
4/05: -Removed the ICS Supercharger script as its creator respectfully asked for it to be removed from the package. You may still install it separately though using the instructions I posted though.
-Cleaned up the init.d file thanks to tweaks made by archrival
4/1: -Includes the ICS Supercharger Script from zepplinrox! Original thread is here: http://forum.xda-dev...44#post16635544
-Cleaned up the init.d tweak file and removed conflicting code
-Updated the build.prop to the latest official nightly
-Added database defragmentation
-Added removal of temporary system files at bootup
3/10: -MANY new tweaks!
-Fixed some wifi issues due to some unruly init.d tweaks
-better sqlite management for apps
-faster app switching between google apps
3/3: -Added an init.d tweak file!
-270 degree rotation
-uses image dithering for faster performance
-keeps launcher in memory for faster launcher performance
-attempts to always keep the home button on
-better battery management in terms of percentage and associated kernel actions
-kernel tweaks for less debugging/more RAM
2/27: -Added comments to build.prop file so that you guys can customize it easier if you want to
-increased quality of photos and videos
-added initial dalvik heapsize for better start up
2/26: -Initial release
this sounds amazing but i am just wondering if i could edit this so it doesnt touch the dpi at all? i use 132 right now and dont want to mess with it, other then that this sounds amazing
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
slyr114 said:
this sounds amazing but i am just wondering if i could edit this so it doesnt touch the dpi at all? i use 132 right now and dont want to mess with it, other then that this sounds amazing
Click to expand...
Click to collapse
I added the build.prop text in the OP near the bottom, in a pastebin link. Copy the text from there, paste it into your build.prop, and then find the line for the density and edit that back to 132 before saving.
freaktractor said:
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
Click to expand...
Click to collapse
I don't own the game so I was not able to test it, sorry! I know this change has worked for Modern Combat 3, Asphalt, and a couple other games. I will look into making 9mm work, since this might be a problem across multiple games!
Testing now, will let you know how it goes over the next few days
apply dalingrin's 120dpi
Click to expand...
Click to collapse
Sorry for the n00b question, but how do you apply this ? By just installing the Alpha 2 or is there a standalone zip ?
JohnKoffee said:
Sorry for the n00b question, but how do you apply this ? By just installing the Alpha 2 or is there a standalone zip ?
Click to expand...
Click to collapse
Install the zip file from the link in the first post in clockwork recovery mode after you have installed Alpha 2.
I'm on Classicnerd Butta 0.1.1-v3.2 and will definitely flash this at work to test it out.
Sent from my SAMSUNG-SGH-I727 using XDA App
Im really looking forward to a smoother scrolling experience. I love my tp immensely but I've always found the very subtle studder of scrolling to be a little displeasing when it comes to scrolling in between home screens. Does this "smooth scrolling" enhancement effect web browsing scrolling?
I am definitely going to give this a shot bud, brb with thoughts and opinions. Thanks again for your work in this community.
---------- Post added at 03:05 AM ---------- Previous post was at 02:39 AM ----------
Anyone have a link to dilinger's 120dpi fix?
Please help me to fix usb storage fix
Please help me to fix usb storage fix.Because when i connecting my touchpad to computer, nothing is happening.Touchpad memory is not opening.
i tried turning off developer mod.then also same.How to fix this
please help me
thanks
bentech4u said:
Please help me to fix usb storage fix.Because when i connecting my touchpad to computer, nothing is happening.Touchpad memory is not opening.
i tried turning off developer mod.then also same.How to fix this
please help me
thanks
Click to expand...
Click to collapse
Lmao.
Plug in your device. Then Go to: settings, then click on storage on the left. then on the top right you will see 3 vertical dots, click it for more options. "USB computer connections" will be available. Select it. Then check mark the "media device (MDP)" field.
If you're using windows, ignore the driver installer error prompt. Your TP should still be visible when you go to my computer.
Push Thanks if I helped. i hope I did. >.> lol
thanks it's working now.
freaktractor said:
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
Click to expand...
Click to collapse
its the dpi change to 160 9mm works just fine i beat the game on my TP i use PG86100 on the build prop evo 3d
What changes did you make to make better media streaming?
I don't want to make all the changes.
Sent from my cm_tenderloin using Tapatalk
Can someone point me to dalingrin's dpi fix? Can't find it anywhere. thanks!
grukko said:
Can someone point me to dalingrin's dpi fix? Can't find it anywhere. thanks!
Click to expand...
Click to collapse
Taken from Alpha 0.6 thread on rootzwiki.
LCD Density Updates:
120: http://goo.gl/2vd7h
Revert to 160: http://goo.gl/mndEs
Click to expand...
Click to collapse
This really works! I was stuck using 160dpi on Alpha2 because 120 or 132dpi both were not smooth, they had a small skip or judder when transitioning screens. Bugged the heck out of me so I set it to 160dpi where it is smooooth.
I flash this build.prop this morning and 132 is now just as smooth! Not sure what else it fixed but it didn't break anything which is always a good thing. Me happy
Thanks Rohan!
Nice one
Changed the build.prop in notepad to 160dpi then saved over the top and just flashed, now I'm playing BackStab HD! Thank you very much!
Thanks for doing this but I have a question. In your OP, you listed:
disables error checking (may have side effects)
Does this affect the SD card error checking (fsck_msdos) that the TP does on boot, which shows up as Preparing SD card on notifications?
Btw, just a suggestion that it might be a good idea to put a line in your OP and recommend doing a nandroid backup or at least backing up of the original build prop file before flashing this. Thanks again.
Mike T
Hi guys, sorry, just got back from school. I've answered some of your questions below.
Also, just wanted to say that tonight I will be adding a whole boatload of improvements via the init.d file. I worked on it at school today for a little bit at lunch and it should bring a whole host of speed improvements and smoother aspects to CM.
@Mr.Quipster Yes, this also affects the web pages. It increases the screen's refresh rate when scrolling, thus allowing a "smoother" experience.
@ruthienu I've changed it so that StageFright, the media streaming tool in Android 2.2+ scans meta tags, as well as HTTP filesystems for media. It doesn't hurt to have these lines in there if you aren't using media streaming. It also doesn't interfere with anything else. If you want to delete it, flash the zip and delete lines 101-104 [the ones starting with media.stagefright(...)]
@webdroidmt Nope, this disables something called CheckJNI. It basically scans the system every now and then for things such as invalid variables and arrays, bad buffers, and some UTF-8 errrors. None of the errors it catches are system-threatening and disabling it frees up a substantial amount of RAM. If you do not want this to be enabled as a feature then simply flash the zip, then edit your build.prop and delete the line "ro.kernel.android.checkjni=0". And thanks for the suggestion, added a warning
** DoPa6 (AOSP - Marshmallow) ** is now available - see this post for details and downloads
Click to expand...
Click to collapse
DoPa5 v1.3 is a Lollipop ROM for Sero 7 Pro owners worldwide. It focuses on core functionality that must be built-in and relies on 3rd-party apps to provide features that can be added-on. This release also offers a version of TWRP Recovery that is compatible with all models of the S7P.
Key Features
International Support - a single ROM for all Sero 7 Pros sold worldwide (US, UK, Australia, Germany, and elsewhere)
Speed Control - speed when you need it and stock performance when you don't
OTG Charging - charge the tablet while an external device is attached to the USB port
Flexible Formatting - full support for both F2FS and EXT4 on your internal storage, and exFAT/FAT32/NTFS/F2FS/EXT4 support for external storage
Installation
First-time Users
If you're upgrading from a stock ROM (any variety), please click the "show content" button and read the instructions very carefully - they're long but your tablet's continued good health may depend on it!
STEP 1: Install TWRP or Philz Touch Recovery
Users outside the US must use the DoPa versions of these recoveries to install the ROM - neither the stock recovery nor other versions of CWM or Philz will work. Users in the US should use them just to avoid problems.
Stock Recovery
If you still have the stock recovery program you'll have to use the 'fastboot' program to install TWRP or Philz. On Windows, this requires installation of the 'ADB' USB drivers while in fastboot mode (see below). A package containing the drivers, fastboot, adb and other files can be found in the 2nd posting on the DoPa Stock ROM thread. Note: there are several batch files (*.bat) in the package - do NOT run them.
put fastboot.exe in a convenient directory, then unzip the recovery zip and put the .img file (twrp.img or philz.img) in the same directory (you won't need the other files)
unplug any USB cable, then press and hold Power+VolumeUp; the word "fastboot" should appear on the screen (nothing further will appear)
plug the USB cable from your PC into the tablet, then install the driver (open Device Manager, right click on "Other Devices->Fastboot", then select "Update Driver Software")
after installing the driver, open a command prompt ("DOS window") and change to the directory containing the files
enter, as appropriate, fastboot flash recovery twrp.img or fastboot flash recovery philz.img
when done, force the tablet off, remove the USB cable, then reboot into recovery: Power+VolumeDown - you should see the word "recovery", then either the TWRP or Philz menu
CWM
If you have CWM installed, copy your choice of recovery zip to an SD card, insert it in the tablet, then:
remove any USB cable, then boot into recovery: Power+VolumeDown
select "Install Zip", then "Choose zip from /storage/sdcard1"
select the file, then OK the selection
when done, back out to the main menu, select "Advanced options", then "Reboot recovery"
after the initial "recovery" screen, you should see the TWRP or Philz menu
Regardless of how you install your chosen recovery, the result should be the same. If it boots OK, compatibility is assured
STEP 2: Backup
I can't emphasize this enough: you must make a backup of your existing ROM. If something goes wrong, there's no way to get your device working again other than to restore it using the backup you've made. There's also another reason to do a backup: before installing the new ROM, you will have to reformat your /data partition. This will wipe out your apps, your settings, and most importantly, all the music/photos/etc stored on your "internal SDcard". These last items can be restored if you follow the instructions below:
You must do your backup onto a real SD card that you can remove because your "internal SDcard" will be erased in the next step. In fact, it wouldn't be a bad idea to do two backups (preferably to different cards) just in case one is faulty.
using Philz, select "Backup and Restore", then "Backup to /storage/sdcard1" -if there's enough space on the card, the backup will start without any further prompt;
using TWRP, select "Backup", then tap "Storage" (halfway down the screen) and ensure that "sdcard" is selected; on the previous screen, swipe the slider to start the backup;
it could take anywhere from 3 to 15+ minutes depending on the amount of data and the speed of your card
if needed, you can enable compression to create a smaller backup: for TWRP, you can check "Enable compression" on its main backup screen; for Philz, select "Misc Nandroid Settings -> Default Backup Format -> tar + gzip", then on the previous menu, tap on "Compression" to set the appropriate level
STEP 3: Install the DoPa5 ROM
Before you begin, you may want to download a Google Apps ("Gapps") package that you can install after the ROM. See the TK Gapps thread for details. I recommend the "Nano Modular" package which gives you the basics - you can always upgrade later. Put your Gapps package along with the ROM zip on an SD card and insert it into the tablet - you can use the same card you're using for your backups.
using TWRP, select "Wipe", then "Format data"; on the next screen type "yes" to confirm you want to proceed;
using Philz, select "Wipe and Format Options", then "Custom Format Options"; next select "format /data and /data/media (/sdcard)" (the 8th item), then OK your choice;
return to the main menu
using TWRP, select "Install"; at the top it should show "Storage: sdcard" - if not, tap there and change the setting
using Philz, select "Install Zip -> Choose zip from /storage/sdcard1"
select sero7pro-aosp511-dopa5-v1.3.zip, then OK your choice - the install process should take about 40-60 seconds
next, install your Gapps package
return to the main menu, select "Reboot" then "System" if using TWRP, or "Reboot System Now" for Philz, then hold your breath for the next 3-4 minutes
the Hisense screen should be up for 30 seconds, followed by the DoPa boot animation for another 3 minutes
If the boot animation is still running after 5+ minutes, force the tablet off, then reboot. If that doesn't fix it, try formatting /data again. If it still doesn't work, restore your tablet from your backup ("Backup and Restore -> Restore from /storage/sdcard1"), then post a message here. If everything works out as hoped for, re-read the first posting in this thread for details on some of the features (and problems) of this ROM.
Upgrades
UK, AU, and DE users must use the DoPa versions of TWRP or Philz Touch to install the ROM because they are the only ones compatible with your tablet. US users can use any SELinux-enabled version of CWM, Philz, or TWRP.
from DoPa5 AOSP Lollipop ROMs - no need to wipe or format anything!
from DoPa AOSP Kitkat ROMs (v1.0-v2.7) - a clean install is recommended but not required
from pre-Kitkat (v4.4.x) or any CM-based ROMs - wipe your /data partition before installing to avoid unnecessary problems.
install sero7pro-aosp511-dopa5-v1.3.zip
- the installer will wipe (but NOT format) /cache and dalvik-cache for you
install your preferred Gapps package
- upgraders: this is required to prevent your downloaded Google apps from crashing
optionally, install the Nexus7 spoof (sero7pro-nexus7spoof-dopa5-v1.3.zip)
reboot (ignore any "fix root" prompt - it's incorrect)
f2fs / ext4 Migration
This DoPa ROM gives you the flexibility to format any of your built-in partitions using either the f2fs or ext4 file systems.
As part of your install - or at any time - you can switch formats without losing any data. Click "show content" for instructions.
If you haven't already installed TWRP or Philz Touch Recovery, please do so first.
TWRP
make a backup to your external SD card
select Wipe then Advanced Wipe
select the partition to reformat, then tap Repair or Change File System
on the next screen, tap Change File System, then F2FS (or EXT4 to restore the default file system)
swipe the slider below to start formatting
when done, use the Restore option on the main screen to restore the contents of the partitions you reformatted
Philz
make a nandroid backup to your external SD card
select Wipe and Format Options, then Custom Format Options
select toggle f2fs <-> ext4 migration
- be sure there's a confirmation message at the bottom of the screen
select each partition you want to convert or wipe, then select the format and OK your choice
Important: to convert your /data partition, you must select format /data and /data/media (/sdcard)!!!
use Custom Restore from /storage/sdcard1 to restore the contents of the partitions you reformatted
Changes since DoPa5 v1.2
Xposed and GravityBox - these staples of the DoPa KitKat ROMs are back and preinstalled to provide all the tweaks you want - and none of the ones you don't
ArchiDroid Optimizations - this version of Android was built using gcc 4.9 and is highly optimized thanks to settings provided by JustArchi. To help ensure stability, the kernel uses standard optimization levels but is better tuned to our Cortex A9 processor due to the use of linaro 4.9 (a version of gcc optimized for ARM processors).
No Odex-ing - odex-ing has been abandoned because Xposed recompiles all apps, making the .odex files redundant. There should now be enough space on the /system partition to install the TK-Gapps Micro package.
Adaptive Brightness - a longstanding bug that could cause the screen to go black has been fixed. Overall brightness levels have been adjusted to provide greater dynamic range in low lighting conditions.
Notes
Xposed - having the Xposed framework installed shouldn't cause any issues, but if you wish to remove it you can do so using the xposed-uninstaller available in the Xposed XDA thread. The Xposed Installer and GravityBox apps will remain but will be inactive - you can use a root-enabled filemanager to remove them if you wish.
Encryption - if you wish to encrypt your /data partition, you must first use Philz Recovery to format it. Using TWRP to format may cause the partition to become un-decrytable, resulting in the complete loss of all your data. This is NOT an issue if you don't plan to use encryption.
WiFi Display - end a WiFi Display session from your television, not the tablet; doing so from the tablet may cause it to lock up. Chromecast is reportedly not subject to this issue.
USB Audio - booting up with a USB audio device attached may result in a bootloop.
Gapps - due to limited space on the /system partition, the TK Gapps's "Mini Modular" and larger packages will not install. I suggest using the "Nano" package, then downloading those apps you really want from PlayStore.
Credits
ziddey
randomblame
davepmer
the CM team
Downloads
sero7pro-aosp511-dopa5-v1.3.zip the full ROM
sero7pro-nexus7spoof-dopa-v1.3.zip identify tablet as a Nexus7 to (possibly) show more apps in PlayStore
sero7pro-twrp287-dopa5-v1.3.zip a customized version of TWRP Recovery v2.8.7 usable on all versions of the Sero 7 Pro
sero7pro-philz6.58.0-dopa-v2.7.zip the final version of Philz Touch CWM-based Recovery v6.58.0 compatible with all models of the Sero 7 Pro
TK Gapps an XDA thread with links to various Gapps packages
sero7pro-format-thirdparty.zip - only needed if you are downgrading from DoPa6 (Marshmallow) to a previous version (i.e. this one)
GPL Notice: the source code for this kernel is available at https://github.com/dolorespark/android_kernel_hisense_m470bsa on the 'master' branch.
XDA:DevDB Information
Sero 7 Pro (US/UK/AU/DE) - DoPa5 AOSP, ROM for the Android General
Contributors
dolorespark
Source Code: https://github.com/dolorespark
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: v1.3
Stable Release Date: 2015-09-26
Created 2015-01-28
Last Updated 2016-01-02
Reserved
Thx for all your hard work
on these tablet
Thx
ok, so I have a question or several as I remember them...
I noticed in Beta 4 that we were (or at least I was) suffering from the well documented play movies bug that was afflicting a number of 2013 Nexus 7 models.
Has this been fixed yet?
If not, is there a workaround?
If so, what is it?
I also noticed some performance and stability issues when using the performance tab along with apps like 3c Toolbox and System Tuner. Unfortunately, I did not see a way to use performance tab to overclock the gpu and leave the cpu clock stock so that I could tweak the system through the aforementioned apps.
Also, can the cpu be overclocked beyond 1.5 Ghz?
If so, is this already enabled, or is there some magic involved?
I really liked the beta 4 (beta r3) Rom and the way it looked, felt, and ran.
I found it to be better at managing free memory than kitkat in that I had at least 50% more free ram than Kitkat. I believe this contributed to some of the performance increase. But I had a hard time with the Google Play Movies bug. And some people were saying it was a general problem within the os's video subsystem.
Legend, keep up the great work
Excellent work! Looking forward to this!
Sent from my Nexus 7 using XDA Free mobile app
alpurl said:
I noticed in Beta 4 that we were (or at least I was) suffering from the well documented play movies bug that was afflicting a number of 2013 Nexus 7 models. Has this been fixed yet?
Click to expand...
Click to collapse
I'm sorry I didn't know about this until you mentioned it. I'm too poor/cheap to buy stuff from Google Play Movies, so I'd never have learned about this on my own. Fortunately this was my day off, so I was able to spend the afternoon chasing down this bug. Here's the fix - install it from Recovery:
sero7pro-video-drm-fix-dopa5-v1.0.zip
I'll repackage the main ROM in the near future to include this fix, but first I want to investigate a few possible problems I noticed while getting this fixed.
I also noticed some performance and stability issues when using the performance tab along with apps like 3c Toolbox and System Tuner. Unfortunately, I did not see a way to use performance tab to overclock the gpu and leave the cpu clock stock so that I could tweak the system through the aforementioned apps.
Click to expand...
Click to collapse
Every time you display the Performance page, it will restore all parameters to the values you set previously. If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off. If neither of the apps you mention knows how to set the GPU speed, you can do so temporarily from a terminal or permanently from an init.d script like so:
Code:
echo -n 1250 > /sys/kernel/tegra_cap/core_cap_level # "1200" is 448mhz - "1250" is 520mhz
echo -n 1 > /sys/kernel/tegra_cap/core_cap_state
Also, can the cpu be overclocked beyond 1.5 Ghz?
Click to expand...
Click to collapse
Nope, not without extending the kernel's DVFS table further, then recompiling. Someone had it running at 1700mhz, but I'd consider that ..umm.. ill-advised for a chip that's intended to run at 1200-1300mhz.
Loving the first build. Very silky smooth speed and pretty stable as well as far as Lollipop is concerned at this point. As far as themes are concerned I haven't had too many issues using them on the current CM12 nightly for the Sero 7 Pro despite the DPI difference. Can't wait to see where this goes from here. Thanks for all the hard work! :highfive:
dolorespark said:
Nope, not without extending the kernel's DVFS table further, then recompiling. Someone had it running at 1700mhz, but I'd consider that ..umm.. ill-advised for a chip that's intended to run at 1200-1300mhz.
Click to expand...
Click to collapse
Well, on nVidia's page it recommend a maximum of 1.6 GHz, so 1.7 is not too much of an overboard if Hisense had built these units well enough. However, even with 1.5 GHz the chips is already running uncomfortably hot so it would be wise to back off from any higher clock. I do however think that the GPU of this tablet is a lacking a bit of oomph (ironically), is it possible to raise the clocks of the GPU beyond 520MHz? (granted that there would be a possibility of artifacts )
dolorespark said:
I'm sorry I didn't know about this until you mentioned it. I'm too poor/cheap to buy stuff from Google Play Movies, so I'd never have learned about this on my own. Fortunately this was my day off, so I was able to spend the afternoon chasing down this bug.
Click to expand...
Click to collapse
Being under that magic number of 10 posts, I couldn't post this in that main thread, and when I tried to post in the q&a thread where "reply" sent me, the forums bot catcher tripped me up.
Thanks, that worked like a charm.
Every time you display the Performance page, it will restore all parameters to the values you set previously. If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off.
Click to expand...
Click to collapse
I did, and had stability. Just didn't know about just gpu o/c.
If neither of the apps you mention knows how to set the GPU speed, you can do so temporarily from a terminal or permanently from an init.d script like so:
Code:
echo -n 1250 > /sys/kernel/tegra_cap/core_cap_level # "1200" is 448mhz - "1250" is 520mhz
echo -n 1 > /sys/kernel/tegra_cap/core_cap_state
Click to expand...
Click to collapse
To my knowledge, they don't, or at least I haven't figured that part out yet. Haven't figured it out in trickster mod either. I'll try the code. I only remember seeing one init.d file, does it matter where in that file I add the code?
Yeungers said:
on nVidia's page it recommend a maximum of 1.6 GHz
Click to expand...
Click to collapse
The Tegra3 is a family of SoCs with models designed for mobile, automotive, and embedded use. Ours is the low-power mobile version. Some variants do have higher maximum clock speeds but they use more power at every frequency step than ours.
I do however think that the GPU of this tablet is a lacking a bit of oomph (ironically), is it possible to raise the clocks of the GPU beyond 520MHz?
Click to expand...
Click to collapse
Possibly. The original overclock patch just upped the GPU speed to 520mhz without increasing the voltage any - and that seemed to work. When I rewrote the o/c code, I increased the voltage when running at 520mhz for what I considered solid reasons, Since it now has more power, I suspect I could up the speed somewhat without causing problems. However, even at a higher speed, it's still going to be an also-ran in today's market.
alpurl said:
dolorespark said:
If 'Speed Control' is enabled, it will reset the CPU & GPU speeds, overriding values set by some other app. Your best bet is to turn it off.
Click to expand...
Click to collapse
I did, and had stability. Just didn't know about just gpu o/c.
Click to expand...
Click to collapse
Having some other app set the CPU or GPU speeds isn't going to make it any more or less stable than having the built-in facility do it.
Be aware that if you're trying to use one of these apps to set the Interactive Governor's parameters, you're wasting your time. Not only does our Interactive Governor NOT work like you'd think - and not work like other implementations - it's totally ineffective. Every time the kernel brings another core online, it kicks all cores to the maximum allowed speed, totally sabotaging the governor's efforts. If you use Trickster to track the time at each speed, you'll see that the bulk of the time is spent either at very low speed or max speed, with all the intermediate speeds hardly used at all.
I only remember seeing one init.d file, does it matter where in that file I add the code?
Click to expand...
Click to collapse
Create a new file named, f'rinstance. "02gpuspeed". Put "#!/system/bin/sh" on the first line, then the code I provided on the following lines. The files will be executed in alpha-numeric order: 00banner, 02gpuspeed, 99SuperSUDaemon. Be sure to set its permissions to '755' so it is executable.
I pretty well figured that would be the case, but...
Based on my somewhat limited understanding ,If you have a utility in the Rom trying to manage the cpu speeds, and an app trying to do the same with me "choosing" to use the performance governor, conflicts are bound tio arise. Based on my pc understanding, conflict equals poor performance and instability.
And it was honestly one where I was using performance settings for the gpu, and then one of the other apps for the cpu.
So, I found that if I simply turned off the performance settings and lived with the lower gpu clock, my system ran stable. So I was asking about how to get the higher gpu clock without using the cpu overclock portion of the performance tab.
You pretty well answered that, and I thank you.
Now, do I need to include the bit in the code at the end of the first line where it says 1200 is 448, and 1250 is 520?
Also, I don't understand setting permissions to 755. I understand setting read, write, own, etc, but not 755, if that's the case, then what app do I use for that? I created the file as a blank text document on my tablet directly and input the code there, then rebooted. Or did I screw the pooch on that one?
Sadly, I know nothing about the individual governor settings within each governor configuration. Therefore, I figure that the wisest and safest course of action is to leave it alone. It's easier and safer to work with the stuff I DO know until I can get feedback and advice from someone who DOES know.
I realize that some of this may seem stupid to you, but it's the only way I know to learn.
I will make another post later when I have more time to comment on some other things I keep seeing and would like to know what to do there.
alpurl said:
If you have a utility in the Rom trying to manage the cpu speeds, and an app trying to do the same with me "choosing" to use the performance governor, conflicts are bound tio arise.
Click to expand...
Click to collapse
The CPU/GPU settings on the Performance page are set-and-forget values. They simply set the maximum speeds once bootup is done, and again when you display that page. They don't monitor anything - the CPU governor does that, and it is constrained by these settings. The corresponding settings in the other apps you've tried operate the same way.
You should be aware that the "performance" governor is really no governor at all. It simply sets the processor to the maximum permitted speed and never changes it. On the whole, this governor generates more heat than performance.
I found that if I simply turned off the performance settings and lived with the lower gpu clock, my system ran stable.
Click to expand...
Click to collapse
This strongly suggests that your device really can't handle the higher speed - at least when the CPU is running full-bore at all times. You may want to search for the postings in some of the early S7P threads where people described attaching copper foil to the SoC to dissipate excess heat.
do I need to include the bit in the code at the end of the first line where it says 1200 is 448, and 1250 is 520? Also, I don't understand setting permissions to 755.
Click to expand...
Click to collapse
Anything after a '#' in a shell script is a comment. As to '755', that's "read/write/execute" for the owner, and "read/execute" for the group and other users. Do a search for the 'chmod' command for more details on setting and interpreting Unix permissions.
Ok, that's fair enough.
Occasionally, I'll boot and get an error that the process called system is not responding and then it wants to know if I want to wait, or close it. It will do this every subsequent boot until I wipe cache and Dalvik (because I end up doing both out of habit) from recovery and then all is well again for several boot cycles where we start up again.
What am I missing here?
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on. I will be spending some time this week to figure this all out.
Sent from my XT1034
kenundrem said:
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on. I will be spending some time this week to figure this all out.
Click to expand...
Click to collapse
Since I'm not familiar with RRO theming how is this different from the themes released for say CM12 and the like?
kenundrem said:
Are we free to discuss RRO theming for the S7P in this thread for now? I have been following BitSyko Development for a week or so and opted into the Layers beta and so on.
Click to expand...
Click to collapse
AngryManMLS said:
Since I'm not familiar with RRO theming how is this different from the themes released for say CM12 and the like?
Click to expand...
Click to collapse
Of course you're welcome to discuss RRO - especially since it gives me an opening to throw in my 2 cents
Runtime Resource Overlays provides a way to override and/or replace the "resources" (icons, layouts, colors, strings, and fixed values) that are built into an .apk file. Since the resources used by Android itself are packaged into an .apk, you can modify the OS as well as individual applications.
RRO has been around for a long time but no one other than Sony ever used it. BitSyko's greatest contribution has been to make people aware that it's a superior way to do theming which is already built into the OS and is fairly easy to use. Unlike CM's theme engine, no custom code is required.
Beyond that, their contribution is somewhat less revolutionary than their many admirers seem to think. Their efforts are directed primarily at ease of use. The Layers app is essentially a file manager that makes copying themes into place a bit easier. What the app does you can do yourself using ESFileExplorer or ADB (though without some niceties they've added).
Their tweaks to the OS are designed to make life a bit easier for themers by changing hard-coded color values into "symbolic references". In other words, rather than specifying the color for each checkbox, you say each one should be the "checkbox_color", then define what that means somewhere else. That way, rather than having to modify the color of many different checkboxes, you change the definition of "checkbox_color" once and they all become that color.
Now, as to what all this means to the Sero 7 Pro and the DoPa5 v1.0 ROM... I delayed the ROM's release for several days until I could get their patches in place and tested, so this facility is in there and ready for use. The problem is that none of the themes I've seen really support the S7P. Any color changes a theme makes will show up just fine (I'm using someone's orange theme currently). However, all the icons are targeted at higher resolution screens than ours, so the OS ignores them and uses the same ones it has always used. If you can find themes for the Nexus 7, or some of the older Asus or HP tablets that also have a 1280*800 screen (213dpi), they should work just fine.
FYI... if you want to install a theme without using Layers, create an 'overlay' directory in '/system/vendor' (i.e. '/system/vendor/overlay'). Next, get some theme packages from this thread and unzip them. Select the .apk files you want, copy them into the 'overlay' directory, then reboot. If you don't like the result, delete them and reboot again.
Perfect explanation @dolorespark on RRO. I'm hoping eventually some kind of dark holo blue theme is made for RRO as all I really need is the color scheme.
AngryManMLS said:
Perfect explanation @dolorespark on RRO. I'm hoping eventually some kind of dark holo blue theme is made for RRO as all I really need is the color scheme.
Click to expand...
Click to collapse
So you want black on holo blue aka 33b5e5? I'm going to make a white/pink themed for my daughter as its her tablet but I will see what I can do for you while I'm at it.
Sent from my XT1034 using XDA Free mobile app
kenundrem said:
So you want black on holo blue aka 33b5e5? I'm going to make a white/pink themed for my daughter as its her tablet but I will see what I can do for you while I'm at it.
Click to expand...
Click to collapse
That would be amazing if you could. Here is an example of what I mean as well.
http://forum.xda-developers.com/android/themes/theme-dark-holo-theme-v1-0-01-25-15-t3012227
ViPER|Audio™ || ViPER|Atmos™
ViPER|DD+™Stock | Sony™ | Beats™
Universal
for 5.x.x - 6.x.x.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not on Lollipop or Marshmallow?
Here is the link to my AndroidFileHost JB & KK folder:
https://www.androidfilehost.com/?w=files&flid=48267
Features:
5.x uses ViPER4Android 2.4.0.1 with its driver preinstalled
4.x uses ViPER4Android 2.3.4.0 with its Super Quality driver preinstalled
Dark Material theme
Works in Permissive and Enforcing Selinux
Works with no root as long as a Permissive kernel is installed
Installed in /system/priv-app
Advanced Linux Sound Architecture
Sony™ and Beats™ libraries and effects (No apk's or settings to look for!)
Library & Effect entries in /system/ect/audio_effects.conf, /system/vendor/etc/audio_effects.conf, /vendor/etc/audio_effects.conf, and /system/etc/htc_audio_effects.conf
Five custom audio_effects.conf files for the Sony™ Beats™ Editions
Deep Buffer removal from /system/etc/audio_policy.conf
Backup script to survive rom updates
Official ViPER Packages
ViPER|Audio™ is for those only wanting ViPER processing. There is also a Stock version that has no additional files or effects for those seeking a pure "vanilla" ViPER4Android installation.
ViPER|Atmos™ includes @worstenbrood's Dolby Atmos™ found here: http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446, fully functional in Enforcing. There is also a Stock version without the additional effects for a pure "vanilla" ViPER|Atmos™ experience.
ViPER|DD+™ includes Dolby Digital Plus™ courtesy of @aki_007 which can be found here: http://forum.xda-developers.com/android/software/audio-mod-dolby-digital-plus-universal-t3078802 and is the perfect solution for those experiencing issues with the Dolby Atmos™ app. Both are fantastic and extremely similar in sound and identical in setup. This is certainly not a downgraded ViPER|Atmos™ but just another available option for the user. Dolby Digital Plus™ requires a Permissive Selinux environment so packages including DD+™ also include a Permissive script during the installation to avoid any issues after the installation. There is also a stock version with no additional effects.
These three versions provide the ultimate compatibility across all devices in your quest for the ultimate experience in seamless sound enhancement.
!! Versions not described above are just for fun !!
!! Make sure /system has 50mb+ of available free space !!
!! If it is necessary for you to run Cyanogenmod 13 with its own SuperUser you must change Selinux from Enforcing Strict to Permissive as SuperSU is required for processing in Enforcing !!
Installation:
Boot to recovery
Wipe > Advanced > Dalvik Cache, Cache
Install > ViPER|Audio™ OR ViPER|Atmos™ OR ViPER|DD+™
Reboot
!! Be sure to enable Storage Permissions for ViPER4Android through its App Info page !!
Open v4a
Menu > Show Notification (block if desired by long pressing notification)
Menu > UI Setting > Expert
Menu > Save Effect Profile > New Effect Profile > "Stock" (this will help you find your working v4a directory)
Begin playing audio file
Open v4a
Uncheck Enable v4a
Check Enable v4a
If you experience problems with the normal installation instructions, the awesome @dr.ketan has allowed me to link his Viper Fix 1.1.apk which will essentially disable all other effects from your system by eliminating their libraries from your audio_effects.conf using v4a instead. Flash this apk as a normal user app, open, reboot when prompted, boot to recovery and flash your desired ViPER package. You can find info and support as well as the apk at this link: http://forum.xda-developers.com/showpost.php?p=61858278&postcount=3079
and
http://forum.xda-developers.com/showpost.php?p=63425983&postcount=658
It is possible your /system is dirty enough to require at least a System wipe in TWRP and a dirty flash of your current rom before flashing ViPER|Audio™ if you experience any Force Closes or any other signs of an incomplete/failed installation.
!! Do NOT delete /system/priv-app/MusicFX !!
In initial testing I found that I had to move MusicFX back to get ViPER working and I haven't removed it since. I do disable it and recommend doing the same if it's not working "out of the box".
!! Audiophile™ Profile zip is NOT flashable !!
Extract both folders in zip into the following two directories:
Code:
/data/media/legacy/ViPER4Android
and
Code:
/storage/emulated/0/ViPER4Android
Uninstallation and Removal:
The best and easiest way to remove this and any other /system mod from your device is to dirty flash your rom after wiping System in TWRP. Before you begin, make sure you have a compatible rom zip on your internal storage as an OS will need to be installed. As long as you do not Factory Reset or check Data or Internal Storage, your data will be left intact but with a fresh /system partition.
Verify compatible rom zip is on device
Boot to recovery
Wipe > Advanced > System, Dalvik Cache, Cache
Mount > uncheck System
Install > current/compatible rom zip
Reboot
Audiophile™ ViPER|Audio™ Active Settings
ViPER4Android™ > Enabled
ExtremeBeats™ Perfection EQ Preset > 3.5, 4.5, 5.0, 3.5, 1.5, 1.0, 3.5, 4.5, 5.0, 3.5 (Enabled when needed)
Convolver > Enabled
Impulse Response > DFX Hip Hop Modern.irs or DFX Metal Rap Big Bass.irs
Cross Channel > 0%
Dynamic System > Enabled (Headset only, when needed)
Listening Device > Common Earphone v2 (I use Sony™ MDR-XB90EX - http://www.amazon.com/gp/aw/d/B008G...ony+xb90ex&dpPl=1&dpID=41dggsErE4L&ref=plSrch
Dynamic Bass > 14%
ViPER Bass > Enabled
Bass Mode > Natural
Bass Frequency > 40hz
Bass Boost > 10db
ViPER Clarity > Enabled
Clarity Mode > Natural
Clarity > 6db
Experience ViPER|Atmos™ & ViPER|DD+™
ViPER4Android & Dolby Atmos™ - Enforcing and Permissive Selinux
ViPER4Android & Dolby Digital Plus™ - Permissive Selinux
When combined with ViPER running my Audiophile™ profile, optimal results can be achieved using the following settings in Dolby Atmos™ or Dolby Digital Plus™:
Music profile
EQ Preset > Open (Flat to tame bass if needed)
Surround Virtualizer > Off
Dialog Enhancer > On
Volume Leveler > Off or On
The resulting sound is absolutely massive!
ViPER|Audio™ || ViPER|Atmos™ || ViPER|DD+™
Sony™ Beats™ Editions
The Xperia™ Z5 Premium Marshmallow audio system and the M7 Beats™ files shared by @androidexpert35 found here: http://forum.xda-developers.com/android/software/mod-htc-beats-audio-beats-xperience-t3281603, compliment ViPER|Audio™, ViPER|Atmos™, and ViPERDD+™ amazingly well. I was surprised how they fit in so seamlessly, adding a very welcomed and natural bass boost while retaining the Audiophile™ clarity. My favorite combination, by far.
Short List of Reference Songs Used for All Sound Profiling
Best processing when used with 16 bit 44.1 kHz FLAC sources. Sound quality degrades deviating up or down from this format. Trust me, I have DSD that play at 30mbps and more.
Nero - Satisfy https://play.google.com/music/m/T3umvfdsg6nlsbyxiq7he7r5enu?t=Satisfy_-_Nero
Born of Osiris - Exhil∆r∆te https://play.google.com/music/m/Tbkw4olkiaj4ncvcuqimh6525oe?t=Exhilarate_-_Born_Of_Osiris
Bar 9 - The Beginning https://play.google.com/music/m/Tcdnzqm4nvitqtnxemjhb5dxwky?t=The_Beginning_VIP_Mix_-_Bar9
Stick Figure - Breathe https://play.google.com/music/m/Tf4jnzzlzx2vgqgpg6gqbckjrpe?t=Breathe_-_Stick_Figure
Tove Lo - This Time Around https://play.google.com/music/m/Tnwlggfz6k7rxth6lkpwympov74?t=This_Time_Around_-_Tove_Lo
August Burns Red - Echoes https://play.google.com/music/m/Txboufaitol43nwfehjwylplmii?t=Echoes_-_August_Burns_Red
August Burns Red - Black Sheep https://play.google.com/music/m/Ti4zm65ym6mfeb4leax6d7t7t6a?t=Black_Sheep_-_August_Burns_Red
Zomboy - Bad Intentions https://play.google.com/music/m/Tnojluypzn2cuirhwc4bhjohzdm?t=Bad_Intentions_Original_Mix_-_Zomboy
Liquid Stranger - Nintendo https://play.google.com/music/m/Tt3ngoekwqkzyre6bm4wlolew3u?t=Rocket_Fuel_-_Liquid_Stranger
All Shall Perish - There is No Business to be Done on a Dead Planet https://play.google.com/music/m/T5uq4qmmsrnepzwcztuzk6xmj4q?t=There_Is_No_Business_to_Be_Done_on_a_Dead_Planet_-_All_Shall_Perish
Crotchduster - Mammal Sauce https://play.google.com/music/m/T3szem6dbui32ghaiy2succx3uy?t=Mammal_Sauce_-_Crotchduster
Testing EnvironmentHeadset
> Sony™ MDR-XB90EX http://www.amazon.com/MDR-XB90EX-In-Ear-Headphones-Japanese-Import/dp/B008G80FIU
Bluetooth
> Pioneer™ DEH80PRS http://www.amazon.com/gp/aw/d/B006Y...s=deh80prs&dpPl=1&dpID=41zvBwNuamL&ref=plSrch
> Focal™ Integration ISC 165 6.75" http://www.amazon.com/gp/aw/d/B0159...cal+isc165&dpPl=1&dpID=41eyRcNORfL&ref=plSrch
> Two unknown 6" subs in a ported box
> Old Kicker™ 2 channel 250 watt amplifier
That completes my service van setup where most testing takes place.
> Sony™ SRSX55 Portable Speaker http://www.amazon.com/gp/aw/d/B00TT...ny+srs+x55&dpPl=1&dpID=51sgE76lJzL&ref=plSrch
Some of your IRS files not active when loaded?
A discovery I made a long time ago that is still largely unknown:
For this to work ViPER4Android™ MUST be uninstalled from /data if applicable.
If ViPER4Android™ still shows in App Drawer after dirty flashing your rom (while you're checking for free /system space and BusyBox ) then uninstall from App Drawer or delete /data/app/com.vipercn.viper4android_v2-1.
After flashing ViPER|Atmos™ or ViPER|Audio™, setting everything up, and confirming everything is functioning, extract the ViPER zip.
Tap on the apk in the extracted location to "install an update to this built-in application."
Tap Open and dismiss the only instance of "ViPER4Android has stopped" that you will see.
ViPER is now installed in /system and /data allowing you to enjoy every IRS in your collection.
In a situation where you could really use all the settings available to other outputs while processing through Speaker tab in ViPER4Android™?Swipe over to output tab with the settings you seek to use.
Menu > Lock Effect Mode
Now, this locked output tab will be the only settings used while processing audio. Remember to unlock effect mode if this is only for certain scenarios when done.
Audio Focus causing processing issues?I haven't had an opportunity to devote enough time testing audio_policy.conf edits but here's a couple that seem to help with no processing after audio interruptions:
Open /system/etc/audio_policy.conf in text editor
Add 44100 to voice_rx
Add 48000 to a2dp
Save changes
Reboot
Do this only if you experience no processing after a notification or voice call when ViPER4Android™ was processing immediately before the audio focus.
derekr44 said:
The audio_policy.conf edits worked. One thing to note (I found out through trial and error) is that the freqs need to be listed in numerical order on those line items (not just added to the end). For example:
Code:
sampling rates 8000|16000|44100|48000
is not seen the same as
Code:
sampling rates 8000|16000|48000|44100
Click to expand...
Click to collapse
Experiencing audio disturbances while using a custom kernel? Our friend @Woody explains:
Woody said:
Back in the day, when Viper4Android started, it only worked on JellyBean 4.1 ROMs. This was when it was new and the iterations were just as fast as they are in this thread. Everything was finally figured out once Viper got to version 2.3.3.0 and then finally 2.3.4.0. Just about the same time that the final version of Viper was completed, KitKat came around with it's new experimental run time called ART. At that time, you could choose between either ART or the traditional Dalvik runtimes. But that choice came with a word of caution-"ART might not work with certain apks." At the same time, the Linux kernel was updated.
So now you have a SoundMOD that was reasonably perfected (and unfortunately abandoned as there has been no update since), a new Android OS and an updated Linux kernel that all needed to work together. Not saying that v4a was instrumental in a change of general ideology, but with so many people using it, many preferred sounds quality over battery quality. Let's not get all high and mighty on the Viper Is King train, as it was not the first to do what it does. If you've been around Android since Froyo/GB times, but more specifically the Galaxy S1/2 series, you should remember Supercurio's VoodDoo Sound Control. For the time, it blew anything away that was available and had a GUI apk that you could tweak. That was then, this is now; but really still talking in the KK days.
Since the sound mod was the greatest thing to headphones since aluminum, people wanted it to work on their custom ROMs/Kernels. In comes faux123 and his tweaks to his kernels that allowed for ramdisk injections of audio patches (generally AnyPatch kernels are what you will mostly find as it uses the "stock" ramdisk as a foundation). So if you ran a kernel during the middle 2013 to 2014, most had the Faux sound patch, as it allowed for peak sound for the device through the use of a custom kernel (this is why most kernels now days have a sound section in their .conf files or GUI). It lasted forever and is still being incorporated in custom kernels to this day (check your Kernel Thread OPs/GITs ). Since kernel devs are few and far between, they tend to either work closely together, cherry pick commits or try depart themselves from each other.
Android moves to Lollipop and ART is no longer optional, like in the previous KitKat. LP also introduced 2 kernel toolchain updates over it's lifetime. This caused kernel devs to tweak their setups and Governors. There were still the usual suspects like Interactive, On-Demand, Performance and Conservative, as well as all their derivatives. At this point sound mods were still working mainly because of the Faux sound and/or Franco patches were being included in most kernels and being built from AnyPatch kept that possible. Viper4Android worked as advertised, even after the /system folder structure had also changed).
Now comes MarshMallow. Again with another folder structure change and the adaptation of custom recoveries to be able to properly wipe them. Ever wonder why you can't find your Profile and Kernel folders when you dirty flash? I figured it out shortly after MM came out. The thing was, with the new OS, something in the kernel changed and now my trusted Interactive governor was creating popping and cracking sounds. I actually posted (should read the few posts after mine as well. They talk about Faux's sound too and my realization that On-Demand removes the popping and cracking) in this thread about it when it was under previous management by kah-el. Here are my final findings regarding using On-Demand over Interactive.
So what does this all mean? It means that if you have popping and cracking, you should switch your kernel governor to On-Demand or one of it's derivatives. Some other culprits can be if you are running a Permissive or Enforcing kernel and/or ROM. If you don't know if you are or not, open a terminal and type (without the quotes) "su" [ENTER] "setenforce" [ENTER] and see which number it puts out. 0=Permissive; 1=Enforcing. You can change this without the SELinuxpolicy changer apk by using the commands above. Some kernels, such as ElemetalX, have a radio button that you can tick at installation to have it as Enforcing or Permissive. Even though the latest zips from OP are getting more directed to being able to be used with Enforcing, it would be good for you to know what yours is. I run Permissive and will for the foreseeable future (Google it to find out why). You also need to check your gain strength and if it is set too high. Louder doesn't mean cleaner.
On-Demand isn't for everyone, but we have to find out why the Interactive governor ramps up the frequencies too fast and the audio portion of the kernel effects the output of Viper. This is something that a new kernel dev upstart could really make his mark in the Android custom kernel/sound mod world. *Hint*Hint* Until then, I don't mind On-Demand and SIO (I used to use Deadline but started to get RRs, though those were probably self-inflicted).
Click to expand...
Click to collapse
Feel free to share this wherever with whomever, no credit or permission needed as this is still the work of the developers below. If you feel obligated to give credit when sharing please include those below.
Thanks to @viper520 & @zhuhang for the glorious ViPER4Android™.
Thanks to @worstenbrood for the Dolby Atmos™ dap_r6.5.zip and the necessary scripts inside which I was able to edit for this Installer.
Thanks to @aki_007 for Dolby Digital Plus™, providing more options for the user and allowing me to extend the compatibility range for devices that might have issues with Dolby Atmos™
Thanks to @BSDgeek_Jake for the highest quality IRS files on XDA - http://forum.xda-developers.com/showthread.php?t=2439254
Thanks to @maximumentropy for the updated Enforcing script for systemless root.
Thanks to @androidexpert35 for the fantastic Beats™ files for the Beats™ editions
Thanks to @dr.ketan for allowing me to link to his Viper Fix apk, useful when the normal ViPER installation doesn't work for you.
Thanks to @Viper4713 for the Material v4a apk's.
Thanks to @Hitti2 for the OP imagery.
Thanks to @-decipher- for the ViPER|Audio™ banner.
Thanks to you guys for always providing feedback and never settling for anything but the best!
And my biggest thanks to these generous donators!:
@joetheshmo X 2!
@Roi007leaf X 3!
@churapa
@dingermtb
@jesssiii
@ffejy462 X 2!
@Brock Guffman
@NullyOne
@luigidk
@derekr44
@elevatorguy
@heleos
@J.Guido85
@bkkzak
@Rhonin86
@Unclecharlo
@stueycaster
@deebray36 X 3!
@GODSPD
@williwood X 2!
@meckipower
@JellyTooth
@jshamoon
Mikko L. (guest)
Many thanks guys!! :good:
Enjoy the zips attached below and provide any feedback you have.
Edit Archive
Edit*******
4.3 is now using the Super Quality Driver to correct an oversight from I don't even know when. The Power Saving Driver file size is the exact same as the Super Quality Driver so somewhere along the way, it got mixed up and placed in the ViPER packages. The MD5 for the Super Quality Driver ends in "27a5" if you want to check libv4a_fx_ics.so on your device in /system/lib/soundfx.
Edit********
4.3.1 modifies the install script to accommodate every scenario of switching from different ViPER packages. No wipes necessary and no need to update unless you are wanting to try a different package. 4.3.1 also introduces the ViPER|DD+™ Stock version with no additional Beats™ and Huawei™ files.
Edit*********
4.4 introduces the phasing out of Huawei™ as part of the official packages as I was never fully convinced of any contribution, but highly suspect its inclusion caused many issues. All 4.4 packages include complete removal of Huawei™ files in the install script so no wipes are ever necessary. I don't plan on adding any Beats™ removal lines into the script as I fear that might delete stock files on HTC devices and that will certainly cause issues and be a very irresponsible act on my part. Essentially, this means a desire to try a Stock package will require a System wipe followed by a dirty flash of your rom before flashing a Stock package, otherwise, you'll still end up with the Beats™ files.
Edit∆
4.5.1 introduces the Xperia™ Z5 libraries and effects from @jancsessz's Xperia™ Z5 port as well as a change in the supolicy script pointing to /su/bin/supolicy for the latest SuperSU systemless root for full ViPER4Android functionality with Enforcing Selinux. 4.5.1 also begins the phasing out of the Beats™ only editions to keep a manageable number of packages.
Edit∆*
4.5.2 makes minor changes to the Supolicy script to make it compatible for all SuperSU users in an Enforcing Selinux environment (Thanks @Shadowghoster!). 4.5.2 also cleans the install script in all packages by removing the former Huawei™ removal lines which should no longer be necessary at this point. Users with a fully functional 4.5.1 installation should not feel compelled to update to 4.5.2, this is for everyone else or if you're flashing ViPER again because your rom update wiped your system in the installation process. Finally, Beats™ only editions will continue for those that have incompatibility issues with the other packages.
Edit∆**
5.0 includes the latest ViPER4Android 2.4.0.1 and its driver as well as a minor tweak to the Supolicy script.
Edit∆***
5.1 brings Material Dark back to ViPER|Audio™ courtesy OS @Viper4713's themed 2.4.0.1 apk. 5.1 also no longer removes ViPER4Android's /data/app installation or /data/data (app data) thanks to @-decipher-'s thorough testing and reports.
Edit∆****
5.2 returns the official ViPER4Android apk into all ViPER packages. This makes for a better flashing experience and the Material apk's can always be easily copied over the existing official apk if desired. 5.2 also includes /system/etc/sony_effect to all Sony™ Beats™ editions. Lastly, all 5.2 packages include a Version Info text file in /system and include more removal lines in the installation script for third party v4a installs including those included in some roms.
Edit∆*****
5.2.1 removes the /system/etc/sony_effect folder introduced in 5.2. A system wipe will be required to remove this folder as deleting through my installer might delete stock files on some Sony™ devices. Alternatively, this file can be manually deleted to avoid a system wipe if desired. 5.2.1 also removes the data removal of ViPER4Android during installation.
Edit∆******
5.3 adds the following lines to /system/build.prop:
audio.deep_buffer.media=false
lpa.decode=false
tunnel.decode=false
tunnel.audiovideo.decode=false
lpa.releaselock=false
lpa.use-stagefright=false
persist.sys.media.use-awesome=1
Edit∆*******
4.6 continues work using the previous ViPER4Android 2.3.4.0 after reports of the new ViPER4Android apk being a downgrade in sound quality. This is not an unreasonable assumption given that the new apk only provides one compatible driver with no reference to its purpose being more sound quality driven or more power saving driven. I am testing this now and would have to say this is definitely the recommended version rather than 5.3 which uses the new apk. 4.6 also includes the /system/build.prop lines from 5.3 which have proven to be very beneficial to Audio Focus and curing all problems experienced with the supolicy scipt on Enforcing Selinux. Honestly, everything seems absolutely perfect and I can't see anything improving this build other than sound enhancements that are later found. :good:
Edit∆********
4.7.1/5.4 introduces Advanced Linux Sound Architecture into all packages. Dark Material returns with an available Light Material switcher flashable in recovery.
Click to expand...
Click to collapse
Edit∆*********
4.8/5.5 are rebased on Xperia™ Z5 Premium Marshmallow's audio system.
Using the entire Z5 Premium library with a custom audio_effects.conf incorporating only what is included in the mod.
Five custom audio_effects.conf locations and correct naming schemes which provide the most compatibility yet.
Sony Effect build.prop section.
Updating only requires the deletion of existing ViPER|Audio™ and Sony Effect build.prop lines if present to prevent duplicate entries.
XDA:DevDB Information
ViPER|Audio || ViPER|Atmos || ViPER|DD+
Contributors
guitardedhero
Version Information
Status: Stable
Current Stable Version: 4.8/5.5
Stable Release Date: 2016-03-15
Created 2016-03-04
Last Updated 2016-03-15
Click to expand...
Click to collapse
Hi man, great mod. Xan you please assist me with something? I have installed your mod together with extrememusic mod. Everything works great, but only with poweramp. Samsung player and soundcloud doesn't use neither of the mods. I can't even see the graphical equalizer reacting to music in dolby atmos. I have tried previously editing the audio profile in a2dp but that didn't help with cloudsound. By the way, i instamled the Huawei version. Thanks in advance
Sent from my SM-N9200 using Tapatalk
Kyrillos said:
Hi man, great mod. Xan you please assist me with something? I have installed your mod together with extrememusic mod. Everything works great, but only with poweramp. Samsung player and soundcloud doesn't use neither of the mods. I can't even see the graphical equalizer reacting to music in dolby atmos. I have tried previously editing the audio profile in a2dp but that didn't help with cloudsound. By the way, i instamled the Huawei version. Thanks in advance
Sent from my SM-N9200 using Tapatalk
Click to expand...
Click to collapse
Thank you!
I recommend wiping System in TWRP, followed by dirty flashing your rom, and then trying just my mod. It's almost impossible for me to properly assist you with so many additional files provided by the XTREMEMusic mod. I'd like to take a look at your audio_effects.conf file though if it's not too much trouble.
guitardedhero said:
Thank you!
I recommend wiping System in TWRP, followed by dirty flashing your rom, and then trying just my mod. It's almost impossible for me to properly assist you with so many additional files provided by the XTREMEMusic mod. I'd like to take a look at your audio_effects.conf file though if it's not too much trouble.
Click to expand...
Click to collapse
Thanks, you are my last hope. Actually I think the issue is with the audio_policy.conf I have tried policy from others, which had no issues with the mods. One of the files solved the issue with the music, however I ended up having issues with the sound during calls. Please find a zip of my policy.
To sum up my issues are:
1. Everything works in PowerAmp
2. Samsung music player does to react to any changes in the mod neither the dolby equaliser reacts to the music played as with power amp
3. Soundcloud does not work with the mod. It starts working only when a notification sounds and only until the next track.
THANKS IN ADVANCE!!!!!
Kyrillos said:
Thanks, you are my last hope. Actually I think the issue is with the audio_policy.conf I have tried policy from others, which had no issues with the mods. One of the files solved the issue with the music, however I ended up having issues with the sound during calls. Please find a zip of my policy.
To sum up my issues are:
1. Everything works in PowerAmp
2. Samsung music player does to react to any changes in the mod neither the dolby equaliser reacts to the music played as with power amp
3. Soundcloud does not work with the mod. It starts working only when a notification sounds and only until the next track.
THANKS IN ADVANCE!!!!!
Click to expand...
Click to collapse
Lol, sorry, I just woke up and thank you for providing what I had actually meant to ask for!
I edited it for you to test with and the zip includes the original you sent me as well. When copying over be sure to set permissions to 0644 and then reboot.
guitardedhero said:
Lol, sorry, I just woke up and thank you for providing what I had actually meant to ask for!
I edited it for you to test with and the zip includes the original you sent me as well. When copying over be sure to set permissions to 0644 and then reboot.
Click to expand...
Click to collapse
I have copied your new policy and edited the permission rights properly. Same results though. Samsung player does not react at all to mod and the soundcloud only after notification sound (it can be clearly heart as well as seen in the dolby equaliser).
Please look at this policy (provided by other user), which solves the music issues but creates instability in the system (no sound during calls, bad reception of one of the sim cards etc.). It should make more sense to you what is the difference.
Kyrillos said:
I have copied your new policy and edited the permission rights properly. Same results though. Samsung player does not react at all to mod and the soundcloud only after notification sound (it can be clearly heart as well as seen in the dolby equaliser).
Please look at this policy (provided by other user), which solves the music issues but creates instability in the system (no sound during calls, bad reception of one of the sim cards etc.). It should make more sense to you what is the difference.
Click to expand...
Click to collapse
I'll take a look. Have you disabled SoundAlive?
Kyrillos said:
I have copied your new policy and edited the permission rights properly. Same results though. Samsung player does not react at all to mod and the soundcloud only after notification sound (it can be clearly heart as well as seen in the dolby equaliser).
Please look at this policy (provided by other user), which solves the music issues but creates instability in the system (no sound during calls, bad reception of one of the sim cards etc.). It should make more sense to you what is the difference.
Click to expand...
Click to collapse
Do you still have XTREMEMusic installed? Keep in mind this mod overwrites your original audio_effects.conf files completely. There may be some libraries and effects on your stock file that are no longer there that are needed. That is why you'll never see an audio_effects.conf file anywhere in my zips as they are patched, leaving previous stuff unbroken. If that's the case, that's what I was talking about when I said, "running in circles."
I strongly recommend this:
Delete /system/addon.d/23-v4adap.sh if found.
Disable SoundAlive
Boot to recovery
Wipe > Advanced > System, Dalvik Cache, Cache
Mount > uncheck System
Install > your current rom zip
Install > ViPER 3.8 package of your choice
Reboot
Great taste in music highly approve will try mod now.
---------- Post added at 02:59 PM ---------- Previous post was at 02:45 PM ----------
Flashed and it is awesome great work viper|atmos beats, huawei version lg Leon running xenon HD 5.1.1
guitardedhero said:
I'll take a look. Have you disabled SoundAlive?
Click to expand...
Click to collapse
You've made it!!! Magic! Thanks man.
This policy solved everything. What was the issue, please educate a noob.
Sent from my SM-N9200 using Tapatalk
Kyrillos said:
You've made it!!! Magic! Thanks man.
This policy solved everything. What was the issue, please educate a noob.
Sent from my SM-N9200 using Tapatalk
Click to expand...
Click to collapse
After the previous edits, I deleted this line.
guitardedhero said:
After the previous edits, I deleted this line.
Click to expand...
Click to collapse
Hmm, I have done that in the past as well, I think actually after your suggestion (deep_buffer). Previous edit I've seen you added some additional frequencies, something that I have played with also but obviously not the right way. Whatever the case, you made my marathon of several days to end in the best way.
Kyrillos said:
Hmm, I have done that in the past as well, I think actually after your suggestion (deep_buffer). Previous edit I've seen you added some additional frequencies, something that I have played with also but obviously not the right way. Whatever the case, you made my marathon of several days to end in the best way.
Click to expand...
Click to collapse
Absolutely, my pleasure!
guitardedhero said:
Absolutely, my pleasure!
Click to expand...
Click to collapse
Man my bad, yesterday after last update i just tested the music and it works. However it happened that i had no phone calls. Now that i made one, i have issues with the sound during phone call. More precisely, no ringtone, no voice, nothing. Everything else works. Any idea how to resolve that? Is it that line that makes the difference?
Sent from my SM-N9200 using Tapatalk
Kyrillos said:
Man my bad, yesterday after last update i just tested the music and it works. However it happened that i had no phone calls. Now that i made one, i have issues with the sound during phone call. More precisely, no ringtone, no voice, nothing. Everything else works. Any idea how to resolve that? Is it that line that makes the difference?
Sent from my SM-N9200 using Tapatalk
Click to expand...
Click to collapse
Try the one attached below.
guitardedhero said:
Try the one attached below.
Click to expand...
Click to collapse
Bad news, still doesn't work. This time it even restarted the phone when I rang (without sound again). really don't understand where the issue is. Thanks once again spending your time on my issues.
Kyrillos said:
Bad news, still doesn't work. This time it even restarted the phone when I rang (without sound again). really don't understand where the issue is. Thanks once again spending your time on my issues.
Click to expand...
Click to collapse
Sorry man, I simply have no way of testing this for you so it's a shot in the dark and the very reason my first reply was to wipe System, dirty flash your rom, and flash ViPER|Atmos™ only, as your current setup combining XTREMEMusic™ creates many opportunities for the many additional files to conflict with others or simply incompatible. Combine that with the fact that your device no longer has its original audio_effects.conf files, the result of flashing a mod that uses its own to overwrite your device's audio_effects.conf files and you end up with a troubleshooting nightmare. I knew from the very start that adequate assistance and support for you would be impossible and any success would be pure luck, which creates a scenario from which nothing is learned if that makes sense.
I strongly recommend trying my mod on its own if you're still interested. I'd be shocked if you still desired more after having a fully functional ViPER|Atmos™ system.
guitardedhero said:
Sorry man, I simply have no way of testing this for you so it's a shot in the dark and the very reason my first reply was to wipe System, dirty flash your rom, and flash ViPER|Atmos™ only, as your current setup combining XTREMEMusic™ creates many opportunities for the many additional files to conflict with others or simply incompatible. Combine that with the fact that your device no longer has its original audio_effects.conf files, the result of flashing a mod that uses its own to overwrite your device's audio_effects.conf files and you end up with a troubleshooting nightmare. I knew from the very start that adequate assistance and support for you would be impossible and any success would be pure luck, which creates a scenario from which nothing is learned if that makes sense.
I strongly recommend trying my mod on its own if you're still interested. I'd be shocked if you still desired more after having a fully functional ViPER|Atmos™ system.
Click to expand...
Click to collapse
I will try and follow your suggestion. Thanks once again!
Kyrillos said:
I will try and follow your suggestion. Thanks once again!
Click to expand...
Click to collapse
My pleasure, I'm here to help you in every way I can so let me know if any assistance is needed once you're done.
I've added a flashable Super Quality Driver zip to the OP attachments section for those that have installed ViPER4Android from anywhere but here.
!! ViPER|Audio™ Super Quality Driver zip is not needed when using any ViPER package !!
I've included this zip only for those using a ViPER4Android installation from any place but here and experience a persistent install driver prompt. Most likely to benefit would be those with a vendor partition that other ViPER4Android installations aren't able to patch /vendor/etc/audio_effects.conf.
Again, those using any ViPER package do not need this. If you experience a persistent install driver prompt after flashing any ViPER package, this will not help you as your issue is likely insufficient free space in /system or something outside the scope of what this zip contains.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to the NitrogenOS Q&A Megathread. Here you can find answers for the most popular problems and questions about NitrogenOS. I started this thread, so that new users don't repeatedly ask the same questions multiple times. While I am fairly new to coding in Java, I can definitely say I know a lot about Android phones and NitrogenOS, but you'll have to trust me on that. If you need any more help, you can even PM me and I'll try to reply as soon as I can.
You can find the original NitrogenOS thread here.
ROM info
Developer: xyyx
Latest Android version: 8.1 Oreo
NOS Download (latest): https://sourceforge.net/projects/nitrogen-project/files/kenzo/kenzo_test/8.1/
Bugs and updates
- A (very) small amount of users reported Google Dialer not working properly while installed through OpenGapps or the Play Store, you can still use stock dialer
1. Test or stable?!?!
Test in this case doesn't mean less stable. xyyx named the two versions a little confusingly.
Test means Oreo (Android 8.0 and 8.1) and Stable means Nougat (Android 7.1.2).
So let's make this a little less confusing:
Oreo (8.0) builds -> Download from here
Oreo (8.1) builds -> Download from here
Nougat (7.1.2) builds -> Download from here
2. Youtube PiP (Picture in Picture mode)
Google has patched PiP a long time ago, so it doesn't work with the latest Youtube releases. The last official release working with PiP is 12.34.55, which you can download from ApkMirror.
My preferred option however is iYTBP (injected YouTube Background Playback), a modified version of Youtube, but it gets a little confusing as there are multiple options.
You can download it from this thread.
Now the tricky part - choosing the right version. I always prefer the Vanced version, which can be found in the 2nd post. Again you have multiple options, but I will not go through all of them since they are explained pretty good in the post itself. While iYTBP enables PiP, it also blocks ads and adds a lot of useful settings and new updates come very frequently. There are multiple installation methods, but I prefer the Magisk one, since it offers options like detaching the Youtube app from Play Store. What this means is, that you don't have to disable auto-updates and it will not bug you to constantly update it.
You can try these methods:
Magisk Module (Easiest):
1. Open Magisk Manager
2. Go to Downloads
3. In the search bar type "Youtube", you should see two results
4. Choose either the normal or the black theme (I personally prefer the black one)
5. Press the download arrow and then "Install"
6. Wait for a while (it's a big package to download and unpack)
7. Reboot
This is by far the easiest option and the module is updated fairly often.
Manual:
1. Delete or uninstall any previous release of Youtube. If you installed it as a system app, disable it or delete the /system/app/YouTube folder. If you had to delete the folder, reboot.
2. Download the Youtube apk
3. Make a folder called YouTube (watch the caps!)
4. Move the apk to this folder and rename it as YouTube (again with the caps)
5. Copy/move the folder to /system/app (The directory should look like this: /system/app/YouTube/YouTube.apk)
6. Reboot
Magisk (manual):
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. Since we're installing from Magisk, you'll need to set MAGINSTALL to YES (MAGINSTALL="YES"). I usually also enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Open Magisk Manager, go to Modules and press the + button. Now select the universal installer zip and flash it in Magisk.
4. Reboot
Recovery method:
Same as for Magisk, but MAGINSTALL is set to NO (MAGINSTALL="NO"). In case you didn't read the Magisk method, here is the recovery method...
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. I usually enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Reboot to recovery, go to Install and choose the universal installer zip, flash it.
4. Reboot
If you open a video in fullscreen mode and press the home button, it should open it in PiP mode. If you want to change some advanced settings, you can go to your Account (the round icon with your profile picture) -> Settings -> iYTBP Settings
3. Goodix & FPC - What are they
Goodix and FPC are two different types of fingerprint sensors (or rather sensor manufacturers). They both work in Android 8.1 builds. Custom kernels or mods may break the fingerprint sensor functionality.
4. Rooting
tl;dr: rooting NitrogenOS is the same as rooting any other custom rom, just flash Magisk, SuperSU, phh's superuser or anything else.
Now for the extended version.
Magisk:
Magisk is a great open-source root manager, developed by topjohnwu. It features a feature rich app, but most people prefer it because of it's "modules", packages which can do a bunch of things, from installing apps like Viper4AndroidFX or Dolby Atmos, to modifying system settings, like the volume steps increase. Magisk also features an option called "Magisk Hide", which can bypass Android's SafetyNet.
Check out the Magisk thread.
You can directly download the latest version of Magisk from https://tiny.cc/latestmagisk
SuperSU:
SuperSU is an alternative root manager. It used to be developed by Chainfire, but has recently been purchased by another company. I still prefer Magisk, but SuperSU is a great alternative for new users. My problem with it though is, that it is not open-source and the new buyer is pretty secretive so I don't really trust them.
Check out the SuperSU website for the download link.
phh's SuperUser:
Another open-source root manager, but the great thing about this one is, that it's very minimalistic and very small in size.
Check out the SuperUser thread and phh's Build Bot.
5. Google Apps (gapps)
Google apps are a vital part of custom roms. You might not know this, but AOSP and CM based roms are made from Google source code. Google actually makes Android open-source, but the Play Store and other Google apps are not. That's why roms like NitrogenOS do not come with the Play Store preinstalled. That is where Open Gapps come in. They are prepackaged apps, updated almost daily. They come in various sizes and versions, but they can all be flashed in TWRP like a normal zip file.
Platform: arm/arm64/x86/x86_64 - RN3 has an arm64 processor (Think of it as a 64-bit CPU for phones)
Android: 8.0/7.1/7.0... - This is the android version, NOS is Oreo based so choose 8.0 (Or 7.1 for Nougat) [Check below for OpenGapps 8.1]
Variant: This is where it gets complicated. There are a LOT of versions to choose from. For more in-depth resources check the OpenGapps' package comparison.
But OpenGapps are a lot more customisable, to the level where you can choose individual apps you want installed. The easiest way to do this, is to flash the Aroma package, which enables you to choose exactly which packages you want installed. Another option is to configure any of the selected packages using a gapps-config.txt file. You can learn more about that in the Advanced Features and Options section.
You can download daily builds for any Android version from https://opengapps.org/
6. TWRP (Recovery)
A recovery is a partition, used to flash files like ROMs, gapps and any other modifications. You do (in most cases) need an unlocked bootloader to use it. Unlocking your bootloader will not be described on this thread, as there are a lot of resources for our device.
Official TWRP - This is the official TWRP (Team Win Recovery Project) for our device
You can find the latest updates for TWRP on their website.
Red Wolf - This is a modified version of TWRP, my absolute favourite because of it's custom features.
Flashing TWRP:
If you don't have a custom recovery installed and you have unlocked your bootloader, then download the latest version of your preferred recovery and follow these steps:
1. Download Minimal ADB and Fastboot on Windows, or use sudo apt install android-tools-adb android-tools-fastboot if you're on Linux.
2. Enable USB Debugging (Settings -> About phone -> Press "Build number" 7 times to enable Developer options). You should find the Developer options in settings above "About Device". Find USB Debugging and enable it.
3. Connect your PC to the phone via a cable. Open Minimal ADB and Fastboot (which will open CMD) or Terminal on Linux and type this (same for both OSs): adb devices. Select "Always allow on this computer" and confirm access on your phone.
4. Reboot your phone to fastboot/bootloader (By holding Power and Vol-, releasing the power button after a vibration and holding the Vol- button until you see the Xiaomi mascot).
5. Type (In CMD/Terminal): fastboot devices, to confirm if the phone has been recognised, then fastboot flash recovery /path/to/recovery.img
6. After it has succesfully finished, remove the cable and reboot directly to recovery (Power and Vol+, release power after vibration, but keep holding the Vol+ button until you see the TWRP or RedWolf logo).
If you do already have a custom recovery installed and just want to update it, flash the .img or .zip file in your already installed recovery and select "Reboot to recovery".
7. NOS asks me for a password after flashing?!!?!?
This is actually not NitrogenOS's fault, it's a byproduct of your previous rom, most often MIUI. What this means is, that your internal storage is encrypted and the only way to fix this, is to backup everything on your internal storage, which you can do by connecting your phone to your pc while in recovery. You should be able to access the phone's storage and move the files from there. If you for some reason can't do that, you can still put in an sdcard and copy the files to it in TWRP. Bottom line, backup the files and then go to "Wipe" and find the "Format data" button. You might see a "wipe data" button, but this is not the same. When you "wipe data" you are wiping your system, cache, dalvik cache and data partitions, but formatting data will format your internal partition as well and thus remove the encryption.
You can finally reflash NOS and gapps or whatever other modification you want.
8. Firmwares
Check out this link to download the latest firmware for our device.
What is firmware? - It's what connects hardware to software (don't confuse it with a kernel). It's what, for example, makes the camera work.
Do I really need firmware - Yes (but it's already installed, even after completely wiping the stock rom, since it's on separate partitions).
Do I need the most up-to-date firmware - Actually no, the only difference you will notice is in the signal and WiFi strength. If yours are good enough, you don't need to update, otherwise feel free to download the newest version from the link above.
What is emmc_appsboot.mbn? - It's a bootloader update. Bootloader or fastboot is the partition in which you have unlocked your bootloader and flashed the recovery. If you have officially unlocked your bootloader, then you can flash firmware with emmc_appsboot.mbn, but if you have unofficially unlocked your bootloader, do not flash these files as they will re-lock it. But you can still flash the version without emmc_appsboot.mbn.
Kenzo? Kate? - Kate devices are the same as kenzo ones but are a little bigger.
Some comparisons:
Kenzo
Size: 150 * 76 * 6.85 mm
Weight: 164g
Kate
Size: 152 * 76 * 6.85 mm
Weight: 167g
Model numbers:
Kenzo: 2015116
Kate: 2015161
Kate devices are 32/3 GB, and some kenzo devices are as well (some are 16/2 GB), not really sure about this part.
Global stable or developer? - Most people use developer roms, but again, this is not the actual ROM, just the firmware extracted from the rom, it doesn't really matter which one you choose.
When do I need to flash firmware? - If you're coming from MIUI8 (or 9), then you probably have the newest firmware. In this case you don't need to flash it, because MIUI roms already have firmware included in the update. If you're coming from a CM or AOSP based rom you also probably don't have to flash it, but I suggest you update it just in case. If your signal is good enough though, there really is no need.
9. How to flash the rom
Flashing is pretty straight forward. Just go to the Install section of TWRP and flash it like any normal zip, nothing special.
If you're coming from MIUI, then the full procedure is this:
1. Unlock your bootloader (google it, useless explaining it here)
2. Flash TWRP
3. Make a full device backup (Nandroid backup)
4. Copy or move all important files from the internal storage to an sdcard or your pc
5. Format data, or in other words, wipe EVERYTHING (excluding external storage) - This will delete all your photos and anything else in internal storage
6. Flash the latest NOS "test" build (Oreo)
7. Flash gapps (I recommend opengapps.org, check above)
8. Reboot to system
10. OTA?
What is OTA? - OTA means Over The Air (Update)
Does NOS have OTA? - Actually yes and no, newer updates (from March 2018 on) do have partial OTA (it does check for updates and notify you, while also giving a direct download link to SourceForge, but you will have to manually flash every update in your recovery.
What about incremental updates? - Sorry, but no. You'll have to download full packages every time. If you have a bandwidth cap then just download an update every week or two, you can check the changelog to see if you think it's worth updating to.
11. Google Camera
If you're having problems with the official Google Camera or just want some added features then look no further than modded camera apps. Check out this thread by emime12, it's very frequently updated and features a lot of different camera mods, including Google Camera, MIUI Camera, MOTO Camera and many more.
Recommended settings:
3x3 Grid - For better photos
I usually disable "Save location" and "Camera sounds"
Model: Pixel XL (corr) - default
Config camera HDR+: NEXUS 6
HDR+ parameters: Default
Panorama resolution: High
Advanced: Enable both
Experimental: I usually leave this disabled but it's your choice.
Back camera video resolution: UHD 4K (30 fps)
In case your camera doesn't work check if you have these two files and delete them:
/System/framework/com.google.android.camera.experimental2016.jar
and
/System/etc/permissions/com.google.android.camera.experimental2016.xml
Credits go to: @emime12 and Njaiker.
You can find more info about problems and updates on emime12's thread.
Settings may differ a lot, so check emime12's recommended or just test until you find ones that work for you
12. RAM Management - Low free RAM
Android's RAM (Read Only Memory) management doesn't work like Windows'. Android manages RAM very well, "Free RAM is wasted RAM" is a very common expression on XDA. Android loads the first couple of apps into the RAM and priorities the open one. More used ram means more apps loaded in ram which means faster load times. Don't worry about it too much and just enjoy the fast loading speeds.
13. VoLTE?
VoLTE should work on Android 8.1. Magisk, Viper or any other mods may break it.
14. Custom kernels
While there are a lot of custom kernels, I suggest you stick with the stock one, as it is made specifically for NOS and thus it is the most stable. If you still want a custom kernel, you can try Radon or Agni but they might break VoLTE or your fingerprint sensor.
Agni XDA Thread - By psndna88
Radon XDA Thread - By Umang96
15. Daily driver or not?
Yes, NitrogenOS Oreo is very stable, definitely enough for a daily driver. It is the best Oreo rom for our device (in my opinion), as it offers just the right amount of customization and stability.
15. GPS
Some users have reported low accuracy, but you should be fine if you turn on High Accuracy mode and/or install Faster GPS.
Update: In recent updates GPS shouldn't be a problem anymore as xyyx has fixed it, but some users have still reported low accuracy.
16. Viper4Android FX
(There may be other ways, but I haven't tested them yet so I can't confirm if they work) By far the easiest way to install Viper4Android FX is using Magisk. There is Magisk module called ViPER4Android FX Materialized. Download and install that module from the Magisk repo, choose your preferred installation option (By pressing Vol+ or Vol- to select which version you want installed and if you want it materialized - for newest materialized version press Vol+ 2 times) and finally reboot. Try playing some music and open the Viper app. Turn on the "Master Power" switch and the "Playback Gain Control" (the easiest way to tell if it worked). If after a little time the volume increases, it means that Viper4Android FX works. If not, press the three dots and choose "Exit" (without turning off the master power or gain control). Now open the app again and it should work. You can also check that in the side menu under "Driver status", if it's enabled and processing, then everything works.
You may or may not have to exit and re-enter the app after reboot to enable processing (in my case I had to).
I would show you my recommended settings (as requested), but to be honest I only use:
Headset
Viper Bass (Natural bass, 40 HZ frequency, 8 dB)
Viper Clarity (Natural, 6 dB)
Sometimes I use Field surround with default settings
Phone speakers
eXtra loud (Slight, 4x max gain, -1.9 dB max output)
Bluetooth device
Playback gain control (Moderate, 6x max gain, -1.9 dB max output)
If I'm at a party with my bluetooth speaker I pump it up to Extreme and 8x max gain
Viper Bass (Natural, 40 HZ frequency, 8 dB), 17 dB for parties
Viper Clarity (Natural, 3.5 dB)
I don't use equalizers or if I do, they are song-specific. I also don't USB/Dock, so I can't recommend anything there.
Of course these settings can vary depending on the song, so choose those, which you like the most and don't stick with just those I chose, try all the functions to see which you prefer.
17. AdAway (Root)
AdAway is a great open-source root ad blocker, which can automatically download and update sources and works by adding those to the hosts file. It work well on the internet, but also inside apps (most of the time).
Check out the official AdAway website. You can also download it from F-Droid.
Adaway v3.2 (60) (direct download link)
Adding custom host sources:
Go to "Host sources" and add your own sources or check out these: AdAway's host sources
Be careful when adding all of them, since some can block legitimate links like goo.gl.
AdAway also offers an option to scan for Adware, which can be found under "Scan for adware". This will bring up a new window, press "Start scanning". If you don't need/want the mentioned apps you can uninstall them, but AdAway can't block their ads.
You can also check out my recommended settings:
wow,really appreciated that sir., it is very helpful specially for those who wanted to try, flashing rom or any mods on their device like me. thanks and keep up the good work sir God bless!
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
saifuk said:
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
Click to expand...
Click to collapse
Thanks for the tip, will update the thread.
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks?
@saifuk what kind of nougat port u are expecting of ?
Aditya1011 said:
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks
Click to expand...
Click to collapse
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
AtomR said:
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
Click to expand...
Click to collapse
Flash latest firmware of developer rom. And volte is sure shot working.
Aditya1011 said:
Flash latest firmware of developer rom. And volte is sure shot working.
Click to expand...
Click to collapse
Mate, I'm already on 7.9.22 firmware. Lots of people are reporting it. Yours is working, must be some kind of random.
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
how to install via dualboot patcher as secondary rom?
AtomR said:
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
Click to expand...
Click to collapse
Idk bro y that happening to u. Flash miui EU rom n thn the nos rom. Mayb that should work.... Bcuz I had done that for the 1st time whn my volte wasn't working at any cost. Best of luck.
smjhh said:
how to install via dualboot patcher as secondary rom?
Click to expand...
Click to collapse
I don't think dual boot patcher supports oreo roms. Try asking on their thread to see if it does.
Google HDR camera 5 or 5.1 work with this ROM??
sagar13190 said:
Google HDR camera 5 or 5.1 work with this ROM??
Click to expand...
Click to collapse
Read op!
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
sagar13190 said:
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
Click to expand...
Click to collapse
It works for many users. Did you flash my zip or install an apk?
Sim card detection issue
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
dhavalmehta said:
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
Click to expand...
Click to collapse
Dude, it's really not a big problem, it detects it like 95% of the time. Just reboot and you're done. Or wait about 2 min and it should detect it. You could also just remove the sim and reinsert it. But since the latest few updates for me it gets detected 100% of the time. So update to 28/10/2017 build and you should be fine.
@JustMeErazem You're giving flase info. to others saying that VoLTE works on both sim. Actually, it works only on first sim. Tried, tested on 3 different Kenzo's. Clean flashed.
Conclusion: VoLTE doesn't work on 2nd sim.
Introduction
Few weeks ago, I got a Pixel 1 as my backup phone, when I try to connect it to the Microsoft Wireless Display Adapter, it couldn't find the Adapter.
I haven't used Android phones for a long time. In my mind, Android natively supports Miracast. After some searching, I was frightened to find that Google has removed Miracast from Android.
I was really disappointed because I often cast my Windows devices easily by using Miracast. My Projector has only two HDMI ports, one for HDMI cable, and one for Wireless Display Adapter. I can't add a Chromecast unless a HDMI switch is used.
One possible solution is to add a line "persist.debug.wfd.enable=1" in "build.prop" to enable WiFi-Display, but many people say that it doesn't work since Android N, the phone can discover WiFi-Displays but unable to cast.
Since Android framework is open source, I did some searching and found that some WiFi-Display related code still exists. Android 9 still keeps the WifiDisplayAdapter in DisplayManagerService, but removed WifiDisplay from MediaPlayerService, that's why we can discover WiFi-Displays but can't cast.
I recovered some code from AOSP history commits, fixed the build errors, and debugged on my Pixel, finally the Miracast can work on my Pixel.
If you also want Miracast to work on your Google phones, you can follow my steps, but first make sure your ROM is open source so that you can change and rebuild it.
If you have a Pixel 1 running the same version of system, you can simply replace some files in your system with the files I built.
If you have other Google phones or running different versions, you can apply my patch to AOSP, and build it by yourself. I have built the latest version for all Google Pixel phones, but I haven't tested except Pixel 1.
If your ROM is not open source, I will no longer be able to help, since MediaPlayerService may have been changed by your ROM, you may can't replace it with the AOSP version.
Prerequisites
Pixel running Android 9.0.0 build number PQ1A.181205.002.A1 or PQ1A.190105.004.
Bootloader unlocked.
adb and fastboot tools and drivers are working for your device.
Note & Disclaimer
These steps will change files in your system, your Pixel should run the exact same version of system. Pushing files to different versions of system may cause unknown problems.
Please check carefully before running each command, a mistaken operation may result in unable to boot up, or destroy your data, or even damage your phone.
If you are not sure about what these steps are doing, but still want to go ahead, please backup your phone firstly, you may not be able to recover your phone to its original state.
I have only tested on Pixel 1 with build number PQ1A.181205.002.A1 and PQ1A.190105.004, for other phones or versions, you should build and test on your own.
Basic Steps
Flash the same version of factory image for your phone.
Download the prebuilt files from https://github.com/sbjbs/android-wfd-patch
Add this line into "build.prop", without it, we will not be able to enable WiFi-Display:
Code:
persist.debug.wfd.enable=1
Replace some files in system:
Code:
system/lib/libaudioflinger.so
system/lib64/libaudioflinger.so
system/lib/libserviceutility.so
system/lib64/libserviceutility.so
system/lib/libmedia.so
system/lib64/libmedia.so
system/lib/libwilhelm.so
system/lib64/libwilhelm.so
system/lib/libandroid_runtime.so
system/lib64/libandroid_runtime.so
system/lib/libstagefright.so
system/lib64/libstagefright.so
system/lib/libstagefright_wfd.so
system/lib64/libstagefright_wfd.so
system/lib/libmediaplayerservice.so
If you have magisk installed, you can refer to Phoenix Wright's post:
Phoenix Wright said:
using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent.
using magisk to overlay them on /system
Click to expand...
Click to collapse
Some extra steps that you may need
Remove dm-verity metadata of system.img
The dm-verity can prevent us from changing the system, and what's more it has a forward-error-correction(FEC) feature, which can detect and correct some corrupted data.
I spend a lot of time on attempting to change the build.prop but fail again and again, it just always correct the file, and I can't enable wifi-display.
I don't know how to disable it. Since the error-correcting info should be stored in the dm-verity metadata, I just removed the dm-verity metadata from the stock system.img, and flash the system.img.
I will list the steps to remove dm-verity metadata, but if you can disable dm-verity entirely, that should work too.
For phones that have a vbmeta partition (like Pixel 2), seems you can flash an special vbmeta.img to disable AVB. You can build the empty vbmeta image by this command, but I don't have a device to test if it works:
Code:
avbtool make_vbmeta_image --flag 2 --padding_size 4096 --output vbmeta.img
For Pixel 1, we need to remove dm-verity metadata that attached to system.img, first convert the sparse system.img to an ext4 image:
Code:
simg2img system.img system.ext4.img
read the block count to calculate the system size:
Code:
od -j 1028 -An -N4 -tu system.ext4.img
for Pixel 1, it should be 516099. You also can read it by a Hex Editor, e.g., WinHEX in Windows, read 4 bytes starting from 1028 bytes, as a little-endian hex value.
so the real system partition size is 516099 * 4096 = 2113941504 bytes.
we need to set the data to zero after that position. It's important to do this, since we need to overwrite the metadata in that area, rather than just truncate the size of system.img.
next get the ext4 image size, for Pixel PQ1A.181205.002.A1, it should be 2147483648.
so we need to write 2147483648 - 2113941504 = 33542144 bytes：
Code:
dd if=/dev/zero of=system.ext4.img seek=2113941504 count=33542144 oflag=seek_bytes iflag=count_bytes
we also can use some other tools to do this, e.g., WinHEX in Windows. Open the file in in-place mode, and jump to 2113941504, and select it as the begin, and jump to the end, and select as the end, and fill the selection with all zero.
after that, flash the changed system.ext4.img to Pixel:
Code:
fastboot flash system system.ext4.img
Test that you can boot up normally. If not, check what's wrong and fix it.
Temporary boot up by TWRP image
We don't have to install TWRP, but just use it to temporary boot up, so that we can mount the system partition for writing. If you have TWRP installed, you can just boot to TWRP.
Download TWRP image for pixel, just need the twrp.img, we won't install the zip file.
boot your device to bootloader:
Code:
adb reboot bootloader
and boot by the twrp.img
Code:
fastboot boot twrp.img
after TWRP booted up, just leave it there, no need to unlock or input password, we will change the system by adb.
Mount system partition for writing.
In the current version of TWRP for Pixel (twrp-3.2.3-1-sailfish.img), its fstab has an entry for system partition, we can directly mount it.
Code:
adb shell mount /system
run mount to check if successfully mounted:
Code:
adb shell mount
you should see an entry like this:
Code:
/dev/block/sda34 on /system type ext4 (rw,seclabel,relatime)
If not, you should stop now, and check the above steps.
after mount, we can use adb to push files into system.
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
jean_michmich said:
Hey guy,
You helped me a lot to understand why it was not working with Pie. I tried several custom ROMs + the official Pie and it was not working.
There is Wireless display option in quick settings but it' doesn't find my Microsoft Wireless Display Adaptor also.
I so downgrade to Oreo. With Oreo it works without any issue. (there is an option "allow Wireless display" to tick and then your miracast dongle will appear).
You did a great job to make it working on Pie. Congratulations. I will anyway stay on Oreo. I think google will change that (many people already complained i guess).
Jean Michel
Click to expand...
Click to collapse
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
sbjbs said:
Thanks for your reply!
I have tested on Pie on my Pixel, I often play online games while cast is on, and didn't meet any problems last week.
I also hope that Google will support Miracast again in the future, but it seems unlikely in the near future.
Google has abandoned it since Android 6 (source: Wikipedia), and now they're deleting unused source code related to wifi-display.
I'm more worried about that there will be more build errors and potential issues when we try to enable it for future Android versions.
Click to expand...
Click to collapse
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
jean_michmich said:
OK it's getting more clear. You are right. Wikipedia says : "but support was dropped with Android 6.0 Marshmallow in 2015 in favor of Google's own proprietary Google Cast protocol.[15] Some manufacturers of Android devices step in and support Miracast through their software"
I'm not an "official android ROM" user.
I always use Pixel Dust custom ROM. For this custom ROM, Miracast was supported for Oreo but not for Pie (not yet).
Click to expand...
Click to collapse
I used to be a ‘latest official ROM’ user
For custom ROMs, since they may have changed the framework, we can't replace files with AOSP version, but as long as they're open source, we can try to contribute to it.
Adding Miracast support in Android is not difficult, and many manufactures have their own support.
I hope your custom ROM will support Miracast for Pie in the near future.
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
spezi77 said:
Hi @sbjbs
If I understand you right then you have patched the AOSP codebase. Would you mind sharing the repositories/commits on your GitHub? That would be highly appreciated. :good:
Regards
spezi
Sent from my Pixel 3 using XDA Labs
Click to expand...
Click to collapse
There's a link in the OP: https://github.com/sbjbs/android-wfd-patch/tree/master/patches/android-9.0.0
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Great to hear that!
You method is simpler and more elegant, that's awesome!
Phoenix Wright said:
Tested on Pixel 2 XL and working (for what it's worth, using "setprop" to set that property once is enough, no need to touch build.prop; given it's a "persist" property it'll be permanent). I built the .so files on my local aosp tree and I'm using magisk to overlay them on /system.
Click to expand...
Click to collapse
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
nitin.chobhe said:
Can you elaborate how you did use "magisk to overlay them on /system"?
I pushed them using adb as mentioned on github but it is stuck at Google splash screen. I've taimen BTW and am on Pixeldust ROM. It booted while writing this post but the screen was not responding to touch.
Nitin
Click to expand...
Click to collapse
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Phoenix Wright said:
I made a module with the .so files I compiled: https://workupload.com/file/pd4EUBdw
Note that I can't vouch for this to work on your ROM, it works on taimen on stock 9.0 with January security patches though.
Click to expand...
Click to collapse
Thanks!
sbjbs said:
Did you build the so files for your ROM from source? the patch has changed the interface of IMediaPlayerService, if anything else in your ROM is using IMediaPlayerService.h, you'd better rebuild and replace them.
that's why I uploaded the libwilhelm.so and libandroid_runtime.so, even though I didn't change the source code of them.
Click to expand...
Click to collapse
I tried building with my ROM but I got build errors related to OMX.h, I need to find a solution for them. Thanks anyways!
Nitin
Someone tries on Pixel 3? Thanks
It works perfectly ! I used the prebuilt files on the march build.
Do you know if we can force the 16/9 ratio ?
Thanks
edit : I will try with second screens !
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
marshyrob said:
this works a treat on my Pixel 3 XL (Stock Pie) just overlayed the files from Phoenix Wright using magisk and it works now....sweet thanks, now just need to figure out how to fool sky sports app into letting me cast.....
Click to expand...
Click to collapse
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
EMJI79 said:
Can you explain more how did you do?
Did you just flash the zip from Phoenix Wright in Magisk?
Click to expand...
Click to collapse
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
marshyrob said:
Yes just copied the .zip file from Phoenix Wright's post to my device then used the module install option in Magisk like if you are installing a module found in Magisk (use the plus sign to add your own .zip file instead and browse to the file you just saved) then reboot. Then i went to the cast option in settings - connected devices - connection preferences, there i could tick in the top right corner under the 3 dots "enable wireless display" and it showed my Panasonic TV, chose connected and boom it connected. Needed to enable the mirroring option on my Panasonic but this is a TV setting nothing to do with the phone, you might need to do a similar step based on your TV as they need to be able to see each other.
Click to expand...
Click to collapse
It did work today with my Sony television.
Thanks!
OMG!!! You made my week. Few hiccups tho....
Can anyone else confirm that Hulu and HBO go and Amazon prime . YouTube works.
Hulu and amazon I can log on but when it plays all you get is audio. Haven't tried Netflix I don't sub them.
HBO go as soon as I try to play a video it says this video cannot be played. If I disable the mirror it plays perfectly. Same thing with Hulu and prime. Disable the mirror an it works perfectly on my phone.