Hi all,
I wrote a program which runs in Terminal on my phone (Android 9), this program makes some computations and writes the result in a file. No input, no app.
I have realized that after a few minutes I suspend the display the execution is frozen and resumes when I switch it on again, very annoying since my goal is to take advantage of the CPU during day and night.
Is there any way to avoid this? Note the phone is not rooted
Thanks a lot to whomever will reply
S
The terminal's output device is phone's screen. It should be obvious that terminal app interupts working when you suspend the screen and resumes working when you turn on screen again.
No, should not be, in the options of Terminal there is something like Activate Wakelock which should make so that the processing continues even in suspension, But does not seem to work
Related
Hi all,
I tried searching but cannot find anything on this, so as my first post, here goes...
I have a Touch Diamond with official ROM (WM6.1). I want to get over the known "issue" that with the device set to pin lock after 0 minute timeout, it still locks automatically after 1 minute of idle time.
Of course, I found an answer on this forum, see, for example http://forum.xda-developers.com/showthread.php?t=291868: in the registry, set AEFrequencyType to 2 (instead of 1), which works as hoped as far as the device is concerned... it no longer auto-locks after any amount of time, but locks instead whenever it goes into standby.
The issue is this: Activesync no longer requires the pin to connect to the device and without pin can read ALL files from its memory, even if the phone is locked at the time. Setting AEFrequencyType back to 1 forces Activesync to require the pin even if it is not locked when it is plugged in to the computer. Does anyone know a way to force Activesync to require the pin... of course, I am looking for a setting on the device, not the PC, as I want to make it hard for anyone who might steal the phone (or if I lose it!) to read the data on the device.
In case anyone is wondering, I also found another workaround. Having set the pin timeout to some large time, like 30 minutes, I can then use a pin locking program, Zenyee's 'Pin Lock.exe', and create a wakeup event notification with Dotfred's Task Manager (seems very useful app for free!). This works, until I run FlexMail, which seems to intercept these notifications and prevent it from locking!! So, I have to override a soft key on the home screen to run the pin lock, then hit the power button to put the device into standby. Not too bad, but there must be a better way...!
Thanks in advance,
Martin
Just a quick follow up for anyone who may be interested. FlexMail DOES NOT intercept the wakeup events... however, because it causes a little processing to be done, it seems it can delay the device from sleeping for a while (a minute or two) whenever a full synchronisation is performed. So, the wakeup event, whilst normally quick to activate, can sometimes take a minute before becoming effective.
However, I now have a workable solution for me. Just as I said above, I set my Pin Lock timeout to something large, like 30 minutes. However, instead of relying solely on wakeup events, I have now installed Gyrator 2 (http://forum.xda-developers.com/showthread.php?t=427805) which is an excellent application for many reasons... I particularly like being able to identify the window class/title using the stylus-in event to identify the in-focus window! More importantly, for this issue, it has the option to both Pin Lock and Suspend the device whenever a certain criteria is met. For me, this is when it is held face down for a second. So, now I just do this instead of hitting the power button and I'm guaranteed to have the device Pin Locked on next wakeup. ActiveSync also requires the Pin as AEFrequencyType is the default value of 1. A perfectly workable solution.
All the best,
Martin
I strongly suggest you take this towards the Diamond section as knowledge about specific problems in specific devices are usually conversed over at that specific section.. more than here.
Thanks, but I think this is WM6/WM6.1 specific, not Diamond specific. The problem with AEFrequencyType set to 1 giving a timeout even with zero minutes is known and seems to be device independent. I just found that setting it to 2 to fix this timeout issue, as many people do, seems to prevent ActiveSync from requiring the PIN as well! Not a good result.
That said, my workaround solution is probably Diamond specific, sorry! Perhaps I should post in the original thread that I found out about the AEFrequencyType registry tweak?
All the best,
Martin
Hi all,
I have an apps idea but I am not a developer and thus will really love if a developer will try to do it for the communities.
It's to check when is your phone ready to be use after a reboot.
Often the time, I must look at my widget continuously to know if the phone has gotten stable to use after a reboot or not. So, I guess this would be a nice addition.
The idea is that the apps should start very early in the boot up process and monitors the CPU usage continuously.
If the CPU usage is less than 10% (or any other value) for 10 seconds (or longer), then the apps will prompt the user, either by a toaster, or via notification, or via sound/vibrate etc.
After the user learns that, the apps will shut down itself and no longer takes up any memory or juice.
What do you all think?
I had the same idea, and solved it with this tiny and handy application : CPU Notify
https://market.android.com/details?id=com.beemer.cpunotify&feature=search_result
It is loaded at boot time, and you can observe that the CPU is at 100%. When it goes down to botton (green) steadily, the phone is ready.
I keep this application constantly since it is very small and battery friendly. It shows your phone activity like task manager in tray icon in Windows world.
Hi.
Since coming from android I've been a frequent user of apps who lets the phone change it's settings due to specific triggers, like turning silent at night and loud in the morning, turning silent when a certain calendar happening occurs, turning of wifi when leaving home etc.
Is there anything like this for using along with windows phone?
Thanks in advance
Pemell
Actually, (some of) this is theoretically possible, but nobody has done it so far. It's also not going to be allowed on the Marketplace; you'd need to use some unofficial APIs.
For example, the DllImport Project already has shown the ability to control the phone's volume. Programmatically muting the phone at a certain time, for example one minute after a meeting is supposed to start, should be pretty easy.
The trick would be to make sure the phone also un-mutes it when the meeting ends. WP7 doesn't (officially) allow third-party software to run continuously in the background, and while you can schedule a time for the software to run, it make no guarantee ot to-the-minute accuracy. There are ways around the official restrictions, but most of them have serious battery-life considerations (although telling the process to sleep for the next 30 minutes * 60 seconds * 1000 miliseconds would probably work without draining battery). Additionally, I'm not sure how much access apps officially have to calendar data, although on interop-unlocked or full-unlocked phones there are varius ways to access that data.
For things other than volume control, like enabling or disabling WiFi (almost completely unneccessary on WP7, the WiFi power management is, if anything, too conservative already) you'd need to find the place in the OS that controls it. Probably just sending SetDevicePower to the Wifi driver would work to disable it, though I don't know if that would show up correctly in the UI.
Hello,
I'm doing a simple Android background service that implements the raise to wake up feature. Thus, when the phone is in sleep mode (i.e. screen off) and the user raises the phone from the table, it will be waked up by the service.
When I attach the phone to the computer using the debug USB to test the application, in particular looking at the message of logcat, everything work well. Even if the screen is turned off, I can see from android studio that the service is alive and when I try to raise the phone from the table it will wake up.
However, when I detach the phone from the computer, the service won't work. In details, sometimes it works, but if I leave the phone asleep it doesn't work anymore. Checking the running services on my phone I can see that my service is alive, however it is not responsive.
What could be the problem?
I tried both making the service as background service and foreground service. The result is the same.
I'm testing the service on Android 7.0.
You can see the source code (with a precompiled binary) and/or contribute on github (look for the project called raison, I don't have the permission to put the link). The service is started after the boot of the phone or when the user opens the activity.
It doesn't seem a bug of the application (e.g. in the logic), because it works during the debug phase.
Furthermore, I don't have any power saving option and I see the service running (using the developer options).
Another note is that my phone has the double tap to wake up, however the double tap often doesn't work or is really slow (it wakes up after >10 seconds), thus seems that my system is slowing down so much during the sleep. However, applications like whatsapp work well.
There is a way to force my phone to keep the service running (without slowing it down) even in the sleep mode?
Thank you! It could be helpful also to have a feedback of the application on your phones, to see if it is just a problem of my phone or it is some behaviour of Android that prevents the correct execution of the service.
EDIT:
I've also tried to use a wake lock to keep the CPU awake (preventing the deep sleep) without success.
Why is my Android Tv set top box lagging badly after I put it in deep sleep, and then wake it up again? This normally happens after I have been using the youtube app to watch videos, then put it to sleep, with the power plugged in. I tried everything to fix the problem, including memory clean, restart all apps, virus scan, speed boost app and even system UI reset. The only thing that fixes the problem is to reboot the whole thing. Without reboot, the performance improves but only after a long time. But I don't like shutting down my device, I prefer putting it to sleep so it can start up quickly when I need to use it again and rebooting is too slow. So what do I do to fix it? My device is rooted.
Update: It seems that after searching other posts, this is an update issue to the android firmware for tv boxes but no solution has been found. One user claimed that putting the device to sleep without exiting app to home screen reduces the lag upon wake up somehow.