Ahoi!
Finaly I installed Xposed, but now I'm facing a problem:
When I set my preferred MicrosoftLauncher, it shows only until I press Home or Backbutton from other apps or reboot.
Then again the launcher/homescreen falls back to stock Launcher3.
The dialog, asking for default launcher does not show.
Same Problem, when choosing Launcher from settings, as when starting MicrosoftLauncher by app icon.
The dialog however shows, when I choose the "set-default" option in the MicrosoftLauncher settings – but the setting only persists until reboot.
Any suggestions how to set and keep my launcher settings?
problem persists
kai-dj said:
Ahoi!
Finaly I installed Xposed, but now I'm facing a problem:
When I set my preferred MicrosoftLauncher, it shows only until I press Home or Backbutton from other apps or reboot.
Then again the launcher/homescreen falls back to stock Launcher3.
The dialog, asking for default launcher does not show.
Same Problem, when choosing Launcher from settings, as when starting MicrosoftLauncher by app icon.
The dialog however shows, when I choose the "set-default" option in the MicrosoftLauncher settings – but the setting only persists until reboot.
Any suggestions how to set and keep my launcher settings?
Click to expand...
Click to collapse
Problem is still there – any solution or hint?
I'm almost about to write some kind of script, that manualy switches to MS-Launcher after boot – does any1 know, where default launcher is stored in config-files – maybe it'd be enough to just insert the right value while init at boot…
bump…
I "disabled" bloatwares via ADB or rather "uninstall" it and was using Package disabler before the dev ran away rendering the app unusable.
Recently, I factory-reset my mobile and the bloatwares came back which was expected but I had problem accessing some of the options to customize such as AOD. I wanted to customize my AOD and whenever I hit the AOD's settings in the menu it had a couple of second of freeze time and display "Always on Display has stopped" There are 1 or 2 more apps/settings that do that. Not sure how to fix that anyone?
Long story short:
I installed mortal kombat x and didnt get any push notifications. I then changed some settings under Battery menu (App launch - >manual control) and under Apps (special access - > disable battery optimization) and then it worked like a charm.
But now i accidentally clicked "automatic control" in the App launch submenu and even after setting it back to manual, the notifications wont appear again.
I restarded the phone many times and switched back and forth the configurations, but nothing works. There is some kind of software conflict but i cant figure it out. Any thoughts?
Like the title say, I'm in trouble getting the notification of any app I install : I disabled vivo.pem as suggested in one other thread and allow notofication per single app (that were turned off before) and last disabled the background battery optimization for those apps.
No luck after all, as nothing show up when I send whatsapp mess e.g.
Any ideas?
(Latest Origin firmware)
PassingComplexion said:
Like the title say, I'm in trouble getting the notification of any app I install : I disabled vivo.pem as suggested in one other thread and allow notofication per single app (that were turned off before) and last disabled the background battery optimization for those apps.
No luck after all, as nothing show up when I send whatsapp mess e.g.
Any ideas?
(Latest Origin firmware)
Click to expand...
Click to collapse
I had to use the uninstall command on vivo.pem to get my notifications to work, disable didn't help me on the latest firmware.
Also, check the app permissions, hold down app, info, app permissions.
Turn off (remove permissions if app isn't used)
Single permission settings (turn all on the switches), you can also review permissions
Go back 2 screens and select notifications, select all sliders and then check your desired app notification is going out via priority display.
Finally go to settings, battery, background power consumption management, and change the setting for the app you want to not sleep by choosing high background power usage.
So annoying, I know, too many settings and easy to forget one
Good luck!
DJorgio said:
I had to use the uninstall command on vivo.pem to get my notifications to work, disable didn't help me on the latest firmware.
Also, check the app permissions, hold down app, info, app permissions.
Turn off (remove permissions if app isn't used)
Single permission settings (turn all on the switches), you can also review permissions
Go back 2 screens and select notifications, select all sliders and then check your desired app notification is going out via priority display.
Finally go to settings, battery, background power consumption management, and change the setting for the app you want to not sleep by choosing high background power usage.
So annoying, I know, too many settings and easy to forget one
Good luck!
Click to expand...
Click to collapse
Thanks for the time spent in the long answer; however still no notifications on the tested app (whatsaap) with all the reccomended settings.
Is since 2015 I think that I don't have a chinese firmware phone and the things have changed, in fact, before, was enough to install play store and all the notification were received without further settings.
DJorgio said:
I had to use the uninstall command on vivo.pem to get my notifications to work, disable didn't help me on the latest firmware.
Also, check the app permissions, hold down app, info, app permissions.
Turn off (remove permissions if app isn't used)
Single permission settings (turn all on the switches), you can also review permissions
Go back 2 screens and select notifications, select all sliders and then check your desired app notification is going out via priority display.
Finally go to settings, battery, background power consumption management, and change the setting for the app you want to not sleep by choosing high background power usage.
So annoying, I know, too many settings and easy to forget one
Good luck!
Click to expand...
Click to collapse
Hey Guys,
i also did every setting as told and my Notification for especially WhatsApp isn't working at all.
Sometimes it does, but then all of a sudden it just refreshes when I open the App itself.
I even put it down in the Bar with the 5 Main Apps, in hope those would be refreshed or kept alive in the Background.
Not sure anyway what you mean with uninstalling vivo.pem.
Suckz kind of, because apart from that it really is a great Phone... aside from Android Auto not working.
F4ISR said:
Hey Guys,
i also did every setting as told and my Notification for especially WhatsApp isn't working at all.
Sometimes it does, but then all of a sudden it just refreshes when I open the App itself.
I even put it down in the Bar with the 5 Main Apps, in hope those would be refreshed or kept alive in the Background.
Not sure anyway what you mean with uninstalling vivo.pem.
Suckz kind of, because apart from that it really is a great Phone... aside from Android Auto not working.
Click to expand...
Click to collapse
You have to plug in phone on computerand run ADB command to uninstall vivo.pem.
Vivo.pem is a system that aggressively shut down apps to save battery power, to much shut downs and notifications stop working.
Check the thread "Origin Os initail review" on here and you will find out how to do it. Takes only 10 minutes
Robsjo said:
You have to plug in phone on computerand run ADB command to uninstall vivo.pem.
Vivo.pem is a system that aggressively shut down apps to save battery power, to much shut downs and notifications stop working.
Check the thread "Origin Os initail review" on here and you will find out how to do it. Takes only 10 minutes
Click to expand...
Click to collapse
Just did that, thanks for the advice, much appreciated
F4ISR said:
Just did that, thanks for the advice, much appreciated
Click to expand...
Click to collapse
After doing the uninstalling did it stop the issue?
I uninstalled, rather than disabled, their power saving vivo.pem, ensured all my apps had priority permissions for notifications, disabled battery saving, and added them to 'autostart' in their respective permissions, and I get proper notifications for all the social media and messaging apps. The only small glitch come with Google Messages which won't display notifications in system wide dark mode. You can get around that by enabling the 'chat bubbles' option in Google Messages settings as they do work in dark mode.
Notifications are not the only issue , i cannot select Mock gps location app in Developer Mode ...
I press on the app i want to use ,but nothing happend , the app is not selected .
Anyone noticed that too ?
Thanks
There is no need to uninstall vivo.pem, I think. Just some few steps:
1. Go to recent apps and lock it.
2. Settings -> Apps & permissions -> App manager -> WhatsApp -> Permissions -> Single permission settings -> Autostart and Startup enabled.
3. Settings -> Battery -> Background power consumption management -> WhatsApp -> Select high background power usage.
4. Settings -> Battery -> More settings -> Disable Sleep mode.
Works fine for me.
Do you use Whatssup? after the latest OS update it cannot connect to linked devices
[FOR REFERENCE ONLY]
Problem solved!
The confounding variable was NOT Xposed Framework, but conena's Gesture Control app that was set up to use Immersive Mode to hide the navigation bar. And according to this post that I landed on purely by chance, if you don't exempt the Lockscreen Settings app, it causes all these problems.
Note that this problem has nothing to do with the app, it's the Immersive Mode setting to blame, on which any setting change at all will cause these same problems (to be fair, conena's app does preemptively discourage this)
Solution
Use a Substratum overlay to hide the navbar instead; do NOT use GravityBox to do that by setting navbar height to 0, or qemu.hw.mainkeys=1 in build.prop (which doesn't work, BTW). Next, backup your gesture bar data and wipe the data of the app, then restore the bar data – just don't fiddle with that Immersive Mode setting again!
Well, some explanation is in order because it wouldn't make for a great thread title:
I am running the last stock Oreo build on this G8441, which is 47.1.A.12.20, for the primary reason of being able to use rovo89's Xposed Framework because the original XPrivacy module that's vitally important to me does not run on any of the EdXposeds or LSPoseds.
Using systemless Xposed with the latest Magisk version (and older ones too, nothing changes) I find that if I were to set a lockscreen to anything other than "None" and reboot, I will have times where I simply can't see the display when pressing the power button -- but weirdly enough the touchscreen still keeps taking touch input! The only way around is to remove the lockscreen, reboot, then set your locking method and try not to have it restart for any reason.
It's quite obvious that systemless Xposed is causing this problem (Xposed can't be installed normally on this firmware version) because this problem can be reproduced even without any modules active. But I'm at a complete loss as to what's actually causing this lockscreen interference, because I've tried taking system logs with and without Xposed and there's simply nothing at all different except it taking insanely long times for the display to activate upon unlock (but the touch input working just fine for some reason?) and there's a small, dim red LED near the proximity sensor that stays stuck as long as the display is.
Please help me, I'm absolutely out of ideas -- and no, I can't upgrade to Pie, I have to stay on Oreo for the sake of the XPrivacy module.
So it seems like 47.1.A.12.75 is the last problem-free Oreo version for normal Xposed Framework, and I wouldn't mind using that, if it weren't for the fact that there doesn't seem to be any VoLTE-activating SIN file for India for it below 47.1.A.12.270. There's a 2G phaseout in progress with the largest carrier and it's only a matter of time before there'll be no fallback network and I'll have to have VoLTE at any cost.