Button savior no longer working :( - Nook Color General

For some unknown reason my button savior stopped working.
The home button is working fine but back and menu buttons will work
only once and then nothing. (they will change color when I touch them but nothing happens)
Can you help - PLEASE ?
Thanks

Use SoftKeys.
It's better anyways.
I tried Button Savior and always hated that no matter where I put it, it would get in the way of something like the keyboard, or a button in a game, etc.
With SoftKeys, I can move the button anywhere I need to. And I have it at 25% transparency too

That wasn't the answer.
I'm having the same issue. I just noticed it in some applications.
I'm on 1.1 if that matters. I don't particularly like SoftKeys.

Did you disable USB debugging by any chance?

No, it's enabled but the problem possibly started after connecting nook via USB to pc

Does it have superuser priviledges? Is it shown on the Superuser white list? This is exactly what happens if it does not have superuser rights. Check in superuser app to see it is listed. If so remove it then restart it. If that doesnt work I would uninstall it, reinstall it and make sure you press allow when prompted for superuser rights.

Done all that already
Yes it's on the white list and every time allowed.
After restarting the service it works once and then it stops.
Also it looks like USB debug likes to disable it self - not sure what to do about that.
This drives me crazy

I had the same issue before. I uninstalled it then reboot and reinstalled from the market. That solved the issue. Since then it has been working for a few days. Had no idea what the problem was.
Sent from my PC36100 using XDA App

Just occurred to me that I also created CWR backup just before I noticed this
problem. Is it possible that it can damage some files ?

This has happened to me ever since I used the pre-root 1.1 method. I could get it working after a reboot and/or when I wipe the data of Button Savior using Titanium Backup. Since I can't find a consistent fix for it, I reverted back to the 1.0.1 root, and just disabled the OTA update that may be pushed into the device.

y3n0 said:
This has happened to me ever since I used the pre-root 1.1 method. I could get it working after a reboot and/or when I wipe the data of Button Savior using Titanium Backup. Since I can't find a consistent fix for it, I reverted back to the 1.0.1 root, and just disabled the OTA update that may be pushed into the device.
Click to expand...
Click to collapse
Deleting data of Button Savior using Titanium Backup finally fixed the problem for me as well.
THANKS!

Deleting data of Button Savior using Titanium Backup did not work for me. I solved my issue bu uninstalling Button Savior, rebooting, turning USB Debugging mode on and then re-installing Button Savior through the market.
It did not ask for SuperUser permissions on install, instead, I had to press an action on the Button Savior dock and it prompted me for SuperUser permissions.
Hope this helps.
G

i just turn off button savior service, toggle usb debugging (if it's checked uncheck then recheck), and then restart button savior service.
you can access buttons saviour's service in the app itself. kill/start service.
that way i don't lose my settings.

Unfortunately I have the same problem all over again and no matter what I do this time it refuses to work.

lifeisfun said:
Unfortunately I have the same problem all over again and no matter what I do this time it refuses to work.
Click to expand...
Click to collapse
Same problem here using the overclocked froyo. Oddly if I force apps to close using advanced task killer then it works for a while. Until a reboot or installing uninstalling an app.
From 1.1 Nook Color with 1.1 ghz overclock

That's exactly right, if I get it to work I will NEVER reboot again

I have the same problem and to get BS to work, I have to disable and then enable USB debugging. Then I open the Button Savior settings and kill the service and then restart it. This works everytime. I think somehow the USB debugging setting is not being saved or some background process is disabling it.

marcusau2 said:
I have the same problem and to get BS to work, I have to disable and then enable USB debugging. Then I open the Button Savior settings and kill the service and then restart it. This works everytime. I think somehow the USB debugging setting is not being saved or some background process is disabling it.
Click to expand...
Click to collapse
Unfortunately it's not reliable fix for me
Sometimes it works but sometimes it doesn't
Any other tips ?
Thanks

It took me a while to figure out but here is what you need to do to fix it.
Go to your nooktool and go to all settings. Go into Development. Then uncheck USB debug
Then go to button Savior and disable button Savior.
Reboot
Go back in and enable USB debug.
Then enable button Savior. It should work for good now.
I think that button Savior reads from the USB debug setting upon obtaining superuser rights. So you have to make the changes first.
If that doesn't work, disable BS then unchecked USB debug then run BS again so it will write the disable USB debug change. Then disable BS again then reactivate USB debug then reactivate BS. I think you get the idea..
Sent from my LogicPD Zoom2 using XDA App

I've got this problem too - none of the above fixes seem to help.
Anyone got anything else to try??
I hate Soft Keys.

Related

[Q] Unable to Download from AndroidMarket

Hi,
I have this issue for the past one week.
The APP downloads starts and stalls. The downloads are stuck at 'Starting Download'. I have been using captivate for the past one month, everything was ok until past one week.
I am unable to figure out whether the issue is with my mobile or something to do with my gmail account.... No idea.
Can someone help me?
Thanks in advance.
-Sattvic.
Well, I've uninstalled google talk application. Is this creating an issue?
Google talk is in some way used by the market, though I am unsure exactly how...
Generally the fix to this issue would be to go into settings, applications, manage applications, and then clear cache/clear data/force close the following apps: Market, Google Talk, checkin service.
Then reboot phone.
Unfortunately you have installed google talk... Oops ;-) don't know what to tell you there.
If you installed with Titanium Backup, donate and then restore, if you installed by some other method you may be able to sideload an apk of google talk on to your phone...
Sent from my SAMSUNG-SGH-I897 using XDA App
I too am unable to install anything, it started last last night and still going on.
Happened to me this morning at 4am. When i tried updating google earth. Now nothing will download nor install.
Shut off the phone. Hold down the up and down volume button and then press the on/off button... When the phone comes on, keep holding the up/down button and relesae the on/off button. A screen will pop up and then you can release the volume button. Using the up/down volume button, scroll down to clear the cache... then hit the on/off button. That may help...
GaryS1004 said:
Shut off the phone. Hold down the up and down volume button and then press the on/off button... When the phone comes on, keep holding the up/down button and relesae the on/off button. A screen will pop up and then you can release the volume button. Using the up/down volume button, scroll down to clear the cache... then hit the on/off button. That may help...
Click to expand...
Click to collapse
nope didnt solve it. thanks though
Is there a difference between using wifi and 3g? I know that sometimes the market will refuse to intall via wifi and then i just use airplane mode kill the market turn off airplane mode and then use 3g to download. It fixes the issue most of the time.

Problem with fresh install of cyanogen, probably an easy fix (phone wont lock....)

I just reinstalled cyanogen mod 5 (HTC DREAM) because I was having problems. Reinstalling it fixed the problem I had (it wasn't booting for some reason)
The problem I have now is retarded. When I push the end (red) button it doesn't lock the screen. [I've done this: spare parts > end button > set to sleep & settings > apps > dev > stay awake off. ]
Also the home button does not do anything anymore (it still works, as it will unsleep my phone and light it up). It should return me to screen 3.
Also, when I hold the end (red) button it use to suggest airplane mode. Now it just has restart/shutdown. thats not really a big deal though. It not locking the screen at all though is a huge problem. makes the phone unusable (due to pocket dialing )
Please help. thanks!
I tried reinstalling cm5 with dalvik-cache cleared. nothing. those features still dont work. I just installed cm6 (also cleared dalvik) STILL can't lock the screen.
Please help. This problem makes the phone unuseable.
Did you wipe your phone? For me this happened some time ago and the only chance was wiping data. You can try doing a nandroid backup, wipe your data and chech if it works then. Otherwise you can restore your backup
Send from my G1 with HTCClay's UNOFFICIAL Superfly 1.6 D/S ADS using XDA App
Njord0 said:
I just reinstalled cyanogen mod 5 (HTC DREAM) because I was having problems. Reinstalling it fixed the problem I had (it wasn't booting for some reason)
The problem I have now is retarded. When I push the end (red) button it doesn't lock the screen. [I've done this: spare parts > end button > set to sleep & settings > apps > dev > stay awake off. ]
Also the home button does not do anything anymore (it still works, as it will unsleep my phone and light it up). It should return me to screen 3.
Also, when I hold the end (red) button it use to suggest airplane mode. Now it just has restart/shutdown. thats not really a big deal though. It not locking the screen at all though is a huge problem. makes the phone unusable (due to pocket dialing )
Please help. thanks!
Click to expand...
Click to collapse
was it the latest version of 5?
I do remember in some of the RC's the menu button would unlock the phone no matter how it was set, that was specifically fixed in the next version, same with the home button. just throwing out ideas
Njord0 said:
I just reinstalled cyanogen mod 5 (HTC DREAM) because I was having problems. Reinstalling it fixed the problem I had (it wasn't booting for some reason)
The problem I have now is retarded. When I push the end (red) button it doesn't lock the screen. [I've done this: spare parts > end button > set to sleep & settings > apps > dev > stay awake off. ]
Also the home button does not do anything anymore (it still works, as it will unsleep my phone and light it up). It should return me to screen 3.
Also, when I hold the end (red) button it use to suggest airplane mode. Now it just has restart/shutdown. thats not really a big deal though. It not locking the screen at all though is a huge problem. makes the phone unusable (due to pocket dialing )
Please help. thanks!
Click to expand...
Click to collapse
I don't know @ the unlock screen stuff, but the home button action in cm6 can be configured in cmparts, so I'm assuming it can be configured in spare parts in cm5. Sometimes it can also be configured in the launcher's settings. @ the power options only containing restart and shutdown, if I remember correctly, the addition of airplane mode and sound on/off into the power button hold menu was an addition in cm6, but someone please correct me if I'm wrong there.
For the screen not locking, definitely suggest what the other guy said, do a full wipe/factory reset and reflash, and make a nandroid backup beforehand. So either way, even if it doesn't fix it, you can just restore, like the other guy said. Start with that, beyond that I don't know what else it would be.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Check your cm settings for screen time off delay and make sure its set to a reasonable amount.
-----
Sent from my CDMA Hero. I got some hot Froyo-on-Hero action here!
Did you fix this? I'm using AOSPs version of CM7, and to get this to work I changed the setting in Spare Parts > End Button Behavior > Go To Sleep

[Q] Soft Keys on Facebook

Hi - I wanted to know if anyone has found the best way to configure the keys.
I am using Zeam right now, but if you do this:
1. Login to facebook
2. View pictures
3. your viewing and sliding through them, there is no way to exit out, unless you hit the home button where you are forced back to the main home screen.
Is there a way to get the back hand soft key there or something?
Right now, I am just using hovering arrow from Soft Keys as a workaround.
Thanks!
I found that if you choose to comment on one, then you can hit the back button twice fast. I know its not a perfect solution, but its better than totally exiting the app and re-opening it.
Download button savior. I use it when the soft keys buttons disappear
Sent from my LogicPD Zoom2 using XDA App
MissKristine said:
Download button savior. I use it when the soft keys buttons disappear
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
I actually USE button savior, and while I admit it is a great app, it has this problem in facebook as well. Often the back button just does not work. I often have this issue in full screen apps or video. Sometimes enabling "USB Debugging" helps for a bit, but the problems creeps back up. I have emailed dev, but no response.
Program sift keys as your launcher. When i single press the n i get the softkeys many to just go back. Double press lands me at home screen.
sent from my nootered nook color
It's invariably the USB Debugging disabling itself. I've had it happen twice and both times it has been the cause. I'm pretty sure the second time was due to the 1.1 upgrade (flashed using the zip in the dev forum).
IMHO Button Savior is the app to use. It's much less intrusive than soft keys and works everywhere (when USB Debugging is enabled of course )
Button Savior needs both USB debugging on, and device being rooted in order to function properly(and, of course, being allowed in superuser). I've seen mention of people having issue with usb debugging turning off randomly or with restarts. Once that is fixed, there shouldn't be any problems. My SD build once also lost root for some reason, but that seemed to be rare (prob due to me messing with /system files).

Reset itself overnight

Without doing anything myself, my Moto X 2014 has almost reset itself whilst I was asleep.
The first warning was no notifications, there's always an email or two, but then it wouldn't let me pull the quick settings down either. The phone wasnt using Smart Lock, in fact most system settings were reset. I figured something might be wrong with xposed (however, it's been running for months with no change, no updates to Android, xposed framework, or modules) so I updated all the modules and rebooted, still nothing. For some reason I went and switched to guest account, then switched back to my account and I'm now able to see notifications I missed and use phone almost normally. But my settings had reset and after setting swiftkey back up I see "Predictions not available. Check SD card." so typing is a pain.
My home button isn't working either, it flashes but doesn't do anything. The back and multitasking buttons work. Holding home button brings up Google Now on Tap, but it doesn't take me to home screen.
What could have happened? Is my storage knackered? Its not near full. Just to be clear, all my apps remained installed and logged in as far as I can tell. Only SwiftKey and the Home buttons remain as a problem.
Edit: Bluetooth devices also reset, wasn't connected to car stereo.
Edit 2: reinstalled swiftkey and predictions came back. Rebooted and they went again! Home button still not working.
Edit 3: Installed CatLog and when I press home it says: Not starting activity because user setup is in progress. So it thinks I'm trying to do first time setup? My accounts are already there (one of the settings that did remain).
Edit4: Ran
Code:
am start -n com.google.android.setupwizard/.SetupWizardTestActivity
as root (use su command) in terminal emulator and managed to complete setup... Home button works now and SwiftKey predictions seem to be working after a few reboots.
I hope that never happens again.

Hold back to kill?

Ok. So here's what I've found so far. I installed 3+ xposed module that claim to have hold to kill and the 1 app I can find, from xda, and non of them work. I'm running 6.0.1 rooted with xposed and twrp 3.0 and I've noticed that when I long press back I get a flash of a menu popping up then it's gone. As for the app it seems to be good until late I try to kill then it does nothing. I also noticed that when using the app, I choose to activate the toggle in accessibility menu and when I leave it or use the kill it turns back off. Any ideas? Sorry for crappy texting...on friends phone.

Categories

Resources