yashsingh1/xdaforums huggingface dataset:
[Android Apps and Games] kcdubya:
Accessibility Service Turned Off When Closing Gravity Screen

Using a Samsung Galaxy Note 10. I just started using Gravity Screen. For security reasons I have created a set of Bixby Routines that ensure that Gravity Screen is open during the day time if I am home. They close Gravity Screen if I am not home or if its night time.

The issue that I have run into is that when the Bixby Routine closes Gravity Screen the Accessibility Service for Gravity Screen is turned off and I need to manually turn it back on when opening Gravity Screen is automatically started.

Any ideas how to keep the Accessibility Service from turning off?

Note, I did see that battery optimization can be an issue with Accessibility Services, and I have disabled it for Gravity Screen, but this did not solve the problem.

I suppose I could use Tasker as, from this forum, it appears to have tighter integration with Gravity Screen, but I have quite a large number of Bixby Routines that work together, and I would prefer not to redo them unless that is my only choice.

Thanks
[Android Apps and Games] devinpatterson:
EDIT: ooops never mind, I found that disabling phone permission disables the proximity sensor. Thank you for Gravity screen BTW it's a great app, much appreciated.

Hi Plexnor, I was wondering if under the "Lying face up" heading, it might be possible to make the proximity swipe/cover actions (to add 1.5 secons & 5 minutes to timeout) optional settings? I have an older Axon M folding phone and the orientation I hold it in results in my finger covering the proximity sensor while I'm holding it.

If possible I'd also love to have a option added to the "power button support" that the screen will not be turned on *until* a specified period of time has passed after clicking the power button, (a few seconds to put down my phone, so motion and proximity sensor don't activate until it's on the table.....since I can't use the "Lying face up" mode without the proximity sensor adding to my display time out).

Thanks for your time
[Android Apps and Games] :
Been using this for 5 years. It's a solid app. Good work.
[Android Apps and Games] Grossmeister_T:
Hi everyone,

Are there known issues with Android 11?

Hi,

My Problem is that my Device Oneplus 7T worked perfect. Now after updating to Android 11 the Problem is that if the Screen is turned on by the App the Face ID camera doesn't start anymore - only BY double tap or Power Button. That's REALLY annoying...

Cache cleared, re-installed, any other ideas? Permissions are given...

Without this it is Just a waste of battery - I bought the App.
[Android Apps and Games] DavidGP:
Just was going to say thanks for the awesome app, and keep up the great work. Works perfectly on a Google Pixel 6 Pro.
[Android Apps and Games] sidapo:
Hello, I really like this app. I would like to upgrade to the pro version, but I cannot activate the upgrade process within the app ("error billing service unavailable", I am running lineageOS without gapps). Can I pay you some other way & receive the pro version?
[Android Apps and Games] aZZ!:
Love the app. Been using it for quite some time. It does what its supposed to do on my Pixel 6 Pro, but there is one thing. I was wondering why my Pixel is stuck at 60 Hz, and there it is.. sadly its Gravity Screen, that causing the 60 Hz on the homescreen, app drawer etc. basically the whole launcher. I neither want to deal with less than 120 Hz anymore, nor i want to go without Gravity Screen. Help! Anyone else experiencing similar behavior?

Edit: Tested around a bit, and to be more specific its the "Any Direction (Flip Cover)" option in the Pocket Sensor section. If its enabled, it immediately locks the refresh rate to 60 Hz.
[Android Apps and Games] ri0thamus:
Just got a new S22 and while at first GS seemed to be working, after a couple of updates it keeps flashing a fingerprint/PIN request while trying to turn the screen off. All of my settings are correct. Any suggestions?

EDIT: After some poking around, it seems to be the "Fingerprint unlock, Smart Lock Support" causing the trouble. If I select the "timeout" option, the above issue happens. If I select "accessibility" then the screen will turn off. Though it will be locked whenever the screen turns back on.

I've also figured out that the Keep Screen on by Motion isn't working, at least the timeout isn't being extended.
[Android Apps and Games] EnigmaXtreme:
Was there anyway to setup a delay with GS, like you need to have the prox sensor covered for 2 seconds before it switched on/off, because on my new S21 it just immediately flashes off
[Android Apps and Games] libove:
The app works exactly as advertised on my Pixel 6a, which unfortunately isn't exactly as what I hope to find 😅

Particularly, I don't want the screen to lock - I don't even want the app to need the device administrator permission; for me, it would be perfect that the app detect the closed cover/ face down/ in pocket (so, only either proximity or light sensor for detection), and then just dim the screen down to very low or minimum brightness, without affecting at all the Android system settings for screen timeout and when to actually lock (requiring PIN to unlock).

With the app features configured per how Gravity works, to get to as close as possible to the way I'd like to use it, I end up with two problems (again, working exactly as advertised, so I'm making feature requests here):

1. When set to NOT PIN-lock the screen, the screen timeout (which I usually keep at 30 minutes) gets set to (null) which the Pixel 6a's Android 13 interprets as the minimum setting (15 seconds), so the screen will timeout much much too quickly

2. when set to NOT PIN-lock the screen, it seems that Gravity actually prevents the screen from ever being PIN-locked, which is unacceptable for me for security reasons.

So, feature request - does Android permit that the app could use sensors to detect face down/ in-pocket/ cover closed, and in that circumstance do nothing more than dim the screen to very low (to reduce screen battery use), then restore to the previous brightness when the cover is opened, without ever modifying any system settings at all other than current-brightness?

thanks to the author for a great app; no thanks to Google for making it so very difficulty to actually have our devices behave in the usable ways that we want!
[Android Apps and Games] Laugh2:
Gravity Screen is one of my favourite apps - as it is for many. :) I've used it for years with great success on a Samsung Galaxy S5 running LineageOS (lately LOS 18.1). Thank you to the developer(s) esp. Plexnor. However, due to the need for VoLTE I've had to change devices to a Galaxy s10e , unfortunately.

On the Galaxy s10e (Android 12, Stock ROM), however, Gravity Screen is not behaving well. Sometimes the screen goes dark when it is put into a pocket - often not. Even when the screen is turned off I never have to put in a password or meet any kind of lock/security screen - I return to exactly where I left off. This behaviour is completely different to the years of previous experience.

I've tried un-/reinstalling, going through the menus to allow background operation i.e. prevent sleeping, and reallocating permissions incl. stopping their removal if unused. However, this was not successful.

Does anyone have any suggestions how to get GS back to its normal, excellent performance?
[Android Apps and Games] ri0thamus:
According to the logs, Plexnor hasn't logged in since sometime in 2020 so I'm pretty sure the app is dead with no updates to come which is a shame. I greatly preferred the GS behavior prior to newer android updates from 2022 to the only other option I've found, which is KinScreen (which doesn't turn off when face down). If anyone has any contact with the devs or an alternate suggestion for an app that will turn off when face down, I'd appreciate it.
[Android Apps and Games] ze7zez:
I suppose that by providing gesture and motion functions by manufacturers in many new devices, GS has lost potential new and old users.

Very often the functions duplicated and interfered with each other to the detriment of GS stability. The natural death of GS is therefore fully understandable to me.

I stopped using the GS I bought since I use wake-up before double-tapping the screen on my new phone, and close the screen thanks to Button Savior, which still works great on new phones despite the fact that the last update was in 2017.
[Android Apps and Games] ze7zez:
Your assessment is unfair.

Since 2012, for almost 9 years, GS worked perfectly in many devices. Any developer has the right to end support of his program without giving reasons.
[Android Apps and Games] ri0thamus:
I don't see how what I said is unfair. 1) Dev hasn't logged in for almost 3 years, seems probable that other things (RL or lack of interest) have taken attention away from the app, therefore likely not to be future updates. 2) I said it was a shame, which I think is a fair opinion of someone that used the app and wished to continue using it. 3) I never said the dev couldn't stop support. 3a) However, for a paid app (for which I did pay) it would be nice if a dev would announce the end of support.

I fully appreciate the 9 years of a working app. But I also feel I'm allowed to express disappointment in the apparent end of a useful app, whatever the reason.
[Android Apps and Games] ze7zez:
So we will accept that it is a disappointment, instead of judging that it is an shame for the developer. Whether we like it or not, we have to accept the developer's decision. Nota bene, you bought the app from Google, so you can report your dissatisfaction to Google.
[Android Apps and Games] ri0thamus:
I think you're assigning meaning to my choice of words that are not my intent. You're focusing on the word "shame" instead of the phrase "which is a shame." From several dictionaries, "If you say that something is a shame, you are expressing your regret about it and indicating that you wish it had happened differently" or "used for expressing sympathy or disappointment." Regardless, I'm not going to further engage about this here. Cheers
[Android Apps and Games] lsirg:
Does anyone know how to unlock the free version to the paid version? Google play store will not accept the payment.
[Android Apps and Games] lee714:
I LOVE IT!!! My power button broke, so the only way for the screen to be turned on was through connecting it to a USB. You save me from buying a new phone!
[Android Apps and Games] plexnor:
To turn off while charger is connected is not a real solution. It has disadvantages as well. Please, try to use the method I recommended earlier until we find a better solution for the problem..

Oh, I cannot add more checkboxes, it has already too many :)
[Android Apps and Games] plexnor:
Good to hear it helps you :)
[Android Apps and Games] steveathome:
I don't use an Android phone but this works awesome on my Samsung Tab 2 10.1. Functional and well thought out. Appreciate your work on this app. :cool:
[Android Apps and Games] plexnor:
Thank you. Nice to know it works fine on tabs as well :cowboy:
[Android Apps and Games] Acousticbeatz:
That's not an option for me because the phone and the wiring are hidden in the center console fold.

Meanwhile i'm trying to find a work around with Llama, but when i set the rule to terminate the app when a charger is plugged, the service starts itself again after a few seconds! Maybe you can provide me any hints on what i have to do to get it to work properly !?

maybe as advanced settings available over the 3 dot menu ??
[Android Apps and Games] plexnor:
Use Tasker and this plugin (https://play.google.com/store/apps/details?id=com.laptopfreek0.taskkill) and you will be able to stop the service.
[Android Apps and Games] airjyp:
its cool ! i should tried this app ! :D

[FONT="Arial ="5"]

• Sony Live with Walkman
[Android Apps and Games] Acousticbeatz:
Thank you :good: the plugin works like a charm with Llama too!

No need to buy Tasker:D
[Android Apps and Games] plexnor:
That's great. :)
[Android Apps and Games] nagendraps:
I have been using this app over two weeks & having tried many others I would say this is best tool to control screen. Besides I like the lot of choices provided for control .

However I am facing a strange issue after recent updates, whenever I move hand over proximity area screen turns off and when moved away the screen turns on. This is quite frustrating at times screen goes off when I accidentally touch the proximity area (even for a second) while trying open status bar or during playing games.
[Android Apps and Games] airjyp:
anyway i have a problem.. when i put my phone on the table, yeah its turn off itself and really works, but in a second it turn on by itself .. i dont know why? please help me

[FONT="Arial ="5"]

• Sony Live with Walkman
[Android Apps and Games] cappuccina:
I'm really impressed, it works really good on my One X with Slim Bean Rom. THANKS!!! Good Job!

Although I'm a bit sad, not to have to use the Lockscreen anymore ;D and I also kinda liked the s2w feature! LOL

Well, the On/Off feature lets me decide! And if I don't want to use it anymore I can just uninstall!

But by far best option for me is the "Keep the phone awake", cause I read A LOT, not only in forums like XDA :) but I use my device also as E-Reader for my fantasy collection! :P

And those Smart Eye or whatever apps where the camera scans your eyes are *beep* really not a good of an option for me. :D

AGAIN BIG THX!
[Android Apps and Games] nagendraps:
Please ignore my reported issue, I disabled Proximity Tool Extension which i has using before. Now working smoothly. :good:

thanks plexnor
[Android Apps and Games] plexnor:
Doses it related to the sensitivity of the Keep / Turn Screen On by Motion features? One of them may be set too high, but I just guess because I hear this issue at the first time.
[Android Apps and Games] plexnor:
I was sad little bit too when I had to stop using my lockscreen :) But if you put your favorite widgets (weather, clock, torch etc ) from the lockscreen to the home screen you do not loose anything just recognizing how big time wasters are the lockscreens :)

I'm happy to hear you like the Keep Screen On feature.
[Android Apps and Games] zerosys:
I guess i found a little bug, because of my bad english i try to explain it with an example.

Turning on the screen by swiping over the sensor works, holding my hand over the sensor a little longer the "screen-timeout" goes up to 1 minute, again 5 minutes, then 10, 15.... thats fine. But i discovered that when the screen-timeout is set to 5minutes because of this swiping the screen turns off after 5 minutes, thats right but swiping after the screen turned of over the sensor the timeout is set to 10minutes. But the screen was already turned off because of the timeout so i guess there should be a kind of reset so that swiping over the sensor again after the screen turned off should set the timeout to 1 minute, then 5 minutes...

Or am i getting something wrong?
[Android Apps and Games] plexnor:
Thank you for sharing your findings. Actually the logic of the app is: the timeout set back to normal when the phone is removed from the table, not when the screen goes off. I'm not sure this is the best for everyone needs, but I guess it's in more case convenient than to reset it at screen off but I'm not sure of that :)
[Android Apps and Games] zerosys:
Ah ok, i just can speak for myself and in my opinion its better to set back the timeout to normal when the screen goes off instead of when is removed from table.

But you´re the dev, you can do whatever you want :).
[Android Apps and Games] Gunde:
I've tried many proximity/accelerator screen on/off tools and usually I needed at least 2 different ones running at the same time to accomplish what I wanted.

This app does it all AND it does it better than any other I've tried.

So awesome! Pro bought.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mikeioannina:
[COLOR="Purple"]#include <std_disclaimer.h>[/COLOR]
[COLOR="Navy"]/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/[/COLOR]

This is an unofficial build of CM10.1.

This is an attempt to stay close to official cm10.1 and not make crazy hacks to make things working.

This is a pure CM build, only contains official CM features. I will not add any other external feature/app/etc.

For an up-to date working/not working list, bug tracker, useful guides & FAQ, visit our new website:

http://legacyxperia.github.io

Requirements:

* Only use the included kernel for 100% compatibility, bug reports with non-standard kernel will be ignored.

Installation instructions:

1. Flash boot.img (in the zip) with fastboot or FlashTool

2. Install update zip in CWM recovery

3. Install Google Apps (gapps) zip in CWM recovery (this step is optional for those who don't want Google Apps)

4. Wipe data (do this only if you come from stock ics, a newer version of android like cm-10.2 or if you have problems like Force Close after installation)

How to build:

[GUIDE][DEV] How I build my own CM10.1 test builds

Changelog:

Release/nightly changes

Downloads:

http://legacyxperia.basketbuild.com

PLEASE DON'T MIRROR OUR UPLOADS

Google apps:

Fast mirror of official gapps

http://goo.im/gapps/gapps-jb-20130812-signed.zip

NOTE:

Following xda's rule #12 spirit: If you are developing something that is based on my work, you MUST first seek my permission, you must add my name in the credits and you must add links pointing to my original thread and to my github sources.

Breaking this rule will lead me to report the thread to the moderators.

WE NEED YOUR HELP!

NEW!!! BUG Tracker

If you want to help fixing those bugs, please report the bugs in the bug tracker. Thanks!

Logs are needed (logcat/dmesg/last_kmsg), not just "got FC" or "+1" useless replies.

XDA:DevDB Information

LegacyXperia, a ROM for the Sony Ericsson Xperia Mini, Mini Pro, Active

Contributors

mikeioannina, FXP, nobodyAtall, M66B, pcfighter, shufuking, Steph310

ROM OS Version: 4.2.x Jelly Bean

ROM Kernel: Linux 3.4.x

ROM Firmware Required: Latest version of official ICS firmware: 4.1.B.0.587 or the latest supported baseband: 8x55A-AAABQOAZM-203028G-77

Based On: CyanogenMod

Version Information

Status: Stable

Current Stable Version: stable 20130908

Stable Release Date: 2013-09-08

Current Beta Version: nightly 20131108

Beta Release Date: 2013-11-08

Created 2013-09-26

Last Updated 2013-11-30
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mikeioannina:
Reserved
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] DaleX:
First

Hey is there a difference between your Rom and Shufuking's Rom. U mentioned the sources are different???
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mikeioannina:
Yes the sources are not the same, I'm trying to stay close to official cm10.1 and send bugfixes there. Bluetooth is not working here, it will be probably fixed with nAa's 3.0.8 kernel when it will be released. This rom is not intended for simple users, I created it to gather information from devs & advanced users to fix the bugs in a clean way.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] DaleX:
Can i help in some way.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] przemek4113:
Will you add support for mini pro ?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] gandhar:
my build was successful, no problems,

@anybody using this,

my apollo is crashing on the first launch. clear the data of apollo and report here if it crashes for you too.

i have a sd-ext partition, so that may have something to do with it, and so i want someone else to confirm this.

i have already created an issue on the cm bugtracker,

https://jira.cyanogenmod.org/browse/CYAN-808

logcat is attached in the issue,

i'll try to see what causes the problem,

edit:

they have closed the issue, since coconut is not an official cm-10.1 phone.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mikeioannina:
smultron build is up, mango is coming next
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Null VoiD:
i think we never be able to have a Working Bluetooth because 4.2 brings the new bluetooth stack ... We have to back port bluez which hikari no

tenshi did for cm42semc builds ... but let's hope for the best ..!
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mikeioannina:
I'm already porting the new drivers for the BlueDroid stack.

EDIT: mango build is up
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Nosferatu Alucard:
I just flashed your mango build and so far I can report two bugs:

1. Softkey Backlight not working (hardware key lighting fine though)

2. Light Sensor not working (constantly reports 0 lux as value)

Just minor stuff, does not really bother me, just wanted to state it.

Also the 4.2 camera is working in shufuking´s ROM (photos only), in your build it does not work at all, but I suppose that

is due to one of the "crazy hacks" you don´t want to use?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mikeioannina:
Key backlights is a known issue and it is already fixed in the next build

Have you flashed both kernel & rom? Check the FAQ about bug reporting :)

About the camera, don't expect working camera on cm10 or 10.1 roms except LegacyCamera. These apps will never work, only hope that sony is going to release some camera source or precompiled libs for JB or some dev makes magic things to fix the camera :P I'm not willing to hack android to fix camera since it requires extensive changes.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] porcupine02:
Hi Mike,

It's great you decided to do things sane way, try to push changes upstream and provide us with clean sources.

I have been playing with them for a few day to further customize my Cyanogen experience, but I can't figure out how to prevent 4.2 camera from building. Uncommenting BOARD_USES_LEGACY_CAMERA := true like on cm10 breaks the build for me. I suppose I could just remove camera project from manifest, but I'm going to build for mako so that's really not an option.

Thanks.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mrahmanda:
pinch to zoom in browser , gallery , and most app working ?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Nosferatu Alucard:
I tried both. The Kernel inside ZIP and nAa Kernel (which i am using now)

The reason why I did not include a logcat is because there is nothing related to light sensor in it (captured 2 logcats with and without automatic brightness and no difference in output)

When I activate automatic brightness it just dims the screen down to almost complete dark.

As said before this is not really an issue for me as I dont use auto brightness anyway. So maybe it is better to wait if other user report the same behaviour...

Gesendet von meinem Xperia Mini Pro mit Tapatalk 2

//EDIT:

In Case anyone is interested:

Here is a patch for openpdroid to work with the mango build
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Mysteryagr:
New kernel

I think the new kernel sources is ready for development:

https://github.com/nobodyAtall/msm7x30-3.0.x-nAa
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mikeioannina:
New builds are coming for all mdpi devices including nAa's 3.0.8 kernel
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] [W]ar[H]ead:
Everything will works in new builds?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mikeioannina:
Check changelog in the first post.

I'm porting 4.2 bluetooth now, maybe we'll have a proper functional 4.2 bluetooth in the next 1-2 releases
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] SS-4050:
Bluetooth will be crucial moments, when it fully fixed then we will have a "Not a perfect but Close to Perfection" 4.2.2 JB for our device despite the Camera Problem that even still exist on CM10