DISCLAIMER: I'm new to Android and I have no idea of some tech android stuff (e.g. ADB etc) please do dumb down your answer for me. thanks
I just paid for Andromeda and and then did the process that you do on the laptop. I downloaded ozone substratum theme and selected all the overlays (I think that's what they're called?). I clicked on build and enable option and the phone did its thing. after it was completed, substratum said to reboot the device to make the theme to show up. I reboot the phone but nothing has changed and I mean literally nothing. I used ozone because I was told it is 100% compatible with oxygenOS. I don't know what to do now. I did try some other themes but still had no success. I'm using OnePlus 5t on oreo beta 12. sometimes when the phone is downloading the overlays, it says 'substratum could not connect to the andromeda backend' and then gets stuck. everytime this happens I just force close the substratum app and try again and then it starts working. thanks for your help.
Sufyyan said:
DISCLAIMER: I'm new to Android and I have no idea of some tech android stuff (e.g. ADB etc) please do dumb down your answer for me. thanks
I just paid for Andromeda and and then did the process that you do on the laptop. I downloaded ozone substratum theme and selected all the overlays (I think that's what they're called?). I clicked on build and enable option and the phone did its thing. after it was completed, substratum said to reboot the device to make the theme to show up. I reboot the phone but nothing has changed and I mean literally nothing. I used ozone because I was told it is 100% compatible with oxygenOS. I don't know what to do now. I did try some other themes but still had no success. I'm using OnePlus 5t on oreo beta 12. sometimes when the phone is downloading the overlays, it says 'substratum could not connect to the andromeda backend' and then gets stuck. everytime this happens I just force close the substratum app and try again and then it starts working. thanks for your help.
Click to expand...
Click to collapse
When you reboot your device, andromeda loses connection and you will need to run the PC commands again.
haikalizz said:
When you reboot your device, andromeda loses connection and you will need to run the PC commands again.
Click to expand...
Click to collapse
Yh I know that. After I reboot the device nothing changed. So one of the many things I did was to run the PC commands again to see if it had worked. However nothing changed.
Go to Manager and make sure that all applied themes are enabled. then reboot.
Sufyyan said:
DISCLAIMER: I'm new to Android and I have no idea of some tech android stuff (e.g. ADB etc) please do dumb down your answer for me. thanks
I just paid for Andromeda and ..... thanks for your help.
Click to expand...
Click to collapse
Dude, take a look at this thread.
https://forum.xda-developers.com/apps/substratum/andromeda-desktop-clients-release-notes-t3668682
nicorvienne said:
Dude, take a look at this thread.
https://forum.xda-developers.com/apps/substratum/andromeda-desktop-clients-release-notes-t3668682
Click to expand...
Click to collapse
This thread doesn't really help. I looked over it and couldn't find a solution to my problem
Related
Guys how do I fix this? I open up substratum and it keeps giving me this message saying I'm on a compatible oreo device so I should get Andromeda.... But the thimg is I went and bought Andromeda app and then that doesn't let me change themes from my device either I'm rooted so I don't see the problem why won't substratum let me use it? It used to work even on Oreo! I'll post a pic to show
zee24 said:
Guys how do I fix this? I open up substratum and it keeps giving me this message saying I'm on a compatible oreo device so I should get Andromeda.... But the thimg is I went and bought Andromeda app and then that doesn't let me change themes from my device either I'm rooted so I don't see the problem why won't substratum let me use it? It used to work even on Oreo! I'll post a pic to show
Click to expand...
Click to collapse
Having the same issue, play store is also crashing.
jweavis said:
Having the same issue, play store is also crashing.
Click to expand...
Click to collapse
Fixed the issue. I lost root due to ota and even after getting root back it wasn't working but then it's because substratum was checked in magisk hide and also you have to uninstall Sun and then reboot then re download and it should ask you for root permission and it should work
Hi to all,
Is there any possibility that we can we can use substratum themes on our OnePlus 5 official oreo ?
Akil Imran said:
Hi to all,
Is there any possibility that we can we can use substratum themes on our OnePlus 5 official oreo ?
Click to expand...
Click to collapse
Yes, you can use andromeda.
There's plenty of guides if you google for it
Andromeda kind of sucks, especially if you are used to using Substratum with root. Using the non-root Andromeda method you can't even open the Substratum app on your phone unless it's connected to your computer. Sometimes when an app updates in the Play Store the theme overlay will cause the app to crash. When that happens you have to remove and then reinstall the overlay--which cannot be done using the non-root method until you can connect your phone to your computer. The affected app can't be used until then because you can't open Substratum to disable the overlay.
KpChuck said:
Yes, you can use andromeda.
There's plenty of guides if you google for it
Click to expand...
Click to collapse
Yeah i googled for it and downloaded andromeda but whenever i was trying to open it was not opening. I clicked on app icon there was nothing happening.
Akil Imran said:
Yeah i googled for it and downloaded andromeda but whenever i was trying to open it was not opening. I clicked on app icon there was nothing happening.
Click to expand...
Click to collapse
This is the right thread for your issue.
Akil Imran said:
Hi to all,
Is there any possibility that we can we can use substratum themes on our OnePlus 5 official oreo ?
Click to expand...
Click to collapse
yes you can. just check out for the compatible themes, all themes don't support OOS Oreo
jhs39 said:
Andromeda kind of sucks, especially if you are used to using Substratum with root. Using the non-root Andromeda method you can't even open the Substratum app on your phone unless it's connected to your computer. Sometimes when an app updates in the Play Store the theme overlay will cause the app to crash. When that happens you have to remove and then reinstall the overlay--which cannot be done using the non-root method until you can connect your phone to your computer. The affected app can't be used until then because you can't open Substratum to disable the overlay.
Click to expand...
Click to collapse
Strongly agree with you. BUT we should appreciate developers (Ozone, Andromeda and Substratum ) to make it 90% possible for non-rooted phones. Its not a small work... [And that's why its paid and it will be]
jhs39 said:
Andromeda kind of sucks, especially if you are used to using Substratum with root. Using the non-root Andromeda method you can't even open the Substratum app on your phone unless it's connected to your computer. Sometimes when an app updates in the Play Store the theme overlay will cause the app to crash. When that happens you have to remove and then reinstall the overlay--which cannot be done using the non-root method until you can connect your phone to your computer. The affected app can't be used until then because you can't open Substratum to disable the overlay.
Click to expand...
Click to collapse
When using Substratum rooted or not, ALWAYS and i say ALWAYS disable auto updating apps in the Play Store. You can manually update all your apps when a update for the theme you are using gets pushed. That way all your apps will always be themed without issues, crashes etc. Ofc using Andromeda isn't ideal, but if you want to be unrooted behind a locked bootloader, that is your best option. Maybe Google will do something for Android P to not eliminate the need for connecting to a pc. Another good tip for using Andromeda is if you reboot remember to fire up the desktop client and enable Substratum.
Pixel 2 XL on 9.0
Bootloader Unlocked
TWRP Recovery
Rooted via Magisk 17.1
The Uconnect app for my Jeep no longer functions because the new version for Android 9.0 checks for an unlocked bootloader or root. When trying to login to the Uconnect app, I receive a popup that states I'm using an unapproved device. When contacting the developer, they claim that it's because my device is a security threat. I've tried Magisk Hide to no avail.
Any suggestions?
Same thing here too. I have an older S6 Edge + running a rooted Android 7.0 with Magisk 17.1. Magisk Hide doesnt fix it as well.
having this issue as well with the latest uConnect app. Pixel 2XL is rooted and unlocked. I loaded the latest stock firmware 9.0 and tried the uConnect app prior to rooting and it works on my end, but still a no-go once Magisk is installed. I even tried the magisk hide and the module that can alter prop to further hide magisk and no go. I think it may be that it is looking for root and is awfully good at finding it. If anyone can get this to work, would be great! I dont get why FCA is so worried about root. One would think that since we have to go through a VERY specific sequence to get root and unlock the bootloader, that we would have quite a grip on what goes on with our phones. Anyways, if someone comes up with something......
Uconnect is detecting Magisk Manager. You have to uninstall it in order for Uconnect to work.
Well that sucks
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
TechnovationLLC said:
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
Click to expand...
Click to collapse
And you are rooted?
CyberpodS2 said:
And you are rooted?
Click to expand...
Click to collapse
I tested root and non rooted. Both seemed to function fine for me. I initially thought rooted might be the issue for me, but it ended up being the old app.
Fresh install from play store gets me this.
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
Sadly, if I install an older version it prompts to update with no way around it... If anyone knows a version that works please post here.
Wondering if a logcat would help to pinpoint the issue and assist the magisk developer with a fix.
MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
The old (black) version of the app doesn't work with 9.0
Very discouraging
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Viol8ter said:
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Click to expand...
Click to collapse
Which version of Android are you on and which app version? Thanks!
lu270bro said:
Which version of Android are you on and which app version? Thanks!
Click to expand...
Click to collapse
I am on 8.0. Though I read somewhere someone said to hide the magisc manger with random name and it worked after clearing app cache. I'm happy and thankyou.
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Machine318 said:
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Click to expand...
Click to collapse
I have never been able to get it working on this phone since the blue icon change. Sucks...
why does a car/radio company care what a joke glad i dont have a car with unconnect
OK boys and girls. I think I found a fix. might not work for all of you, but I got the App to load and let me in.
I'm running the latest Pie version, Magisk 18.1 (Riru - Core v16, Riru - Ed Xposed) and XPrivacyLua (xposed module)
in XPrivacyLua for the Uconnect App, I restricted, Get Applications. Uconnect Logs in.
Okay so everything was working fine up until yesterday. Then i uninstalled a theme and applied it again with a different accent color, and it didnt apply. I tried it with other themes and overlays and they werent compiling either. I tried uninstalling all overlays and now i cant get any themes to work. It says compiled without any errors when i build it but after i reboot my device theres nothing there, the theme hasnt applied at all. Anybody know what happened??
If your running a custom rom than it is probably sue to the system partition being full and therefore Substratum cant work.
Sarim26 said:
Okay so everything was working fine up until yesterday. Then i uninstalled a theme and applied it again with a different accent color, and it didnt apply. I tried it with other themes and overlays and they werent compiling either. I tried uninstalling all overlays and now i cant get any themes to work. It says compiled without any errors when i build it but after i reboot my device theres nothing there, the theme hasnt applied at all. Anybody know what happened??
Click to expand...
Click to collapse
Archangel said:
If your running a custom rom than it is probably sue to the system partition being full and therefore Substratum cant work.
Click to expand...
Click to collapse
Im on stock android 9.0
Well then thats def weird my themes run perfect so far. Are you making sure that you go back into Substratum manager and enabling all overlays that you previously built after rebooting?
\
Sarim26 said:
Im on stock android 9.0
Click to expand...
Click to collapse
Archangel said:
Well then thats def weird my themes run perfect so far. Are you making sure that you go back into Substratum manager and enabling all overlays that you previously built after rebooting?
Sarim26 said:
Im on stock android 9.0
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Thats the problem, after i reboot nothing shows up in the manager, they never compiled even though it says compiled without any errors before the reboot
Hi there,
I'm facing the same issue at the moment... @op did you find the culprit?
Cheers...
Same here. Anytime got any ideas? Magisk installed, root granted, stock 9.0. Themes compiled and visible in Substratum. I install overlays, see nothing in Manager tab (which is normal), get no errors, reboot, and still nothing in Manager tab.
I've been trying to get viper4android working on Android q for quite some time but the module and the app itself does not want work at all. Plus when viper asks you to install the driver from the app it will end up in a bootloop. Has anybody found a temp workround for it?
Device: Pixel 2 XL Android version: Q Beta 3
I'm having a similar issue, only the driver install is asked again upon reboot ;_;
Thats only why i rollback from Q.
Total**** sound without
Ok, got it working on beta 3, using the apk 2.7.1.0 from XDA. It appears to install as a magisk module, along with AML. It didn't work on my first try, then all was good. I need to run it in compatibility mode from the menu. https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
In android P what version did you use?
Always used the magisk repo version before- I tried this many times on Q, with and without AML, but always got the dreaded install driver dialogue. Also tried SE Linux permissive, but no luck. I've never used the apk before, but am sat here now listening to music quite happily. It's survived a couple of reboots (just checking).
1959best said:
Ok, got it working on beta 3, using the apk 2.7.1.0 from XDA. It appears to install as a magisk module, along with AML. It didn't work on my first try, then all was good. I need to run it in compatibility mode from the menu. https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Click to expand...
Click to collapse
Hm, I just tried that. I downloaded the one off XDA LABS and checked compatibility mode on the app. Still showing up as driver not installed. Viper4Android is literally the key element for my phones such a good module.
Try another reboot?
Knxed_ said:
Hm, I just tried that. I downloaded the one off XDA LABS and checked compatibility mode on the app. Still showing up as driver not installed. Viper4Android is literally the key element for my phones such a good module.
Click to expand...
Click to collapse
I just upgraded to Android 10 on my Pixel 2XL and have Viper running now. Download stable 2.7.1.0 from XDA Labs, grant root with Magisk. Check compatibility mode THEN install the driver. Restart, make changes, and then be sure to check "Attach audio effects" in settings once you make your changes.
ifellouttabed said:
I just upgraded to Android 10 on my Pixel 2XL and have Viper running now. Download stable 2.7.1.0 from XDA Labs, grant root with Magisk. Check compatibility mode THEN install the driver. Restart, make changes, and then be sure to check "Attach audio effects" in settings once you make your changes.
Click to expand...
Click to collapse
Mhh doesn't work for me this way.still asking for driver after reboot lol
Thanks. Worked for me on second try. Followed the instructions rebooted didn't work, installed drivers again rebooted and then it worked.
pa.pn2 said:
Mhh doesn't work for me this way.still asking for driver after reboot lol
Click to expand...
Click to collapse
Same here sadly...
sidhaarthm said:
Same here sadly...
Click to expand...
Click to collapse
Ok, here's what you gotta do to get it to work, this is the ONLY method I've had consistently work for me from beta 3-public release(did it an hour ago and worked perfectly)
First, uninstall any viper you have also make sure you completely uninstall audio modification library if you have it installed, not disable, uninstall it and reboot after uninstalling what I've listed.
After you're all booted back up, install viper from labs (link in this thread)(Also, forget about compatibility mode, don't use it) now open viper but do NOT install the driver yet, just open the application then go to magisk and install audio modification library but dont let magisk reboot the phone after it installs. Once installation completed, go back to viper and install the driver and let it reboot. Once booted, go straight to magisk and DISABLE audio modification library (uncheck the box next to it if you dont get what I mean) don't uninstall it. After disabling AML head back to viper and install the driver again. Now once rebooted is the moment of truth, if you open viper and its installed you're obviously done but if it's not installed you have to take this next step: don't install the driver just yet, go to magisk and re-enable AML then back to viper and install the driver. I don't see why this would not work for you guys, I know this isn't the easiest tutorial to follow but make sure you follow it to a T, if you mess any step up you need to start from scratch and uninstall both AML and viper and start again.
Good luck guys and may the audiophile Gods be on your side through this process!
1dopewrx05 said:
Ok, here's what you gotta do to get it to work, this is the ONLY method I've had consistently work for me from beta 3-public release(did it an hour ago and worked perfectly)
First, uninstall any viper you have also make sure you completely uninstall audio modification library if you have it installed, not disable, uninstall it and reboot after uninstalling what I've listed.
After you're all booted back up, install viper from labs (link in this thread)(Also, forget about compatibility mode, don't use it) now open viper but do NOT install the driver yet, just open the application then go to magisk and install audio modification library but dont let magisk reboot the phone after it installs. Once installation completed, go back to viper and install the driver and let it reboot. Once booted, go straight to magisk and DISABLE audio modification library (uncheck the box next to it if you dont get what I mean) don't uninstall it. After disabling AML head back to viper and install the driver again. Now once rebooted is the moment of truth, if you open viper and its installed you're obviously done but if it's not installed you have to take this next step: don't install the driver just yet, go to magisk and re-enable AML then back to viper and install the driver. I don't see why this would not work for you guys, I know this isn't the easiest tutorial to follow but make sure you follow it to a T, if you mess any step up you need to start from scratch and uninstall both AML and viper and start again.
Good luck guys and may the audiophile Gods be on your side through this process!
Click to expand...
Click to collapse
Take a bow good sir, it worked! Had to follow the steps to the end as first time around it didn't work. Now seems to be alright (see attached)
For anyone else wondering, I upgraded from Aug 9.0 build to Q (020) last night by flashing the factory ROM without wipe. Rooted, ads disabled and now ViperFX working. Life is goooood :angel:
sidhaarthm said:
Take a bow good sir, it worked! Had to follow the steps to the end as first time around it didn't work. Now seems to be alright (see attached)
For anyone else wondering, I upgraded from Aug 9.0 build to Q (020) last night by flashing the factory ROM without wipe. Rooted, ads disabled and now ViperFX working. Life is goooood :angel:
Click to expand...
Click to collapse
I think it also worked for me now but in your screeny it says not enabled.same with me.
But i have all the options for speaker headphones usb etc.think it worked
pa.pn2 said:
I think it also worked for me now but in your screeny it says not enabled.same with me.
But i have all the options for speaker headphones usb etc.think it worked
Click to expand...
Click to collapse
Ah yeah, it's probably because I hadn't enabled it until that time. Here's a fresh screenie
sidhaarthm said:
Ah yeah, it's probably because I hadn't enabled it until that time. Here's a fresh screenie
Click to expand...
Click to collapse
what do you mean with didnt enable it?
i did all the steps, i can adjust all settings but if i play something in g music it still says not enabled....what did i miss?
pa.pn2 said:
what do you mean with didnt enable it?
i did all the steps, i can adjust all settings but if i play something in g music it still says not enabled....what did i miss?
Click to expand...
Click to collapse
By enabling, I meant turning on the master limiter and other settings. I adjusted mine with a nice YouTube track playing in the background and it all worked a treat. Yet to do my Bluetooth earphones though
sidhaarthm said:
By enabling, I meant turning on the master limiter and other settings. I adjusted mine with a nice YouTube track playing in the background and it all worked a treat. Yet to do my Bluetooth earphones though
Click to expand...
Click to collapse
I switched on the master and now its working.awesome find
@1dopewrx05 I followed your mini tutorial to a T and it worked perfectly. Thank you for taking the time to do this, I really appreciate it. Just updated my old faithful to 10 earlier and gonna mess around with some of the neat features. I can't live without Viper, it's essential to me.