Develop Bugs

Has anyone else noticed Power Saver and AudioWizard stop working when ASUS Clock app

So I've done a lot of testing after being hit with some bugs earlier in the day where Power Saver would stop working and I'd pop-ups telling me com.asus.services has stopped working - here's the thing, I've had that package frozen for weeks without running into hardship!
After a factory reset and everything working correctly, I again had Power Saver stop working (I also noticed AudioWizard wouldn't open). I noticed these things happened to me after freezing ASUS Clock so I decided to test. Sure enough, defrosting ASUS Clock and rebooting fixed the problems! I was able to open Power Saver and AudioWizard again!
Just to make sure, I refroze ASUS Clock and defrosted various other packages (including previously frozen com.asus.services). It's the ****ing clock app. I don't know why but the goddamn clock app is the key.

The Power Saver App has an Auto mode which switches Modes depending upon the user defined Times.
I think that without the clock app, the Power Saver app is unable to startup, as it finds a dependency missing.
Regarding audio wizard, even i am confused. Maybe both the apps share a common file which became unaccessible when clock was frozen.
Just out of curiosity.
Why do you need to freeze clock????

Oh I prefer the stock Android Clock and sometimes Timely and don't like having apps duplicating function. ?

Recent apps button does nothing and I can't pull down quick settings tiles!

I'm having a couple of issues on my HTC 10 that started to happen when I enabled Xposed on my device (it was installed through Magisk when everything was working, but the module was disabled).
Today I enabled the Xposed Magisk module and Xposed itself and rebooted my device. Enabled a few Xposed modules and rebooted the device again. I noticed my phone was very sluggish after enabling Xposed... Home screen widgets took a lot more than they used too to load, long-pressing the power button (to show the reboot/power off menu) too like 10 seconds to show up (it used to take like 1 second or less) and overall device was a bit slow. I decided to disable all modules but keep Xposed enabled, rebooted and the phone was still very sluggish, like nothing changed. Uinstalled all Xposed modules and the Xposed Magisk module too for now, the phone is not slowing down to a crawl anymore.
However, after all this I'm having some issues that I didn't have before all this:
I can no longer open the "recent apps" menu. The button works (it vibrates when I press it) but nothing happens.
Pulling down the screen from the top to bottom I can expand the notification bar but pulling down again to display the quick settings tiles does nothing.
I don't understand the relevance of Xposed with these issues but they started to happen when I enabled Xposed. At first I though some module was interfering with these things, that's why I disabled/uninstalled Xposed, but the problems remained.
Thoughts?

Fixed this issue like this: https://stackoverflow.com/a/39394723

This is OS issue. RUU or a clean flash of w.e rom you're on would work as well. However, your solution is easier and saves your data.

New Samsung settings and GPS

On android devices it was always possible to switch localisation services and GPS separately.
You could keep localisation services turned on (with wifi and phone) and turn off GPS to spare battery.
Now with android pie and new smasung settings it is all or nothing as there is onlys one setting :
I can turn on localisation and it turns on GPS
But if you turn it off, it disables everykind of localisation : GPS but also wiifi ...
Has anyone noticed this and is there a workaround ?

I'm not a fan of the always enabled GPS
I really do not like this at all. I have typically always kept GPS off as far back as Jellybean, favoring Locations battery saving mode, unless I needed navigation or something like that. GPS is power hungry and there's no reason to have to have it always enabled. I know Pie is supposed to help with battery usage and I honestly can't judge whether or not it really does yet as this is day two for me.
Pie is supposed to prevent apps from accessing sensors in the background but I've read that this doesn't apply to GPS so this whole thing is probably part of a marketing thing giving Google as well as app devs the ability to monetize ads based on specific location of us the users. Location is frequently wrong about where I am anyway, showing me a street over and even though I have WiFi and Bluetooth scanning enabled. As a result, my Safe Unlock no longer works when I'm home (only location I have enabled) which sucks. With Oreo I saw this somewhat often and only after I had been home for a while would the Safe Unlock work properly and I accepted this as a consequence of having Location in battery saving mode but now I'm not sure. I just no that with Pie, so far, Safe Unlock hasn't functioned once. My designated home WiFi that I'm on as I type should cause Safe Unlock to do it's thing but it's not. Maybe Location or Safe Unlock are broken. I have seen reports of both regarding Pie so I can't blame it in Samsung. I guess I'll have to try to figure out which of these features is broken.
I'm not sure if this is related to the Location issue but I also noticed that Samsung+ is not working for me. When I first tried to open it I got a notification that I need to have location enabled, I agreed (it was anyway), then I was shown a red screen with error or format codes that force closed faster than I could decipher it. This could be related or could have been broken in an update. Other than for ad purposes, and I don't recall seeing any other than Samsung ads in the Samsung app, I don't know why Samsung+ needs to access location services as it only works in the US and the network tells the app I'm in the US as well as the tower I'm accessing. I suppose it's another attempt to collect user info related to WiFi, Mac address and Bluetooth. I only got the "enable location" request the first couple of times I tried opening the app but the red error screen and FC both still occur. I tried to get a screenshot but I could only manage about half of the screen before it FC'd. I attached the partial pic. It's the bottom half of the screen. When it closes, the app window seems to slide up like when you close apps in the recents view. This brings up another complaint...Screenshot is slow to respond so events like this are next to impossible to capture. I'll have to get a camera out and try.

dronarg said:
On android devices it was always possible to switch localisation services and GPS separately.
You could keep localisation services turned on (with wifi and phone) and turn off GPS to spare battery.
Now with android pie and new smasung settings it is all or nothing as there is onlys one setting :
I can turn on localisation and it turns on GPS
But if you turn it off, it disables everykind of localisation : GPS but also wiifi ...
Has anyone noticed this and is there a workaround ?
Click to expand...
Click to collapse
Yes I noticed this. I use 'Tasker' app as a workaround. I set Location Mode to High Accuracy when using Navigation apps, and set to Battery Saving after closing the Navigation app. You can also just create a widget on home screen to toggle Location Mode to High Accuracy or Battery Saving.
I confirmed this setting by using 'Power Toggles' app widget. When the GPS toggle in widget is highlighted, it means on High Accuracy mode, if not highlighted it's on Battery Saving mode.

dronarg said:
On android devices it was always possible to switch localisation services and GPS separately.
You could keep localisation services turned on (with wifi and phone) and turn off GPS to spare battery.
Now with android pie and new smasung settings it is all or nothing as there is onlys one setting :
I can turn on localisation and it turns on GPS
But if you turn it off, it disables everykind of localisation : GPS but also wiifi ...
Has anyone noticed this and is there a workaround ?
Click to expand...
Click to collapse
I have yet to notice any adverse battery performance since I've been on pie and I've been on it since the start of the official betas. I was annoyed at first because I had always used battery save mode but really it's been a non issue for me.

Tilt-to-wake broken in recent update

Recently (last week or two) tilt-to-wake has stopped working, and the option to enable it no longer exists on the on-watch settings menu.
The toggle for tilt-to-wake is still present in the Wear OS phone app (under Advanced settings) but even when on, the tilt-to-wake functionality no longer worked. The only way to wake the watch is to tap the screen or press the side-button.
Anyone else noticed this? It is driving me mental!
Cheers

Uhh... scratch that. After rebooting watch, new Google App was installed and it is back to working as normal! Should have tried that first.

Location stop working when screen is off

Hello,
I have a Honor 5X on LineageOS 15.1 (kiwi).
After several weeks, i found a curious behaviour : GPS location is stopped when screen is off.
I use Google Maps to record my journey between home > work > home, and all is allright when phone's display is on. If screen is turning off, no location is recorded.
Same observation with IFTTT app. Applet using location aren't triggered in the correct area. It's triggered after 15/20mn or when i'm turning on the screen.
- Complete reinstall of ROM : Issue persist
- Disable optimization battery for "IFTTT", "Fuse Location", "Google Maps" : No effect.
Have you got a similar issue ? Or a solution ?
Thanks !