Is it possible to somehow put the AFTV to sleep with a button combo on the remote?
I would like to be able to do it from within Kodi/XBMC, Netflix. Hulu, etc without having to go into the settings.
An existing button combo is not known. If you have a rooted aFTV you could try to use LLama with a shell command:
Code:
input keyevent KEYCODE_POWER
A PC Power/sleep button on a USB keyboard, like the one on the Logitech K400, also works. You can also do it with a FLIRC. There is no way to do it with the standard remote.
AFTVnews.com said:
A PC Power/sleep button on a USB keyboard, like the one on the Logitech K400, also works. You can also do it with a FLIRC. There is no way to do it with the standard remote.
Click to expand...
Click to collapse
I have a similar question. I'm rooted. Is there a way to kill SPMC when it hangs vs going into managed installed apps find spmc and force stop? Something like longpress pause should help immensely.
navigates said:
I have a similar question. I'm rooted. Is there a way to kill SPMC when it hangs vs going into managed installed apps find spmc and force stop? Something like longpress pause should help immensely.
Click to expand...
Click to collapse
No, there's no way. You're only other option would be a full system restart by holding Select and Play.
AFTVnews.com said:
No, there's no way. You're only other option would be a full system restart by holding Select and Play.
Click to expand...
Click to collapse
That is surely another option but that is a trade off. Wait for the whole boot or navigate down. thanks aftvnews
Calibaan said:
An existing button combo is not known. If you have a rooted aFTV you could try to use LLama with a shell command:
Code:
input keyevent KEYCODE_POWER
Click to expand...
Click to collapse
Nice. Wish some one would make a FTV/FTVS app that can be trigger from the Recent/FiredTV/Kodi Apps to turn the screen off... That would help things...
Y314K said:
Nice. Wish some one would make a FTV/FTVS app that can be trigger from the Recent/FiredTV/Kodi Apps to turn the screen off... That would help things...
Click to expand...
Click to collapse
I did try this with ShellExecute and also with sending a KeyEvent programmatically from an app. It seems that this still needs root to be done. The only way I know it can be executed without root is via ADB.
Calibaan said:
I did try this with ShellExecute and also with sending a KeyEvent programmatically from an app. It seems that this still needs root to be done. The only way I know it can be executed without root is via ADB.
Click to expand...
Click to collapse
Guess there might be a different code that the keyboards power button use like on the K400...
No, the K400 does use exactly this KEYCODE_POWER code
The problem is that it seems that a default app isn´t allowed to shellexecute the /system/bin/input binary. Same problem for SendKey events. External ADB access seems to have more system rights.
Since I´m not an Android nor Java coder perhaps a more experienced app coder could tell details about this.
Calibaan said:
No, the K400 does use exactly this KEYCODE_POWER code
The problem is that it seems that a default app isn´t allowed to shellexecute the /system/bin/input binary. Same problem for SendKey events. External ADB access seems to have more system rights.
Since I´m not an Android nor Java coder perhaps a more experienced app coder could tell details about this.
Click to expand...
Click to collapse
yeah KEYCODE_POWER is exactly the same as the old (not-quite-deprecated) keyevent 26. and as people have mentioned, it's what the power/sleep/crescent-moon key on your keyboard is doing.
yep - adb shell input keyevent 26 'sleeps' the KFTV immediately (but remember, childrens of the world, KFTV NEVER SLEEPS. it is a lie. although if it makes your TV happier, cool.)
and you're right, the adb shell has a bit more rights than e.g. if you get an internal shell (from, say, terminal emulator) it is weaker. and probably also right, apps have diminished privileges too.
however... ok, this is an extremely stupid trick I came up with a while ago...
it's still possible to get an adb shell from a lesser shell (e.g. if you come in using sshdroid, or are typing on the terminal emulator app, etc.) - check out:
http://forum.xda-developers.com/showthread.php?t=2715315
sadly I was never able to find out a programmatic way to perform the above, so it's not terribly useful.
There are two ideas beside the keyevent I did not try.
1.) It is possible to switch manually "off" from menu Settings > System > Sleep. Maybe an app could set an intent action to this menu call.
2.) Probably an app could use the Android power manager in a way to change the system power state to force sleep: http://developer.android.com/reference/android/os/PowerManager.html
Related
Since updating Pandora a while back, the audio quality is less than decent. It sounds like every song that's been played has the treble turned all the way down, or that the singer is trapped in a tin can. After doing some light reading, the nexus forum came up with the solution that I've applied to my EVO. Click For Thread
The issue I'm having is getting the build.prop file to stay permanently changed, even after trying the listed instructions in post #13. When I pull the file using adb pull, I cant see the file immediately on my C:\ drive. I can only find it using search, then after changing and adb push'ing it to my phone the adb shell getprop listed says media.stagefright.player-enable is true (still on).
Any suggestions?
Use root explorer and make the changes from your phone. Should work after a reboot.
Sent from my PC36100 using XDA App
Also, make sure that in your Pandora Settings, you have it set to Higher Quality Audio!
I noticed the same thing (only in the car, with the volume up loud) and changing this setting did the trick!
Doh had completely forgotten about that Higher Quality Audio thing!
Your NAND might not be unlocked. Use these commands before pushing build.prop:
Code:
adb shell
su
mount -o remount,rw /system
exit
Topher227 said:
Also, make sure that in your Pandora Settings, you have it set to Higher Quality Audio!
I noticed the same thing (only in the car, with the volume up loud) and changing this setting did the trick!
Click to expand...
Click to collapse
Yeah I tried that, but while it sounds better than on Normal/Low quality I can still tell something isn't quite right. Especially in the car. Using the "temporary" way to turn off the stagefright makes it WAY better so I know something needs to be done.
drmacinyasha said:
Your NAND might not be unlocked. Use these commands before pushing build.prop:
Code:
adb shell
su
mount -o remount,rw /system
exit
Click to expand...
Click to collapse
I'm rooted with unrEVOked 3, I was under the impression that it permanently unlocks NAND. Should I try that anyhow?
One of the first things I do when flashing a rom is edit the build.prop to fix Pandora...root explore is the way to go...it's totally easy
A smartphone is not very smart in the hands of an idiot.
Thanks works perfect
Hi Guys,
I'm getting bug reports often, the phone vibrates and tries to email out a report and a screenshot (to nowhere in particular) it also stores the text files in a folder, around 2/3mb each
Some history about the actual phone:-
I picked it up from Hong Kong, GSM 4.02 yakjuzs variant.
I managed to unlock it the other day, and root it (su was showing up on the phone) but for some reason clockwork mod did not flash permanently to the phone. it was the standard recovery.
anyways, I then used a root tool to flash a stock 4.02 image to the phone, and got the phone to yakju. I then flashed 4.04.
Not sure if the phone is rooted? as su no longer works...and recovery is stock.
I don't care too much about all that, but I'm just wondering where and why these bug reports keep popping up.
did I miss a step or do something I shouldn't?
Try a factory reset?
any help or clue would be great.
Check my sig to re-root.
As far as the bug reports...
They pop up if you accidentally press volume+, volume-, and power at the same time.
Try it now.
/system/bin/bugmailer.sh can be deleted/renamed...but you'll need root access to do so.
Thanks for the reply. Is this a new thing introduced to 4.04?
And this seems to be happening on its own? I'm pretty.sure I'm not pressing any buttons...unless there's a.delay.on it.
HSKalay said:
Thanks for the reply. Is this a new thing introduced to 4.04?
And this seems to be happening on its own? I'm pretty.sure I'm not pressing any buttons...unless there's a.delay.on it.
Click to expand...
Click to collapse
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
chandradithya said:
This is a manual bug report triggered by pressing both volume keys and the power button at the same time. It will vibrate once when you do it and then it takes a good minute or two for it to compile the report. The phone will then vibrate 3 times quickly when the report is ready, but only if the phone is awake and unlocked. So, for example, if you hit the power button to check the time and happen to press all three buttons or your TPU case (just an example) is holding down your volume buttons, then it will trigger then. You won't actually see the results until the next time you unlock the device. They are addressed to your default email address unless your ROM developer adds an email to them. Obviously being stock this would not be the case.
Click to expand...
Click to collapse
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Sent from my brain using human to phone transport technology.
ABQNM said:
While I appreciate the fact that you are helping out, please do not take my responses from another forum and paste them here verbatim as your own.
Source: http://rootzwiki.com/index.php?/topic/18671-Disable-bug-report-error-messaging?#entry488123
Sent from my brain using human to phone transport technology.
Click to expand...
Click to collapse
No offence to you. Seriously.
was annoyed with this issue, google searched it , opened a lot of tabs, found many posts never had answers,
I agree it was copy paste, sorry for not mentioning the source.
chandradithya said:
No offence to you. Seriously.
was annoyed with this issue, google searched it , opened a lot of tabs, found many posts never had answers,
I agree it was copy paste, sorry for not mentioning the source.
Click to expand...
Click to collapse
No worries. It is just a little strange reading a thread and seeing something you know you have taken the time to explain posted by someone else. Verbatim. Just caught me off guard. Cheers.
Sent from my brain using human to phone transport technology.
Or you could just disable USB debugging:
Snip from bugmailer.sh:
Code:
# Do not allow bugreports on user builds unless USB debugging
# is enabled.
if [ "x$(getprop ro.build.type)" = "xuser" -a \
"x$(getprop init.svc.adbd)" != "xrunning" ]; then
exit 0
fi
sirkro said:
Or you could just disable USB debugging:
Snip from bugmailer.sh:
Code:
# Do not allow bugreports on user builds unless USB debugging
# is enabled.
if [ "x$(getprop ro.build.type)" = "xuser" -a \
"x$(getprop init.svc.adbd)" != "xrunning" ]; then
exit 0
fi
Click to expand...
Click to collapse
Now that everyone is on 4.0.4 that is correct. Prior to 4.0.4, this was not an option. The only way to disable it prior was to rename/delete the shell script.
Sent from my brain using human to phone transport technology.
Hi,
I wondered if anyone could help me, Im trying to disable the 30 min sleep on my Fire TV stick as I need it to remain on a webpage 24hrs as a communication tool. I tried used the dolphin browser with the auto refresh but it crashes and I cant root the stick. I tried a stay awake app too which didn't work either, any help would be greatly appreciated.
Thanks
KoKee
kokee said:
Hi,
I wondered if anyone could help me, Im trying to disable the 30 min sleep on my Fire TV stick as I need it to remain on a webpage 24hrs as a communication tool. I tried used the dolphin browser with the auto refresh but it crashes and I cant root the stick. I tried a stay awake app too which didn't work either, any help would be greatly appreciated.
Thanks
KoKee
Click to expand...
Click to collapse
Have you tried Tasker? That maybe able to do this for you? If it's not possible it maybe because you need root to stop the timeout? & root isn't possible via the fire stick
deanr1977 said:
Have you tried Tasker? That maybe able to do this for you? If it's not possible it maybe because you need root to stop the timeout? & root isn't possible via the fire stick
Click to expand...
Click to collapse
Tasker has worked a treat - thank you very much
Tasker
Hi there I have the same problem with my Amazon fire TV box going in to sleep mode (black screen) where can I find and install tasker. Thanks in advance.
evertheoptimist said:
Hi there I have the same problem with my Amazon fire TV box going in to sleep mode (black screen) where can I find and install tasker. Thanks in advance.
Click to expand...
Click to collapse
There is a trial version in the play store but if you have a rooted phone,tablet or what ever just buy it, it was one of the first apps I bought & have used it for years & is so useful, a little hard to use at first but well worth learning how to use it.
Sent from my SM-G900F using Tapatalk
What did you do with tasker to stop the screen blanking?
Ewle said:
What did you do with tasker to stop the screen blanking?
Click to expand...
Click to collapse
I'd imagine it was something like - when app open, display timeout (then input what ever length of time you wany it to stay open for?)
Sent from my SM-G900F using Tapatalk
Updated my firetv stick and tasker doesn't work anymore , I have set it up again but no joy - anyone had success with any other app?
fire tv stop sleep mode
turn your screen saver to never to stop sleep mode on fire tv
beechie100 said:
turn your screen saver to never to stop sleep mode on fire tv
Click to expand...
Click to collapse
that stops the screensaver but the firetv will goto sleep with a black screen after 20/30 mins
kokee said:
that stops the screensaver but the firth will goto sleep with a black screen after 20/30 mins
Click to expand...
Click to collapse
You are right i posted a bit quick. But i have found that it will not sleep with certain apps for instance i played a hour long you tube mix of music and it never went to sleep but when i play a normal music app its sleeps.
Have any of you guys been able to find a fix? i couldn't even use tasker as it wanted me to hit the + button but due to the limited functionality of the remote control which accompanies the fire stick, i cant even get down to it. is there anyway to prevent the fire tv stick from sleeping ? as i need it to display a website, constantly
Not sure if this works on FTV stick and/or non-rooted, need to be tested. It works on FTV2 rooted (don't have a stick to test).
Scroll to the last post on this thread:
http://forum.xda-developers.com/fire-tv/help/how-off-sleep-mode-fire-tv-t3123111
dbdoshi said:
Not sure if this works on FTV stick and/or non-rooted, need to be tested. It works on FTV2 rooted (don't have a stick to test).
Scroll to the last post on this thread:
http://forum.xda-developers.com/fire-tv/help/how-off-sleep-mode-fire-tv-t3123111
Click to expand...
Click to collapse
is that with the latest OS?
rav0100 said:
is that with the latest OS?
Click to expand...
Click to collapse
No, one version back, I think. Mine is at 5.0.5 (537174420), pre-rooted RBox.
have the same issue here... have you find a solution?
Any updates on this (2018) ?
I'd like to share my work-around as of 2018. I install "Stay Alive" app on my fire stick and open it. After you open it, it will keep the screen awake. Keep in mind that it's a third party app, so you have to sideload it, it should be quite easy to google for a tutorial on how to sideload apps onto fire tv stick.
There are many other apps in the play store that claim to keep the screen alive, but in most of them it takes quite some navigation to set them up and navigation within third-party apps can be tricky using fire tv remote or app. Fortunately, Stay Alive has the right settings (keeping the screen alive forever) enabled by default, so just opening it does the job!
Simple TV Display (No Sleep Webpage TV) - an app that helps solves the the original post. Lets you put in a webpage, set how often you want to refresh, and then shows the webpage while keeping it the screen awake
Use a program called Stay Alive! It will appear not to work and complain about google play services not being installed, but my launcher is always open after I turn my tv on in the morning now, with CEC enabled too.
Hi! I wanted to install this app for using it's floating window functionality, but when I go to enable it, as the screen is on landscape mode, and I guess the resolution is to low? (1280x600), instead of showing the entire window, it shows me only the red area on the picture, making it impossible to enable the "draw on screen" function.
Any guess?
Sorry to Bump an old thread, but does anybody have an input on this? Having the same issue
Shep156 said:
Sorry to Bump an old thread, but does anybody have an input on this? Having the same issue
Click to expand...
Click to collapse
Still can't install..
If.u get.it, please.let me know!
Sent from my Pixel 2 using Tapatalk
groggycl said:
Still can't install..
If.u get.it, please.let me know!
Click to expand...
Click to collapse
So here was my process, I should mention this was on a PX5 Dasaita MTCD(E) I noticed after the fact this was for MTCB.
Installed system updates to latest, MCU as well, I then rooted the head unit and tried to use a resolution changing app to see if it would allow me to see the permission button, in doing so it got stuck sideways without showing apps and I had to factory reset the head unit and start over.
In the end after reorganizing and installing apps, the head unit is now unrooted I'm pretty sure, I went into the advanced menu in app permissions for Musixmatch, and toggled the "Draw over apps" switch to ON, it somehow seemed to work because it didn't when I tried that before root, all of a sudden the app started drawing over like normal and floating lyrics worked.
I mention all this only because it might have something to do with the root/fresh install that allowed it to work. At the end of the day the app is sort of sluggish, floating icon looks blurry, and it seemed to cause the unit to spaz out and freeze up when running the floating lyrics with Google Maps + Spotify, too much to handle I guess.
I hope it helps to some degree! My advice would be to mess with the permission setting and reboot it before rooting unless you're comfortable rooting just for the hell of it.
As the title. I've disabled it on the phone (Note 9) but can't find how to get it off the watch.
RR-99 said:
As the title. I've disabled it on the phone (Note 9) but can't find how to get it off the watch.
Click to expand...
Click to collapse
I don't think you can get rid of it completely but you can get on the gear app, select Samsung pay and in settings it will let you disable it.
Maybe going on recovery mode and reseting the watch can wipe it a bit more or take off any update it had? I'm not sure if it had any. You could even try changing the watch region to one that doesn't have pay enabled but that would be a bit overkill as the app doesn't use that much storage and it may be still somewhere in there but not visible.
Thanks. I'd just like to stop it showing up if I press the button too long.
RR-99 said:
Thanks. I'd just like to stop it showing up if I press the button too long.
Click to expand...
Click to collapse
Yeah me too, dam thing always comes on
Sent from my [device_name] using XDA-Developers Legacy app
If I disable NFC on my Watch SM-R800, the long press don't fire up S-Pay until I enable it back.
Give it a try
RR-99 said:
As the title. I've disabled it on the phone (Note 9) but can't find how to get it off the watch.
Click to expand...
Click to collapse
Thanks for the suggestion, but no go here. I've had NFC turned off since new, still get the S Pay prompt.
If you connect with sdb and run this command.
pkgcmd -D -t app -n com.samsung.samsung-pay-app --global
you can disable the package, and it will not open when you long press the menu button.