Tuesday, October 14, 2014

FDT error : Could not connect to the player, will try to connect for the next 72000 ms [Info] Listening to port 7935.

Select the Adobe Flash Player in viewer configuration
Run –> Run configurations –> Select your Launch Configuration file –> “Start” tab –> Viewer configuration.
Make sure you point out to the Debug version of the player in Windows –> Preferences –> FDT –> Tools –> Flash –> Flash Player. In my case the path is C:\Program Files\Adobe\Adobe Flash CS6\Players\Debug\FlashPlayerDebugger.exe but you should adjust this to wherever your Debug player resides.

Thursday, June 13, 2013

Evaluation of different Android debugging tools

Objective : Evaluation of different Android debugging tools and selecting one which can be used to debug our apps on mobile and tabs.

Analysis : We have experimented with different debugging tools present for android debugging and following is the analysis:
1)      ADB :
Limitation :  Only applicable for chrome browser issues. Not suitable for debugging issues with default browser on mob or tab.
Remarks : Very tricky installation and can take hours of time. But we will document the steps we took for installation which may help. (A separate blog post will be dedicated to this).
Evaluated platform : Samsung s2 mobile and google nexus 7

2) JSConsole :
Limitation : Only suitable to debug javascript related issues.
Remarks : Simple installation and easy to use.
Evaluated platform : Samsung s2 mobile and google nexus 7

3) Firebug Lite :
Limitation :
a)      Very inconsistent behavior shown. Sometimes the firebug frame is visible, sometimes its not.
b)      Need usb support on the device (mob or tablet) to attach a mouse for smoothly navigating through DOM shown in the firebug toolbar.
Remarks : Simple installation but very difficult to debug.
Evaluated platform : Samsung s2 mobile and google nexus 7

4) Weinre :
Limitation :
1)      Javascript issues can be debug only using console.log but not using breakpoint techniques.
2)      Server is tightly bound with IP, so there needs to be static ip where the weinre server can be run.
3)      The web page that needs to be debug needs to include a javascript file which needs to be loaded from the server url hence same limitation as 1
4)      The network tab does not display any information about the request/response cycle.
Remarks : Simple installation and can be used to debug DOM /CSS related issues.
Evaluated platform : Samsung s2 mobile.

5)  Other Techniques :
The other techniques like About:debug are also less developer friendly and lack community support.

Useful links:

This document provides plenty of solutions

I like the "4. USB Remote-Debugging" but "This is only possible with Google Chrome, not the default browser. (Chrome is available for Android 4+)."


There is an alternative even better


This is a google Play app, that give access to the JS LOG

Firebug lite
<script type="text/javascript" src="https://getfirebug.com/firebug-lite-debug.js"></script>





Conclusion :  Weinre is the most suitable tool for debugging in default android/stock browser. However, before we jump to debug any issue we should test if the issue is reproducible in chrome so that we can make use of adb remote debugging which provides the ability to debug in chrome inspector on the desktop and can save plenty of time.


Environment : Windows 7
These steps can be followed to setup weinre which can be used for mobile debugging. Links are mentioned for further assistance.

1) Install node (preferably v0.8.19 or above as the subsequent steps may fail with other versions)

2)  Open command prompt and check if node is installed by executing the command “node -v” (without inverted commas). If setup correctly, it will output version of the node that was installed.
Tips : Add to your path environment variable if its not updated immediately after node installation.

3)      Open command prompt and check if npm is installed by executing the command “npm -v”. (npm gets installed along with node)

4)      Open command prompt  and Install weinre using npm (node package manager).
npm –g install weinre

5)      Start weinre server by following these steps:
a)      Modify the file attached and replace the boundHost parameter to your ip
b)      Create a directory named “.weinre” in your home directory (execute the following command on the command prompt to find it)
 echo %HOMEPATH%
c)       Create a file server.properties with the contents from the file attached with the email.
d)      Execute the command
start weinre

6)       Copy following line in your web page html.

7)      Load the web page in your device. This will set your device as debugging target.

8)      Open browser and go to the address
<your-ip>:8000/client
Note : This the window where we can see debug the page loaded in the target device.

Important Links :


Friday, December 21, 2012

eclipse Specified VM install not found: type Standard VM name java 6, sun-1.6.0.35


In Eclipse, click the ant file -- Run As -- External Tools Configuration and click on the JRE tab.
Select "Run in the same JRE as the workspace"

Wednesday, January 4, 2012

Oracle 10g installation struggle

Inspiration: Oracle 10g did not work for me on Ubuntu 11.10, Ubuntu 10.10, Oracle Linux x86_64. I spent 3 weeks trying different distros and ended up doing the following steps which saved me from wasting any further time and I was able to work without any problems. So here's to those three weeks :)

Step1: Take backup of your data if you have any of the linux distros mentioned above.
Step2: Skip this step if you already have Ubuntu 9.1. Install Ubuntu 9.1 (karmic).
Step3: Install oracle 10g as a root user. Problem becoming root? solution follows :
sudo passwd root
su root

Download debian package from Oracle 10g from oracle website (western european).

Double click on it and you will be done.

Install the oracle-xe-client if you want one!

Upgrade your ubuntu to any of the newer version if you want fancy UI and more security.

Any questions? would love to reply to your precious comments :)

Tuesday, December 6, 2011

Setting up redmine 1.2 on heroku with redmine_s3 plugin


Tested system cnfg: Ubunut Lucid 10.04.3 LTS
Libraries Requirements: Essential libraries and rvm installed ( Refer the post with title “setting up a naked bare m/c and then view this post…Don’t start doing something else :P )
0) rvm rubygems 1.4.2
1) rvm install ruby-1.8.7-p334
2) rvm use ruby-1.8.7-p334 ( Still thinking about the photo! Few more commands dude, c’mon not now :) )
3) rvm gemset create rails-2-3-11
4) rvm gemset use rails-2-3-11
5) sudo gem install rails -v=2.3.11 / sudo gem install rails -v=2.3.11 –no-ri –no-rdoc ( For all the Indians who bought cheap systems and don’t have hard disk space a.k.a BPL )
6) sudo gem install rake -v=0.8.7
7) sudo gem install bundle
8) svn co http://redmine.rubyforge.org/svn/branches/1.2-stable redmine-1.2
9) find ./ -regex ‘.*svn’ -exec sudo rm -r {} \; ( Dont panic if it show a long list of ‘not found’ )
10) Create a file with name ‘Gemfile’ in your application directory with follwing contents (if you have followed this post correctly so far the directory name would be “redmine-1.2″ and you are already into it if you didn’t get any error.)
==============================================================
source :gemcutter

gem "pg"
gem "rake", "0.8.7"
gem "rails", "2.3.11"
gem "rack", "1.1.1"
gem "i18n", "0.4.2"
=============================================================
Note: Dont copy the "======" :) 11) bundle install
12) cp config/database.yml.example config/database.yml
13) Edit your config/database.yml to look like following:
=====================================================================
# MySQL (default setup).

production:
  adapter: postgresql
  database: redmine_heroku
  host: localhost
  username: postgres
  password: postgres
#  adapter: mysql
#  database: redmine
#  host: localhost
#  username: root
#  password:
#  encoding: utf8

development:
  adapter: postgresql
  database: redmine_heroku
  host: localhost
  username: postgres
  password: postgres
#  adapter: mysql
#  database: redmine_development
#  host: localhost
#  username: root
#  password:
#  encoding: utf8

# Warning: The database defined as "test" will be erased and
# re-generated from your development database when you run "rake".
# Do not set this db to the same as development or production.
test:
  adapter: mysql
  database: redmine_test
  host: localhost
  username: root
  password:
  encoding: utf8

test_pgsql:
  adapter: postgresql
  database: redmine_test
  host: localhost
  username: postgres
  password: "postgres"

test_sqlite3:
  adapter: sqlite3
  database: db/test.sqlite3
===============================================================
14) rake generate_session_store
15) Add following line in your config/environment.rb before last line i.e before "end"
===============================================================
****Here key is the key from "config/initializers/session_store.rb"
Here secret is the secret
from "config/initializers/session_store.rb"
Example: ****
config.action_controller.session = { :key => "_redmine_session", :secret => "56acb9c4c9e6165ad25a8f747e014b54eb219a6e7db2a549a0178ddc4bc73e68b16314c4054c7595" }

16a) RAILS_ENV=production rake db:migrate
16b) RAILS_ENV=production rake redmine:load_default_data
17) gem install heroku / sudo gem install heroku
18) heroku create redmine-manoj --stack bamboo-ree-1.8.7 --remote redmine-manoj
19) find ./ -regex '.*~' -exec sudo rm {} \;
20) git init
21) git add .
22) git commit -m "your commit message"
23) git remote add redmine git@heroku.com:redmine-manoj.git
24) git push redmine master
25a) sudo gem install taps
25b) heroku db:push ( When promted to enter your repository name on heroku, enter the correct name from step 18, in this example it will be redmine-manoj ))
26) git clone https://github.com/tigrish/redmine_s3 vendor/plugins/redmine_s3
27) cp vendor/plugins/redmine_s3/config/s3.yml.example config/s3.yml
28) Enter your S3 credentials in config/s3.yml created in step 27
29) git add config/s3.yml vendor/plugins/redmine_s3/
30) git commit -m "Add s3 support"
31) git push redmine master
32) Test by creating a project and uploading files.
If you face any issues the author is very willing to help, If you think this post can be improved further go on and give feedback.
Thank you for your time :) 

Tuesday, November 29, 2011

Postgres error: psql: FATAL: Ident authentication failed for user “postgres”


I am in a hurry so i will just post the solution this time.
CAREFUL Ctrl+c and Ctrl+v users: Remove the angle brackets in names
———————————————————————————
***Restart the postgres server after finishing the changes***
user@desktop: /etc/init.d/postgresql-8.4 restart
———————————————————————————–
user@desktop: psql -Upostgres
FATAL:  Ident authentication failed for user “postgres”
user@desktop: emacs /etc/postgresql/8.4/main/pg_hba.conf
user@desktop: Replace the phrase Ident with trust
Additional details:
If it complains FATAL:  password authentication failed for user “
su root
su postgres
ALTER USER WITH PASSWORD ‘’;
Drop in your qs and i will edit the post a/c.