FORUMS

Analysis & Opinion

Top Forum Discussions

[Android 2.2-3+] Killswitch for tablets and phones with cases [12 May]]

7,047 posts
Thanks Meter: 2,050
 
By ftgg99, Account currently disabled on 10th March 2011, 05:06 PM
Thread Closed Subscribe to Thread Email Thread
MOD EDIT: links removed

Killswitch for tablets and phones


Fahrbot Mobile presents Killswitch, a utility made specifically for devices with cases.


What does Killswitch do?

The app uses a combination of sensors to control the sleep state and screen lock of any device.

At the moment, it uses the proximity sensor, light sensor and accelerometer.

Killswitch now has a night mode for weak sensors - if you find there are errors working in low light conditions on your device, simply set up a schedule!

Killswitch has the added advantage of removing your lockscreen via two different methods if you so wish. If you have a case, it really isn't necessary and can be annoying.


Why use Killswitch?

Killswitch will save you battery - putting your device to sleep is as intuitive as shutting your case or turning your phone face down.

And, of course, Killswitch will show all your ipad and iphone loving mates why android is just that much more awesome

After upgrading to a newer version, please go into the settings dialog and enable Killswitch again. This is not optimal, but it saves battery and cpu time by removing the necessity for a constantly running service!

In order to uninstall the app, untick "Admin privileges" in Killswitch or via the Accessibility page of your device's settings.


sleeplessninja video review:

Thanks bud.




Android Market link:
The app is available right now on the Android Market.

Screens:
Attached Thumbnails
Click image for larger version

Name:	config-1.jpg
Views:	683
Size:	39.1 KB
ID:	538856   Click image for larger version

Name:	config-2.jpg
Views:	578
Size:	27.8 KB
ID:	538858   Click image for larger version

Name:	configspng.jpg
Views:	554
Size:	25.9 KB
ID:	538859   Click image for larger version

Name:	switchoff-confirm-1.jpg
Views:	540
Size:	29.0 KB
ID:	538860   Click image for larger version

Name:	screen-20110404-1327.jpg
Views:	331
Size:	33.4 KB
ID:	560098  
Last edited by Diamondback; 19th February 2013 at 11:31 PM.
The Following 3 Users Say Thank You to ftgg99 For This Useful Post: [ View ]
 
 
10th March 2011, 10:32 PM |#2  
OP Account currently disabled
Thanks Meter: 2,050
 
1010
More
Killswitch 1.0.5

+ Added scheduling
+ Added night mode
+ Fixed bugs on many devices

Killswitch 1.0.4

+ Verbose debugging mode added

Killswitch 1.0.3

+ Bigger buttons
+ Sensitivity tweaks for Samsung 2.2 devices
+ Bug logging

Killswitch 1.0.2

+ Minor layout tweaks
+ Added new icons

Killswitch 1.0.1

+ Fixed orientation-related problems
+ Tweaked default activation delay value
+ Cleaned up Help and Tips dialog
+ Added license check delay to fix caching problems on Google's end

Killswitch 1.0.0 RC

+ Added license check, nag screen, functionality restrictions for unlicensed copies
+ Alternative no-lock mechanism reintegrated
+ About page added
+ Issues related to ProGuard fixed
Last edited by ftgg99; 12th May 2011 at 02:34 PM.
10th March 2011, 10:33 PM |#3  
OP Account currently disabled
Thanks Meter: 2,050
 
1010
More
reserved for suggestion list
14th March 2011, 11:56 AM |#4  
OP Account currently disabled
Thanks Meter: 2,050
 
1010
More
Just a heads-up for those who have not managed to work out how to use Killswitch - despite very clear instructions in the Help and Tips dialog.

On a tablet with case the settings should look like this:

Enable Killswitch: tick
Admin Permissions: tick

Confirmation time: 10sec
Activation delay: 6sec

No-lock: Disable screen lock

Use proximity: no tick
Use light sensor: tick
Sensitivity: 10%
Use accelerometer: no tick

For a phone the settings should be exactly the same, except with "Use proximity sensor: tick". These are the settings Im using right now and they work perfectly.

The point of the app is also to avoid accidental sleep mode in a dark room through the popup dialog. Do not choose "Use accelerometer" unless you plan on using both light sensor and facedown at the same time. Instead, choose "Enable facedown mode only" if you see the popup dialog while using the tab in a dark room - this will disable the light sensor but enable facedown until you next swich on/ off.

Please read the Help and Tips section before giving up!
Last edited by ftgg99; 14th March 2011 at 11:59 AM.
14th March 2011, 03:06 PM |#5  
Senior Member
Flag Kidderminster
Thanks Meter: 7
 
More
I've bought and installed Kill Switch for my galaxy tab, used the exact same settings shown above but it doesn't appear to be doing anything on my tab. I'm on overcome 1.2.3 and have the fugutweaks applied
14th March 2011, 03:16 PM |#6  
OP Account currently disabled
Thanks Meter: 2,050
 
1010
More
After upgrading to a newer version, please go into the settings dialog and enable Killswitch again. This is not optimal, but it saves battery and cpu time by removing the necessity for a constantly running service!

Im using overcome 1.2 and its working just fine... also, its tested to work on JK5 and up stock roms.

Decrease activation delay in settings to 2 seconds, then try putting your finger over the light sensor to check whether its working - its just to the right of the front facing camera.

If not this is a kernel-related problem, so please send logcat!
Last edited by ftgg99; 14th March 2011 at 03:29 PM.
14th March 2011, 03:43 PM |#7  
Senior Member
Flag Kidderminster
Thanks Meter: 7
 
More
Hmm...I appear to be having a problem with the light sensor. I can get the accelerometer to switch it off. I think I'm going to undo the fugutweaks, see if that's the problem.
14th March 2011, 03:57 PM |#8  
OP Account currently disabled
Thanks Meter: 2,050
 
1010
More
Could you please post a logcat? This would be the easiest way to check what the problem is.

You can get the app aLogcat for free from the market. Use it after youve turned on killswitch and just post the resulting text here.
14th March 2011, 04:05 PM |#9  
Senior Member
Flag Kidderminster
Thanks Meter: 7
 
More
Sorry, I undid the fugutweaks before I read your reply and this appears to have cured the problem
14th March 2011, 04:12 PM |#10  
OP Account currently disabled
Thanks Meter: 2,050
 
1010
More
OK, no problem! I hope you find the functionality useful!
14th March 2011, 04:33 PM |#11  
Senior Member
Flag Kidderminster
Thanks Meter: 7
 
More
Quote:
Originally Posted by mrgrey1701

Sorry, I undid the fugutweaks before I read your reply and this appears to have cured the problem

I spoke too soon...its very temperamental with the light sensor - sometimes it works, most times it doesn't. Installing logcat and will post results here shortly:

D/alogcat ( 4511): stopped
D/alogcat ( 4511): starting ...
W/InputManagerService( 2829): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$ Proxy@48a7f9b8
D/dalvikvm( 2917): GC_EXPLICIT freed 15 objects / 536 bytes in 77ms
D/dalvikvm( 2917): GC_EXPLICIT freed 7 objects / 288 bytes in 71ms
D/BatteryService( 2829): update start
D/BatteryService( 2829): updateBattery level:77 scale:100 status:4 health:2 present:true voltage: 3874 temperature: 323 technology: Li-ion AC powered:false USB powered:false icon:17302168
D/WifiService( 2829): ACTION_BATTERY_CHANGED pluggedType: 0
D/dalvikvm( 4449): GC_EXPLICIT freed 17829 objects / 1823232 bytes in 448ms
D/dalvikvm( 2924): GC_EXPLICIT freed 2942 objects / 120712 bytes in 274ms
W/PowerManagerService( 2829): Timer 0x7->0x3|0x0
I/PowerManagerService( 2829): Ulight 7->3|0
V/WindowManager( 2829): onOrientationChanged, rotation changed to 1 false mLockedRotation=-1
E/WindowManager( 2829): Overwriting rotation value from 1
V/WindowManager( 2829): Rotation changed to 1 from 0 (forceApp=-1, req=1)
I/WindowManager( 2829): Setting rotation to 1, animFlags=0
E/SurfaceFlinger( 2829): Surface Flinger::setOrientation mIsRotationPossible = 0, nBackupOrientationValue = 1
I/TvOut-Observer( 2829): setTvoutOrientation rotation = 1
E/TvOut-Observer( 2829): SetOrientation
I/ActivityManager( 2829): Config changed: { scale=1.0 imsi=234/20 loc=en_GB touch=3 keys=1/1/2 nav=1/1 orien=2 layout=35 uiMode=17 seq=6 FlipFont=0}
D/PhoneApp( 2921): updateProximitySensorMode: state = IDLE
I/UsageStats( 2829): Unexpected resume of org.jtb.alogcat while already resumed in org.jtb.alogcat
V/alogcat ( 4511): save instance
V/alogcat ( 4511): paused
D/alogcat ( 4511): stopping ...
V/alogcat ( 4511): destroyed
D/alogcat ( 4511): stopped
V/alogcat ( 4511): created
D/alogcat ( 4511): canceling periodic saves
V/alogcat ( 4511): started
V/alogcat ( 4511): restore instance
V/alogcat ( 4511): resumed
D/alogcat ( 4511): starting ...
V/Thumb Keyboard( 2917): HAAALLLOOO widht: 1025
V/Thumb Keyboard( 2917): HAAALLLOOO height: 272
V/WindowManager( 2829): onOrientationChanged, rotation changed to 2 false mLockedRotation=-1
E/WindowManager( 2829): Overwriting rotation value from 2
V/WindowManager( 2829): Rotation changed to 2 from 1 (forceApp=-1, req=2)
I/WindowManager( 2829): Setting rotation to 2, animFlags=0
E/SurfaceFlinger( 2829): Surface Flinger::setOrientation mIsRotationPossible = 0, nBackupOrientationValue = 2
I/TvOut-Observer( 2829): setTvoutOrientation rotation = 2
E/TvOut-Observer( 2829): SetOrientation
I/ActivityManager( 2829): Config changed: { scale=1.0 imsi=234/20 loc=en_GB touch=3 keys=1/1/2 nav=1/1 orien=1 layout=35 uiMode=17 seq=7 FlipFont=0}
D/PhoneApp( 2921): updateProximitySensorMode: state = IDLE
I/UsageStats( 2829): Unexpected resume of org.jtb.alogcat while already resumed in org.jtb.alogcat
D/dalvikvm( 2917): GC_EXPLICIT freed 1479 objects / 99312 bytes in 137ms
V/alogcat ( 4511): save instance
V/alogcat ( 4511): paused
D/alogcat ( 4511): stopping ...
V/alogcat ( 4511): destroyed
D/alogcat ( 4511): stopped
V/alogcat ( 4511): created
D/alogcat ( 4511): canceling periodic saves
V/alogcat ( 4511): started
V/alogcat ( 4511): restore instance
V/alogcat ( 4511): resumed
D/alogcat ( 4511): starting ...
V/Thumb Keyboard( 2917): HAAALLLOOO widht: 606
V/Thumb Keyboard( 2917): HAAALLLOOO height: 462
D/dalvikvm( 2917): GC_EXPLICIT freed 2064 objects / 123784 bytes in 98ms
D/dalvikvm( 2917): GC_EXPLICIT freed 581 objects / 23088 bytes in 69ms
D/dalvikvm( 2917): GC_EXPLICIT freed 7 objects / 296 bytes in 60ms
D/UpdateService( 3192): rotation (new config = { scale=1.0 imsi=234/20 loc=en_GB touch=3 keys=1/1/2 nav=1/1 orien=1 layout=35 uiMode=17 seq=7 FlipFont=0})
I/DBG_WSS_DM( 3338): [wssTelephonyData.java Line:153] getInstance PHONE_TYPE_GSM
V/AlarmManager( 2829): set: Alarm{48f8a5d0 type 2 com.google.android.apps.maps}
D/dalvikvm( 2829): GC_EXPLICIT freed 19940 objects / 871280 bytes in 288ms
D/dalvikvm( 4177): GC_EXPLICIT freed 272 objects / 14272 bytes in 108ms
I/DBG_WSS_DM( 3338): [wssTelephonyData.java Line:153] getInstance PHONE_TYPE_GSM
V/AlarmManager( 2829): set: Alarm{48faf1a0 type 2 com.google.android.apps.maps}
D/dalvikvm( 3049): GC_EXPLICIT freed 14292 objects / 815880 bytes in 159ms
W/PowerManagerService( 2829): Timer 0x3->0x3|0x0
V/WindowManager( 2829): onOrientationChanged, rotation changed to 0 false mLockedRotation=-1
E/WindowManager( 2829): Overwriting rotation value from 0
V/WindowManager( 2829): Rotation changed to 0 from 2 (forceApp=-1, req=0)
I/WindowManager( 2829): Setting rotation to 0, animFlags=0
E/SurfaceFlinger( 2829): Surface Flinger::setOrientation mIsRotationPossible = 0, nBackupOrientationValue = 0
I/TvOut-Observer( 2829): setTvoutOrientation rotation = 0
E/TvOut-Observer( 2829): SetOrientation
V/AlarmManager( 2829): set: Alarm{48e73de8 type 1 android}
D/dalvikvm( 2829): GC_EXPLICIT freed 2694 objects / 116128 bytes in 259ms
E/ShutdownThread( 2829): IsShutDownStarted()
I/KeyInputQueue( 2829): Input event
I/PowerManagerService( 2829): Ulight 3->7|0
V/WindowManager( 2829): Dsptch to Window{48f9bc90 org.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
W/KeyCharacterMap( 4511): No keyboard for id 0
W/KeyCharacterMap( 4511): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
E/ShutdownThread( 2829): IsShutDownStarted()
I/KeyInputQueue( 2829): Input event
V/WindowManager( 2829): Dsptch to Window{48f9bc90 org.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
V/VibratorService( 2829): vibrateImmVibe: 13, magnitude: -1
V/VibratorService( 2829): setVibeStrength = 10000
V/WindowManager( 2829): Delivering toWindow{48d4a768 AtchDlgrg.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
V/WindowManager( 2829): Delivering toWindow{48d4a768 AtchDlgrg.jtb.alogcat/org.jtb.alogcat.LogActivity paused=false}
Last edited by mrgrey1701; 14th March 2011 at 04:40 PM. Reason: added logcat

Read More
Thread Closed Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes