Related
The instructions to enable system ui tuner on the web don't appear to be working...holding down the sprocket on the toggle screen till it spins doesn't enable the menu...anyone else know how to get to it?
Also still looking for a way (non xposed) to assign long hold of back button to kill foreground app.
Should say system UI tuner added to settings after holding for about 5 seconds.
seabro01 said:
Should say system UI tuner added to settings after holding for about 5 seconds.
Click to expand...
Click to collapse
It should..I agree...thats what all the suggestions say and I can see the wheel spin....but it's not in the list. Are you saying it worked for you? If so I may need to go back to a fresh install and try this again.
famewolf said:
It should..I agree...thats what all the suggestions say and I can see the wheel spin....but it's not in the list. Are you saying it worked for you? If so I may need to go back to a fresh install and try this again.
Click to expand...
Click to collapse
Yeah, I have system UI tuner in settings.
famewolf said:
It should..I agree...thats what all the suggestions say and I can see the wheel spin....but it's not in the list. Are you saying it worked for you? If so I may need to go back to a fresh install and try this again.
Click to expand...
Click to collapse
For me also it worked.
I finally got the thing to appear and I'm still not certain how...I think marshmallow is much more picky about the touchscreen and the glass screen protector I have on it....taps are not being interpreted right all the time....anyway thanks for confirming. Ironically by the time I enabled the menu I had already enabled xposed and found ways to set all the things I woul d have been able to do from system ui.
So ive been having this issue recently where the phone will turn off apps that i want to run in the background and i cant figure out a way to fix it. The biggest issue is with AdGuard. When im using it, the phone will randomly kill the background process and the vpn will turn off allowing all the adds to come pouring in. I've mentioned this issue on the oneplus forums and nobody there seems to know how to fix it. I'm considering moving to a custom rom once i find one that works well with my needs but first i want to make sure this isnt something that i can fix on the stock rom since i dont really need all the custom settings that come with custom roms. Im running the latest stable 9.0 pie/OOS.
Thanks for any help in advance
When you open the recent app tab press on the 3 dots right above the app. The press lock. That worked for me
did you set it to not optimize in battery settings?
under battery optimization. disable advanced optimization.
MrSteelX said:
under battery optimization. disable advanced optimization.
Click to expand...
Click to collapse
ive disabled all battery optimization options including adaptive battery.
whizeguy said:
did you set it to not optimize in battery settings?
Click to expand...
Click to collapse
yes ive gone into the specific adguard app and disabled battery optimization in that app
noppoer2 said:
When you open the recent app tab press on the 3 dots right above the app. The press lock. That worked for me
Click to expand...
Click to collapse
Ive enabled the lock and it still clears it and i have to reopen the app and re-enable the lock
Ive also set background process limit to be unlimited in the developer options. I cant think of anything else to do except maybe install adguard as a system app???? I've seen that this problem occured with the OP5 as well and people modified build.prop to increase the process limit, i've since found out that the option thats in the build.prop file is gone in the OP6 so i cant do that either. This is driving me crazy and i dont even know if its related to the os or the kernel.
Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/...apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
blackhawk said:
You mean unlocking or just turning the screen on an unlocked phone?
The app DoubleTap does away with using any buttons to turn the screen on/off. Simply 2x tap it. https://play.google.com/store/apps/details?id=com.vinance.lockdown&hl=en_US&gl=US&referrer=utm_source=google&utm_medium=organic&utm_term=double+tap+apk&pcampaignid=APPU_1_oD7zX7-SMMvesAWsh5_ADA
Click to expand...
Click to collapse
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
gsosacristian said:
I mean turning on a phone screen. Since if it allows me to unlock it, but not turn it on.
P.S: I did not know the app you mention (it did not occur to me to look for something like that XD) I will try it, thanks for the link
Click to expand...
Click to collapse
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
blackhawk said:
That's strange. Have you tried remapping the button? Are there options to do so in settings?
Possibly another 3rd party apk remapped without you being aware of it?
I been using this app for over a year. To spite the ad warnings, it has none. Uses almost zero battery, never connects with the internet and is rock solid stable. Saves button life just keep the screen pointed away from your flesh when in your pocket to avoid accidentally taps.
Note: I never gave it administrator privileges as I never use a lock screen. So not sure about its behavior in that mode of operation.
Click to expand...
Click to collapse
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
gsosacristian said:
I tried the app a few moments ago and it seems to work fine, the flesh thing is apparently configurable (assign the volume key, which is the most similar).
Regarding the mapping or 3rd party apks using the button, I see it almost impossible, not only because I don't use any app of this type (that reassigns keys) but in completely clean installations of stock firmware this happens to me (and I don't have any option key remapping that I know of).
It's very weird, at least for me. Because not only does it "break" to unlock, but it is only with stock firmware and even if I change the kernel (I tried using the quantum kernel) the key does not work when turning on the screen. But with the GSI it works without problems.
I even googled questions related to Always in display, power or something similar and nothing, there seems to be no conflicts.
Click to expand...
Click to collapse
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
hehe, if it is true that there are really hidden things XD
Anyway, I am testing this app and if I see that it works I will be encouraged to install the stock firmware and by the way I will try to dig deep into the configuration in search of an option that I have overlooked
blackhawk said:
Make sure there's no remapping options for it in settings. If so it may be buried or under accessibility options... I've seen hidden Sammy drop down menus with no indication they are there until you double tap the top label. Swell.
Or simply bypass and double tap it!
Click to expand...
Click to collapse
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
gsosacristian said:
Update:
I have installed the stock firmware and used the app you recommended, but no results: / The same thing keeps happening.
I have checked the accessibility options and there is nothing blocking the button :O
Click to expand...
Click to collapse
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
blackhawk said:
You enabled the appropriate buttons in it's settings?
I'm running Pie; it may not be compatible with 10 and up because of the overlay crap.
Click to expand...
Click to collapse
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
gsosacristian said:
Oh! There is the problem, the firmware is Android 10
Bad luck for me, it will be time to return to a GSI momentarily XD
Click to expand...
Click to collapse
Can't verify that but suspect it... Q sucks.
Lol, Google wants to protect you... I feel safer already. Not.
gsosacristian said:
Hello everyone. I would like to know if anyone experienced this, and if anyone has a solution (or at least an idea why).
The power button of my Samsung Galaxy A7 (2018) (SM-A750G) phone does not work at unlocking the screen (if it works in the rest of the functions such as opening the shutdown menu, entering recovery, etc.) when I am using stock firmware, but it works perfectly when using a GSI or any other custom OS.
Do you have any idea what could happen? It should be noted that this happened to me when my phone had the stock firmware and I had never modified my equipment at all... It just happened suddenly and for that reason I switched to a GSI. But now I would like to use the stock firmware, but I will not be able to do it with this "bug".
Thanks 4 the help
Click to expand...
Click to collapse
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
droidz94 said:
It seems like I have a similar problem. Do you have any recommendations ROM for SM - A750GN?
Click to expand...
Click to collapse
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
gsosacristian said:
Personally, the one that I liked the most (and the one that works best) is the Google official (Android 10): https://developer.android.com/topic/generic-system-image/releases But one problem is that it is very outdated.
Anyway, here is a list of some GSIs that you can check and test which one works on your device: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
And here is a tutorial that worked well for me to install GSI: https://forum.xda-developers.com/t/guide-workings-gsi-best-treble-gsi-roms-for-a7-2018.4069121/
Click to expand...
Click to collapse
Thanks! I'll try that
EXACTLY same problem here. I will not repet your words, I'll just say you described EXACTLY what is happening with my phone, a Galaxy A7 2018 (128GB RAM, Brazilian model - A750G/DS).
I can confirm that:
1 - Problem of screen never turning on after being turned off for the first time happens at all stock ROMs. Tried at android 10, downgraded to 9, couldn't downgrade to 8 because odin would not write the image, but the problem persisted on ALL stock ROMs up untill now.
2 - Problem DOES NOT happen at the TWRP recovery. Flashed TWRP just now, so I can flash a GSI, and I can turn the screen on or off as many times as I wish at TWRP screen, without any problem.
These informations corroborate, almost without a shadow of doubt, the idea that this is actually a software problem, not a hardware one. I'm gonna flash the google 10 GSI now, with quantum kernel V3 (seems to be a requirement, I would like to make as litle changes as possible) and post the results.
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
joaodalvi said:
Having a hard time installing the GSI, gets stuck at bootloop all athe time...
Click to expand...
Click to collapse
[GUIDE][A-ONLY][A750x] Guide on How to flash GSI (Updated: 10.06.2019)
I'm not responsible for whatever damage this could possibly cause to your device. If you appreciate the work i have done, Feel free to buy me a cup of coffee @paypal Welcome to GSI For Galaxy A7 2018 ONLY FOR A750F/A750FN/A750GN Some...
forum.xda-developers.com
Try this. You need flash a "GSI Boot Fix" to use a GSI on A750.
I'm using Lineage OS 19 on Samsung A52 4g for a while and I've found some bugs:
- Bluetooth handsfree doesn't work in internet calls, like WhatsApp, Telegram, etc.
- when you're in a call, the screen will go off but when you want to hang up, you must turn the screen on with power key.
- screen light is a bit crazy! I put it in automatic mode, it changes for no reason! When I turn on power saving mode, light will go to the max!
I'll write further bugs in this thread when I find it.
Thanks for developing Lineage OS.
parsa_foss said:
I'm using Lineage OS 19 on Samsung A52 4g for a while and I've found some bugs:
- Bluetooth handsfree doesn't work in internet calls, like WhatsApp, Telegram, etc.
- when you're in a call, the screen will go off but when you want to hang up, you must turn the screen on with power key.
- screen light is a bit crazy! I put it in automatic mode, it changes for no reason! When I turn on power saving mode, light will go to the max!
I'll write further bugs in this thread when I find it.
Thanks for developing Lineage OS.
Click to expand...
Click to collapse
2nd one is fixed btw. Install the latest version
Ryzen5950XT said:
2nd one is fixed btw. Install the latest version
Click to expand...
Click to collapse
There isn't any new update in updater
parsa_foss said:
I'm using Lineage OS 19 on Samsung A52 4g for a while and I've found some bugs:
- Bluetooth handsfree doesn't work in internet calls, like WhatsApp, Telegram, etc.
- when you're in a call, the screen will go off but when you want to hang up, you must turn the screen on with power key.
- screen light is a bit crazy! I put it in automatic mode, it changes for no reason! When I turn on power saving mode, light will go to the max!
I'll write further bugs in this thread when I find it.
Thanks for developing Lineage OS.
Click to expand...
Click to collapse
parsa_foss said:
I'm using Lineage OS 19 on Samsung A52 4g for a while and I've found some bugs:
- Bluetooth handsfree doesn't work in internet calls, like WhatsApp, Telegram, etc.
- when you're in a call, the screen will go off but when you want to hang up, you must turn the screen on with power key.
- screen light is a bit crazy! I put it in automatic mode, it changes for no reason! When I turn on power saving mode, light will go to the max!
I'll write further bugs in this thread when I find it.
Thanks for developing Lineage OS.
Click to expand...
Click to collapse
Where is the hide app option?!
parsa_foss said:
There isn't any new update in updater
Click to expand...
Click to collapse
Because the updater only works on official builds.
parsa_foss said:
Where is the hide app option?!
Click to expand...
Click to collapse
Use any third-party app from Play Store.
Simon1511 said:
Because the updater only works on official builds.
Use any third-party app from Play Store.
Click to expand...
Click to collapse
So how can I update it?!
parsa_foss said:
So how can I update it?!
Click to expand...
Click to collapse
Download the latest update from the XDA thread and flash it with TWRP or Lineage recovery.
Simon1511 said:
Download the latest update from the XDA thread and flash it with TWRP or Lineage recovery.
Click to expand...
Click to collapse
Is that mean I must erase all of my data again?!
parsa_foss said:
Is that mean I must erase all of my data again?!
Click to expand...
Click to collapse
No, just flash the ROM without wiping anything.
parsa_foss said:
I'm using Lineage OS 19 on Samsung A52 4g for a while and I've found some bugs:
- Bluetooth handsfree doesn't work in internet calls, like WhatsApp, Telegram, etc.
- when you're in a call, the screen will go off but when you want to hang up, you must turn the screen on with power key.
- screen light is a bit crazy! I put it in automatic mode, it changes for no reason! When I turn on power saving mode, light will go to the max!
I'll write further bugs in this thread when I find it.
Thanks for developing Lineage OS.
Click to expand...
Click to collapse
I've installed the latest version and first thing doesn't work is hotspot!
It turns on but no device can connect!
parsa_foss said:
I've installed the latest version and first thing doesn't work is hotspot!
It turns on but no device can connect!
Click to expand...
Click to collapse
Already known. We have a fix, will be done in the next update
parsa_foss said:
- screen light is a bit crazy! I put it in automatic mode, it changes for no reason! When I turn on power saving mode, light will go to the max!
Click to expand...
Click to collapse
Yes I noticed it also in pixel rom. I remember before some months when the rom was just launched, the screen brightness were going up and down quickly, like the sensor is just purely honest any small change in environment (even unnoitced by naked eye). But now after I returned, I saw the developer seemingly fixed it.
T
parsa_foss said:
I've installed the latest version and first thing doesn't work is hotspot!
It turns on but no device can connect!
Click to expand...
Click to collapse
There is an app "intent filter verification service" which keep pops up error and suggest to close the app!
It was in older version too.
kingozilla said:
Yes I noticed it also in pixel rom. I remember before some months when the rom was just launched, the screen brightness were going up and down quickly, like the sensor is just purely honest any small change in environment (even unnoitced by naked eye). But now after I returned, I saw the developer seemingly fixed it.
Click to expand...
Click to collapse
Well I reduced it, but the problem has no fix yet.
I'm using this nova launcher, and whenever I attempt to use split screen I receive the error "pixel launcher has crashed." Nova is set as my default launcher though. I'm on a p7p latest update.
Yeah, I'm on Nova 7 and split screen is working just fine for me.
It's working fine on my P7Pro as well...
Schroeder09 said:
I'm using this nova launcher, and whenever I attempt to use split screen I receive the error "pixel launcher has crashed." Nova is set as my default launcher though. I'm on a p7p latest update.
Click to expand...
Click to collapse
Works fine as we speak
I really loved split screen when we had the three button navigation. You could double tap the recents button and then split your screen immediately. I wish Google would make it easier than it currently is. I really wish if you went into recents by swiping up to your right from the bottom and it was an option below like screenshot. This is one of the things that drives me nuts with Google and there horrible human factors
Here's the log.
rester555 said:
I really loved split screen when we had the three button navigation. You could double tap the recents button and then split your screen immediately. I wish Google would make it easier than it currently is. I really wish if you went into recents by swiping up to your right from the bottom and it was an option below like screenshot. This is one of the things that drives me nuts with Google and there horrible human factors
Click to expand...
Click to collapse
I agree. I've wondered for a long time how Split Screen went from being so easy to no longer anything I think about anymore
I just went back to the pixel launcher to see if it would do split screen. It does. Whenever I go back to nova it crashes and split screen doesn't work. What are the motions/ gestures to get it to work on a13 on a p7p? I've read on some older threads where people had the same issue that they had to find a way to make it work with seemingly "secret" gestures.
You have to swipe from the bottom up to the right to access your recent apps. Press the app icon you are currently using in recents. A selection menu will pull down and you select split screen. The current app will move to the top of the screen and allow you to select another app to split screen with.
With split screen in the past, you would have a three-button navigation at the bottom. The button on the right was recents. If you double pressed the reasons button, the app you are currently on would go to the top of the screen and allow you to select another app to split screen. It was easy and one of the best functions of Android. When they move to gestures, they took the function away and now it takes three more touches to get to split screen.
At the same time, Android has not worked on this function and over time it has become bug laden mess. I find it crashes often.
Have you tried nova launcher 8 beta? Split screen works fine with that build. Also the prime if you have paid from it works too.
lil_kujo said:
Have you tried nova launcher 8 beta? Split screen works fine with that build. Also the prime if you have paid from it works too.
Click to expand...
Click to collapse
Thanks for the reply. Yes, I updated to 8.0.3 last night and I still have the same issue. I think aosp mods through lsposed is causing me trouble. I'm asking for help in that tread. Others have similar setups to mine, so idk what's going on. Anyone here in a13 with nova launcher on a p70 and have split screen working?
I use nova on a13 but I'm fully stock and there is no issues. So it might be the some mod. Typically if searching for the culprit of a bug you would first disable all the mods and go from there testing one mod at a time. It's very hard to find a solution when you have a modded environment. Basically since on stock android with no mods it's not having issues most likely it's one of the mods you are using that is perhaps causing the issue.
Schroeder09 said:
Thanks for the reply. Yes, I updated to 8.0.3 last night and I still have the same issue. I think aosp mods through lsposed is causing me trouble. I'm asking for help in that tread. Others have similar setups to mine, so idk what's going on. Anyone here in a13 with nova launcher on a p70 and have split screen working?
Click to expand...
Click to collapse
I also use Nova 8.xx beta with AOSP Mods and have no issue with split screen
Split screen breaks when you disable animations in developer options
Specifically you can't turn off Animator duration scale
dr.wtf said:
Split screen breaks when you disable animations in developer options
Specifically you can't turn off Animator duration scale
Click to expand...
Click to collapse
Wow. You got it. This was it. I DESPISE animations though. They make the phone feel slow like an iphone. Disabling animations is always the very first thing I do with a new phone. So is this a nova launcher problem? If I go back to the pixel launcher with animations totally disabled there is no issue.
I typically use split screen at least once a week, and sometimes it's more or less. I've been using nova for almost a month it seems. Maybe I really hadn't tried split screen prior to making this post, but that seems odd. What I'm getting at here is that it seems even nova had to have functioning split screen while animations were totally disabled. I have all animations disabled except for the "animator scale." Now I have animations when swiping back from apps to go home. Popping a new app open still doesn't have an animation.
The lowest animation scale I have is . 5x. On past phones and older android versions I think there were even smaller options. Anyone know of a root or Xposed module to give me more options? If I can cut this down to .1x or even . 25x I will deal with it.
At . 5x animations and only using split screen 1x/week or I might just deal with not having split screen. I despise animations.
Edit: https://forum.xda-developers.com/t/animations-set-scale-set-to-25.4365695/
Will those adb commands through my on-device terminal work? Can I use other scales like . 1 instead of just . 25x? Will this add animations for everything? Currently I only set the animator duration scale to . 5x. All the other animation options are still toggled off.
I also found a scaleR magisk module, but the last activity in the thread was in 2020, and I don't wanna message round with bootloops, wiping, and restoring my phone this weekend.
EDIT 2: I issued the command "settings put global animator_duration_scale 0.01" in terminal (had to use SU /root command) and the command itself works, but anything below the menu options of . 5x makes the nova launcher behave as if you have animations off, ie split screen doesn't work.
I also turn animations off first thing. I'll rather pass on the dual screen feature than turn animations on.
dr.wtf said:
I also turn animations off first thing. I'll rather pass on the dual screen feature than turn animations on.
Click to expand...
Click to collapse
So the limitation is on the nova side? The feature still works on the pixel launcher with animations off. Any suggestions on overcoming this? So I just need to email the nova team or report it as a bug? I would consider it a a bug- flip a switch (animations) that has nothing to do with the functionality and that functionality then works? That's a bug. I wonder if a magisk module could do this or if through tasker the animations could be toggled on only when the split screen option was selected. Whenever split screen was exited another shell command ran through tasker would turn animations back off.
Guess a bug report is always good. For Tasker I think autoinput can do this
dr.wtf said:
Guess a bug report is always good. For Tasker I think autoinput can do this
Click to expand...
Click to collapse
Collect a bug report through android system?
I have autoinput, but have never used it a single time. I was understanding that it actually had to do its tasks in the foreground. If I use it to toggle the animation scale does that mean I'm going gto see the settings app flash to the foreground, an automated button click on the animation scale toggle, and then have things revert back to where I was in trying to split screen something?
I don't know how Nova launcher devs can receive bug reports. They probably have some support link somewhere.
My idea was sending the command via Tasker as soon as you open the recents view which can be recognized with autoinput. And then you can come up with an idea for an exit task condition. Just play around with it.