Database Info

notification fix

OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.

sam00561 said:
OK guys I hope this hasn't already been covered but here goes anyway. I have found this fix for notifications not arriving when doze is enabled. Iff you go into the particular app e.g what's app then into data usage you must select the following settings see pic below. then all the notifications will arrive straight away regardless of doze state.
Click to expand...
Click to collapse
Yes that seems to be the problem. I had made a post months ago. It's very hidden feature by Lenovo and I think it's wrong to pre-restrict all background data. User should decide what to do.

I think they lenovo did it to block unnecessary data usage but i agree it is not needed and people are thinking their is something wrong with their phones.

Thanks for the tip

Thanks Sam, I saw this on the JJ review of Nougat. Is this for Nougat as my MM P2 settings don't look like the screenshot.
Sent from my Lenovo P2a42 using Tapatalk

Hi yes it is for Nougat the comment posted on JJs review regarding this fix was posted by me also.

Confusing settings these as the first one makes it look like enabling the "Restrict background data" option will disable background data, when in fact it does the opposite. You need to have both of these options enabled so the sliders are green, then you need to open Settings > Power Manager > Battery Optimization
Then you need to search for the apps that you need to fix notifications and change the option so it says "Don't optimize". Then the phone won't 'helpfully' close the app when the phone has been unused for a long time. This is why notifications are stopping.

precisely i agree quite confusing it took me a while i had to get a friend to send me whats app messages continuously untill i figured all this out but im glad i finally did.

If you make the changes to fix the notifications, shut down and power the phone back on rather than do a reboot. The settings don't seem to work until the phone has properly rebooted.

Is it worth noting that elsewhere it's stated that turning off doze altogether (using ADB) might be a saner option? Consensus seems to indicate it's basically a curse with little value, and that would certainly hold water in light of the battery capacity of the P2.
https://forum.xda-developers.com/lenovo-p2/help/regretting-purchase-t3611968

I think the following helps. Credit goes to JasonMR and manototh (Taken from oneplus.net forum)
JasonMR
KitKat
JasonMR, Nov 2, 2016 :
Guys, to avoid having to run the ADB command after each reboot follow these instructions (please note, the files should be downloaded to a PC and then transferred to your phone via USB otherwise they mess up sometimes):
You need to enable USB debugging mode in Developer options first
Download and install this apk and transfer it to your phones storage - https://drive.google.com/file/d/0BxD...w?usp=drivesdk
Then connect phone to PC and allow the drivers to install
Download and install ADB here - https://drive.google.com/file/d/0B0M...ljU2NPR0k/view
Go into the ADB folder, hold shift, right click and select "Open command prompt here"
Type the command: adb devices (now hit enter)
It should return your phones serial number is connected correctly
Run this command in ADB: adb -d shell pm grant com.adamioan.scriptrunner android.permission.DUMP (now hit enter)
Download this file and transfer it to your phones storage - https://drive.google.com/open?id=0Bx...VA4YmxGTS1OX3c
Open the SH Script runner app and tap the three dots in the top right corner, select "Load" and locate the file from teh previous step
Click the Circle button with the play sign at the top of the screen
You should see the message "Idle mode disabled" which means that Doze has now been disabled.
Whenever you reboot your phone, open the SH Script runner and the command will still be there, just click the play button to run the script again.
And that is it, two clicks to disable Doze after each reboot.
Full credit to manototh for putting this together originally.

Doze does not need disabling iff you follow my advice in the initial post i have tried and tested this and can confirm it works fully.

This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?

Spacedog79 said:
This is really frustrating. No matter what settings I use I still don't get notifications after a while. I don't want to go modifying my phone, can someone post a step by step if they have it working properly?
Click to expand...
Click to collapse
Follow my ordinal post and also go into battery optimisation and disable optimization for things like sms eggs what's app Facebook etc all the things you need notifications for should be disabled from sleep mode under battery optimization.

Like this

sam00561 said:
Like this
Click to expand...
Click to collapse
Yes thats exactly how I've done it. I've also tried every combination of settings under Apps for Unrestricted data usage.

And also the setting here

sam00561 said:
And also the setting here
Click to expand...
Click to collapse
Yep doesn't work either.

Perhaps your only option left is to try the disable doze app which has worked for many people but it's a paid app.

Just to update it does seem to be working properly now. I'm not 100% sure but I think turning the phone all the way off and on again instead of rebooting with the settings correct had the desired effect.

Nav bar stuck on in full screen apps

Ok, guys, I tried searching through the forums and I'm not seeing a thread related directly to this so here goes.
Last night my daughter had my phone and now when I'm in full-screen apps, (specifically I play summoners war) the nav bar won't auto minimize like it should. It's pretty annoying since it covers up my skills and nothing I can really do. There has to be a specific option I can't find but in settings>display, there is no navigation section. I am running totally stock pixel, no root. android 8.1.0. I don't want to get into any command line prompts because this had to have happened without it, so I hope someone can help me out here.

Not sure what could be, but if in adb you type "settings put global policy_control immersive.full=" (yes, with nothing after the "=") it will reset any kind of modifications made on navbar/statusbar immersive settings, reverting back to stock.
I know you asked a solution without commands, but since I don't know what could be the cause I don't have specific ideas. So if you want, give it a try.

Keyboard typing not recognized by apps in OOS

Hi - I am running OOS 10.3.1 on my OP7P. I am currently using the GBoard keyboard, and I have also used SwiftKey.
I have been experiencing a problem where I go into an app, start typing on the keyboard (say, entering a search in the browser or replying to a text message), but the keys are not being recognized in the app. If I switch to another app, the keyboard typing is recognized again. The keyboard typing is also recognized again when I switch back to the application that didn't recognize the keys a moment before.
This problem occurred with GBoard and SwiftKey, so it looks like it is an OOS issue - not keyboard related.
This seems to occur most frequently when bringing the phone out of sleep, but I'm not 100% sure on that.
I have been seeing this problem for over a month now, and some of my friends with OP phones have seen this as well.
Has this keyboard issue been previously identified?
¿GJ?

Has anybody else seen/debugged this problem?
I have seen this keyboard problem referenced by other users on Reddit, so I know that I'm not the only one having this issue.
¿GJ?

That happens to me randomly, mostly when I'm typing something on a site in any web browser. I still haven't figured out why it happens.

Happend to me randomly in messenger apps and in-game chats as well.
I am using fleksy keyboard.

This happens to Ice Bear when an app is open in the foreground and then locking the OnePlus 7 Pro for a few minutes. If Ice Bear recalls, this has happened since OOS 9.

I may have found a potential solution, which was posted here on Reddit.
For the TL;DR crowd, set up an ADB session to your OP phone, and type this: adb shell settings put global policy_control null*
Apparently, there could be an issue on our phones with immersive mode combined with gesture navigation, which this command is supposed to fix.
I can say that I haven't seen the keyboard typing problem reoccur since I sent this command to my OP7. I will keep y'all informed on how this works for me long-term.
¿GJ?

¿GotJazz? said:
I may have found a potential solution, which was posted here on Reddit.
For the TL;DR crowd, set up an ADB session to your OP phone, and type this: adb shell settings put global policy_control null*
Apparently, there could be an issue on our phones with immersive mode combined with gesture navigation, which this command is supposed to fix.
I can say that I haven't seen the keyboard typing problem reoccur since I sent this command to my OP7. I will keep y'all informed on how this works for me long-term.
¿GJ?
Click to expand...
Click to collapse
Ah..so immersive mode and gestures combined causes the issue. Ice Bear will also give the solution a shot and will report back in a week.
Edit: For anyone wanting to execute the ADB command from their OnePlus 7 Pro, use any terminal app. Grant root with: su
After, type: settings put global policy_control null

Ice Bear said:
Ah..so immersive mode and gestures combined causes the issue. Ice Bear will also give the solution a shot and will report back in a week.
Edit: For anyone wanting to execute the ADB command from their OnePlus 7 Pro, use any terminal app. Grant root with: su
After, type: settings put global policy_control null
Click to expand...
Click to collapse
Oh, yeah - I forgot to mention root is required to execute this command.

Update: I haven't seen this issue reoccur at all since I made the patch.

How To Guide Found a way to fix MIUI dark mode problems!!! (Without ROOT)

I'm using a poco x3 pro so i decided to post it here but it should work with all the miui devices so hope other people can find it as well...
here's the problem i had:
https://www.reddit.com/r/DBZDokkanBattle/comments/pe4q54
forced-dark was making some text invisible in my favorite game. and that game was not listed under the "individual apps" section.
i searched for a fix and i only found other peoples' complaints about the same issue, i just bought this phone 5 days ago and it's a relatively new model so i thought it was a device specific bug and i was expecting a fix but i see complaints from months ago... some people were able to fix it with a root but i don't wanna root my main device.
anyways, here's the fix, just enable usb debugging and type this command:
Code:
adb shell setprop debug.hwui.force_dark false
that's all...
if you switch between light and dark mode or reboot your device you have to repeat this.
this will disable forcing dark mode on all the apps.
i really hate that this is possible but xiaomi just doesn't let us choose this option via user interface..

Konetsu said:
I'm using a poco x3 pro so i decided to post it here but it should work with all the miui devices so hope other people can find it as well...
here's the problem i had:
https://www.reddit.com/r/DBZDokkanBattle/comments/pe4q54
forced-dark was making some text invisible in my favorite game. and that game was not listed under the "individual apps" section.
i searched for a fix and i only found other peoples' complaints about the same issue, i just bought this phone 5 days ago and it's a relatively new model so i thought it was a device specific bug and i was expecting a fix but i see complaints from months ago... some people were able to fix it with a root but i don't wanna root my main device.
anyways, here's the fix, just enable usb debugging and type this command:
Code:
adb shell setprop debug.hwui.force_dark false
that's all...
if you switch between light and dark mode or reboot your device you have to repeat this.
this will disable forcing dark mode on all the apps.
i really hate that this is possible but xiaomi just doesn't let us choose this option via user interface..
Click to expand...
Click to collapse
Welcome to XDA and thanks for sharing!

delete pls

Konetsu said:
I'm using a poco x3 pro so i decided to post it here but it should work with all the miui devices so hope other people can find it as well...
here's the problem i had:
https://www.reddit.com/r/DBZDokkanBattle/comments/pe4q54
forced-dark was making some text invisible in my favorite game. and that game was not listed under the "individual apps" section.
i searched for a fix and i only found other peoples' complaints about the same issue, i just bought this phone 5 days ago and it's a relatively new model so i thought it was a device specific bug and i was expecting a fix but i see complaints from months ago... some people were able to fix it with a root but i don't wanna root my main device.
anyways, here's the fix, just enable usb debugging and type this command:
Code:
adb shell setprop debug.hwui.force_dark false
that's all...
if you switch between light and dark mode or reboot your device you have to repeat this.
this will disable forcing dark mode on all the apps.
i really hate that this is possible but xiaomi just doesn't let us choose this option via user interface..
Click to expand...
Click to collapse
How to fix with root

nani666 said:
How to fix with root
Click to expand...
Click to collapse
Install the app Buildprop editor from Play Store.
Give it root access.
Tap the three dots.
Tap New.
Under name type "debug.hwui.force_dark" without the quotes.
Under value, type "false" without the quotes.
Reboot.

Themes / Apps / Mods Quick tip on adjusting screen saturation on rooted pixel

I always found stock pixel color saturation to be a bit washed out. I prefer the look of more saturated color palette. Even choosing "adaptive" color on display options is still not good enough for me.
If you're rooted and want to increase color saturation do the following:
Open any Android terminal with root capabilities, I personally use Termux.
Type "su" and hit enter to grant root privileges. I don't know if it's a necessary step, but I change the directory to the root of the phone by typing "CD /". Then I copy and paste the below code into the terminal. I personally set my "x.x" to 1.25. hit enter and it will automatically take effect. You can change the values at anytime afterwards to go higher or lower. Values will go back to stock after a reboot using this method, so if you don't like it, just reboot to go back to stock values.
"service call SurfaceFlinger 1022 f X.X" (x.x sets saturation up to 2.0)
I HAVE NOT TESTED THIS, but in the past I have used this code to permanently set the saturation level on boot:
Setprop persist.sys.sf.color_saturation X.X
using this, the saturation level will remain to the chosen value on boot. Again, I have not tested this on the pixel 7 Pro.

That's interesting as I also find the "adaptive" setting too washed out on Pixels.
I wonder if this could be used through a root app with more control over colors and such?

works - thank you!

Ghisy said:
That's interesting as I also find the "adaptive" setting too washed out on Pixels.
I wonder if this could be used through a root app with more control over colors and such?
Click to expand...
Click to collapse
I'm sure it could but that's beyond my capabilities lol l

Gotta wonder what effect this might have on...everything? Battery life...screen life...brightness level adjustments when on auto? YMMV

But what can we use after
"service call SurfaceFlinger 1022 f X.X" to disable if needed ?

Attinderkahlon said:
But what can we use after
"service call SurfaceFlinger 1022 f X.X" to disable if needed ?
Click to expand...
Click to collapse
I believe 1.0 is the stock value. So you can either enter the line again and replace whatever previous value you used with 1.0, or you could just reboot the device and it'll go back to the stock saturation settings.

jaseman said:
Gotta wonder what effect this might have on...everything? Battery life...screen life...brightness level adjustments when on auto? YMMV
Click to expand...
Click to collapse
It could have a negative effect on battery life....but I would guess its minimal. Been using a custom saturation value for 2 days now, no known issues.

I haven't checked yet but going by previous devices, there is probably a way to access other color modes using tasker. "boosted" has been taken away from the menu, my guess is its still there and can be accessed with tasker. I'll check it if i keep the phone.

Thank you for this, legit the only thing driving me crazy was the dull colors now it looks more like I wanted. You da man.

Glad I could help!

Dope. Going to give this a shot whenever I decide to root.
Now, has this always been a thing? If so, I wish I knew about it so I didn't have to use apps the entire time to tweak it to my liking.

Curiousn00b said:
Dope. Going to give this a shot whenever I decide to root.
Now, has this always been a thing? If so, I wish I knew about it so I didn't have to use apps the entire time to tweak it to my liking.
Click to expand...
Click to collapse
I've been using this mod since the OnePlus 6T....so it's been a thing for a while at least for me.

Has anyone tried this? Getting a Parcel Null error when I enter the code. Rooted. That "CD /" comes back as inaccessible too. It's probably me, but not able to get this to work as of now.

Unable to set up after boot, i get the setprop inaccessible

System is read-only for now. There's no rw mount mod so can't really edit build prop to set it on boot. We'll just have to wait for twrp or any system rw mount mod

xgerryx said:
Has anyone tried this? Getting a Parcel Null error when I enter the code. Rooted. That "CD /" comes back as inaccessible too. It's probably me, but not able to get this to work as of now.
Click to expand...
Click to collapse
I get parcell null response as well but it still works.
Also, I just tested changing directory in not necessary so you can skip the "CD /" part.
Trust me on this, run the script with a value of 0.5 and hit enter. Go to your home screen, open apps and scroll through your phone. Then open your emulator again, run the script with a value of 3.0 and hit enter. Then look about your phone it will look completely different. From there, just keep messing around with different values until you get one you like.

Pain-N-Panic said:
I get parcell null response as well but it still works.
Also, I just tested changing directory in not necessary so you can skip the "CD /" part.
Trust me on this, run the script with a value of 0.5 and hit enter. Go to your home screen, open apps and scroll through your phone. Then open your emulator again, run the script with a value of 3.0 and hit enter. Then look about your phone it will look completely different. From there, just keep messing around with different values until you get one you like.
Click to expand...
Click to collapse
Ok yes I'm seeing it now. Thanks for following up. It does change exactly what we're looking for. I bet you someone can make this into a little app or a magisk module.

xgerryx said:
Ok yes I'm seeing it now. Thanks for following up. It does change exactly what we're looking for. I bet you someone can make this into a little app or a magisk module.
Click to expand...
Click to collapse
Glad ya got it working! Yeah I'm sure it's possible, having to run the script everytime you boot is kind of annoying

I wish we could adjust the white balance. This screen is so yellow looking