Is there any way to install Viper4Android on Android Oreo? Rooted ofc.
Gesendet von meinem Pixel XL mit Tapatalk
I installed by
1. Boot the Android O TWRP mod while in bootloader
2. Flash the SU config Aroma zip
2.5. Left all settings at Let Device Decide except changed to Permissive
3. Flash Super SU SR3
4. Flash Root Hide
5. Reboot to System
6. Boot the Android O TWRP mod from bootloader
7. Flash the 08-11 Arise zip
After that it was processing on opr6 and safetynet is passing.
Forgot to mention that first I deleted almost 400 mb of apps from /system/app. All the keyboards for other languages and some Google apps that can be downloaded from the Play Store.
Thanks.
Gesendet von meinem Pixel XL mit Tapatalk
I'm really bummed that nothing has been done for audio quality on Oreo besides providing bluetooth codecs that require hardware to net licensing fees. Viper has been out for years now blowing stock audio out of the water. How long do we have to wait to even have half of the quality increase added from Viper.
cmo220 said:
I installed by
1. Boot the Android O TWRP mod while in bootloader
2. Flash the SU config Aroma zip
2.5. Left all settings at Let Device Decide except changed to Permissive
3. Flash Super SU SR3
4. Flash Root Hide
5. Reboot to System
6. Boot the Android O TWRP mod from bootloader
7. Flash the 08-11 Arise zip
After that it was processing on opr6 and safetynet is passing.
Forgot to mention that first I deleted almost 400 mb of apps from /system/app. All the keyboards for other languages and some Google apps that can be downloaded from the Play Store.
Click to expand...
Click to collapse
Do you have a link for the Arise.zip?
cmo220 said:
I installed by
1. Boot the Android O TWRP mod while in bootloader
2. Flash the SU config Aroma zip
2.5. Left all settings at Let Device Decide except changed to Permissive
3. Flash Super SU SR3
4. Flash Root Hide
5. Reboot to System
6. Boot the Android O TWRP mod from bootloader
7. Flash the 08-11 Arise zip
After that it was processing on opr6 and safetynet is passing.
Forgot to mention that first I deleted almost 400 mb of apps from /system/app. All the keyboards for other languages and some Google apps that can be downloaded from the Play Store.
Click to expand...
Click to collapse
it doesn't say su binary occupied for you when you changed it to permissive ? mine did and lost root access
Here's the link to the 08-11 file. I had to use Root Explorer and change system to r/w to get it to actually install and show the Viper app.
cmo220 said:
I installed by
1. Boot the Android O TWRP mod while in bootloader
2. Flash the SU config Aroma zip
2.5. Left all settings at Let Device Decide except changed to Permissive
3. Flash Super SU SR3
4. Flash Root Hide
5. Reboot to System
6. Boot the Android O TWRP mod from bootloader
7. Flash the 08-11 Arise zip
After that it was processing on opr6 and safetynet is passing.
Forgot to mention that first I deleted almost 400 mb of apps from /system/app. All the keyboards for other languages and some Google apps that can be downloaded from the Play Store.
Click to expand...
Click to collapse
I've done this multiple times, v4a will show enabled and processing before I try to play anything. Once I play music or whatever, it'll go to not processing abnormal status.
evilryry said:
I've done this multiple times, v4a will show enabled and processing before I try to play anything. Once I play music or whatever, it'll go to not processing abnormal status.
Click to expand...
Click to collapse
mine is the opposite.
lost root access but viper4android is working. i need both to work lol
{
"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"
}
TheUndertaker21 said:
it doesn't say su binary occupied for you when you changed it to permissive ? mine did and lost root access
Click to expand...
Click to collapse
I didn't have that problem. I did it from a clean install but I have no idea if that would help with that problem.
cmo220 said:
I didn't have that problem. I did it from a clean install but I have no idea if that would help with that problem.
Click to expand...
Click to collapse
Had that, when I was trying to install Viper some time ago, I had to completly clean install EVERYTHING, then it worked.
Gesendet von meinem Pixel XL mit Tapatalk
What you all could try, is reinstall superSU stuff, and select Permissive, and dont let Aroma decide.
Gesendet von meinem Pixel XL mit Tapatalk
I got it working.. by playing around aimlessly. I was able to break it while working and get it working again without rebooting.. I don't really know how long it's gonna work for. With arise magnum opus 8-11.
In my case, I use core+v4a 2.5+atmos. It would initially show processing and supported until I played something and then it would break.
Well a few minutes ago I was playing around with YouTube, and I noticed it was louder than normal. My speaker Xtra loud setting was turned on. I could turn it on and off and hear a difference in audio like it was working. Then I put my headphones on and bam it was working. Then I tried to open Dolby and it force closed and my music went all choppy. I looked back at v4a driver status showing not processing and abnormal status. I manually force stopped v4a, and both Dolby apps. Opened Dolby without playing any music and I was able to set my desired settings. Played music again and did the little speaker trick above (unsure if it matters or a fluke) and it was working. Put headphones back on and it's still working normally. Hopefully it'll last! It's been working as of right now about 20 minutes. My selinux is also set to permissive and supersu is working just fine. I've been working on this since last night, it's been frustrated. Lets hope it continues to work.
evilryry said:
I got it working.. by playing around aimlessly. I was able to break it while working and get it working again without rebooting.. I don't really know how long it's gonna work for. With arise magnum opus 8-11.
In my case, I use core+v4a 2.5+atmos. It would initially show processing and supported until I played something and then it would break.
Well a few minutes ago I was playing around with YouTube, and I noticed it was louder than normal. My speaker Xtra loud setting was turned on. I could turn it on and off and hear a difference in audio like it was working. Then I put my headphones on and bam it was working. Then I tried to open Dolby and it force closed and my music went all choppy. I looked back at v4a driver status showing not processing and abnormal status. I manually force stopped v4a, and both Dolby apps. Opened Dolby without playing any music and I was able to set my desired settings. Played music again and did the little speaker trick above (unsure if it matters or a fluke) and it was working. Put headphones back on and it's still working normally. Hopefully it'll last! It's been working as of right now about 20 minutes. My selinux is also set to permissive and supersu is working just fine. I've been working on this since last night, it's been frustrated. Lets hope it continues to work.
Click to expand...
Click to collapse
Great, but try restarting your phone.
See if you either get it working instantly, or maybe you have to do your workarounf thing again.
Gesendet von meinem Pixel XL mit Tapatalk
Ammonarrow said:
Great, but try restarting your phone.
See if you either get it working instantly, or maybe you have to do your workarounf thing again.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Rebooted and it's working immediately without any extra encouragement. Guess it finally clicked. I'm honestly not sure what I did. But I'm not gonna argue with it lol
If anyone else is struggling and frustrated give my other post a read and start playing and tinkering to see if you guys can get it too. It was really random things I did there was no process I followed or anything. On my old 6p that's on Oreo too i flashed arise and it worked immediately no tinkering necessary but I've been working on getting it going on my XL from 8pm-1am last night and about 10am-3pm today lol. Good luck everyone else who is having trouble
Got it, download this app: https://forum.xda-developers.com/showthread.php?t=2524485
Then select permissive in here, and let it do its job.
After that, taskkill Viper, and play Music, open Viper and there you go.
SuperSu is not affected by this.
Gesendet von meinem Pixel XL mit Tapatalk
evilryry said:
Rebooted and it's working immediately without any extra encouragement. Guess it finally clicked. I'm honestly not sure what I did. But I'm not gonna argue with it lol
If anyone else is struggling and frustrated give my other post a read and start playing and tinkering to see if you guys can get it too. It was really random things I did there was no process I followed or anything. On my old 6p that's on Oreo too i flashed arise and it worked immediately no tinkering necessary but I've been working on getting it going on my XL from 8pm-1am last night and about 10am-3pm today lol. Good luck everyone else who is having trouble
Click to expand...
Click to collapse
I guess, its (somehow, and who knows why) random, which SELinux Mode it selects. I guess that is whats breaking it.
Gesendet von meinem Pixel XL mit Tapatalk
Ammonarrow said:
Got it, download this app: https://forum.xda-developers.com/showthread.php?t=2524485
Then select permissive in here, and let it do its job.
After that, taskkill Viper, and play Music, open Viper and there you go.
SuperSu is not affected by this.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Did you get yours working doing it that? I don't bother with that app btw, you can use permissive zip so it'll set permissive on boot without messing with an app.
https://www.androidfilehost.com/?fid=23991606952602503.
Permissive isn't supposed to matter but in my case I found with atmos it worked better with permissive rather than enforcing so it's why I use it but give it a shot if you want.
evilryry said:
Did you get yours working doing it that? I don't bother with that app btw, you can use permissive zip so it'll set permissive on boot without messing with an app.
https://www.androidfilehost.com/?fid=23991606952602503.
Permissive isn't supposed to matter but in my case I found with atmos it worked better with permissive rather than enforcing so it's why I use it but give it a shot if you want.
Click to expand...
Click to collapse
Yes, worked for me.
But the App has a script, which Autostarts. Plus the app instantly changes it, without having to restart.
Gesendet von meinem Pixel XL mit Tapatalk
Ammonarrow said:
Yes, worked for me.
But the App has a script, which Autostarts. Plus the app instantly changes it, without having to restart.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Ah, whatever works for you man
Related
I was updating pokemon go to version 0.37.0 and then the app shows me this error
{
"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:The Device In The Photo Is Not Mine
NOTE: I Dont Have Root or Custom Rom On My Device
I asked this here because I have Elephone P8000
and for my friend it work and he Dont has root or custom reovery quite like me (BUT HE DONT HAS ELEPHONE P8000)
Please help me!!!
new update... (0.39.0) now I has another problem here is a screen shot:
NOTE : I am using a google account
and I think that I know why this happening to me and others that has this new problem because of that I cant pass the google saftynet test
I think that you cant pass too if you wanna test just download the app from this link:https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample&hl=en
NOTE: IF YOU DONT PASS , then that's why the other problem happens to you that's something I know about that.
more information : In the test what I got is X and SafetyNet request: success , response vaildation: success , CTS profile match :false
Try your best to help me and all the others in the two problems!:victory::good:
I'd also love an answer to this, there must be a ROM that we can use? I unrooted but that wasn't enough.
This "error" is caused by a rooted phone and the latest appupdate. Unroot the phone and you can play the game again. https://support.pokemongo.nianticlabs.com/hc/en-us/articles/221958248
Gesendet von meinem p8000 mit Tapatalk
alandur said:
This "error" is caused by a rooted phone and the latest appupdate. Unroot the phone and you can play the game again.
Gesendet von meinem p8000 mit Tapatalk
Click to expand...
Click to collapse
Hi there,
Same problem Here. My Elephone P8000 is not rooted, when I bought it, it came without ROOT. I've checked with ROOT CHECKER and actually says it is not rooted, but the problem is there, so the solution is not to unroot the phone because it isn't... Sooooo any advice for all the people who are suffering this problem?
Same Problem. P8000 is not rooted. Checkt by Root Checker.
Android 5.1 installed.
Kernal : 3.10.65
Baseband-Version : MOLY.LR9.W1444.MD.LWTG.MP.V16.P10
Build-Nummer :
ALPS.L1.MP3.V2_NB6753.65U.L1_P22
Custum build Version
Elephone_P8000_20160319
Can anyone play the Pokémon Go Version 0.37.0 with the P8000?
alandur said:
This "error" is caused by a rooted phone and the latest appupdate. Unroot the phone and you can play the game again. https://support.pokemongo.nianticlabs.com/hc/en-us/articles/221958248
Gesendet von meinem p8000 mit Tapatalk
Click to expand...
Click to collapse
I Dont have root You know that! (I worte that)
ghostger said:
same problem. P8000 is not rooted. Checkt by root checker.
Android 5.1 installed.
Kernal : 3.10.65
baseband-version : Moly.lr9.w1444.md.lwtg.mp.v16.p10
build-nummer :
Alps.l1.mp3.v2_nb6753.65u.l1_p22
custum build version
elephone_p8000_20160319
can anyone play the pokémon go version 0.37.0 with the p8000?
Click to expand...
Click to collapse
wow i am not the only one that have that problem.....
Steve571 said:
I'd also love an answer to this, there must be a ROM that we can use? I unrooted but that wasn't enough.
Click to expand...
Click to collapse
this will help you? http://www.androidpolice.com/2016/09/11/guide-play-pokemon-go-0-37-rooted-android-magisk/
NOTE: ROOT YOR DEVICE AGAIN BEFORE YOU USING THIS SOLUTION!
NOTE : I Dont Want To Root My Device That's Why this thread is not closed
liraz747 said:
this will help you?
NOTE: ROOT YOR DEVICE AGAIN BEFORE YOU USING THIS SOLUTION!
NOTE : I Dont Want To Root My Device That's Why this thread is not closed
Click to expand...
Click to collapse
No, I have tried that, something else (I think unofficial ROM) is causing it to fail.
Steve571 said:
No, I have tried that, something else (I think unofficial ROM) is causing it to fail.
Click to expand...
Click to collapse
I hope That Someone with knowledge will come soon.
Still no fix?
I'm using Blueflames Cyanogenmod and find a way to make PG working on my rooted P8000.
1. Install SManager from Playstore.
2. Download the attached Script from cyanogenmod forum.
3. Check if the path to the su binaries is correct.
4. If it is not running, try to set the Script in non daemon mode. If it's working than edit line 6 of the Script from if['$1"!="-D]; then to if['$1"="-D]; then. This is how the script works on Blueflames Cyanogenmod.
5. Add the Script to SManager and enjoy.
Most Questions that can come up are answered in the thread at the cyanogenmod forum.
hth
Cheers
jknarf said:
Still no fix?
I'm using Blueflames Cyanogenmod and find a way to make PG working on my rooted P8000.
1. Install SManager from Playstore.
2. Download the attached Script from cyanogenmod forum.
3. Check if the path to the su binaries is correct.
4. If it is not running, try to set the Script in non daemon mode. If it's working than edit line 6 of the Script from if['$1"!="-D]; then to if['$1"="-D]; then. This is how the script works on Blueflames Cyanogenmod.
5. Add the Script to SManager and enjoy.
Most Questions that can come up are answered in the thread at the cyanogenmod forum.
hth
Cheers
Click to expand...
Click to collapse
Does this still work for you?
Still working with root.
jknarf said:
Still working with root.
Click to expand...
Click to collapse
Which Superuser app do you use? Somehow I don´t get it to work
I use the cyanogenmod built in super user app, but it should work with Chainfires SU too.
I just don't get it to work it would be super awesome if you could Upload your edited Skript. Probably it could solve it
That simple app worked for me
"root switch" apk from https://www.asus.com/zentalk/tw/for...wNDk1fGJmMjhjZGZifDE0NzY0MDUzNjB8MHwxNzM1NDI=
Okay, it's update time.
This night there comes the PokemonGo 0.43.4 and the previous work around with the script will not work any longer.
So there are two ways afaik, that make PoGo work again.
1. If simply SuperUser on a stock ROM installed, you may have luck with the latest 'root switch' , version 1.3.3.2, from chakalaca at zentalk
http://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=173542&page=37#pid962740
2. Use the latest Magisk, that will make it too.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Magisk Manager and the latest phh SuperUser and install the zips with TWRP or any other recovery.
Now comes the tricky part.
You have to remove every other sign of SuperUser from other installation. Often it is enough to use the unroot option of the installed SuperUser app, but if you have Cyanogenmod, or an Cyanogenmod based ROM, installed you need to remove the su binaries by hand. Best way for me is, to remove the su binaries use the recovery and adb. The su binary is located in /system/bin or /system/xbin. You need to mount the sytem partition rw but that should be an easy task with TWRP. And, Cyanogenmod Users, don't forget to disable builtin root first.
Cheers
jknarf said:
Okay, it's update time.
This night there comes the PokemonGo 0.43.4 and the previous work around with the script will not work any longer.
So there are two ways afaik, that make PoGo work again.
1. If simply SuperUser on a stock ROM installed, you may have luck with the latest 'root switch' , version 1.3.3.2, from chakalaca at zentalk
http://www.asus.com/zentalk/tw/forum.php?mod=viewthread&tid=173542&page=37#pid962740
2. Use the latest Magisk, that will make it too.
http://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Magisk Manager and the latest phh SuperUser and install the zips with TWRP or any other recovery.
Now comes the tricky part.
You have to remove every other sign of SuperUser from other installation. Often it is enough to use the unroot option of the installed SuperUser app, but if you have Cyanogenmod, or an Cyanogenmod based ROM, installed you need to remove the su binaries by hand. Best way for me is, to remove the su binaries use the recovery and adb. The su binary is located in /system/bin or /system/xbin. You need to mount the sytem partition rw but that should be an easy task with TWRP. And, Cyanogenmod Users, don't forget to disable builtin root first.
Cheers
Click to expand...
Click to collapse
do there is a way without root ?
and if not, do there is a way to root without recovery?
please reply
PoGo should work, if there is really no root. You can check with a file manager of there is a su binary in /system/bin or /system/xbin.
If there is a su binary, you need to delete it.
{
"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.
Latest update: 2018-06-12 To view a changelog, you can visit https://review.lineageos.org/#/q/status:merged+branch:cm-14.1 for a rough idea up to the build date.
Hi all. I was able to compile this stock build of LOS 14.1 thanks to the efforts/hard works of Skrilax_CZ, bhb27, the folks who created RR, and those over at Lineage OS/CyanogenMod. It takes some minor features from RR (i.e. notification light, some tiny performance/battery tweaks, and the ability to install Motorola apps). It is otherwise stock LOS 14.1 and I use this daily. The other authors/devs and I assume no responsibility if you damage your device somehow.
Please don't feel pressured to update any more often than you wish .
Notes:
In order to make my calling work for Verizon, I had to go under Settings -> More -> Cellular networks -> Preferred network type, and select LTE/CDMA (not LTE/GSM/UMTS). I assume GSM users should be fine with the defaults.
Also if on Verizon, you should most likely select VZWINTERNET as your APN under Settings -> More -> Cellular networks -> Access Point Names (might not show up at first, but eventually loads)
My recommendations to install:
Install TWRP if you haven't already
3.1.1 - https://www.androidfilehost.com/?w=files&flid=39562 (forum:http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308)
Perform a backup of your current system/ROM (if coming from another ROM).
Perform a factory reset/wipe (if coming from another ROM).
Install the .zip
Install the appropriate google apps.
http://opengapps.org/. I would think nano or micro is best, ARM, and 7.1
Wipe dalvik/art cache if you install another kernel. I highly recommend BHB27 kernel
https://www.androidfilehost.com/?w=files&flid=135512
Reboot and enjoy
Here is the link to the latest ROM on the hosting website:
[2018-06-12]https://androidfilehost.com/?fid=746163614322270411
Previous Builds:
https://www.androidfilehost.com/?w=files&flid=128790
Optional Components:
Remove SU/Root: https://mirrorbits.lineageos.org/su/addonsu-remove-arm-signed.zip (Lineage OS extras:https://download.lineageos.org/extras)
BHB27 Kernel: https://www.androidfilehost.com/?w=files&flid=135512 (forum:http://forum.xda-developers.com/moto-maxx/development/kernel-bhb27-kernel-t3207526)
BHB27 Kernel Adiutor: https://www.androidfilehost.com/?w=files&flid=48767
iSU: https://www.androidfilehost.com/?w=files&flid=120360 (forum:http://forum.xda-developers.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348)
TurboToast: https://play.google.com/store/apps/details?id=com.bhb27.turbotoast
I'll be back to post updates fairly regularly (~ every few weeks), but I also work full time in addition to being a dad (those of you who are know how that is ) and won't really be able to respond to PMs very well. The sources I used can be found under the post on XDA here at http://forum.xda-developers.com/moto-maxx/development/rom-resurrection-remix-t3511109 (device, vendor, and kernel trees). Thanks and God bless.
Nice, downloading... made changes in the kernel?
Thanks developer @calsurferpunk
hpbrasil said:
Nice, downloading... made changes in the kernel?
Thanks developer @calsurferpunk
Click to expand...
Click to collapse
Thanks. No I didn't change anything about the kernel. There isn't a good alternative (that I know of yet) so I just used it straight from bhb for now.
How do I disable the capacitive buttons and use on screen nav bar instead?
Sent from my DROID Turbo using Tapatalk
My device is showing no root on this ROM and if I install super su it gains root but shows no sim card available. Fixed by enabling root permission in development settings.
The rom is almost 100%, the battery is well lasting me .... 1 screen time every 10% quietly, the only problem I really noticed was sending images on whatsapp that is not 100%, you send catch screen and photos taken by whatsapp ... now send images from the gallery do not know why, it just outside joys and once again thank you for your development. @calsurferpunk
eddiemc12 said:
My device is showing no root on this ROM and if I install super su it gains root but shows no sim card available. Fixed by enabling root permission in development settings.
Click to expand...
Click to collapse
It's not fixing it for me. I enabled root in developer options.
What can be the issue here @calsurferpunk
Sent from my DROID Turbo using Tapatalk
{
"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"
}
Root ok
muhammadtalha-13 said:
It's not fixing it for me. I enabled root in developer options.
What can be the issue here @calsurferpunk
Sent from my DROID Turbo using Tapatalk
Click to expand...
Click to collapse
I'm not sure what could be going on. I haven't flashed su and just use the stock CM root manager. Enabling root for apps only in developer options makes everything work for me when an app requests it. I did notice that I had to make sure that iSu was setting the policy as permissive (causes FC when set as enforcing).
If not bother you wanted to report a small simple mistake that can not encomodar only to warn even ... In Menu> Settings> Developer Options> animator duration scale, the second option is 0.5x and there is 5x....When I click on the Home screen and select background he simply FC, that's Gallery problem equal to whatsapp that has pictures not ...
The maintainer of CrDroid said I do not know how to use the Android and it really is a problem of rom and he would not listen to me and said she did not like my attitude. @calsurferpunk
calsurferpunk said:
I'm not sure what could be going on. I haven't flashed su and just use the stock CM root manager. Enabling root for apps only in developer options makes everything work for me when an app requests it. I did notice that I had to make sure that iSu was setting the policy as permissive (causes FC when set as enforcing).
Click to expand...
Click to collapse
So if I flash ROM and iSu says no root, then I just have to enable root in developer options without flashing SuperSU? I actually tried developer option after flashing SuperSU. Maybe that's why it didn't work. Let me know if I am right then I'll try the correct procedure.
Sent from my Pixel XL using Tapatalk
muhammadtalha-13 said:
So if I flash ROM and iSu says no root, then I just have to enable root in developer options without flashing SuperSU?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
That's all that I did and I haven't had any issue yet. I didn't have to change anything with iSu either (even if I did mess with it later just to see what it does).
Just as a quick update, next time I post an updated build I believe I know how to skip including iSu and kernel auditor by default. I'll make sure to include a way to download them and include them separately if this is successful. The goal of this is to keep it as close to stock CM 14.1 and still be functional so that anything you want to add can be done by your own free will .
calsurferpunk said:
That's all that I did and I haven't had any issue yet. I didn't have to change anything with iSu either (even if I did mess with it later just to see what it does).
Click to expand...
Click to collapse
Okay got it now. I'll try again later tonight and will confirm here.
Sent from my Pixel XL using Tapatalk
no super su, i enabled root in developer setting and it works fine.
太棒了
Hey @calsurferpunk, very good job. But I have to tell u about a bug I notice. When you'll transfer a music from pc to the phone, the music player says "That's impossible to play (Name of the Music)" and in the Google Play Music the music it's with 0 seconds. The music only goes if you put in recovery mode and transfer the mp3 archive while you're at TWRP.
Hlcpereira said:
Hey @calsurferpunk, very good job. But I have to tell u about a bug I notice. When you'll transfer a music from pc to the phone, the music player says "That's impossible to play (Name of the Music)" and in the Google Play Music the music it's with 0 seconds. The music only goes if you put in recovery mode and transfer the mp3 archive while you're at TWRP.
Click to expand...
Click to collapse
It might be a bug with Play Music. I have transferred music normally and Poweramp plays it without any problems.
Shooting Star Max said:
It might be a bug with Play Music. I have transferred music normally and Poweramp plays it without any problems.
Click to expand...
Click to collapse
No man, the problem still at the music player which goes installed in the ROM.
Is it possible to get viper4android working?
SteveMcQueen87 said:
Is it possible to get viper4android working?
Click to expand...
Click to collapse
I imagine it would work since there are zips for V4A and Pie, we just need TWRP.
airmaxx23 said:
I imagine it would work since there are zips for V4A and Pie, we just need TWRP.
Click to expand...
Click to collapse
Or you can just use the Magisk module for it.
i've been curious about this... when I attempt to load the module from magisk, the viper app states driver needs updated and i follow the prompts but every reboot same dialog stating update driver. after some further reading, i evidently needed to download busybox, also available as a magisk module. ok now busybox and viper... no more "driver update" needed, but i'm not convinced viper is actually working with any setting in the viper app (ultimately im looking for louder headphone volume)
>>> what am i missing? do i need another module? custom kernel?
SteveMcQueen87 said:
Is it possible to get viper4android working?
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
I have this one installed and working. It has its bugs but it works
cadg71 said:
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
I have this one installed and working. It has its bugs but it works
Click to expand...
Click to collapse
This is the only version I've found that works. Doesn't work well switching between audio sources though.
cadg71 said:
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
I have this one installed and working. It has its bugs but it works
Click to expand...
Click to collapse
Do you need root for this to work?
boxcar8028 said:
Do you need root for this to work?
Click to expand...
Click to collapse
Yes
Have you guys installed the Audio Modification Library as well? This helps a lot with getting V4A to work properly.
https://forum.xda-developers.com/apps/magisk/mod-audio-modification-library-t3745466
mcgleevn said:
i've been curious about this... when I attempt to load the module from magisk, the viper app states driver needs updated and i follow the prompts but every reboot same dialog stating update driver. after some further reading, i evidently needed to download busybox, also available as a magisk module. ok now busybox and viper... no more "driver update" needed, but i'm not convinced viper is actually working with any setting in the viper app (ultimately im looking for louder headphone volume)
>>> what am i missing? do i need another module? custom kernel?
Click to expand...
Click to collapse
Did you get this to work???
cambunch said:
Have you guys installed the Audio Modification Library as well? This helps a lot with getting V4A to work properly.
https://forum.xda-developers.com/apps/magisk/mod-audio-modification-library-t3745466
Click to expand...
Click to collapse
I tried it but v4a wouldn't work with it installed. I uninstalled it and v4a started working again.
Installed AML after and it removed Viper app, still see it in Magisk. Deleted everything and now when I install driver, Viper app disappears.
Update: installed APK from OP on that thread. Kept magisk module installed. Working
Sent from my Pixel 3 XL using Tapatalk
I keep getting the, update driver for V4A. I've done it like 5 times. I had busybox installed first even. I also installed ViperXHiFi, and it keeps asking for V4A driver to be updated... I'm going to test in my car anyway, but something is off for sure. This didn't happen on my 2 xl.
gettinwicked said:
I keep getting the, update driver for V4A. I've done it like 5 times. I had busybox installed first even. I also installed ViperXHiFi, and it keeps asking for V4A driver to be updated... I'm going to test in my car anyway, but something is off for sure. This didn't happen on my 2 xl.
Click to expand...
Click to collapse
Checked permissions and SU access granted?
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
Checked permissions and SU access granted?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Yep! I installed V4A through the Magisk module, after SELinux and Busybox and a reboot. In settings, went into developer mode then disabled SELinux. I'm guessing yours works? If yes, what were your steps?
Not processing but I can hear effects when toggled
{
"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 my Pixel 3 XL using Tapatalk
Use this one 2.6.
https://androidfilehost.com/?w=files&flid=267359
The FX one does not work.
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
Moostafa29 said:
This is the only version I've found that works. Doesn't work well switching between audio sources though.
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
Use this one 2.6.
https://androidfilehost.com/?w=files&flid=267359
The FX one does not work.
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
Is this one different than the Viper FX Android Magisk module? The material, 2.5.0.5 or something like that? That's the one that worked on my 2xl, so, I repeated the steps that got it working on my 3xl. I tested in my SUV, and, sure doesn't sound like it's working...
gettinwicked said:
Is this one different than the Viper FX Android Magisk module? The material, 2.5.0.5 or something like that? That's the one that worked on my 2xl, so, I repeated the steps that got it working on my 3xl. I tested in my SUV, and, sure doesn't sound like it's working...
Click to expand...
Click to collapse
Yes it is different it looks like it's a newer version with the higher number and all....
The FX version would not install the driver. It doesn't work
So I take it you removed all audio mods flashed the module in mm and rebooted. Then you installed the recommended driver when prompted and rebooted? If so, are you sure the driver is installed by checking in the Viper app?
Sent from my Pixel 3 XL using Tapatalk
MArtyChubbs said:
Yes it is different it looks like it's a newer version with the higher number and all....
The FX version would not install the driver. It doesn't work
So I take it you removed all audio mods flashed the module in mm and rebooted. Then you installed the recommended driver when prompted and rebooted? If so, are you sure the driver is installed by checking in the Viper app?
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm not sure what you are referring to as far as me removing all audio mods? I simply flashed the one version of V4A FX after busybox, rebooted, and I get a prompt every time I open it to install the driver. Every time I do it, it says successful and reboot. When I click no and check the driver status, it shows it's not correct. So, doesn't look like the driver installs at all.
I guess I'll remove it and install the one you posted. If that works, color me happy. Have you tried it with Viper XHiFi? I used that on my 2xl when dolby wouldn't work on Pie. Didn't sound AS good, but still a big improvement, even over just regular viper.
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