Database Develop

Home and Back buttons gone.

I just installed the All in one Rom and it seems to work well....however, the buttons on the bottom (for "back" and "Home") are gone. Is there a way to get it back or should I just reflash?

It says this right in the first post of the thread for that ROM:
For first time users after bootup:
Settings > System > Navigation Bar >Tablet UI soft buttons, check
Settings > Rom Control > General UI > Show Menu UI Overflow (otherwise there is no way to enable MTP, open browser settings, wifi settings, etc)
Settings > Storage> Menu (three-buttons at top right)-> USB Computer Connection > Media device (check MTP)to make sure your TP usb charges properly. I had to go into portrait to see the three buttons. It should already be checked

jsgraphicart said:
It says this right in the first post of the thread for that ROM:
For first time users after bootup:
Settings > System > Navigation Bar >Tablet UI soft buttons, check
Settings > Rom Control > General UI > Show Menu UI Overflow (otherwise there is no way to enable MTP, open browser settings, wifi settings, etc)
Settings > Storage> Menu (three-buttons at top right)-> USB Computer Connection > Media device (check MTP)to make sure your TP usb charges properly. I had to go into portrait to see the three buttons. It should already be checked
Click to expand...
Click to collapse
OOPS....I should have read more...Thanks a lot!

Pebble app close on Huawei P10

Hello all,
I notice a strange thing.
I set up my pebble app to be not closed by the mobile when screen off and to not be in battery optimisations.
But, sometimes, the pebble app is still closed by the system.
Any idea or maybe script to avoid this?

Something similar happens with running apps like Strava and Runkeeper. I haven't read any solution yet. I think the power manager is a bit too diligent )-:

M1chiel said:
Something similar happens with running apps like Strava and Runkeeper. I haven't read any solution yet. I think the power manager is a bit too diligent )-:
Click to expand...
Click to collapse
That's what i think too....

Same happens for me with Spotify, ive disabled the battery optimisation for it, but sometimes it still closes.

inoxas said:
Hello all,
I notice a strange thing.
I set up my pebble app to be not closed by the mobile when screen off and to not be in battery optimisations.
But, sometimes, the pebble app is still closed by the system.
Any idea or maybe script to avoid this?
Click to expand...
Click to collapse
I have the same problem with some apps, I found a possible solution online (don't remember where exactly).
The steps are:
> Settings > Battery > Settings (upper right corner, cog icon) > disable "Close excessively power-intensive apps"
Hope this helps.

xcascax said:
I have the same problem with some apps, I found a possible solution online (don't remember where exactly).
The steps are:
> Settings > Battery > Settings (upper right corner, cog icon) > disable "Close excessively power-intensive apps"
Hope this helps.
Click to expand...
Click to collapse
Thank you mate..
it makes no sense but this seems to be the best working solution at the moment...
These are my current settings for pebble and AdroidWear (got a german device so maybe there are some translation issues)
----------------------------------------------------------------------------------------------------------------------------------------------
- Settings > Battery > Cog Icon (upper right) > disable "Close excessively power-intensive apps" SOLUTION MAYBE
- Settings > Apps > (another) settings (button middle) > special access > ignore battery optimisations
- Settings > Battery > close when screen off whitelist
- Phone Manager > cleaning > Cog Icon (upper right) > eceptions whitelist
- No power saving activated
All of them are a bit similar but only one seems to take advance of the pebble problem
cheers

Hello all,
I found something strang, i rebrand my P10 VRT-L09C109 (Orange France), and no more problem.......
I think something is different vs VTR-L09C432 but what???? i don't know

inoxas said:
Hello all,
I found something strang, i rebrand my P10 VRT-L09C109 (Orange France), and no more problem.......
I think something is different vs VTR-L09C432 but what???? i don't know
Click to expand...
Click to collapse
What do you mean rebrand?
Sent from my VTR-L29 using Tapatalk

App kill

How do I get an app like Animated Navbar keep running in the background?

Go to Settings -> Battery -> App Launch and search for the App. Set it to manuelly and allow it to keep running in the Background.

tobi2709 said:
Go to Settings -> Battery -> App Launch and search for the App. Set it to manuelly and allow it to keep running in the Background.
Click to expand...
Click to collapse
Thanks but I already tried that but it still close it

The memory management on this phone is hyper aggressive and causes problems with lots of apps, even when they're whitelisted. No solution until someone makes a custom kernel, AFAIK.

LSHA1980 said:
How do I get an app like Animated Navbar keep running in the background?
Click to expand...
Click to collapse
Try this:
Settings
Apps & Notifications
Apps
Settings (down to left)
Special access
Ignore battery optimization
(Choose)All apps
Tap on app of your choice:
(Choose) Allow

Thanks guys. It's working now after firmware update to 120 (C432)

Thanks guys. It's working now after firmware update to 120

How do you reset Optimize battery usage settings modifications?

"Settings > Apps > ⋮ > Special access > Optimize battery usage"
How do I reset any changes I make to this panel?
"Settings > Apps > ⋮ > Reset app preferences" doesn't work for this.

Duplicate the original one was here
How to reset Optimize battery usage settings modifications?
"Settings > Apps > ⋮ > Special access > Optimize battery usage" How do I reset any changes I make to this panel? "Settings > Apps > ⋮ > Reset app preferences" doesn't work for this.
forum.xda-developers.com

nixnixnixnix4 said:
"Settings > Apps > ⋮ > Special access > Optimize battery usage"
How do I reset any changes I make to this panel?
"Settings > Apps > ⋮ > Reset app preferences" doesn't work for this.
Click to expand...
Click to collapse
Check to make sure nothing is set as Device Administrator that's graying it out*.
Setting>Biometrics and security>Other security settings>Device Amin apps
If that's not locking it out another app or setting likely is. Google searches are useful; it can be another Samsung model or OS as the operation, issues and solutions many times tend to be similar. So this is how you can find more solutions for newer Androids.
*My Goggle Play Services disable and stop tabs were grayed out. Until I realized the Find My Device was enabled as a Device Administrator which it automatically does after a reboot.
Disabling it restore the grayed out tabs.
Ha-ha, it had me going for a bit

"Settings > Apps > ⋮ > Reset app preferences" doesn't reset the "Optimize battery usage" back to defaults.
What's the fix for this?

nixnixnixnix4 said:
"Settings > Apps > ⋮ > Reset app preferences" doesn't reset the "Optimize battery usage" back to defaults.
What's the fix for this?
Click to expand...
Click to collapse
If they're not grayed out simply toggle them off one by one. With Samsung you find occasional miscommunication probably due to technical writers that may not understand what they're writing about. It's funny sometimes.
Worse are hidden double tap to open options and menus. There's a at least one on my 10+ not including the Easter egg and Developer options.

blackhawk said:
If they're not grayed out simply toggle them off one by one. With Samsung you find occasional miscommunication probably due to technical writers that may not understand what they're writing about. It's funny sometimes.
Worse are hidden double tap to open options and menus. There's a at least one on my 10+ not including the Easter egg and Developer options.
Click to expand...
Click to collapse
I have about 70 apps with Optimize Battery usage turned OFF.
Then there are about 500 apps with Optimize Battery usage turned ON.
I think I should toggle this off on all 500 or some apps and then see if I this affects performance or notification reception in any way.
Either way, the system will show me if there is an app sucking an egregious amount of power.

nixnixnixnix4 said:
I have about 70 apps with Optimize Battery usage turned OFF.
Then there are about 500 apps with Optimize Battery usage turned ON.
I think I should toggle this off on all 500 or some apps and then see if I this affects performance or notification reception in any way.
Either way, the system will show me if there is an app sucking an egregious amount of power.
Click to expand...
Click to collapse
I found it best not to use this on my device/OS version (Pie).
As for usage reporting that can be misleading as dependencies may not be reported but be responsible for the excess usage.
Android Services has a huge number of apks under its umbrella; I simply firewall block it as it's rarely needed. Disabling it though will cause issues.
The worst offenders were clearly visible on Karma Firewall's logs which doesn't function on Android 10 or 11.

blackhawk said:
I found it best not to use this on my device/OS version (Pie).
As for usage reporting that can be misleading as dependencies may not be reported but be responsible for the excess usage.
Android Services has a huge number of apks under its umbrella; I simply firewall block it as it's rarely needed. Disabling it though will cause issues.
The worst offenders were clearly visible on Karma Firewall's logs which doesn't function on Android 10 or 11.
Click to expand...
Click to collapse
Stop fighting these losing battles:
Look at my thread/post here: https://forum.xda-developers.com/t/...c-of-google-and-samsung.4276505/post-85010119

nixnixnixnix4 said:
Stop fighting these losing battles:
Look at my thread/post here: https://forum.xda-developers.com/t/...c-of-google-and-samsung.4276505/post-85010119
Click to expand...
Click to collapse
My 10+ is running fast and stable with good battery life but more importantly it's fulfilling its mission 100%.
Cry me a river of tears...

Themes / Apps / Mods [App] Fix of buggy proximity sensor - Locking screen from being pressed during phone call

Note: app compatible with any phone with 1080x2400 screen or lower. Probably higher too, try it. Also it's impossible to make such block when talking in messengers (more precisely, it's difficult). App won't work without gapps, rare case.
Instead of classic reliable optical sensor we have sucky ultrasonic one.
Sometimes it does not turn off the screen while phone call and something is pressed with ear or cheek up to dropping call.
Popular workaround is app "Call Proximity Sensor Fix" which automatically turns off the screen. Or you can press the power button immediately after the answer.
But IMHO this is inconvenient because if you need to look at something on the screen it will not turn on by itself which is so familiar.
My simple application makes screen insensitive to taps. And unlike analogs soft buttons and status bar are blocked too (but not gestures).
On screen will be translucent button that disables lock if you need to use the phone:
– Long tap on button - unlock (button will turn green)
– Short tap when unlocked - lock again
– Long tap when unlocked - remove button at all so as not to interfere with e.g. for entering text
When second call comes in screen will automatically unlock so you can easily answer or hang up. Then it blocks again.
When manually launching the application there will be a question whether to enable 4 seconds delay for an outgoing call. So you able to choose SIM card.
Made by powerful Tasker, the project was exported as standalone application via App Factory. Implemented via scenes with new full-screen blocking type.
Location of button adapted for default AOSP / Google Dialer. It can be misplaced for third-party dialers and / or interface scale. It's impossible to cover all possible variants. So if it really bothers you, install Tasker and project below. Then change coordinates of the buttons.
Installation
Follow manual carefully, otherwise nothing will work.
Application is safe and doesn't have internet access.
1. Download APK below this post
2. Install it via file manager and launch
3. Answer the question about delay, decision can be changed later by launching app again
4. Open Settings > Apps & Notifications > In-Call Screen Lock
5. In "Notifications" turn off them all completely, otherwise they will be annoy you
6. In "Permissions" enable everything: Contacts, Call List and Phone
7. MIUI: right there in application settings enable "Autostart"
8. MIUI: and in "Background" select "No restrictions"
9. Custom: Settings > Apps & Notifications > Advanced > Special app access > Battery optimization > All apps > In-Call Screen Lock > Don't optimize
10. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
11. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > In-Call Screen Lock > Allow display over other apps
12. Settings > [MIUI: Advanced settings] > Accessibility > In-Call Screen Lock > enable "Use In-Call Screen Lock"
If you using Tasker
1. Download ZIP archive below this post
2. Extract file from it to phone/Tasker/projects
3. Tap on "House" icon at the bottom > Import Project > In-Call_Screen_Lock
4. If you don't need a delay on an outgoing call: delete / disable action #3 ("Wait") from the "In-Call Lock Start" task
5. Custom: Settings > Apps & Notifications > Advanced > Special app access > Display over other apps > Tasker > Allow display over other apps
6. MIUI: Settings > Privacy > Management > Special app access > Display over other apps > Tasker > Allow display over other apps
7. Settings > [MIUI: Advanced settings] > Accessibility > Tasker > enable "Use Tasker"
UPD: files updated, fixed small bug.

does this affect battery life

shakeelbirmani said:
does this affect battery life
Click to expand...
Click to collapse
No.

Tested now on my RN10-pro... works just fine! Thank you!

Tested without gapps and it didn't work. I use the standard phone app from Arrow OS. I do all settings from your instruction.
There was no 4 seconds query of the sim card. The and no lock screen button.

Social_Work said:
Tested without gapps and it didn't work.
Click to expand...
Click to collapse
Unfortunately, APK's exported by Tasker always have dependencies from GMS no matter actions it should perform. Sorry, I can't fix that.

I reinstal Arrow with Gapps and Install tasker. IT works great! Thx a lot! Now ist this Phone uesable.

Great application. Tested it via Tasker and works. Thank you so much!
Small question, if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again. How do I get the button back then?

Note: sensors are automatically calibrated and sometimes this creates a problem.
To cleanup and recalibrate the sensors, all you need to do is this:
Bash:
# dd if=/dev/block/by-name/persistbak of=/dev/block/by-name/persist conv=notrunc
For me that solved everything on official MIUI V13.0.12.0 (and previously on V12.5.9.0).

Amazfit User said:
if you do use the power button while in call to lock the screen and you unlock it again and then use your unlock button, it unlocks but the button disappears so you can't lock it again
Click to expand...
Click to collapse
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
Zibri said:
sensors are automatically calibrated and sometimes this creates a problem
Click to expand...
Click to collapse
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.

Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
Thanks for the information. Tested it and ticking the block overlay + fixes the issue. I guess it's because even though I'm able to tap the icon and other call icons the phone is still locked. I guess the overlay + makes sure that the lock off scene is still visible on the "lock" screen. I'm on Samsung One UI 4.1 with the native Google dialer.
Thanks for the help.

Bonoboo said:
That's strange. I tested as you wrote and button visible, nothing in profile logic should block its appearing. I used clean Android 11 and AOSP dialer.
As possible workaround please test this: Tasker > tab "Scenes" > Lock On > tap on lock icon > tab "Long tap" > action "Show Scene" > tick "Block Overlay+"
That's legit for classic sensor, but I'm doubt, that ultrasonic store its calibration data there (if even have it). "Sensor" unreliable just by design.
Click to expand...
Click to collapse
ultrasonic sensor can be even manually calibrated and the calibration is indeed stored and used.
Also: the ultrasonic sensor works in software, relying also on the position and angle of the phone.
If that measurement fails or is inaccurate, everything is ruined.
Trust me: try to do a fastboot flash of V13.0.12.0 then reset that partition as I said.
Then you can tell me if it improves or not.
For me now it works perfect both in DUO both in the stock dialer and messenger.

You can find the latest stock firmwares here:
Codes and study of the Redmi Note 10 PRO (SWEET) and some findings
code name 76937 com.miui.powerkeeper.cloudcontrol.CloudUpdateReceiver 8437625 com.miui.powerkeeper.thermalconfig.ThermalConfigReceiver 37263 com.miui.powerkeeper.ui.framerate.FrameRateSecretCodeReceiver 2877...
forum.xda-developers.com