Develop Bugs

[APP] on{x}

Found this app via a lifehacker write up, developed by Microsoft ironically.
Basically lets you setup automations on your phone like sending a text to your wife that you're on your way home automatically when you leave work.
There's a collection of recipes you can pick from their site but you can also code any automation you'd like.
I'll let you guys read the article which explains it in more detail. It's currently in beta in the play store.
http://lifehacker.com/5916841/supercharge-and-automate-your-android-phone-with-onx
Here's a screenshot of some recipes on the web interface.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I already use Tasker to manage these things. This is only interesting for the functionality it provides by being location-aware, and able to detect the difference between walking, driving, or being at rest. However, usually that kind of detection translates to a massive drain on your battery life.
How often is it scanning for your location? What's the context it uses to trigger a location scan? What are the parameters for the accelerometer to determine walking, driving, etc?
Such an app is useless if I can't set my own parameters for how often/aggressively the app is scanning for a context.

haven't used tasker...does it allow you to actually code the tasks like on{x} does?
I think what you're asking is all dependent on what you decide in the code. I'll post two examples: first one is text my wife when I'm going home and second is play music while walking

lazaro17 said:
haven't used tasker...does it allow you to actually code the tasks like on{x} does?
I think what you're asking is all dependent on what you decide in the code. I'll post two examples: first one is text my wife when I'm going home and second is play music while walking
Click to expand...
Click to collapse
You can essentially write code for Tasker as well, it's just not presented in any recognizable language to the user, it's more like a simplified approach to coding. You start with a context and write a task for that context. Tasks are written as a series of actions, and you can input if/then/else statements to check for conditions before executing actions. For more complex tasks, you can set variables for several different contexts and have the tasks check against all of them.
Tasker is fully aware of location, wifi, Bluetooth, proximity sensors, screen settings, sound settings, headset plugs, accelerometer orientation, or just about anything the phone is capable of sensing, and also allows third party plugins to add more functionality in terms of contexts available and additional actions that the tasks can execute.
The difference with on{x} is that it has additional preset contexts for when you are moving and where you are located. It's not difficult to write something similar for Tasker, but you're going to run down the battery because the phone is constantly scanning for your location and running operations to translate accelerometer readings to either the walking, driving, or rest states. Whether or not this is actually the case with on{x} remains to be seen, but unfortunately they haven't made public what kind of algorithm they're using to set the phone into these various states.

Pretty interesting app, can't wait to really dig into it
What are some of the best tasks so far you goes have found?
On a side note, I just told my girlfriend I found it weird this is only on Android and she said "How come? Microsoft doesn't have a phone platform" and I thought she was joking, but she genuinely forgot about WP7
Sent from my Galaxy Nexus using xda premium

Problem is, how much will this app affect the battery life?

CM10.1 Battery life expanding

I have been having issues with cm10.1 "android OS" using too much battery. And i have seemed to squash out the bugs. nearly doubling screen time. (in the sense that by bed time i had about 4 hours screen time and 10% battery left and now can hit 8 hours in a day)
I am going to slowly try different things to see where hte main issues were. but here are the majority of the changes i made.
1. Wifi, this should be off during the day, simple but true. Also i noticed build.prop had wifi scan interval set to 15 instead of the recommended 120
2. Auto rotate screen, i have read this has bugs in some builds (not sure on ours) it should be disabled unless you absolutely need it, you can add a quick tile for quick toggling. (I honestly think this is the biggest cuplrit)
3. Dev options, try to have all unneeded dev options off. I had strict mode enabled, not sure if it made a difference, but its useless cpu cycles.
4. Battery apps, as helpful as they are, uninstall asap, unless you are isolating a problem they eat cpu cycles trying to figure out what is eating your cpu cycles...
5. Notification Light, its not the LED so much as it is the CPU cycles required for the timing of the led light.
6. sign out of or uninstall/freeze (disable) google talk.
7. disable gps (use quick toggle for when really needed)
8. go to system settings -> google (under accounts) -> maps & lattitude -> make sure "report from this device" is unchecked and if you dont move around a lot (aka you work really close to home) turn location reporting to either do not update, or set location...
9. and of course any other common place one, screen brightness etc...
I will slowly implement these back in to see if they cause the drain to come back.
I think its auto rotation honestly, but it could have been a combination of all of them.

I get 8-9 hours on stock 4.1.2

I get 6 hours screen time in 4.2.2 without doing any of that, and I still think that's pretty bad compared to touchwiz. I use all those functions mentioned (except gtalk) all the time, so cm10.1 is nowhere near usable as a daily driver for me.

So battery is not draining on its own anymore.
Now time to find the culprit.
If its autorotation then the cm team can fix it and that's a good thing
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GN2 using XDA app.

simonxliu said:
I get 6 hours screen time in 4.2.2 without doing any of that, and I still think that's pretty bad compared to touchwiz. I use all those functions mentioned (except gtalk) all the time, so cm10.1 is nowhere near usable as a daily driver for me.
Click to expand...
Click to collapse
I'm not saying cm10.1 is the culprit. I'm trying to figure out what is and so I can help squash it.
Sent from my GN2 using XDA app.

I get 8-9 hours on stock 4.1.2

I use Deviant's Xone rom. Get 2 days+ of use depending on how I use my phone. Even with heavy use I get a good day out of it, at least for what I need.

Question Pixel 6 (Pro) Variable Refresh Rate

Hey guys, looking for confirmation. I recently started exploring this phone's VRR to see if I could find a way to force max refresh of 90hz on the pro to try and save battery. Ran into trouble and found this video showing the phone only goes from 60-120hz:
I've heard arguments against being able to see the refresh rate with the developer options tool, as refresh rates of LPTO displays happen at lower (hardware) level than the "show refresh rate" tool (software) can view.
Many VRR displays use profiles rather than true "seemless" switching, ie: 1hz, 10hz, 11hz, 24hz, 30hz, 40hz, 60hz, 120hz.
Does anyone have the necessary expertise to tell me what's going on here? Do our Pixel 6/Pro displays have two refresh profiles, 60hz and 120hz, and that's it? Or is this a failure of the methodology being used in the above video's test? Further, is this a hardware limitation, or something that can be fixed via a software update in the future?
Thanks to anyone with some insight
*Edit* Here's a pic of the website "smartprix" claiming the P6P is variable down to 10hz
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Here's another troubling post about the display on this thing, if anyone is interested. I'm hoping we can get some of these things addressed in updates, because I really love this phone. I just want to find a way to make the battery last a bit longer..
Are these issues that perhaps custom kernels may also address? Sorry if any of these are obvious questions, I just plan on keeping this phone a long time and hate seeing these head-scratching issues. Thanks

Opensystem said:
Here's another troubling post about the display on this thing, if anyone is interested. I'm hoping we can get some of these things addressed in updates, because I really love this phone. I just want to find a way to make the battery last a bit longer..
View attachment 5464901
Are these issues that perhaps custom kernels may also address? Sorry if any of these are obvious questions, I just plan on keeping this phone a long time and hate seeing these head-scratching issues. Thanks
Click to expand...
Click to collapse
He also mentions in that thread that this is pretty much unfixable. I wouldn't bet on custom kernels etc being able to fix this.

It is fixable (in theory).
The hardware supports a variable refresh rate from 10-120 Hz, so in theory that can be used "fully". Meaning 10, 30, 60, 24, 90, whatever.
BUT - Google locks it down. As of now, we do not know why, or how.
Maybe someone will find/make a fix/a mod one day, maybe Google will do it.
Right now we do not have a fix, and don't know more. Not much more to say.

So, would it be better to force 120 Hz in developer options?

gpvecchi said:
So, would it be better to force 120 Hz in developer options?
Click to expand...
Click to collapse
I don't see how, it would just cost more battery. The phone ramps up to 120hz fine, it's lower frequencies that are the issue. Which leads to yet another thing that's compounding battery problems

Is it possible to get different control with a custom ROM?

Interested to know if you've found any updates on this in the almost 2 years since you asked. Setting the max refresh rate to 90Hz would be cool!

Question How is That Even Possible

As you can see my phone Charges pretty fast. It Charges 0 to 100 in one hour. But charge Drains fast also like 4 and half hour screen time. Im on MIUI 13 global.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Koriam said:
As you can see my phone Charges pretty fast. It Charges 0 to 100 in one hour. But charge Drains fast also like 4 and half hour screen time. Im on MIUI 13 global.View attachment 5579973
Click to expand...
Click to collapse
That's stock MIUI, right? It's possible you have some background stuff going on that drains the battery on a regular basis. If you haven't already, try clearing your Recents view to see if that helps.
I am using Arrow OS 12.0, myself, and ended up enabling the Developer Options selection for 'kills all activities once user leaves them'. This improved my active consumption rate from being ~8-9% per hour to ~6% per hour. You can give it a try, too!

Veiranx said:
That's stock MIUI, right? It's possible you have some background stuff going on that drains the battery on a regular basis. If you haven't already, try clearing your Recents view to see if that helps.
I am using Arrow OS 12.0, myself, and ended up enabling the Developer Options selection for 'kills all activities once user leaves them'. This improved my active consumption rate from being ~8-9% per hour to ~6% per hour. You can give it a try, too!
Click to expand...
Click to collapse
Yes its stock. I couldnt find any app yet, im Still searching and looking for a help.

Oh, maybe you have the same issue that I had.
Check if the MIUI gallery is going crazy in the background. I have yet to figure out what caused that, but it wrecked havoc on my device.
Get something to view your CPU frequency in real time, normally all cores should idle at under 1000MHz with nothing else open in the background (I used CPU Float to check that).
If your little and/or middle cores appear to be clocked high, try to see if force closing the gallery and not reopening it helps. I fixed it for good only after having disabled its storage permission, ended up switching to google photos instead.
Hope this helps.

Dariusdd said:
Oh, maybe you have the same issue that I had.
Check if the MIUI gallery is going crazy in the background. I have yet to figure out what caused that, but it wrecked havoc on my device.
Get something to view your CPU frequency in real time, normally all cores should idle at under 1000MHz with nothing else open in the background (I used CPU Float to check that).
If your little and/or middle cores appear to be clocked high, try to see if force closing the gallery and not reopening it helps. I fixed it for good only after having disabled its storage permission, ended up switching to google photos instead.
Hope this helps.
Click to expand...
Click to collapse
It looks like this and going crazy up and down all the time. I force stopped gallery and remove the permission but its Still the same.

Question AOSP ROM's are closing recents automatically?

Good afternoon!
I have a question about AOSP based ROM's. At first I thought this was only occurring in the Nameless ROM but I can also find this behavior on other custom ROM's. It seems that apps are getting closed automatically after some time, as if I would go to the 'Recents' screen (or however this screen is called) and I would swipe those apps away.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is definitely noticeable when I wake up in the morning, almost all my apps are gone from Recents while I almost never swipe any apps away. I find this behavior not efficient since my phone never makes use of the 12GB RAM which I've spend extra money on. Here you can see that only 7 GB is actually used (including cached processes).
When I open up all my apps at once my RAM usage goes up but after some time it seems to close apps and it goes back to 5-6 GB of usage or so.
I find this frustrating. I have an iPhone 12 from work and I use that phone rarely. But a week later I can expect my app to still be open where I left it.
In the ROM's I tried, I tried disabling any battery savers if there were any, without result. I also have FKM installed and tried changing some memory related kernel settings which did appear to have some effect but that also might be a placebo and tbh I'm not fully aware what kernel settings I should apply.
TLDR: Can anyone advice me how I can stop my AOSP rom from clearing apps in the background?
Thanks for your input
Kind regards,
GolovaRaoul

Hi,
I have not tried any custom ROM yet, but I can confirm that default ROMs for "OnePlus, Xiaomi, Samsung" are all doing the same behavior once the phone is setting down and not being used for a while "sleep mode" this actually good in my opinion, it will automatically close all apps except the apps you are choosing to not to be closed "locked apps" in oxygen os, you can select multiple apps to prevent them from being closed during night or even when you tap "close all" button.
So, I think this is an Android optimization to save battery during night not only in AOSP ROMs.

Thanks for your response
Well I don't like this behavior personally. It takes time and processing power to re-open apps and navigate them back to the stage where I had them before. I need to relaunch Spotify 5 times per day which is annoying and I really shouldn't need to on a flagship smartphone with 12 GB of RAM.

GolovaRaoul said:
Thanks for your response
Well I don't like this behavior personally. It takes time and processing power to re-open apps and navigate them back to the stage where I had them before. I need to relaunch Spotify 5 times per day which is annoying and I really shouldn't need to on a flagship smartphone with 12 GB of RAM.
Click to expand...
Click to collapse
This actually not belong to RAM capacity itself, it is system implementations and how should apps behave. As I said it will only close the apps during "sleep period" and you can select multiple apps that you want them run in background all the time see attached photos.
You are welcome

dream2poet said:
This actually not belong to RAM capacity itself, it is system implementations and how should apps behave. As I said it will only close the apps during "sleep period" and you can select multiple apps that you want them run in background all the time see attached photos.
You are welcome
Click to expand...
Click to collapse
Yeah you could be right about the behavior. I still want to change it tho. And by default, AOSP does not have something like 'memory locking' and this is a feature of Oyxgen OS.