TriggerTrap Offers Android Users to Remote DSLR Controls For almost every Camera Makers

Unleash the full potential of your camera via your android smartphone!!!!!!!!

TriggerTrap, a remote DSLR trigger app that is must have for every photographers and geeks. It’s not the only remote DSLR app we have plenty remote DSLR apps flying on the android playstore, but this one has almost supported to all the popular camera makers and models. You can control almost anything and more than your camera osd gui. To know, if your camera is in the list check here. You can also issue a request to them if your one is not listed. They are offering this app with a nominal cost and also they are providing USB OTG cables in a very cheap price, which is very difficult to get on a local market.

This slideshow requires JavaScript.

You can download the app directly from the Google play here.

https://play.google.com/store/apps/details?id=com.triggertrap

[Guide] How to setup and execute ADB and FASTBOOT on your Windows PC very easily

So, first of all you might be asking what is ADB ?

It’s  basically a tool through which you can issue shell commands via your computer to your phone. ADB stands for Android Debug Bridge. It comes as a part of the standard Android SDK, which you can grab here. Basically, it provides a terminal-based interface for interacting with your phone’s operating system. Since Android platform is based on Linux, command-line is the only way to obtain and manipulate root access often required to perform certain advanced operations on your device using root access.

You can also directly issue commands by installing a terminal applications like terminal emulator, but it’s not handy to execute complex commands on such a small screen.
So, want to get into the android era?

1. So, first step is to get the android SDK on your computer from here. Just download the installer and install it to any drive, in this guide I am installing to a folder called android in C drive i.e (C:\android).

   This slideshow requires JavaScript.
2. after installation has completed just click finish and it will automatically launch the SDK Manager. Now select both the option i.e platform tools and SDK tools and accept it and click Install. Once the process is done, you will have a ‘platform-tools’ folder inside your (C:\android) folder. That folder will have your ADB and all its dependencies.
3. Now, set the path variable. So, that you can easily issue commands via any location in cmd.To make ADB along with other Android SDK tools and platform tools easily accessible from anywhere at the command line, we shall add their paths to the PATH environment variable.
4. Right-click on the ‘Computer’ icon and click ‘Properties’. Now click ‘Advanced System Settings’ from the options in the left pane to bring up the ‘System Properties’ window. In the ‘System Properties’ window, click the ‘Environment Variables’ button on the ‘Advanced’ tab. 
5. Go-to the ‘Path’ in the ‘System variables’ section and double-click it to edit it and click on the text box and bring the cursor to the last.
6. Just add the below lines at the end of it, including both the semi-colons:

7. ;c:\android\tools;c:\android\platform-tools

   Note:If you have installed the SDK’s contents to another directory, make sure to use that one for your PATH variable.
   Notice that the semi-colons are necessary to separate each path variable entry from the next and previous ones.

8. Reboot your machine.

USB Driver installation (Optional if you already have your driver software pre-installed).

• The first step will be to download the USB drivers. To do this, launch SDK Manager from the SDK(android) folder and click on ‘Available packages’ in the left pane.

• Expand ‘Third party Add-ons’ followed by ‘Google Inc. add-ons’ and check ‘Google Usb Driver package’,
• Click ‘Install Selected’ and in the window that pops up, click the ‘Accept all’ radio button followed by the ‘Install’ button. After the installations completed. The drivers for both 32 bit and 64 bit systems will now be present in the SDK(C:\android) folder under ‘usb_driver\x86′ and ‘usb_driver\x64′ sub-folders respectively.
• Now, on the device(your mobile) go to Menu, select Settings > Applications > Development and enable USB Debugging.
• Manually browse to the location of the driver and select whether it’s x64 or x86 depending on your OS version and click OK then Next. Now open Device manager and manually install the driver.
• Once drivers have installed, you can verify successful installation by going to Device Manager. Your phone should be showing under ‘ADB Interface’, like the below screenshot.

Now, all the settings has been done. So, now it’s time to verify your ADB is working properly.

Open Command prompt by pressing  WinKey+R > type “cmd” > type ” adb devices “.

Now, it should list your android devices with the serial ID as shown.

Now, for a list of commands of adb go here.

[Guides] How to bypass the android pattern lock in case if you forgot the pattern a detailed GUIDE

Disclaimer: This is for educational and personal purposes only,You should not apply this to other people phones without permission.

So, today I am going to post a very detailed guide about how we can unlock android device pattern in-case you forgot, and can’t bypass it via official method i.e. via Google account login authentication because of you didn’t have DATA connection enabled or it was disabled before it got locked.

Actually this happened to me once, That day while going to sleep I just set a unlock pattern, but the next day when I woke and trying to wake my device, It was asking for the unlock pattern but my mind was completely back and I just forgot the pattern and it got locked.

But I tried going via Forgot pattern? option but no luck due to unable to sign in cause I have disabled the data connection last night before going to sleep. But, I somehow managed to unlock it via CWM and restored a nan-droid backup.(my device was already rooted & CWM recovery flashed, was running 2.3(Gingerbread))

This slideshow requires JavaScript.

So, later I found a way to bypass it via ADB.(android debug bridge).

These methods are confirmed working on Eclair(2.1), Froyo(2.2),Ginger-bread(2.3), Ice cream Sandwich(4.0) and Jelly-Bean(4.1) versions.

Prerequisites:

• The device needs to have ” USB Debugging “ enabled in application settings under development menu.

• Or in-case usb debugging isn’t enabled and you have ” cwm ” installed then you can run the same instructions from cwm.

• Root is not mandatory but chances would be more if the device was rooted.

• Setup ADB on your machine.(I have already explained a topic here on how to setup adb very easily in a previous guide).

Now, connect your phone USB to your computer and browse to your ABD Directory  via command prompt.

below are the commands you should be executing now one line at a time.

So, below are the commands you should be executing it via ADB.

• adb shell
• cd /data/data/com.android.providers.settings/databases
• sqlite3 settings.db
• update system set value=0 where name=’lock_pattern_autolock’;
• update system set value=0 where name=’lockscreen.lockedoutpermanently’;
• .quit
• exit
• adb shell rm /data/system/gesture.key

Instructions:

1. Execute all the commands via adb while phone is connected via usb.
2. Restart the phone.
3. After rebooting you may see the pattern lock, just try any random pattern and it will unlock and then remove the pattern from settings.