Develop Bugs

rk-Sleep(Location based phone flight mode switcher)

Ok, built a new app phone switcher (flight mode on/off) based on the cell tower location.
System automatically switches the phone OFF based on the time you set when you are at predefined location (Say Home). When you are at home, say from 10:00 PM to morning 6:00 AM no one can call your mobile. But if you are not at home, then phone is ON even at night. This also saves your battery life and privacy too.
It is working on Hermes, and I have tested it on WM5 emulators. Will NOT work on WM2003.
Please check the link to the application under my signature.

I have a question, can it only change to "vibrate" instead of turning off the phone? That would be more appropriate for me. Thanks for your answer

Nice App! How about changing call forwarding (when busy, no answer, etc...) baased on location?
If the phone could forward all calls automatically, or forward when you press "hang up" based on location it would safe battery and reduce radiation using the phone.

szturchen_pl said:
I have a question, can it only change to "vibrate" instead of turning off the phone? That would be more appropriate for me. Thanks for your answer
Click to expand...
Click to collapse
Nice Idea!, I will do my homework to find out what it takes to do that

ahlok_hk said:
Nice App! How about changing call forwarding (when busy, no answer, etc...) baased on location?
If the phone could forward all calls automatically, or forward when you press "hang up" based on location it would safe battery and reduce radiation using the phone.
Click to expand...
Click to collapse
Since the application do not keep polling for location, if it does not know the current location for some reason(reason = In the original post) then there might be problems such as wrongly 'forwarded' calls...
But its a great idea. I keep it in mind

past 21:00 hours
does not seem to work if you go past the apointed hour? radio stays connected

david.dupuis said:
does not seem to work if you go past the apointed hour? radio stays connected
Click to expand...
Click to collapse
Are you saying.. You were not at appointment time at sleeping location... And you came in late... and the phone does not turn off?
If so it is by design.. As i am not keep polling to find out the locaton. Just because then the application has to be running in the background or keep getting activated say for every 5 Minutes.
But let me know if you are saying the samething too.

not shutting off past sleep time
I think we're saying the same thing. Last night I installed the software set the home location and set the sleep time to 21:00 to 6:00. Actual time was 22:00. I expected it to shut down the radio and it did not.

Hi,
does not work for me
Install works fine, Test is OK, device went on Flight Mode and Back.
I set Sleep Location and Times and clicked Enable button.
When I want to save an error occurs lile: "InvalidCastException at Save. Please report this!"
The settings won't be saved then. I tried to manually edit the cnf file with
found cell values and True State, and saved this back to device, but when
time comes, nothing will happen.
I am on Schaps WM6 3.57a german and O2 Germany Provider.
What I was found out is, everytime I start the program it
randomly changes the location behind the dot.
Once it is xxxxx.8311 and the next time it is xxxxx.48311
May this be the culprit?
Any suggestions welcome bc I would really love this tool working
Olioaglio

david.dupuis said:
I think we're saying the same thing. Last night I installed the software set the home location and set the sleep time to 21:00 to 6:00. Actual time was 22:00. I expected it to shut down the radio and it did not.
Click to expand...
Click to collapse
OK for this i have to implement a constant polling mode.. Which i will do it for next release.

Olioaglio said:
Hi,
...The settings won't be saved then. I tried to manually edit the cnf file with
found cell values and True State, and saved this back to device, but when
time comes, nothing will happen.
...Once it is xxxxx.8311 and the next time it is xxxxx.48311
May this be the culprit?
Olioaglio
Click to expand...
Click to collapse
If you don't mind can you send me your cnf file?
Since your Location keep fluctuating... May be its failing to ON/Off
So when you are at home (Sleep Location) and if you keep refreshing the location (Button Refresh Location) you are getting diffent values?
Let me know

Something similar, sort of
I use Teog's CallFilter instead. What I like about it is that I can set the filter to only allow calls through from specific people. This way if there's an emergency in the middle of the night I'll get the call. It doesn't work on a schedule, you have to run it when you want it and disable it when you don't. But it is a simple app that runs with just a click after it's configured and has worked over several different operating systems. Would work well for meetings, movies, etc. too.

tytnguy said:
If you don't mind can you send me your cnf file?
Since your Location keep fluctuating... May be its failing to ON/Off
So when you are at home (Sleep Location) and if you keep refreshing the location (Button Refresh Location) you are getting diffent values?
Let me know
Click to expand...
Click to collapse
Check PM
Olioaglio

Hi tytnguy,
thanks for fast PM. You were abolutely right with the idea of interfering date format. I customized my HTC Home with the SDTe Override string (by HTCustom Proggie) to display the week day, which turned out to be the culprit that your prog did display the error message at Save.
So I deleted this in registry and the app now saves without a glitch. So I set the time (1 minute in the future) again and saved. When the time comes, the turning wheel appears, but nothing happens. I figured out, that the Status page says: "Out of location so NOT switching off the phone", so this is maybe, why the program starts but do not turn to flight mode as suggested.
Since I set the home location and did not even move a meter from this position I cannot imagine, why it does display I am not in the sleep location?!?! Any ideas
Olioaglio
edit: It WORKED now for the first time !!!! Great!!
Just wondering, what happens when I just do the phone in another room in my flat, where maybe it is in another broadcast cell....
Think, it won't work then!! Is it possible to create, let's say, kind of a radius, where the program activates??
So my sleep or home location is maybe a bit more then just one room or even my desk
edit 2: May it work, if I set the SDTe string to override again, after saving correctly? Or will the app then stop working again? Sorry for those dumb questions though.
Thanks anyway!!! Great program!!

tytnguy said:
OK for this i have to implement a constant polling mode.. Which i will do it for next release.
Click to expand...
Click to collapse
Would constant polling mode affect the battery drain significantly?
If yes, I would suggest a check box in your proggy to toggle this option on/off
Just my 2 cents
Olioaglio

Olioaglio said:
...what happens when I just do the phone in another room in my flat, where maybe it is in another broadcast cell....
May it work, if I set the SDTe string to override again, after saving correctly? Or will the app then stop working again? Sorry for those dumb questions though.
Click to expand...
Click to collapse
Olioaglio,
Can you set the home location from the other room?
If you change the date format to someother non standared format it will not work. Since program needs to keep saving the stuff on each try.

Update 1.0.1
Multiple location on the schedule: If you want to set more than one location as you 'Sleep Location' you can do it now. On the sleep location box bring the context menu up, and choose 'Append to location' now add the new location to the list. You can add any number of sleep locations!
Now if you were not at home at set time, system will keep polling based on the poll time you specify. So as soon as you reach home your phone will be switched off.
If you turned on your phone manually after the rk-Sleep set it to flight mode, then your phone remains on till next scheduled sleep session

Olioaglio said:
Would constant polling mode affect the battery drain significantly?
If yes, I would suggest a check box in your proggy to toggle this option on/off
Just my 2 cents
Olioaglio
Click to expand...
Click to collapse
Olioaglio,
No it should not make any significant affect on the battery.
I have programmed it to poll only on sleep time if you are not at home. But since I am not running the program in the background, it is ok.
The new update I release just keeping your problem in mind. So you go to both your rooms where you get different towers. Update both as your sleep location.

tytnguy said:
Olioaglio,
No it should not make any significant affect on the battery.
I have programmed it to poll only on sleep time if you are not at home. But since I am not running the program in the background, it is ok.
The new update I release just keeping your problem in mind. So you go to both your rooms where you get different towers. Update both as your sleep location.
Click to expand...
Click to collapse
Thanks, will monitor it...
Olioaglio
UPDATE:
OK, tested it now... Dude, the 1.0.1 really works like HELL!! I'm totally satisfied for now.
The Append function is very good thing, since I found 8 (!) different cell locations (about 3 with GSM and 4 with 3G) in my 3-room flat. They are always fluctuating even at the same place, so maybe this was the problem of the others, who tested the program with having only one location saved. But with the Append function AND the new Poll function (which also works great), it absolutely ROCKS!! Had no problem with several tests. Battery consumption with poll function really does NOT seem to be more than without poll.
Just some suggestions if you plan to make updated release. The Append function is not easy to find, I had to read your instructions three times to get it. Maybe you'll find another way. Also an extra tab with a list of all appended cells would be appreciated.
I would have another idea for an "extended" flight mode. Maybe you could add some checkboxes for Phone, Bluetooth, Wlan and Beam for - lets say - "Extended Flight Mode" options. So one could save even more battery as with just the phone function off. With the checkboxes you would have the choice what to turn off/on, when rk-Sleep will engage.
Best regards,
Olioaglio

tytnguy what about vibration mode? have you had time to check into that? Regards

[wifi][Tweak]Change Wi-Fi idle time before wifi sleep (title changed)

The information in here is only tested on the ICS (Stock based roms) and (stock or repacked kernels). It's not been tested on any other roms. So, if you want to apply the tweak that I provided in here, do it with your own risk. I'm here to help or share the good and bad things but not responsible for any bricked phones.
Update: Wifi Sleeps well! But you need to understand what's going on here.
We are expecting wifi to sleep when the screen is off and 'Keep Wi-Fi on during sleep' is set to 'Never'.
But wifi does not go to sleep mode even every options are satisfied on ICS stock roms with Stock or Rogue repacked Kernel).
I tried many ways to make it sleep (from settings, from build.prop tweaks and from through the init.d script) but none of those worked. Only the way to make it sleep is turning off the wifi manually before turning off the screen.
There is one workaround that making the wifi sleep during the screen off. The method is using Wifi Fixer app from google market but it does not work 100 %. Sometimes, it makes wifi sleep but other times, nothing happens.
So, anyone who is expecting wifi sleeps by any tweaks or by wifi option changes, don't expect it any more. There's no hope yet. For me, I'm waiting for the next build to test this function out.
There's some additional information at http://forum.xda-developers.com/showthread.php?t=1625299 and check wifi section.
If anyone knows the method to make wifi sleep on stock rom/kernel, please post your info here. There are some tools that we can use to check wifi is sleeping or not during the sleep mode. I'm currently using Battery Widget Pro.
Because I've tested lots of things so far, if you know the methond or if it works on your phone, please show how it works and screenshots if possible.
[Update] Wifi sleeps finally as I wanted!
OK. Here is the story.
One specific app mis-led me to wroing conclusion - Battery Monitor Widget Pro (v2.2.4). This app shows that wifi is always on if wifi is turned on. This app does not exclude the time wifi was turned off during the sleep mode.
Plus, there's some pre-allocated time to make the wifi sleep after the screen turned off. For most of Android phones, it seems like this value is 15 minutes. So, even the screen is off, wifi does not enter to the sleep mode immediately. Phone spend 15 minutes after the screen off, and kill the wifi session if wifi option was set to never (keep wi-fi on during sleep).
How to check whether wifi sleeps or not :
Do NOT use Battery Monitor Widget to check the wifi status.
You can easily check it from the stock Battery app. Settings > Battery > click on the graph > check wi-fi status if there is any gap (means sleep or turned off).
Then, How to change the default 15 minutes value to make the phone sleep early?
Update 5/16/12 - Fixed wifiSleepWait tweak, so it works without any manual database handling. The below is just for informational. Now you don't need to manually create a row into the table.
There were one or two information available on XDA but nothing is correctly applicable to Epic 4G Touch. So, here is the tweak that I made for E4GT.
To do this you will need root explorer -
1. move to the folder, /data/data/com.android.providers.settings/
2. copy the databases folder to your /sdcard
3. Move to /sdcard/databases click settings.db
4. select secure
5. it will ask you which editor you are going to use. If you installed sqlite then select sqlite, otherwise use root explorer (only at first time)
6.Check if there is column name 'wifi_idle_ms'. If there is, then change the value to whatever mili seconds you want. For example, 10000 = 10 seconds, 30000=30seconds. If you want to wait 15 minutes until wifi sleep, then 15*60000 = ?
7.If there is no 'wifi_idle_ms' row, the click long time anywhere on the table. It will show you the actions, select new record. Do not change _id, put the 'wifi_idle_ms' in the name field (without quote sign) and put the value explained above. For me, I just put the 10000 (for 10 seconds). Click save.
8. Now you can see the value changed or row created. Exit editor and move up to /sdcard. Copy (or Move) databases folder to original location (/data/data/com.android.providers.settings/). Sometime, the copy is not successful because database is currently being used. If it's not copied, then try it agaon to copy until it's successful. For me, it was successful on second try.
9. Reboot the phone and click the power button shortly to change to screen off mode(sleep mode).
10. After the time passed defined in above, click the power button again and notice that phone was working on 4G or 3G mode and not wifi mode. Phone will try to reconnect wifi after the screen turned on.
11. That's it. Now you can change the idle time until wifi turned off as much as you want.
The above was the manual way to change the wifi_idle_ms value from database. But there is another way to change this values automatically. The method is using sqlite and of course you need to know the sql query.
In my case, I tried to add this sqlite query statement into my init.d tweak but only update sql command worked and insert was not successful. Maybe I need someone's help to get this insert statement successful.
In here, I'm adding only the update tweak which can be added into init.d. What this mean is, at first time you have to insert the database row manually but once it's created, you can update the idle value during the boot thru init.d script.
Because you don't need to run this init.d script everytime on boot, once you update the value, change the permission to 644 and it won't run again until you change it back to 755.
To run this init.d script, you will need sqlite3 - http://chensun.net/android-development/install-sqlite3-on-google-nexus-one/54/
Download it and simply move to /system/xbin foler. Assign the same permission like other files on the same folder.
Of course, you also need root access and busybox.
The init.d script will be found at http://forum.xda-developers.com/showthread.php?t=1625299
70wifiSleepWait_kobridge.zip (previous version)
70wifiSleepWait_kobridge.v2.zip (current)

kobridge said:
This info is just for the ICS (Stock based roms) and (stock or repacked kernels) users.
We are expecting wifi to sleep when the screen is off and 'Keep Wi-Fi on during sleep' is set to 'Never'.
But wifi does not go to sleep mode even every options are satisfied on ICS stock roms with Stock or Rogue repacked Kernel).
I tried many ways to make it sleep (from settings, from build.prop tweaks and from through the init.d script) but none of those worked. Only the way to make it sleep is turning off the wifi manually before turning off the screen.
There is one workaround that making the wifi sleep during the screen off. The method is using Wifi Fixer app from google market but it does not work 100 %. Sometimes, it makes wifi sleep but other times, nothing happens.
So, anyone who is expecting wifi sleeps by any tweaks or by wifi option changes, don't expect it any more. There's no hope yet. For me, I'm waiting for the next build to test this function out.
There's some additional information at http://forum.xda-developers.com/showthread.php?t=1625299 and check wifi section.
If anyone knows the method to make wifi sleep on stock rom/kernel, please post your info here. There are some tools that we can use to check wifi is sleeping or not during the sleep mode. I'm currently using Battery Widget Pro.
Because I've tested lots of things so far, if you know the methond or if it works on your phone, please show how it works and screenshots if possible.
Click to expand...
Click to collapse
Maybe it cannot sleep when sync is on?
I imagine that wifi is needed for weather/news/etc updates and clould2device services.

Wait...the options are changed on ICS correct? Meaning its never off during sleep on Gingerbread and always on during sleep on ICS or am I not understanding?

Huh? Mine sleeps just fine unless I set it to never sleep.
That aside - you are aware that you're better off leaving wifi on anyway, right? It uses less battery power than the cell radio does. Just an FYI

Finally figured out everything!
Took whole one day to find out everything!
First, most importantly, WiFi sleeps!
I'm going to explain what happend and how we could make wifi sleeps better in op section.
edit. Partially updated. I'm checking now if I can make a script to change the leading time that is required before wifi actually sleep.

kobridge said:
Finally figured out everything!
Took whole one day to find out everything!
First, most importantly, WiFi sleeps!
I'm going to explain what happend and how we could make wifi sleeps better in op section.
edit. Partially updated. I'm checking now if I can make a script to change the leading time that is required before wifi actually sleep.
Click to expand...
Click to collapse
All updates are done! Enjoy your ability having control over wifi idle time!

You know, upon further testing, idle battery drain on 3g is pretty damn good as well. I am in a lousy signal area during the day and I have been leaving wifi on 24/7 so a lot of battery got wasted from the phone searching and finding wifi to connect to. Tomorrow I will disable wifi while at work but...
Sent from my SPH-D710 using Xparent Blue Tapatalk 2

JohnCorleone said:
You know, upon further testing, idle battery drain on 3g is pretty damn good as well. I am in a lousy signal area during the day and I have been leaving wifi on 24/7 so a lot of battery got wasted from the phone searching and finding wifi to connect to. Tomorrow I will disable wifi while at work but...
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Based on your screenshot, it seems like you are wasting the battery by turned wifi on wifi 24x7.

kobridge said:
Based on your screenshot, it seems like you are wasting the battery by turned wifi on wifi 24x7.
Click to expand...
Click to collapse
I agree. While I am around the house say going to the store its minimal but when going to work in NYC I am picking up wifi i cant connect to every 10 feet so its definitely negatively effecting battery

nabbed said:
Maybe it cannot sleep when sync is on?
I imagine that wifi is needed for weather/news/etc updates and clould2device services.
Click to expand...
Click to collapse
I think there is a little difference of understand about what has the control over other services/fuctions.
Usually weather/news apps are dependent on wifi or 4g services. Those apps usually do not control the wifi or 4G and many times only able to communicate wifi or 4G are turned on. Those services cannot hold the wifi/4G connections even those services are still running.
KCRic said:
That aside - you are aware that you're better off leaving wifi on anyway, right? It uses less battery power than the cell radio does. Just an FYI
Click to expand...
Click to collapse
That's not true. It's totally based on the signal strength. Usually 3G is not fast but do not use battery as much as wifi when the signal is weak on both wifi and 3G.

you on a roll with these threads kobridge! good work and thanks!

70wifiSleepWait_kobridge.v2.zip released
Now you don't need to manually insert the table row to use this tweak.
This tweak file is a complete set by itself. By running the tweak file, you can change or create the wifi idle timer on/into the database.
Related thread and where to download this tweak - http://forum.xda-developers.com/showthread.php?t=1625299

Not to question yiur style kobridge, but I beleive there is a spelling error in the tittle =D
Sent from my SPH-D710 using xda premium

krisI0N said:
Not to question yiur style kobridge, but I beleive there is a spelling error in the tittle =D
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Looks like he fixed it just for you.
[wifi][Tweak]Chage Wi-Fi idle time before sleep (title changed)
Edit: Well, not ^^^ ALL of it is fixed yet.

krisI0N said:
Not to question yiur style kobridge, but I beleive there is a spelling error in the tittle =D
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
tdunham said:
Looks like he fixed it just for you.
[wifi][Tweak]Chage Wi-Fi idle time before sleep (title changed)
Edit: Well, not ^^^ ALL of it is fixed yet.
Click to expand...
Click to collapse
Thank you both of you! Sometimes, simple mistake is not to catch because it's too simple!

will this tweak work if I set wifi to "only when plugged in"

edlivian said:
will this tweak work if I set wifi to "only when plugged in"
Click to expand...
Click to collapse
I think the right answer is No.
When phone is plugged in - wifi is always connected even after the screen turned off. So, this tweak would not work while phone is plugged in.
When phone is unplugged - wifi will stay offline always. So, this tweak is not applicable.
If you set the option to "Always" - wifi will stay connected during the screen off. So, this tweak does not work.
If you set the option to "Never" - This tweak only works for this option.
The purpose of this tweak is minimizing the waiting(idle) time until wifi moves to sleep mode after the screen turned off.

Kobridge, i came through this topic after some searching for a problem of mine.
I see you know some basics...
If you have some time, take a look at this... that wifi issue is driving me really mad !!!
http://forum.xda-developers.com/showthread.php?t=1673514
thnx in advance

morx said:
Kobridge, i came through this topic after some searching for a problem of mine.
I see you know some basics...
If you have some time, take a look at this... that wifi issue is driving me really mad !!!
http://forum.xda-developers.com/showthread.php?t=1673514
thnx in advance
Click to expand...
Click to collapse
For this, I believe it's related to the value of wifi.supplicant_scan_interval which is normally defined at build.prop.
Check out the value from there.
These days the value 180 (3minutes) are normal for tweaking purpose. But for EPIC 4G Touch's case, it's default is 5seconds (causing lots of battery drain if you are moving around).
For example, if wifi is not available from some location, then your phone will try to searchthe available wifi network after x amount of times. If this value is too big, then it will look like wifi is not connected (so most of you, just try to reconnect the wifi manually before time comes). If the value is too small, again it causes the battery drain.
Once the wifi is connected, it keeps the connection based on the wifi policy. But if the connection is lost, then it will try again to search!

First of all, REALLY REALLY REALLY Really thank you for the reply mate.
My wifi supp value is set at "10"
I know this value only works when there are not any "known" access points in range.
The thing is, that it NEVER connects with screen off or on when i get back in range.
It only does it when i go to wifi settings (refreshes the list and connects without touching anything more!).
(of course, my wifi battery saving policy is set to "never" while screen is off)
Wifi stays on but it freezes AP scanning, while screen is off i guess.
Would a logcat help? Any tips about how to capture a good log about that issue?

HTC ONE M8- Sudden Power Off When Battery Is Below 50%

Sudden power off when battery is less than 50 percent
Hi community,
I would be very glad to get some help for the problem below. Or maybe you can guide me how to provide more information to investigate it.
Problem
The phone sometimes powers itself off abruptly which can lead to database corruption. So it is very annoying...
However, it only seems to occur in some cases:
It happens as soon as battery is below 50% (this is not exact, but pretty close)
It only happens when the screen is off. May happen after 30 sec to 5 min.
It never happens when a USB cable is connected (power-only or computer)
It does not seem to happen when a "background task" is running
In some rare cases, it does not happen at all, or maybe just has not happened for a longer period of time. I could not determine what is different about the state of the phone then. When I turn the screen on once, and off again, the chances are high that it will power off very soon!
By "background task" I mean something like playing music, but I can not exactly define it. It can stay on like for one hour without any problems (screen turned off). It also stays on when, for instance, the timer is running and the screen is on.
So it does not seem to be a problem of the battery...
ROMs
I tried the following ROMs, all with the same issue. When switching ROMs, I always wiped system, data, cache, dalvik-cache. Never flashed another Zip on top (like Gapps). The device is unlocked using the official procedure by HTC.
Two official versions of cm12.1
A BlissPop v3.9 earlier build than below
BlissPop-v3.9-m8-OFFICIAL-20150827-0154 (currently running)
SkyBliss-v3.2.1-m8 (fantastic ROM, btw!)
Stock v4.19.111.2 + OTA to v4.19.111.3
More details of stock:
Relocked and flashed the Firmware v4.19.111.2 (Android File Host fid=95916177934521492)
Unlocked, flashed TWRP, then Stock v4.19.111.2 (Android File Host fid=95916177934527598)
Relocked and receive OTA v4.19.111.3
Debug
Below is a Logcat session. The numbers are line numbers. Of cource, they are not relevant, but they put things into perspective.
1163: I/PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
1371: I/PowerManagerService: Dozing...
1389-1466, 5 times occured: E/libsuspend: Error writing to /sys/power/state: Device or resource busy
1467: I/PowerManagerService: Waking up from dozing (uid 1000)... (I pressed the power button to see, if it is still alive)
...
2743: I/PowerManagerService: Going to sleep due to screen timeout (uid 1000)...
2931: I/PowerManagerService: Dozing...
2942, once: E/libsuspend: Error writing to /sys/power/state: Device or resource busy
2959: The phone is dead
There are also a log of those lines when the screen is off:
I/qdhwcomposer: handle_blank_event: dpy:1 panel power state: 0
(dpy:0/1 changing a lot)
Troubleshooting
I changed the CPU governor in my current BlissPop ROM: was Lionheart, tried Ondemand, Intellidemand, and Interactive. Subjectively, it slightly reduced the amount of battery percentage when the problem begins to occur. However, the problem persists and I did not take note of the battery charge.
Left default setting for "power safer".
???
What can I do about it?
Are there any tools to investigate the problem in more detail?
Does anyone have the same problem?
Thanks a lot,
Adi

Added Debug section

5.0.5 firmware will not let me wake up from remote; not sure which user settings uses

I use my tv remote to control my firetv over hdmi, and previously, the 'escape/back' button would wake up the firetv. after 5.0.5, it no longer works. The simplest solution i can think of is to keep the screensaver on all the time (i like it). I found this post that says you can configure the screen_off_timeout via adb
- stupid rules prevent me from posting link. so here's the text from the other webpage -
you could try adb commands
//Will set screensaver time adb shell settings put system screensaver_timeout 30000
//Will set sleep time adb shell settings put system screen_off_timeout 300000000
permalink
[–]mattgyver83 2 points 1 year ago*
Oh wow this sounds right up my alley and I have an adb session open to my ftv as we speak, it's fate I tell ya!
update:So I did it and just figured id post my findings here in case anyone else follows suit. First of all heres the conversions for the numbers reported from the 'get' variant of these commands;
1000 = 1 Second
60000 = 1 Min
3600000 = 1 Hour
86400000 = 1 Day
2147460000 = "Never" 24 days
So, I didnt modify the screen saver because that can be done via the UI but i did the screen_off_timeout and I just set that to the same value as the "Never" Option for the screen saver because assuming the TV is not touched in 24 days, im dead.
Thanks for your help ill update if it worked as expected and fixes the problem!
Click to expand...
Click to collapse
However, it doesn't work - and it seems that settings now has a per user settings
Code:
|[email protected]:/etc $ settings
usage: settings [--user NUM] get namespace key
settings [--user NUM] put namespace key value
settings [--user NUM] delete namespace key 'namespace' is one of {system, secure, global}, case-insensitive
If '--user NUM' is not given, the operations are performed on the owner user.
so I'm not sure which user NUM I should use, or if it's just ignored now. My most recent attempt is to brute force it
Code:
i=0; while [ $(($i)) -le 5000 ]; do i=$(($i + 1)); settings --user $i put system screen_off_timeout 2147460000; done;
not sure what to do - next step would be to try to root the box which just seems like a pain that i would like to avoid. my fire tv stick still works fine over hdmi (esc to wake it up) so I think it's a unique issue with the fire tv (1st gen).
Any thoughts?

Root not needed. User not needed.
It's almost like screensaver_timeout
and screen_off_timeout are opposite.
Change your Screensaver to Never and screen_off_timeout changes to 2147460000.
You don't need to brute force it as the [--user NUM] is not needed.
Changing screensaver_timeout has no effect.
To recap "screen_off_timeout" IS the screensaver start time within the Amazon settings.
screensaver_timeout does nothing - that I can tell.
I would like the Amazon screensaver to run more than 15 minutes but can't find how to do that.

Bevnrick said:
Change your Screensaver to Never and screen_off_timeout changes to 2147460000.
You don't need to brute force it as the [--user NUM] is not needed.
Changing screensaver_timeout has no effect.
To recap "screen_off_timeout" IS the screensaver start time within the Amazon settings.
screensaver_timeout does nothing - that I can tell.
I would like the Amazon screensaver to run more than 15 minutes but can't find how to do that.
Click to expand...
Click to collapse
About a month ago, I set the "screen_off_timeout" to 2147460000 (never) on my Fire TV Stick and it has worked beautifully playing the screen saver over and over. Then, today, it has mysteriously stopped. While the Stick doesn't go into sleep mode, the screen goes black with no screen saver. I suspect the culprit is Amazon's auto software upgrade to 5.0.5.
If anyone can help with a work around this, I'd be forever indebted to you!

marclamb said:
About a month ago, I set the "screen_off_timeout" to 2147460000 (never) on my Fire TV Stick and it has worked beautifully playing the screen saver over and over. Then, today, it has mysteriously stopped. While the Stick doesn't go into sleep mode, the screen goes black with no screen saver. I suspect the culprit is Amazon's auto software upgrade to 5.0.5.
If anyone can help with a work around this, I'd be forever indebted to you!
Click to expand...
Click to collapse
I second this request. I have noticed the same behavior with 5.0.5.
I am also curious if there is a list of all keys in the 'shell settings system' namespace. I could not find an adb command to output a list. It seems to require a key such as "screen_off_timeout". I noticed in another thread that you could access these keys via sqlite but I can't seem to get that to work on a non-rooted 5.0.5 aftv device.

Hi,
+1 follower here. I have a Fire TV Stick and My screensaver only stays approx. 20 minutes. it seems the setting screensaver_timeout is not read anymore because I tried changing its value to 60000 (1 minute) and 2147460000 (Never) but no effect, the screensaver still only runs approx 20 minutes. It seems Fire TV has another variable for that or maybe the max it could go for is 20minutes. I cannot comment about the version because this is a new stick.

I am also stuck with the same issue. Somebody please help!

Themes / Apps / Mods [MOD/magisk/root] Set charging limit to 90%

Based on: https://forum.xda-developers.com/t/limit-charge.4355851/
All credits to @rickysidhu_
Attached a simple Magisk module to set the charging limit to 90% at boot time.
If you want to "undo", just remove the Magisk module and reboot.

foobar66 said:
Based on: https://forum.xda-developers.com/t/limit-charge.4355851/
All credits to @rickysidhu_
Attached a simple Magisk module to set the charging limit to 90% at boot time.
If you want to "undo", just remove the Magisk module and reboot.
Click to expand...
Click to collapse
I really appreciate you uploading this, man. However, not sure the masses realize that ACCA magisk module can not only do exactly this, but it also has a litany of far more features.
Not only that, but it can actually increase the charging speed slightly. Cool stuff.
Just flash the module, and then install the APK. Then going to settings and set the parameters/limit, or increased charging speed you want.

I can't seem to get this to work on my P6P.
I am running Magisk 23014
The module is installed and "on"
The Damon is running in the App and In settings only temperature control and automatically cycle through switches are selected.
But, it always charged to 100%
Any suggestions?

biTToe said:
I can't seem to get this to work on my P6P.
I am running Magisk 23014
The module is installed and "on"
The Damon is running in the App and In settings only temperature control and automatically cycle through switches are selected.
But, it always charged to 100%
Any suggestions?
Click to expand...
Click to collapse
I have the same experience.
I suspect we can use it but have to change something manually like setting what the control file is, based on the thread that's referenced in the OP:
rickysidhu_ said:
If anyone is wondering how to stop the Pixel from charging at a certain percentage, it's the following command:
Code:
echo 90 > /sys/devices/platform/google,charger/charge_stop_level
Replace 90 with whatever percentage you want to stop charging at!
Click to expand...
Click to collapse

biTToe said:
I can't seem to get this to work on my P6P.
I am running Magisk 23014
The module is installed and "on"
The Damon is running in the App and In settings only temperature control and automatically cycle through switches are selected.
But, it always charged to 100%
Any suggestions?
Click to expand...
Click to collapse
Until the correct switches are implemented in acc, you can make it work by using the current & voltage controls as the charging switch.
> Click on the gear icon for Custom settings
> Click the pencil icon next to Charging switch
> Change the value to 0 mA & Save
> Save the custom settings (save icon in the top right corner)
> Restart ACC daemon

craigacgomez said:
Until the correct switches are implemented in acc, you can make it work by using the current & voltage controls as the charging switch.
> Click on the gear icon for Custom settings
> Click the pencil icon next to Charging switch
> Change the value to 0 mA & Save
> Save the custom settings (save icon in the top right corner)
> Restart ACC daemon
Click to expand...
Click to collapse
Everything is good, until i restart the daemon. then the app crashes. When i restart the settings in charging switch have reverted to automatic.
... test charging switch hangs.
Have disabled pixel battery stuff.
Have force closed and deleted all data for app.
with no luck

biTToe said:
Everything is good, until i restart the daemon. then the app crashes. When i restart the settings in charging switch have reverted to automatic.
... test charging switch hangs.
Have disabled pixel battery stuff.
Have force closed and deleted all data for app.
with no luck
Click to expand...
Click to collapse
Yeah, I don't know why the "Test Charging Switch" hangs in the app. But I'm not sure why restarting the daemon causes the app to crash for you.. You can try to set the charging switch to 0mA, save and reboot

Question from a noob, but why would I want to have my battery at 90% instead of 100%? Does it have something to do with battery health?

batpoil said:
Question from a noob, but why would I want to have my battery at 90% instead of 100%? Does it have something to do with battery health?
Click to expand...
Click to collapse
Correct.

batpoil said:
Question from a noob, but why would I want to have my battery at 90% instead of 100%? Does it have something to do with battery health?
Click to expand...
Click to collapse
Yep. For the last five years, I never quick charge, I charge as soon as my phone gets to 25% and I try to only charge to 75%. That 50% take still lasts me about a day.
Good battery health is also a selling point when I sell my old phones on Swappa.

craigacgomez said:
Yeah, I don't know why the "Test Charging Switch" hangs in the app. But I'm not sure why restarting the daemon causes the app to crash for you.. You can try to set the charging switch to 0mA, save and reboot
Click to expand...
Click to collapse
I finally got it working after multiple uninstall/reinstall/reboot cycles...
Or at least I thought I did. I changed the AccA version from Developer to Master.
That seems to have stopped the crashes and everything seemed to be working correctly. I plugged it in at 75% charge when I went to bed, but when i woke-up this morning I was at 40% charge -Status indicated discharging.
After a few more app and phone reboots it began charging again and now seems to be working: charge to 80%, discharge to 70%...
One thing I did notice was, if I set my Superuser access to "ask every time" I am constantly asks to grant permission every 20-30 seconds.
If it continues to be an issue I will post the log files if you can tell me where they can be found.

biTToe said:
I finally got it working after multiple uninstall/reinstall/reboot cycles...
Or at least I thought I did. I changed the AccA version from Developer to Master.
That seems to have stopped the crashes and everything seemed to be working correctly. I plugged it in at 75% charge when I went to bed, but when i woke-up this morning I was at 40% charge -Status indicated discharging.
After a few more app and phone reboots it began charging again and now seems to be working: charge to 80%, discharge to 70%...
One thing I did notice was, if I set my Superuser access to "ask every time" I am constantly asks to grant permission every 20-30 seconds.
If it continues to be an issue I will post the log files if you can tell me where they can be found.
Click to expand...
Click to collapse
After some time, I realised that the current/voltage switch was not working reliably, especially if you switch between chargers with different capacitites.
But I did find a better way to make acc work on the Pixel 6 / Pro. It uses the same charging switch that the modules above uses, but it will work with the acc pause/resume charging.
I do not know how to set this up using the app becuase it actually uses a combination of two switches the charge_stop_level and charge_start_level.
What you need:
Root (Magisk)
acc magisk modules (AccA app installs this. Tested with acc v2021.11.3)
Terminal emulator app
Steps:
Connect the phone to a charger
Open the terminal emulator app
Elevate to root
Code:
$ su
Reset acc to default (to eleminate any potential conflicts with previous configs)
Code:
# acc -s r
Set your pause (pc) and resume (rc) charge levels
Code:
# acc -s pc=80 rc=70
Specify the control switch
Code:
# acc -s s="/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --"
Validate the config. Check the values for resume_capacity, pause_capacity and charging_switch
Code:
# acc -s
Restart accd (acc daemon)
Code:
# accd
(Optional) Reboot
After that, you can tweak using AccA. Just leave the Charging switch & automatically cycle through switches" options untouched.
Further explanantion about the switch configuration
Code:
/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --
- set charge_start_level to 0 when below the "resume capacity" so that the phone will charge
- set charge_start_level to 95 when at the "pause capacity" so that the phone will stop charging (effectively forces the phone to only start charging if the battery is 95%)
- set charge_stop_level to 95 when below the "resume capacity" so that the phone will charge
- set charge_stop_level to 5 when at the "pause capacity" so that the phone will stop charging (effectively forces the phone to only stop charging if the battery is 5%)
- the double hyphen at the end disables the "automatically cycle through switches" to guarantee that the specified switch is the only one that will be used.

It doesn't work for me neither way. Hmmm

Burt Squirtz said:
I really appreciate you uploading this, man. However, not sure the masses realize that ACCA magisk module can not only do exactly this, but it also has a litany of far more features.
Not only that, but it can actually increase the charging speed slightly. Cool stuff.
Just flash the module, and then install the APK. Then going to settings and set the parameters/limit, or increased charging speed you want.
Click to expand...
Click to collapse
Hiya. What's the best method to keep up with more recent AccA Magisk Module versions? Asking for a friend who doesn't compile stuff. Seriously, I see it on GitHub https://github.com/Magisk-Modules-Repo/acc and I see instructions for building and installing, but is there any easy way for us lazy folks who never compile? i.e. is there any easy way for us non-developers to get files such as "Advanced_Charging_Controller_(ACC)-v2021.11.3(202111030).zip" out of the GitHub entry? Thanks.

@foobar66
I've changed the prefix of this thread from "Development" to "Themes / Apps / Mods" as it didn't qualify for the first one. Please review the stuck guidances at the top of the forum and do not change the prefix back.
Regards
Oswald Boelcke
Senior Moderator

I have the latest ACCA from August and the Dec version of ACC which is installed under the latest Magisk and the December update. I am also running the Kirisa kernel.
My issue is that the settings for "Apply on plug" never stick. The capacity control settings seem to stick.
I made the edit to the default profile which seems to work.

Hey.
Is it possible to make this module work on every charge without reboot?

craigacgomez said:
After some time, I realised that the current/voltage switch was not working reliably, especially if you switch between chargers with different capacitites.
But I did find a better way to make acc work on the Pixel 6 / Pro. It uses the same charging switch that the modules above uses, but it will work with the acc pause/resume charging.
I do not know how to set this up using the app becuase it actually uses a combination of two switches the charge_stop_level and charge_start_level.
What you need:
Root (Magisk)
acc magisk modules (AccA app installs this. Tested with acc v2021.11.3)
Terminal emulator app
Steps:
Connect the phone to a charger
Open the terminal emulator app
Elevate to root
Code:
$ su
Reset acc to default (to eleminate any potential conflicts with previous configs)
Code:
# acc -s r
Set your pause (pc) and resume (rc) charge levels
Code:
# acc -s pc=80 rc=70
Specify the control switch
Code:
# acc -s s="/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --"
Validate the config. Check the values for resume_capacity, pause_capacity and charging_switch
Code:
# acc -s
Restart accd (acc daemon)
Code:
# accd
(Optional) Reboot
After that, you can tweak using AccA. Just leave the Charging switch & automatically cycle through switches" options untouched.
Further explanantion about the switch configuration
Code:
/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --
- set charge_start_level to 0 when below the "resume capacity" so that the phone will charge
- set charge_start_level to 95 when at the "pause capacity" so that the phone will stop charging (effectively forces the phone to only start charging if the battery is 95%)
- set charge_stop_level to 95 when below the "resume capacity" so that the phone will charge
- set charge_stop_level to 5 when at the "pause capacity" so that the phone will stop charging (effectively forces the phone to only stop charging if the battery is 5%)
- the double hyphen at the end disables the "automatically cycle through switches" to guarantee that the specified switch is the only one that will be used.
Click to expand...
Click to collapse
hi! I'm quite new to ACC(A) and was wondering how to better keep my phone's battery healthy. I was wondering about battery idle mode and saw that Roll3r found a working battery idle mode for use with Kirisakura kernel which I'm on. However, I'm just a noob with all the terminal things and don't know how to implement it myself. it's this one:
Just an FYI (because others have asked), the only ACC (Advanced Charging Controller) charging switch with working battery idle mode is:
gcpm/constant_charge_current_max 1866420 0
Several other switches tested as supported idle, but they'd all crash ACC when idle priority is enabled. You may have to add it manually.
Edit: I shouldn't say "only" - this is the only switch (supported by this kernel) that I found get the phone to idle with. There might be others out there, too.
Click to expand...
Click to collapse
was wondering if you could list the terminal commands for this and what options am I not to touch afterwards (since in your example, which I have been using, you said not to touch the cycling option anymore)

As someone who doesn't like touching command lines/terminals, I just did these commands following craigacgomez and hoped for the best, but this time using Roll3r's switch that they found that allowed battery idle mode
su
acc -s r
acc -s pc=80 rc=70
acc -s s="gcpm/constant_charge_current_max 1866420 0 --"
accd
edit: ironically, idk how you add this switch using ACCA itself because entering the switch then the start and stop values just kicks me back to the previous dialogue, the one that says if I should choose auto or add a switch
craigacgomez's switch ( "/sys/devices/platform/google,charger/charge_start_level 0 95 /sys/devices/platform/google,charger/charge_stop_level 95 5 --" ) oddly stops charging when I enable the cooldown cycle feature on ACCA. So if I set the cooldown cycle to start at 45%, my phone stops charging at 45%.
I'm testing Roll3r's switch ( "gcpm/constant_charge_current_max 1866420 0 --" ) now, which passed the battery idle mode test. I've stayed on 80% since reaching it and ACCA reports a -10 current every so often so definitely staying on that battery idle mode. I also have the cooldown feature enabled, also set to 45% and it was working well with no premature paused charging / battery idling.
Quick question, if it says charging speed goes from -10 to +10, does that already signify battery idle mode? That's what happens to either switch so I'm assuming it is since I know my phone would have dropped in battery by now

Delete