codebasepk / neon Goto Github PK

Fast Tapping in App fails immediately on the 2nd TurnOn.

02-14 18:17:13.228 23171-23185/nonameyetsoft.com.torch W/CameraBase﹕ mediaserver's remote binder Camera object died
02-14 18:17:13.236 23171-23183/nonameyetsoft.com.torch W/CameraBase﹕ Camera service died!
02-14 18:17:13.236 23171-23171/nonameyetsoft.com.torch E/Camera﹕ Error 100

Widget Behavior on fast tapping is perfect. No Issues.

Tested on Maguro running stock Android 4.3

Turning the flash on by widget and locking the device for a specific period. On resume the Widget loses it's functionality.
Restarting the device or force killing the app under certain condition resumes widget functionality.
Probably a WakeLock issue on Widget Toggle.
Hard to Reproduce.
May fix if Widget-App Talk is fixed.

Tested on Moto X 2013 Stock Android 4.4.4
Most Probably Hammerhead will drastically slowdown as the InApp WakeLock issue.

Error: "Unfortunately" Neon Torch has stopped.
How to reproduce:
Open "Neon Torch" and turn on the flash. Lock the screen by pressing power button and then wait for 1 minute(minimum). Unlock the screen and press the Main button to Turn off the flash and it will crash.

Reason: java.lang.RuntimeException: setParameters failed.

Doesn't effect when Data Cable is connected.

Turning the flash on and leaving it on with the screen off for about more than 20 minutes restarts the phone.
Occurred a couple of times.

Bug: In App, if you tap the button, torch will first blink for 0.5 seconds while showing off position on Neon Button then turns on automatically like normal.
Same behavior on Widget as well.

How to Reproduce:

1. Open the App by clicking on Neon Icon :P.
2. Tap the Neon button.
3. Bam!

Possible Reason: onClick is automatically being called for two times on TurnON :/
2nd possible Reason: It's conflicting with the widget state.
3rd Possible Reason: The application may be doing too much work on its main thread :P

its a bug in 2.3.5 when we turn on light and leave it.
after some moments when the screen turn off and phone gets locked . Torch turns off and the app is still showing that torch is On and there is also surface Holder present.

We need our code to be flexible and easily usable. While the Service model is great for straight purposes, it becomes a little difficult if we want to do complex things with the code. We need to replace the service implementation with the general Class implementation.

A. Notification intent only works when the app is foreground.

B. Notification intent totally fails after sleep and awake by power button.
Steps to reproduce:
1: Launch the Application.
2: Turn the flash On.
3: Press the power button to standby and then again to wake the device.
4: Unlock the device and the app is foreground as it was.
5: Pull down the notification panel and tap.
6: Shiiii.....!

C. Notification intent should not exit the app if it's foreground.

Tested on Moto X 2013

I/Choreographer﹕ Skipped 34 frames! The application may be doing too much work on its main thread.

Method: Turn on the flash light and go to your homescreen. Drag down the taskbar and click on the notification.
Result: Notification disappears but flash keeps running.

If the battery strength is lower than 15%.
Show Warning Toast in App and on widget toggle as well.

In some conditions the desktop widget stops responding. One of the cases is when the launcher is restarted due to low memory.

1. Make sure to put neon widget on the desktop
2. Open settings > Apps > All and force stop Launcher
3. Go back to desktop and tap on the neon torch widget.

What happens: Nothing
What should happen: well, toggle the torch on/off ?