Substratum crashes on launch after update (Moto G5 Plus) - prjkt.io

I have rooted my Moto G5 Plus, and I cannot figure out what is happening to substratum. This'll take some explaining:
I didn't really want to change the ROM on my phone because the stock was fine for me and it was already pretty much stock android. So, I kept it, and installed substratum (cannot remember what version because it was so long ago, but I know it was in the 800's). I also got the app "ThemeDIY" from google play, and I created a theme in it. I installed it, then went over to substratum to apply it.
Substratum opened like it did before, and I clicked on my theme, and applied it to all apps. Rebooted, and there was my theme. But then the nightmare began.
Applying the theme to my "Documents" app caused it to fail every time it was opened, so whenever I wanted to attach something to a text message or something of the such, it would say "Documents has stopped working". I tried removing the theme in substratum, but Documents still failed. Eventually, I just restored my backup of /system/ and it started working again. From that point on, I only applied the theme to apps I could launch from the home screen so I didn't mess up system processes.
My theme worked really well, and I liked it, but after a while (and several substratum updates installed automatically), I decided I wanted a different theme. So I updated my theme, and reinstalled it. I went to open substratum, but was greeted with a crash message ("I'm so sorry for the crash"). I tried clicking rescue, but the app closed, said "Rescuing your system", then nothing else ever happened.
This was about three months ago, and I can't remember what I did to fix it. I think I deleted something in the file browser in TWRP and reset the substratum config files after uninstalling it, but I don't remember how I did it. Anyway, I did something along those lines and it worked perfectly again. At this time it was in the 800's version.
Now, I wanted to apply yet another different theme, so I opened substratum, and got the same message. Of course, google play had been updating it, but now, I can't find a site that tells me where the overlay file and substratum config files are.
Where are these files, and if I delete them, would it fix the problem? If not, how could I fix the problem without deleting all my data?
Here's the log:
Code:
Build version: nine hundred fourteen
Device: Moto G (5) Plus (potter) [motorola/potter_retail/potter:7.0/NPN25.137-33/35:user/release-keys]
ROM: 7.0 - Unknown
Theme system: RRO (Legacy)
Stack trace:
java.lang.RuntimeException: Unable to start activity ComponentInfo{projekt.substratum/projekt.substratum.MainActivity}: android.view.InflateException: Binary XML file line #25: Binary XML file line #25: Error inflating class TextView
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2659)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2724)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1473)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6123)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:757)
Caused by: android.view.InflateException: Binary XML file line #25: Binary XML file line #25: Error inflating class TextView
Caused by: android.view.InflateException: Binary XML file line #25: Error inflating class TextView
Caused by: java.lang.UnsupportedOperationException: Failed to resolve attribute at index 6: TypedValue{t=0x2/d=0x101009b a=1}
at android.content.res.TypedArray.getColorStateList(TypedArray.java:528)
at android.widget.TextView.<init>(TextView.java:783)
at android.widget.TextView.<init>(TextView.java:704)
at android.support.v7.widget.AppCompatTextView.<init>(AppCompatTextView.java:74)
at android.support.v7.widget.AppCompatTextView.<init>(AppCompatTextView.java:70)
at android.support.v7.app.AppCompatViewInflater.createView(AppCompatViewInflater.java:103)
at android.support.v7.app.AppCompatDelegateImplV9.createView(AppCompatDelegateImplV9.java:1016)
at android.support.v7.app.AppCompatDelegateImplV9.onCreateView(AppCompatDelegateImplV9.java:1073)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:769)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:727)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:858)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:821)
at android.view.LayoutInflater.inflate(LayoutInflater.java:518)
at android.view.LayoutInflater.inflate(LayoutInflater.java:426)
at android.view.LayoutInflater.inflate(LayoutInflater.java:377)
at com.android.internal.policy.DecorView.onResourcesLoaded(DecorView.java:1776)
at com.android.internal.policy.PhoneWindow.generateLayout(PhoneWindow.java:2613)
at com.android.internal.policy.PhoneWindow.installDecor(PhoneWindow.java:2686)
at com.android.internal.policy.PhoneWindow.getDecorView(PhoneWindow.java:2049)
at android.support.v7.app.AppCompatDelegateImplV9.createSubDecor(AppCompatDelegateImplV9.java:374)
at android.support.v7.app.AppCompatDelegateImplV9.ensureSubDecor(AppCompatDelegateImplV9.java:323)
at android.support.v7.app.AppCompatDelegateImplV9.setContentView(AppCompatDelegateImplV9.java:284)
at android.support.v7.app.AppCompatActivity.setContentView(AppCompatActivity.java:139)
at projekt.substratum.MainActivity.onCreate(MainActivity.java:324)
at android.app.Activity.performCreate(Activity.java:6672)
at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1140)
at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2612)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2724)
at android.app.ActivityThread.-wrap12(ActivityThread.java)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1473)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:154)
at android.app.ActivityThread.main(ActivityThread.java:6123)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:867)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:757)
User actions:
2017-12-05 10:22:45: SplashScreenActivity created
2017-12-05 10:22:45: SplashScreenActivity resumed
2017-12-05 10:22:45: SplashScreenActivity paused
2017-12-05 10:22:45: MainActivity created
So far, I've uninstalled the theme in settings (though it's still applied to my system) and I've deleted all folders ending in the name of my theme in /data/data. The theme is still applied, and substratum refuses to open. I've been looking for an overlay file and for substratum's configuration folder.
I will say I've noticed that when substratum tries to launch, I don't see an indicator of it receiving root permissions, though SuperSU is set to grant it permissions. Could it be a problem with receiving root?

Related

AOD service keeps crashing

So last night suddenly my AOD quit working when I went to apply a new theme. Do they remember which one it was. Now I can't get it to work again. it keeps crashing. I am rooted, I unfroze all apps, and disabled the GalaxyMod module for xposed. I also noticed that Titanium backup was automatically freezing my themes.
To try and fix this I deleted the AOD service folder under app/data restarted the phone then installed the apk. It installed fine, but still crashes.
Also I am able to get into the AOD settings through the settings menu, but as soon as I go to change a setting it crashes.
Any help would be appreciated. Thank you in advance.
Install a xposed module called “Cracker”, it will save log when app crash,and this may help to analyse the problem.
thanks I appreciate. installed but I don't know what everything means. anyone able to help? Maybe it's something to do with xposed? I disabled all modules except cracker, and it's the same report.
java.lang.RuntimeException: Unable to create service com.samsung.android.app.aodservice.AODService: java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3817)
at android.app.ActivityThread.access$2100(ActivityThread.java:221)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1882)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:158)
at android.app.ActivityThread.main(ActivityThread.java:7224)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:133)
Caused by: java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:165)
at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:135)
at android.content.ContentProviderProxy.call(ContentProviderNative.java:646)
at android.provider.Settings$NameValueCache.putStringForUser(Settings.java:1457)
at android.provider.Settings$System.putStringForUser(Settings.java:1852)
at android.provider.Settings$System.putIntForUser(Settings.java:1968)
at android.provider.Settings$System.putInt(Settings.java:1959)
at com.samsung.android.app.aodservice.settings.SettingsUtils.setSystemSettings(SettingsUtils.java:610)
at com.samsung.android.app.aodservice.settings.SettingsUtils.setAODVersion(SettingsUtils.java:628)
at com.samsung.android.app.aodservice.utils.AODUpdateVersionController.onUpgrade(AODUpdateVersionController.java:29)
at com.samsung.android.app.aodservice.AODService.onCreate(AODService.java:272)
at android.app.ActivityThread.handleCreateService(ActivityThread.java:3807)
at android.app.ActivityThread.access$2100(ActivityThread.java:221)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1882)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:158)
at android.app.ActivityThread.main(ActivityThread.java:7224)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1230)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1120)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:133)
so I finally got my AOD back. I Uninstalled aod, and completely removed xposed. Then after a restart I reinstalled AOD then after a final reboot it works.

Issue with crypto? All Google apps force close, etc. Read on please...

Hello my highly technical friends,
My missus is using my old international ver. of Galaxy S6 SM-920F, because she fell in love with it and doesn't think about swapping for anything else. But it looks like she might be forced to, because she's having serious problems with it:
1. All Google apps force close. Play Store, Maps, Gmail, Photos, Play Services, everything.
2. Apps like Signal or Telegram that rely on encryption, won't work properly, e.g. she gets "Bad encrypted message" in Signal.
3. Play Store works from time to time, but it's force closing when she wants to download apps.
She doesn't remember when the problems started, so I can't pinpoint what caused it. Unfortunately the device was rooted and she would often use it to install some shady apps like cleaners, ram boosters etc, so it might be a problem created by some malware. Logcat is throwing a lot of errors, googling them didn't bring any reliable answers, so I tried different ways to resolve it:
1. Wiped the device clean in TWRP, all partitions.
2. Installed custom ROM (ResurrectionRemix 8.1 and later 7.1) as a test and flashed it in TWRP, issues persist in clean install.
3. Installed custom ROM (AOSPExtended 8.1) as a test and flashed it in TWRP, issues persist in clean install.
4. Tried different versions of Opengapps - Pico, Nano, Mini, different build dates. Same issue.
5. Wiped again in TWRP, downloaded latest stock firmware from Sammobile (G920FXXU6ERC9) and flashed it in Odin 3.12.10. Issues persist in clean install.
6. Downloaded correct PIT file, flashed it in Odin, along with latest stock firmware from Sammobile. Same issue.
I'm running out of options. Issue isn't ROM related, neither Opengapps, as the issues persist in different ROMS, Gapps and even in stock. Looking at logcat, this might be the problem:
Code:
E/AndroidRuntime(20624): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.apps.photos, sha1=24bb24c05e47e0aefa68a58a766179d9b613a600, atk=false, ver=12685023.true
E/AndroidRuntime(20624): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.android.vending, sha1=38918a453d07199354f8b19af05ec6562ced5788, atk=false, ver=12685023.true
E/AndroidRuntime(21286): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.googlequicksearchbox, sha1=38918a453d07199354f8b19af05ec6562ced5788, atk=false, ver=12685023.true
E/AndroidRuntime(11308): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.gm, sha1=38918a453d07199354f8b19af05ec6562ced5788, atk=false, ver=12685023.true
W/System.err(12435): java.lang.SecurityException: GoogleCertificatesRslt: not whitelisted: pkg=com.google.android.apps.maps, sha1=38918a453d07199354f8b19af05ec6562ced5788, atk=false, ver=12685023.true
But there are many more warnings and errors, which you can see in the attached logcats. It's taken on Android 7.0, baseband G920FXXU6ERC2, build NRD90M.G920FXXU6ERC9, SELinux enforcing, patch level 1 March 2018, Knox Active...but I don't think it matters. What else can I do with this?
Erm...how do I attach files on desktop? I don't see the option anywhere. Here are links to external provider, but only because I can't attach it here.
https://pastebin.com/6732xWn1
https://pastebin.com/DGbz0sMf

Please help with dark theme - 8.0.0

I have tried to follow the tutorials located here:
https://www.xda-developers.com/install-dark-theme-android-oreo-without-root/
https://www.xda-developers.com/custom-themes-android-oreo-substratum/
But with zero luck. I paid for the Andromeda app, but I get an error when building about a recent security thing by Google. Can anyone please
help? I'm using Sai's Oreo Theme, I chose the options in substratum, then hit build and enable, but it errors. Says the application overlay is outdated. Then a pop up comes up saying that with a March security update, Google implemented a reboot check on overlays.
EDIT: I even downloaded a theme called Swift Black which is supposed to be updated, I followed the instructions, but each time after I compile I get a message saying it finished with an error which I think is whats preventing it from applying after the final step and reboot When I go to the manager tab it keeps saying no overlays installed. 2 times now I've spent money and it hasn't worked.
UPDATE: The errors all say this directory does not exist: /data/user/0/projekt.substratum/cache/SunstratumBuilder//res/
Thanks!

java null language error

Hello All
I'm running EMUI 10.1 and recently installed GMS also. I kept getting playstore error and I suppressed all notifications from playstore to avoid error. My device ID is not registered yet and some apps still doesn't work as they don't find "Google play services" framework. But playstore works fine and I'm able to install apps.
Every time I unlock the phone or at random I see an error as below about some java null language. Could someone tell me how to fix this problem!
Error: java.lang.NullPointerException: Attempt to invoke virtual method 'intjava.io.InputStream.read (byte[])' on a null object reference
Kindly help
Thanks

Cant start Messenger help me

So i unistalled messenger, to install messenger with old chat head bubbles for android 11 from this forum and that one crashed on start then i unistalled that one and installed messenger from google play and that one is now crashing too so i realized that is not a problem with the apk file. This is the report i am getting when i am launching :
java.lang.RuntimeException: java.io.FileNotFoundException: /data/user/0/com.facebook.orca/crash_log: open failed: EACCES (Permission denied) path: /data/user/0/com.facebook.orca/crash_log exists: false canWrite: false parent exists: true parent canWrite: false user id: 0 is system user: true openFileOutput error: /data/user/0/com.facebook.orca/files/crash_log: open failed: EACCES (Permission denied) at com.facebook.messenger.app.MessengerApplication.A051436) at X.003.AL95) at X.02s.run15) at Z.init(unknown) Caused by: java.io.FileNotFoundException: /data/user/0/com.facebook.orca/crash_log: open failed: EACCES (Permission denied) path: /data/user/0/com.facebook.orca/crash_log exists: false canWrite: false parent exists: true parent canWrite: false user id: 0 is system user: true openFileOutput error: /data/user/0/com.facebook.orca/files/crash_log: open failed: EACCES (Permission denied) at X.03r.<init>228) at X.00M.A0A167) at com.facebook.messenger.app.MessengerApplication.A05134) at X.003.AL95) at X.02s.run15)
I saw permission denied in report so i allowed every permission but that doesnt help too. My phone is Poco x3 Pro and it is on miui 12.5.2 EU version.
did you fixed this? i have the same problem
ignorujem said:
did you fixed this? i have the same problem
Click to expand...
Click to collapse
No actually, no one known the fix for this so far.
-deleted
CikaMare said:
No actually, no one known the fix for this so far.
Click to expand...
Click to collapse
I found a solution for myself.
I deleted the FACEBOOK FOLDER under "/root/Data/App/" and under "root/data/User/0/".
Then I deleted the app and reinstalled it from Play Store and it worked.
But your device must be rooted!
Samo671 said:
I found a solution for myself.
I deleted the FACEBOOK FOLDER under "/root/Data/App/" and under "root/data/User/0/".
Then I deleted the app and reinstalled it from Play Store and it worked.
But your device must be rooted!
Click to expand...
Click to collapse
Ah i think its worth a try. Will let you known if that fixes the problem for me
Samo671 said:
I found a solution for myself.
I deleted the FACEBOOK FOLDER under "/root/Data/App/" and under "root/data/User/0/".
Then I deleted the app and reinstalled it from Play Store and it worked.
But your device must be rooted!
Click to expand...
Click to collapse
Thank god it works! My Facebook app crashing after fresh installing from play store.
After uninstalling the app then just remove "com.facebook.katana" folder from "root/data/User/0/" and reinstall from play store it will work.
Kudos!!
If someone else has same problem then just open Titanium Backup, search for messenger app and (wipe data - frost - defrost) and then it should work again.
Root needed.

Categories

Resources