Develop Bugs

Anyone able to run Viper4Android?

I just got my OP3 and really like it. I'd love it with V4A... but it's not working. The driver doesn't load.
When I try to load SELinuxModeChanger, it errors out saying that it's unable to gain root access (even though SuperSU grants root). Weird.
So is V4A working for anyone?
Sent from my ONEPLUS A3000 using Tapatalk

Yep. I have busy box installed.
Sent from my ONEPLUS A3000 using Tapatalk

Try using A.R.I.S.E on XDA, it is a full package with a lot more than V4A. Furthermore, try to set your linux to permissive.

dont use superuser 2.74
use 2.67

^ I think that I'm trying to use v2.74. I'll find v2.67. Thanks!
-KLH

Confirmed fix. I'm now running v2.67 (Beta) and I'm now able to run V4A. Thanks again, kramer987.
-KLH

Setting it to permissive worked for me, that may help others as I do have v2.74 installed.
{
"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"
}
Sent from SM-G900Pkltespr

Can you turn off auto brightness?

denny1970 said:
Can you turn off auto brightness?
Click to expand...
Click to collapse
If you are referring to me, yes I can.
Sent from SM-G900Pkltespr

THREAD REVIVE! (Happy July 4th to those in US)
I thought that I had V4A working, but it isn't - even though it says that it is. How do I know? Regardless of what you do with the FIREqualizer, the sound remains the same - clearly unchanged. Has anyone run into this?
To recap, this is what I'm running:
* OOS v3.2.0
* SuperSU v2.67 Beta
* Busybox v1.24.2-meefik
* SELinux (set to "permissive")
* V4A v 2.4.0.1
* Google Play Music v6.10.3019C.3013175 (phew)
Here's what I see when I run the driver status check:
Here are other screenshots of V4A that shows the rest of the settings and me changing the FIREqualizer. Throughout, the sound doesn't change.
Now I have heard that OOS v3.1.2+ uses an internal sound driver called DiracHD so 3rd party sound drivers cannot be used. Since XDA members are more knowledgeable, I request either confirmation or a suggested solution.

I am running Divine beats by @TheRoyalSeeker.
Viper and Dolby Included.
Good sound..!

Joyo-rocker said:
I am running Divine beats by @TheRoyalSeeker.
Viper and Dolby Included.
Good sound..!
Click to expand...
Click to collapse
When I flash anything, it doesn't get installed properly. That includes Xposed, Divine Beats. It shows install success in TWRP but it doesn't install.

edios123 said:
When I flash anything, it doesn't get installed properly. That includes Xposed, Divine Beats. It shows install success in TWRP but it doesn't install.
Click to expand...
Click to collapse
That's strange try a another twrp recovery specially Garak's one. And try to dirty flash your ROM again or check permissions in file manager or maybe try mounting system in twrp and flash.
Was your phone bootloooping and has systemless root.
Try these and tell me your progress.
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
kharrigan said:
THREAD REVIVE! (Happy July 4th to those in US)
I thought that I had V4A working, but it isn't - even though it says that it is. How do I know? Regardless of what you do with the FIREqualizer, the sound remains the same - clearly unchanged. Has anyone run into this?
To recap, this is what I'm running:
* OOS v3.2.0
* SuperSU v2.67 Beta
* Busybox v1.24.2-meefik
* SELinux (set to "permissive")
* V4A v 2.4.0.1
* Google Play Music v6.10.3019C.3013175 (phew)
Here's what I see when I run the driver status check:
Here are other screenshots of V4A that shows the rest of the settings and me changing the FIREqualizer. Throughout, the sound doesn't change.
Now I have heard that OOS v3.1.2+ uses an internal sound driver called DiracHD so 3rd party sound drivers cannot be used. Since XDA members are more knowledgeable, I request either confirmation or a suggested solution.
Click to expand...
Click to collapse
That isn't necessarily needed as I am running v4a and Dolby as well.

Same problem here. Cannot install viper drivers, 2.76 supersu, busybox on rails, cannot figure out how to set selinux to permissive.

edios123 said:
When I flash anything, it doesn't get installed properly. That includes Xposed, Divine Beats. It shows install success in TWRP but it doesn't install.
Click to expand...
Click to collapse
This is most likely because you HAVE to mount system in TWRP before you install divinebeats or viper via zip file. It will say it's successful, but nothing gets written to the system partition unless you mount r/w prior first. I cannot say this for xposed, but I do know that the only 'systemless' version worked for me was 85.1 by RomRacer.

Joyo-rocker said:
That's strange try a another twrp recovery specially Garak's one. And try to dirty flash your ROM again or check permissions in file manager or maybe try mounting system in twrp and flash.
Was your phone bootloooping and has systemless root.
Try these and tell me your progress.
---------- Post added at 01:39 AM ---------- Previous post was at 01:37 AM ----------
That isn't necessarily needed as I am running v4a and Dolby as well.
Click to expand...
Click to collapse
Will try that, but it wasn't a problem when I was on 3.1.2.
js042507 said:
This is most likely because you HAVE to mount system in TWRP before you install divinebeats or viper via zip file. It will say it's successful, but nothing gets written to the system partition unless you mount r/w prior first. I cannot say this for xposed, but I do know that the only 'systemless' version worked for me was 85.1 by RomRacer.
Click to expand...
Click to collapse
I've mounted system the very first time too. It doesn't work.

edios123 said:
Will try that, but it wasn't a problem when I was on 3.1.2.
I've mounted system the very first time too. It doesn't work.
Click to expand...
Click to collapse
You just have to mount system in TWRP, than you can flash divinebeats or xtrememusic mod or anything else. Im running v4a on this setup:
OP3 Lite rom 3.2.0
SuperSU - 2.76 (systemless)
Xposed - 85.1 (systemless)
XtremeMusic - 7.5.2
Viper4Android - 2.4.0.1

ARISE
matssa said:
Try using A.R.I.S.E on XDA, it is a full package with a lot more than V4A. Furthermore, try to set your linux to permissive.
Click to expand...
Click to collapse
A little help, will using this module not damage my hardware?
Also, ELI5, how is it better than the default setup on my OP3, I searched ARISE and read what was there, but it turned out o be too technical for me.
Any help is appreciated.

gro0vr said:
A little help, will using this module not damage my hardware?
Also, ELI5, how is it better than the default setup on my OP3, I searched ARISE and read what was there, but it turned out o be too technical for me.
Any help is appreciated.
Click to expand...
Click to collapse
This will not damage your hardware, unless you change the EQ to boost too much the sound of course, like for every mod. Furthermore, ARISE installs some audio libraries issued from Sony, HTC, etc... with Dobly app and Viper4Android. Everything is linked in order to have a good sound audio. Furthermore, some profiles are included in order to load them directly in V4A.
I suggest you download the Exodus 1 with Aroma installation since it's simplified.

kadett-k2 said:
You just have to mount system in TWRP, than you can flash divinebeats or xtrememusic mod or anything else. Im running v4a on this setup:
OP3 Lite rom 3.2.0
SuperSU - 2.76 (systemless)
Xposed - 85.1 (systemless)
XtremeMusic - 7.5.2
Viper4Android - 2.4.0.1
Click to expand...
Click to collapse
See, I told that I've already mounted system.
I'll try once again.

[MOD] - WETA Audio 9.1 - [aroma][V4A][DolbyAtmos][xloud][srs][beats][+++]

{
"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"
}
You flash this MOD at your own risk,
i take no responsibility for any mishaps.​
Subscribe to update notifications and general chat by clicking the button below
PIXEL TELEGRAM CHANNEL​
This here is my personal setup and thought i'd share. Usually i test extensively before releasing to public, but if you do find something detrimental to the usage of your device that is either Force Closing or simply not working, let me know and i will in turn inform whether that is something i will tend to.
WETA is a rom for Music geeks like me, though because we are still waiting on TWRP to become available i'd thought i'd make this MOD to flash in the meantime. Its main focus is Audio. ​
This mod installs the following...
V4A 2.5.0.5 or 2.3.4.0
Dolby Atmos
Sony Xperia™ Z5 Premium audio system
Beats™ libraries and effects
WETA Reboot app
​
How to install...
As of 9.0 moving forward, you will need to flash this mod using TWRP.
NOTE: There have been some issues with systemui crashing after install. This results in having to flash back to stock and in some cases having to wipe phone completely.
I advise running an un-encrypted file system at this stage, which may or may not help. Just be aware that things are basically experimental at these early stages.
1. Make sure you are on Stock firmware and have rooted device
2. Download mod zip
3. Install this app "Root Browser"
4. Extract the zip (click and hold, select extract) using Root Browser directly into Download folder. (you should have /sdcard/Download/WETA_*** as folder with files in it)
5. Go into Download/WETA_*** folder and select WETA-flash.sh
6. Tick "Execute script as root"
7. Then select the Execute button
8. It will say "Executing script"
9. Once complete you should have a popup box with no errrors.
10. Reboot device and mods should be installed....
Changes...
31st Oct
Fixed some things in audio_effects.conf
Added a new mod, 3minit battery to download page
#3 1st Nov
Modified build.props
Added System wide audio
#5 + #5b
Script modifications to be more universal for build.prop mod
- no longer replaces build.prop, now appends to file instead, keeping existing mod lines
V4ADA1 + V4ADA2
V4ADA1 - V4a 2.5.0.5
V4ADA2 - V4a 2.3.4.0
Both these versions have all audio mods omitted as to help with echoing while gaming.
Only V4A and Atmos present.
Fyi.. this can be flashed over the top of previous audio mods
12th NOV
WETA Audio 7 + 7b + V4ADA1_V5 + V4ADA2_V5
removed modification of audio_policy_config file
12th NOV
WETA Audio 8 + 8b + V4ADA1_V6 + V4ADA2_V6
More audio_policy_config tweaks for spotify
WETA Audio 9.0
This version is an Aroma installer version. TWRP only.
WETA Audio 9.1
Fixed V4A convolver and profile permissions
– FYI this will wipe out your /sdcard/ViPER4Android folder
Added Sony music player
Weta reboot option
BusyBox Install option
Weta audio remover
MOD Download Page
If you like my work, please consider buying this poor guy a craft beer for his efforts
?? --->

Downloading now. Will test as soon as I get to work. Thanks!

All the ports are coming left and right for device... we'll see how this one goes

I downloaded the zip and followed the instructions. Already rooted, had busybox and Root browser. Restarted and everything was installed. I keep getting FC on Dolby and when I enabled Viper it didn't change anything. I am not sure what I am missing.

ExcuseTheN00b said:
I downloaded the zip and followed the instructions. Already rooted, had busybox and Root browser. Restarted and everything was installed. I keep getting FC on Dolby and when I enabled Viper it didn't change anything. I am not sure what I am missing.
Click to expand...
Click to collapse
Did you start off with a clean system and vendor? The files going to vendor are important. Also are you using a custom kernel?
Selinux needs to be permissive, if you go into a terminal emulator and type su , allow root, then type getenforce , does it say permissive?

Mentalmuso said:
Did you start off with a clean system and vendor? The files going to vendor are important. Also are you using a custom kernel?
Selinux needs to be permissive, if you go into a terminal emulator and type su , allow root, then type getenforce , does it say permissive?
Click to expand...
Click to collapse
Yes they were clean and it is permissive. I'm on ElementalX 0.05.
---------- Post added at 08:18 PM ---------- Previous post was at 07:20 PM ----------
What is the easiest way to uninstall the mods? I would like to uninstall them and try to reinstall again.

Working great. I do prefer the old Viper though. I think it sounds better. Great job.

wow, I am super excited, I absolutely love your audio Mods coming from the nexus 6p! Thank you very much for bringing your mods forward to the Pixel XL.
2FunJags.

I have tried to get this to work with no success. I did double check and the newest version of busybox is installed. Selinux is set to permissive. I enable the Dolby app and the Viper app but nothing changes. I do not hear any difference with it turn off or on. The Dolby app will crash and FC if I click on play demo and let it sit for a few seconds. I am not sure what is wrong. I do have a custom kernel installed (ElementalX 0.05). I have used this on my Nexus 6p with no issues before but now it just doesn't work on my Pixel. I would like to uninstall it but do not know how to do that. Do I need to perform a full reset to the phone or is there another way to remove the mods and try to reinstall them?
EDIT: Finally got it to work. Came home and reflashed the stock boot.img to go back to stock kernel then reflashed ElementalX 0.05 and re-rooted and reinstalled the mod. Went into Viper and it started to work. Not sure why it wasn't working before but now it works 100%. Thanks again for the mod!

Hey would love to get this working however I seem to be having issues as well, I flashed the elementalx kernel then went through the install process as the instructions listed (using stericsons BusyBox) I note have dolby atmos and viper4android installed but neither are processing, I then read through these posts, checked that selinux was set to permissive (it is) and then cleared my audio_effects.conf that I found in the /etc/ folder and tried reinstalling via the script. Unfortunately still no processing from v4a. If you can think of anything else to check that would be awesome, v4a is the biggest thing I miss coming from my old note 4!
Sent from my Pixel XL using Tapatalk

Thanks for the great mod !
Dolby Works without any issues (except the demo)
Viper didn't work immediately with just on processing:no everything else was on yes , then it worked for a few minutes and went back to no.
I tested with Spotify and Play Music.
[edit]: It seems that it doesn't always know that music is playing and when it starts processing if the music finishes it stops again.
Compatible mode does nothing

exadeci said:
Thanks for the great mod !
Dolby Works without any issues (except the demo)
Viper didn't work immediately with just on processing:no everything else was on yes , then it worked for a few minutes and went back to no.
I tested with Spotify and Play Music.
[edit]: It seems that it doesn't always know that music is playing and when it starts processing if the music finishes it stops again.
Compatible mode does nothing
Click to expand...
Click to collapse
Thanks, ill try something to make the mod systemwide.
--->

I have been testing a lot, as there has been some instances of SystemUI crashing after flashing this, and other mods for that matter. I am adding to the op that at this stage it is advisable to have an unencrypted file system.
To achieve this you need to flash back to stock, (including data) and re root before you boot up into android.
I have also made some mods to the install package to modify vendor/build.prop as well as system/build.prop. This may have been an issue also.
If anyone has any more info on these systemui crashes that would be appreciated.
--->

DELETED
still getting systemui crash

Easiest way to go back to stock?
Sent from my Pixel XL using XDA-Developers mobile app

v2.2v said:
Easiest way to go back to stock?
Sent from my Pixel XL using XDA-Developers mobile app
Click to expand...
Click to collapse
I just pulled link. Just hold off for a bit. I got another systemui crash, but to flash back to stock, fastboot the stock firmware
-->

So i am still getting systemui crashes with these new changes and an un encrypted system... I am going to dumb down the audio mods to just v4a and dolby. and try that for a day,'
hold tight.
--->

So are there any people who have been running the mod successfully since yesterday?
If so i have one question.. have you activated SystemUItuner?
--->

SystemUI Crashes...
So after trying to figure out what he hell is wrong with my mods, ive gone to the SuperSU thread and have read people are having these crash issues, even with an unmodified system. So this is all related to root in general.
Looks like we are going to have to just wait for a fix on the root side of things..... ill be pulling links until there is an update to SuperSU
--->

Shouldn't be long, Chainfire is pretty active in the Pixel root thread and seems to be making some headway.

[EOL][ROM][7.0] RevivorOS v2.0

REVIVING THE LOVE FOR STOCK ROM. OPTIMISED STOCK ROM on the base of NPJS25.93-14-4 for MOTO G4/PLUS.
{
"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"
}
NOTE: This thread is best viewed on a desktop browser like Microsoft Edge/ Google Chrome/etc.
FEATURES:
1. FULLY DE-ODEXED by smali-2.2.0 and baksmali-2.2.0 .
2. FULLY DE-BLOATED
3. ZIP-ALIGNED ALL SYSTEM AND FRAMEWORK APPS
4. March 1 Security patch & Android Nougat 7.0
ALLEGED PERFORMANCE IMPROVEMENTS THAN STOCK NPJ25.93-14:
1. Faster in general UI performance.
2. Apps will use less storage and memory because the ROM is deodexed, debloated and zipaligned.
3. More battery efficiency as claimed by the update npjs25.93-14-4 + point 2.
4. A bit less of heating than stock owing to debloat.
DOWNLOADS:
1. TWRP 3.1 by @oadam11: Post 2 of Ground Zero ROMs thread for athene
2. ROM: Android File Host Link
3. SuperSU v2.79 SR3: [BETA]SuperSU v2.79 SR3 thread
4. Magisk v12 : Magisk Release Thread
5. Magisk Terminal Debloater v4 module/script: Download manually here from this Thread or from the Download section under Magisk Manager App.
6. ElementalX Kernel v1.04 for Stock N ROM: ElementalX Kernel thread for athene
7. Vegito Kernel v6.5 for Stock N ROM: Vegito Kernel Thread
INSTALLATION PROCEDURE:
1. Make appropriate backups in TWRP.
2. Wipe System, Data, Cache and ART Cache.
3. Install the ROM. (No need for GApps)
4. Reboot.
5. Update Google Play Store via tapping on version in Play store settings and after that update the Google Play services.
6. Update all the apps and reboot once.
NON-ROOTED. Why?
Simply because some people want MagiskSU and some want SuperSU. Moreover rooting would require changing the kernel to ElementalX or Vegito as there was no root exploit in stock N kernel.
BUGS:
1. Settings app MAY crash if you open the Apps section. If you want to configure the default apps tap the gear icon immediately.
Getting it to work is pure LUCK. Sorry I have no fix for it. Happens only to me idk why. No one else reported this.
ROOTING PROCEDURE:
WARNING: IF YOU DIRECTLY FLASH SOME SU MANAGER YOUR DEVICE WON'T BOOT.
1. Take appropriate backups in twrp (Boot partition recommended).
2. Flash ElementalX kernel v1.04 for Stock ROM or Vegito Kernel v6.5.
3. Reboot (Optional).
4. Flash your desired su manager (Magisk v12 or SuperSU v2.79 SR3).
5. Reboot (Incase of SuperSU boot process will loop once).
6. Update the Magisk Manager/ SuperSU from PlayStore(If needed).
IMPORTANT NOTES:
DON'T TRY INSTALLING ANY FUTURE OFFICIAL OTA FROM MOTOROLA ON THIS ROM. FLASH STOCK NOUGAT FROM HERE IF NEED BE. I have already removed the '3c_ota' app using the magisk terminal debloater script, although, if you get any update via the OTA app, don't try installing it.
SUBSTRATUM/OMS Support won't be possible on this ROM as it is based on prebuilt system images instead of some raw source code. Legacy mode may work with root. Do not report bugs for the same. I'm not responsible for the consequences of themeing.
This ROM will NOT upgrade your BOOTLOADER and PARTITION TABLE. They'll remain the same as NPJ25.93-14 (Dec 1 Patch) unless you had flashed the March 1 patch in stock recovery.
Hello moto sound and boot animation works fine
Credits/Thanks:
1. @kosmasgr for the TWRP backup.
2. @Swapney Raul for testing the ROM.
3. @oadam11 for TWRP 3.1.0
4. @Chainfire for SuperSU.
5. @topjohnwu for Magisk.
6. @veez21 for Magisk Terminal Debloater.
7. @flar2 for ElementalX kernel.
8. @Dreamstar for Vegito kernel
9. XDA for the amazing dev portal.
10. Motorola for the device. (Ik many of you hate Lenovo)
11. Google ofc for Android and the open source community.
12. Android File Host for hosting the downloads.
If I missed anyone..do PM for the same. :good:
Do check out the bootlogos/splash screens I have made for athene.
ADDITIONAL SUPPORT:
1. Custom ROM help thread.
2. For further assistance, you can message at Telegram: Personal or Community.
HIT THANKS IF YOU LIKED IT. :good:
XDA:DevDB Information
RevivorOS, ROM for the Moto G4 Plus
Contributors
tywinlannister7
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Stock N 93-14-4
Based On: Stock ROM
Version Information
Status: Stable
Created 2017-05-18
Last Updated 2019-11-22

Reserved :good:

Thanks ? and files manager works fine if u update the app.

Hi! Can I flash without wiping data if I'm already on stock NPJS25.93-14? Thanks!

A BIG NO
pblasi said:
Hi! Can I flash without wiping data if I'm already on stock NPJS25.93-14? Thanks!
Click to expand...
Click to collapse
No I would not recommend this. Since the apps are deodexed and zipaligned with many of them being removed. So this will create a problem on a dirty flash. Instead use Titanium Backup for apps and their respective data.

fr3d0x said:
Thanks and files manager works fine if u update the app.
Click to expand...
Click to collapse
Thanks for the heads-up :good:

Αwesome rom @tywinlannister7. Also i edited build prop , adding line ro.sf.lcd_density=410 before flashing and works excellent.
I have fc with file manager but there is no file manager ( strange ) and fc with appbox but also there is no this app
Wipe data and cache will solve the problem

tywinlannister7 said:
1. Moto File Manager and a few apps may give you Force Stops on first boot. If force stopping the app and then clearing its data and wiping cache (both)
FIX: Force Stop the apps>Clear Data>Update from Google Play>Wipe caches (both ) in twrp> Reboot
Click to expand...
Click to collapse
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?

kosmasgr said:
Αwesome rom @tywinlannister7. Also i edited build prop , adding line ro.sf.lcd_density=410 before flashing and works excellent.
I have fc with file manager but there is no file manager ( strange ) and fc with appbox but also there is no this app
Wipe data and cache will solve the problem
Click to expand...
Click to collapse
Deodexing and debloating might be a reason. These apps work in the background as system apps and create a bit of the force stop thing.

pblasi said:
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?
Click to expand...
Click to collapse
What model do you have? I have tested this on the indian xt1643. Although the base of the ROM is from the European model (Shouldn't make any difference imo).
Can you try disabling or uninstalling it? (Proceed with backup). If no help, I'll need a logcat and try to find a fix. I'm still a beginner and this is my first ROM after Lineage. ?

pblasi said:
I tried this, but still getting "Retail Config Service" FC at boot... Any ideas to get rid of it?
Click to expand...
Click to collapse
I got this error while setting up the device but after the setup it was gone haven't seen that error since then,do you get it often?

If i flash this from mm will my modem will change to nougat?

dedik46 said:
If i flash this from mm will my modem will change to nougat?
Click to expand...
Click to collapse
No

It would be nice if you could add substratum support

[email protected] said:
It would be nice if you could add substratum support
Click to expand...
Click to collapse
I think as this is a stock ROM we can't add Substratum commits in, though if I'm incorrect someone correct me!
Nice work by the way, tywinlannister7 good to see a TWRP flash of the latest security patch and OS!

Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???

diegomartinezlovey said:
is necessary flash official nougat before???
Click to expand...
Click to collapse
I think you should do so, ideally, so that your baseband and other firmware is at least on Nougat, before then wiping your device and then flashing this TWRP file as per the opening post.

diegomartinezlovey said:
Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???
Click to expand...
Click to collapse
You need to first flash the Dec 1 path update then this so that all things work.

echo92 said:
I think as this is a stock ROM we can't add Substratum commits in, though if I'm incorrect someone correct me!
Nice work by the way, tywinlannister7 good to see a TWRP flash of the latest security patch and OS!
Click to expand...
Click to collapse
As far as I know we can add using small editor but it's a hard job so no one does that.

diegomartinezlovey said:
Thanks for this stock rom just only two question....Is RetBR base or wich?? is necessary flash official nougat before???
Click to expand...
Click to collapse
I had used the system and boot dump from the reteu model owned by @kosmasgr . But the ROM should work fine as long as you have updated to Nougat NPJ25.93-14 or above.

[MOD] FCS Xperia X OREO

{
"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"
}
Main advantages
- Best performance at all temperatures (50 ~ 70% faster than stock)
- Less heat (especially during moderate / intense use -5 ~ 10 ° C)
- Maintains very good performance for long periods of time
- Faster cooling
- Overheating has been deactivated
- Do not heat device while in sleep mode
- System improvements and Soc qualcomm
- Optimized CPU and gpu for Soc qualcomm control
- No overheating when used and device charged
- System and kernel functions were fixed
- Add support init.d stock
Requirements
- Xperia X F5121 & F5122
- Compilation 34.4.A.2.70
- Firmware 8.0
- Install busybox
- Twrp
- Magisk 16
- it is unknown if it works for SuperSU
Installation
Attention: it is not authorized under any circumstance to lodge the files of this mod in another cloud of storage, you can add this thread to your post
- Turn off your device
- Enter twrp
- Install - Xperia_X_Thermal_Oreo_Compilation_70.zip
- Before restarting, perform the following steps
- Twrp
- Wipe
- Slide to factory reset
- Advanced cleaning
- Option:
- Dalvik / ART Cache
- Cahe
- Data
- Slide to clean
- Reailize the installation of - initd_magisk.zip
- ready restart and configure your device
- Once the configuration is finished, turn off your device
- and restart the first few times when your device starts, leave it for 2 to 3 minutes and unlock it and go
Now to enjoy your device without worrying that hot :laugh:
credits: @korom42 or its magisk module although it is adapted for the Xperia X

Faq
- will work in another compilation
you can try but it is based on the compilation 34.4.A.2.70 that you probably bootloop
- It is necessary to perform the cleanup with twrp and reestablish my device
if it is necessary for the changes to be applied correctly
- I can upload it to my personal storage cloud
no, but you can place the thread on this topic without any problems
- Works for Android Nougat
Do not

Reserved

It doesn't need Magisk and some suspicious module, I think. Any app which can emulate init.d (like Kernel Adiutor) will work just fine.

How do I know it works?
I installed it in a clean rom, but the phone heats up normally as expected, as data: install the magisk file and I throw error, followed the steps to the letter

winsters said:
I installed it in a clean rom, but the phone heats up normally as expected, as data: install the magisk file and I throw error, followed the steps to the letter
Click to expand...
Click to collapse
the device does not heat up if you follow the steps as you re-check the installation and it will last for 2 weeks

Bootloop wheb used on xgen rom 1.07. . Did I do something wrong

Does this mod also work with Omni Rom Oreo?

Hmm, I found only the 1st thing I'm unable to install, I can install the main FCS thing but it's a no go on the initd magisk thing.. it doesn't install....

lilbrat said:
Hmm, I found only the 1st thing I'm unable to install, I can install the main FCS thing but it's a no go on the initd magisk thing.. it doesn't install....
Click to expand...
Click to collapse
The same here

PNIGGE said:
The same here
Click to expand...
Click to collapse
Copy to internal sd (crucial). Install the zip. Enable init.d using kernel adiutor. Restart phone. Profit.

I was having some weird issues with the mod where the init.d scripts wouldn't run neither with the module suggested in OP nor through Kernel Adiutor and was also tired of having to reflash the mod every time a new security update was released, so I went in and made a pure Magisk version of the mod (attached on this post).
This Magisk version is exactly the same as the OP, the only difference is that it's now a Magisk Module (so it applies systemlessly) and that you don't need busybox nor any kind of init.d support for it to work (the init.d scripts from the mod are executed directly through Magisk late_start hook instead). Download the ZIP, install through Magisk Manager, reboot and done.

mbc07 said:
I was having some weird issues with the mod where the init.d scripts wouldn't run neither with the module suggested in OP nor through Kernel Adiutor and was also tired of having to reflash the mod every time a new security update was released, so I went in and made a pure Magisk version of the mod (attached on this post).
This Magisk version is exactly the same as the OP, the only difference is that it's now a Magisk Module (so it applies systemlessly) and that you don't need busybox nor any kind of init.d support for it to work (the init.d scripts from the mod are executed directly through Magisk late_start hook instead). Download the ZIP, install through Magisk Manager, reboot and done.
Click to expand...
Click to collapse
How would the installation process differ from OPs instructions with this Magisk module?

CntrlAltDel45 said:
How would the installation process differ from OPs instructions with this Magisk module?
Click to expand...
Click to collapse
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.

mbc07 said:
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.
Click to expand...
Click to collapse
Thank you. I used the second method you mentioned. Everything went by seamlessly.

mbc07 said:
You have two options:
1) Boot into TWRP and flash the attachment from my previous post (works only if you already have Magisk installed and working!), then reboot when done.
2) Open Magisk Manager, go to Modules, click the + button, locate the attachment from previous post, then reboot when done.
That's it. You don't need to flash/install anything else.
Click to expand...
Click to collapse
Used the 2nd method, but there's a problem: after 2 minutes in stand by from the restart of the phone, it restarted by itself...
What's the problem? Need a dalvik/cache wipe after the installation with Magisk? Is it incompatible with Xposed framework (installed on my phone)? Or maybe the compilation base (I'm on fw .118) is different and cause bootloop...
Thanks in advance.
Edit: I used the first method, I had an installation without restart, but it doesn't work!

will it work with .118 rom?

AlexUnder2010 said:
will it work with .118 rom?
Click to expand...
Click to collapse
No! But you can get the right file at this link: https://mega.nz/#F!DZAGDY6B!d6CeWtv-tqD0RHtsOHS02w
When you open the folder, find and download fcs thermal v. 1.3. Then install through twrp.
I've installed on stock rom .118 and works great

Niquillo said:
No! But you can get the right file at this link: https://mega.nz/#F!DZAGDY6B!d6CeWtv-tqD0RHtsOHS02w
When you open the folder, find and download fcs thermal v. 1.3. Then install through twrp.
I've installed on stock rom .118 and works great
Click to expand...
Click to collapse
It's for Nougat only ??*

[ROM][P905][UNOFFICIAL] CrDroid-5.10 | Android 9.0 20191113

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
This firmware was developed for the p905. It doesn't apply to the p905v at this time because it's bootloader locked and a custom recovery isn't possible.
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
I'm using nano gapps.
{
"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"
}
Features
https://github.com/crdroidandroid/crdroid_features/blob/9.0/README.mkdn
Instructions
1. Install custom recovery
2. Download the zip(s) - firmware and Google Apps additional package (optional)
3. Backup all partitions (it least efs) and store somewhere - it need to do - because you can loose imei
4. Full wipe all
5. Flash firmware and gapps
Work
All
Known Issues
Rotate buggy a bit
Links:
CrDroid Builds
6. 20191113: november security patch: https://drive.google.com/file/d/1Pfu7y84PAaI4zydNm-Yo9GqcCvK0yOwP/view?usp=sharing
5. 20191023: october security patch: https://drive.google.com/file/d/12-h2_sWcYKQUp_Q0gU7j9NlFMTGmM5Rp/view?usp=sharing
4. 20190812: august security patch: https://drive.google.com/file/d/1yq0q2Va6LkavCKiNBO3yqKP-IRkL8MOh/view?usp=sharing
4. 20190708: july security patch, kernel up to orignal msm8974 lineage kernel, small sensors update: https://drive.google.com/file/d/1sDZ9FplHpiGyyuE19BFtdvYsgNNcF2yE/view?usp=sharing
3. 20190528: may security patch: https://drive.google.com/file/d/1ch9ehxLL8jUylr2X1w55MKUDmikhYAiW/view?usp=sharing
2. 20190219: fix flip, fix mic gain: https://drive.google.com/file/d/1BwhkVYPwzrq8ELHE3q_MhhuCejd2BY4E/view?usp=sharing
1. 20190217: https://drive.google.com/file/d/1w7QjUyuTt4YEdBi4RySbmaZg_g3j26ZH/view?usp=sharing
Gapps
https://opengapps.org
Recovery
Use official 3.0.2-0 version from: https://twrp.me/samsung/samsunggalaxynotepro122qcom.html
or use my twrp version: https://forum.xda-developers.com/galaxy-note-pro-12/development/recovery-twrp-3-1-1-0-t3684802
Sources
Sources: https://github.com/crdroidandroid
Device: https://github.com/Valera1978/android_device_samsung_viennalte
Kernel: https://github.com/Valera1978/android_kernel_samsung_msm8974
Vendor: https://github.com/Valera1978/android_vendor_samsung_viennalte
Thanks
Thanks to CrDroid team
Thanks to LineageOS team

Thank you very much just flashed it on my P905 running good so far!

Is P905 compatible with P900? I'm not familiar with the pertinent diffrences, if any.

I have recognized 3 things :
The notification ton is playing endless in a loop (e. g. happen after install the App (Battery Charge Limit) and connect the Power.... also after reboot :if the charging Level reached... also after reboot: from the trustagebt
The Mic gain is too low for : sound recorder, recorder from WhatsApp, Phone application from WhatsApp, Livechat(Audio) from Postident.
I try the app Microphone Amplifier. Till a little Mic gain was added, the Record in this app was. ok. Without gain, the volume was to low. Uncomfortable there is. no way to save the gain in the System out from this app.
OK Google for example works without any issues
The P905 does not react anymore of the magnet Flip from the cover to switch the screen on/off

dwkindig said:
Is P905 compatible with P900? I'm not familiar with the pertinent diffrences, if any.
Click to expand...
Click to collapse
Unfortunately P900 and P905 has differ hardware (exynos 5420 vs qcom 800). It's not compatible.

mad0701 said:
I have recognized 3 things :
The notification ton is playing endless in a loop (e. g. happen after install the App (Battery Charge Limit) and connect the Power.... also after reboot :if the charging Level reached... also after reboot: from the trustagebt
The Mic gain is too low for : sound recorder, recorder from WhatsApp, Phone application from WhatsApp, Livechat(Audio) from Postident.
I try the app Microphone Amplifier. Till a little Mic gain was added, the Record in this app was. ok. Without gain, the volume was to low. Uncomfortable there is. no way to save the gain in the System out from this app.
OK Google for example works without any issues
The P905 does not react anymore of the magnet Flip from the cover to switch the screen on/off
Click to expand...
Click to collapse
Thanks for feedback.
Flip - I missed that moment, when I added fixes in kernel for p905. Evening will check flip and build
Audio - look like I took a bit more, already discarded audio fixes. Will check today evening.
playing endless in a loop - need to check it in logs, a bit later, may be today\tomorrow.

Valera1978 said:
Thanks for feedback.
Flip - I missed that moment, when I added fixes in kernel for p905. Evening will check flip and build
Audio - look like I took a bit more, already discarded audio fixes. Will check today evening.
playing endless in a loop - need to check it in logs, a bit later, may be today\tomorrow.
Click to expand...
Click to collapse
Hi Valera, it doesn't flash in my device (a p905 that worked well with your previous images). It says:
E3004: This package is for device: viennalte, viennaltexx; this device is .
Updater process ended with ERROR: 7
Error installing zip file ...
I wiped it before, but still it doesn't work.

ultraradical said:
Hi Valera, it doesn't flash in my device (a p905 that worked well with your previous images). It says:
E3004: This package is for device: viennalte, viennaltexx; this device is .
Updater process ended with ERROR: 7
Error installing zip file ...
I wiped it before, but still it doesn't work.
Click to expand...
Click to collapse
This is twrp question (it cannt return name). Look like you have old one.
In any way - right now you can remove check:
extract from crDroidAndroid-9.0-20190217-viennalte-v5.1.zip file: \META-INF\com\google\android\updater-script
remove first 2 lines (assert(getprop("ro.produ......................................)
and add updated updater-script back in archive

Valera1978 said:
This is twrp question (it cannt return name). Look like you have old one.
In any way - right now you can remove check:
extract from crDroidAndroid-9.0-20190217-viennalte-v5.1.zip file: \META-INF\com\google\android\updater-script
remove first 2 lines (assert(getprop("ro.produ......................................)
and add updated updater-script back in archive
Click to expand...
Click to collapse
Thanks. I opted for installing your TWRP and now it does flash and everything works very well (including hotspot), except the microphone which records too low (I suggest you to look for noise cancelation problems).

I believe, I must check, which version I've installed CM or CRDrois... I'm not sure in this moment... Both versions were released at the same time

OK, the first flash from yesterday was CM.
Today I try this Rom:
Simular with sound loop, if I connect the Power for charging (Google is updating all Apps) Only chance to get it silent : push all to 0 (sounds) the tone is parallel to all other sounds.
With this rom I haven't get Magisk Manager to defekt root (Magisk 18.1). It wasn't an issue with CM. With this rom the manager doesn't detect root???
Maybe it's about the app SuperSu from Playstore? Haven't test it right now. I just flash the ROM one again (wipe cache/data/dalvik) Internal SD not. With CM wasn't it possible to mount an USB Stick via OTG cable.
I try to install SuperSU (root & app) afterwards and also to mount an external USB.......

Short update ;
In this rom I can disable the charging notification... (CrDroid settings, near on right hand) the loop is away... that's the good news.
The bad one : I don't receive root access : nor via SuperSu nor via Magisk... Any Hints? A short time I could see teh root settings in the Dev menu, but the corresponding apk did not see root in anycase

mad0701 said:
Short update ;
In this rom I can disable the charging notification... (CrDroid settings, near on right hand) the loop is away... that's the good news.
The bad one : I don't receive root access : nor via SuperSu nor via Magisk... Any Hints? A short time I could see teh root settings in the Dev menu, but the corresponding apk did not see root in anycase
Click to expand...
Click to collapse
Yes, in CrDroid no root options in devs.
But latest Magisk is working great. Install latest Magisk 18.1, then boot and manually install Magisk Manager apk file.
You can do check "safery net" in the magisk manager - it will complete pass.
P.s. mic fixed, flip should fixed too (but I cannt check it right now) - I can make small update for draft check.

Valera1978 said:
Yes, in CrDroid no root options in devs.
P.s. mic fixed, flip should fixed too (but I cannt check it right now) - I can make small update for draft check.
Click to expand...
Click to collapse
I would be interested in an update to check flip cover.
Thanks a lot for continuing the work for that great tablet!

Valera1978 said:
But latest Magisk is working great. Install latest Magisk 18.1, then boot and manually install Magisk Manager apk file.
.....
Click to expand...
Click to collapse
I have used the same Version.... but the Manager 7.0 doesn't detect the Root (18.1) . I have flashed 18.1 some times, reboot ... the Manager didn't saw root. I checked this 3 times ... in between the CM Version ... no luck ?!?!?
Does you install root systemless or let you TWRP patch the System partion ?

Just installed this, Netflix doesn't seem to be working. Can't install it from the play store. (The app is not compatible with this version)

Mad07 said:
I have used the same Version.... but the Manager 7.0 doesn't detect the Root (18.1) . I have flashed 18.1 some times, reboot ... the Manager didn't saw root. I checked this 3 times ... in between the CM Version ... no luck ?!?!?
Does you install root systemless or let you TWRP patch the System partion ?
Click to expand...
Click to collapse
Just checked in the latest 20190219:
1. install crdroid, magisk
2. load into the firmware. install the magisk manager
3. back to recovery and reinstall magisk
4. load firmware

Yesterday, I forgot my eyeglas at work... so only reflash a backup was possible.
In the evening, I give the 19.02 Version a new try.
I'll believe, I know why Magiask Manager didn't see the root: There was also a Bug-Report in the Magisk-Thread, that, if the old Manager is in the Background, the new Manager didn't see Root. On other Hand, I've read, that Magisk dedect root simular as SuperSu. The SuperSu Manager was automaticaly installed from Google Store during Setup the P905 at the first Startup.... I don't should Forget to uninstall SuperSu after first boot
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
Bluewave653 said:
Just installed this, Netflix doesn't seem to be working. Can't install it from the play store. (The app is not compatible with this version)
Click to expand...
Click to collapse
Same as it was in CM 18 (Orego) I've download the apk direct form Netflix ( you can found the link via help on the Netflix HP )
https://netflixhelp.s3.amazonaws.com/netflix-4.16-200217-release.apk

New try with Version 2
Magisk is woerking after uninstall SuperSu
FlipCover Witz Magnet works
Problems:
After each reboot, the Tablett forgot the Standard Launcher (Nova) and New keyboard(Swiftkey)
If the Tablett shoot down with power cable, the shoot down looks like a litte bit irretation
Also it is not possible to Boot the Tablett Düring active charging.
The charging loop sound just be disabled in the settings
Netflix was installed Form the APP store before rooting, hide Magisk, an nupdate was received, working
Thats the first impression after a few Minuten

Usb OTG looks like, that it doesn't work.
There is in this moment no reaction, if I insert an USB with an OTG cable.
Maybe I must change something in the Dev-Settings?
Gesendet von meinem SM-P905 mit Tapatalk
---------- Post added at 06:17 AM ---------- Previous post was at 05:33 AM ----------
The notification Ton has a problem at all, not only with the charging cable. If a notification occurred, the ton is playing in a loop till I pull down the tiles/notification from the top.
I would expect, that this ton is played only one time