Thursday, January 12, 2017

What are the hidden features of android smart phone?

Hidden Secret Android Codes
*#*
#778O#*#* = Factory Data Reset
*#*
#I472365#*#* = Quick GPS Test
*#*#0673#*#* OR *#*#0289#*#* = Audio Test
*#*#2664#*#* = Touch Screen Test
#’#273283*255*663282*#*#* = Backup Media Files
*#*#0283#*#* = Packet Loopback Test
*2767*3855# = Reinstalls The Phones Firmware & Format Your Phone *#*#232339#*#* OR *#*#526#*#* = wireless Lan Test
*#*# 1575#*#* = Different GPS Test
*#*#4636#*#*‘ = Complete Information About your Phone
*#*#2663#*#* = Touch Screen Version
*#*#232337#*# = Displays bluetooth Device Address
 *#*#4986*2650468#*#* = PDA, Phone. Hardware, RF Call Date
 *#*#44336#*#* = Displays Build Time
*#06# = Displays IMEI Number
 *#*#8255#*#* = Google Talk Service Monitoring
 *#*
#I I I I#*#* | *‘#*#2222#*#* = FTA Software Version FTA | Hardware /Version
 *#*#3264#*#* = Rom version
*#*
#23233I#‘*#* = bluetooth Test
*#*# 1234#’#’ = PDA and Phone Firmware Info
*#*#0*#*#*= LCD Display Test
*#*#0842#*#* Vibration and Backlight Test
*#*#0588#*#* = Proximity Sensor Test
*#*#232338#*#* = Wi-Fi Mac Address
*#*#7262626#*#*= Field Test
*#*#34971539#*#* = Camera Update
*#*#19732840#*#* = Enable Test Mode
 *#06# – IMEI number
*#0*# – Enter the service menu on newer phones like Galaxy S III
*#*#4636#*#* – Phone information, usage statistics and battery
 *#*#34971539#*#* – Detailed camera information
*#*#273282*255*663282*#*#* – Immediate backup of all media files
*#*#197328640#*#* – Enable test mode for service
*#*#232339#*#* – Wireless LAN tests
*#*#0842#*#* – Backlight/vibration test
*#*#2664#*#* – Test the touchscreen
*#*#1111#*#* – FTA software version (1234 in the same code will give PDA and firmware version)
*#12580*369# – Software and hardware info
*#9090# – Diagnostic configuration
*#872564# – USB logging control
*#9900# – System dump mode
*#301279# – HSDPA/HSUPA Control Menu
 *#7465625# – View phone lock status
*#*#7780#*#* – Reset the /data partition to factory state
*2767*3855# – Format device to factory state (will delete everything on phone)
##7764726 – Hidden service menu for Motorola Droid
*#*#7594#*#* – Enable direct powering down of device once this code is entered
*#*#273283*255*663282*#*#* – Make a quick backup of all the media files on your Android device
 ##778 (+call) – Show EPST menu These codes are specific to HTC devices only:
*#*#3424#*#* – Run HTC function test program
*#*#4636#*#* – Show HTC info menu
##8626337# – Run VOCODER
##33284# – Perform field test
*#*#8255#*#* – Launch Google Talk service monitor
 ##3424# – Run diagnostic mode
##3282# – Show EPST menu
##786# – Reverse Logistics Support

Wednesday, January 11, 2017

What is the best website very few people know about?


Its CybrHome!
CybrHome is the fastest way to explore the internet. CybrHome connects people to great websites. People discover new websites, apps, blogs and products everyday.
There is also a strong socialization component on the platform which makes it more usable and fun. You can like, rate, review, bookmark websites. Also, you can mark websites as used to tell the world. You can follow your friends and people to get to know what websites they like or have tried.
CybrHome is the one place for everything on the internet.
TOP FEATURES
Discover new websites, blogs and products everyday and review them
Explore topics, categories, our curated collections and top charts
Follow your friends and see their reviews and other activity
MORE FEATURES
 Submit new websites or edit the existing ones
Create, edit or delete topics and categories
Connect your social accounts and Invite your friends

There are lot of resources to help you experience CybrHome in a better way. Happy Exploring!

What is GitHub for a beginner and how to get started with it?

Hello,

I understand what you have been facing.
Lets start with a few basics shall we ?
Terminology :

Repository : A repository is a folder inside which you are going to store every piece of your code
Fork : Copying someones repository into your account is called forking.
Upstream : The guy or organisation which owns the code that you forked.

 


1. What is Git ?

Version Control System ( Keep reading and this will make sense towards the end ) .
Lets say you have a project you want to work on. 
Now you have 2 primary motives.
          (a)  To write some code
          (b)  To take up the project as a team , meaning that more than  one people are going to be responsible for writing the code.

So suppose you write a "Hello World!" program and then your friend/other developer decides that it should say "Hello, I am awesome"
instead of the original "Hello World!".

Even for this little piece of code, you will have a copy in your PC and your friend will have one in his PC. 
Lets say you change the code, now at this point your friend wouldn't know the changes you have made and vice versa.

This is where the Git magic comes.  
    1. Git lets you save your code online.
    2. Git will allow all the developers of a project to see what changes the  other one has made.
    3. It allows you to discuss issues in your code with other developers.
     And a lot more...

I think now you have a decent idea of what git is.

2. Getting Started 

First, Signup on Github.
-> Next, Download git for you OS from this page Git - Downloads
-> Next you go and do this   Create A Repo · GitHub Help

So now you have created a repository Online, and you have installed git on your PC. Until now they are not linked to each other. 

-> To do that follow the instructions under "setting up git" Set Up Git · GitHub Help

Setting Up is done !!

3. One step ahead

If you forked someones repository ( Forked , explained under terminology, scroll up ) then follow these instructions Fork A Repo · GitHub Help and then the commands below.

If you are the upstream yourself ,( ie. you are the guy who created the original repository ) then follow the instructions below

$ git clone <add the repository address here>
( Clones/copies everything from that repository to your local machine )
$ git add filename.extension
(this adds the file you want to change on the server)
$ git commit
(this commits your changes to the repository with an explanation message)
$ git push origin master
(this finally sends all your changes to the server. This is the final step of changing the code on your repository on the server)

You just started using github. Congratulations :D

Sunday, April 17, 2016

What are the best blogs on BigData?

I am looking for some good bigData or Data Science there are some blogs which I found really useful 

 Hadoop Tips - Rant about Big Data and related technologies.

Most of the articles and tutorials posted are of installing and learning hadoop 1.12 which is significantly a older version of hadoop.You can check this blog:
http://technichesblog.wordpress.com



You can learn about the installation procedure and how to run hadoop from this tutorial blog it is well written and there are some demo tutorials of running a hadoop map reduce job in python.
You can download virtual machines preinstalled with hadoop to quickstart learning hadoop but i would suggest learning installation too.  
Download Hortonworks or Cloudera Sandbox
Cloudera QuickStart VM
Hortonworks Sandbox

You can also go through the data analytics materials of google
Data Mining - Research at Google

you can also check youtube for Edureka tutorials.

Edureka Tutorials


Some basic blogs Like.

There are some best books to start learning Hadoop
1.Hadoop: The Definitive Guide
2.Hadoop Beginner's Guide
3.Hadoop For Dummies
Despite of this books you need to stay in touch with some of the blog posts on Hadoop in order to know the updates of BigData like Hadoop Weekly, BigData Weekly-here every week they will publish some best blogs on Hadoop.
You can also get best blogs on BigData technologies in the below link


Happy Hadooping

Wednesday, April 13, 2016

Oozie actions with Sqoop and Pig Joining

This blog is about executing a simple work flow which imports the User data from MySQL database using Sqoop.

The below DAG was generated by Oozie. The fork will spawn a Pig action (which cleans the data) and a Sqoop action (which imports the user data from a MySQL database) in parallel. Once the Pig and the Sqoop actions are done.



Here are the steps to define the work flow and then execute it. This is with the assumption that  MySQL, Oozie and Hadoop have been installed, configured and work properly

Create Tables in SQL

  • Customer Table
 CREATE TABLE customer ( c_id INT NOT NULL,  first_name VARCHAR(14) NOT NULL, Age INT,        gender VARCHAR(20)  NOT NULL,   city VARCHAR(14),         PRIMARY KEY (c_id));

  • Sales Table
 CREATE TABLE sales (
c_id int NOT NULL,
item_id int NOT NULL,
date DATE,
Status VARCHAR(20),
quantity INT
);
ALTER TABLE sales
ADD FOREIGN KEY (item_id)
REFERENCES inventory(item_id);
ALTER TABLE sales
ADD FOREIGN KEY (c_id)
REFERENCES customer(c_id);

  • Inventory Table
create table inventory(
item_id int NOT NULL,
p_name VARCHAR(30) NOT NULL,
price int NOT NULL,
UNIQUE KEY(p_name),
PRIMARY KEY (item_id)
);
Create Job.Properties File

nameNode=hdfs://localhost:9000
jobTracker=localhost:9001
queueName=default
examplesRoot=oozie-ingesting-example
examplesRootDir=/user/${user.name}/${examplesRoot}
oozie.use.system.libpath=true
oozie.wf.validate.ForkJoin=false
oozie.wf.application.path=${nameNode}/user/${user.name}/${examplesRoot}/apps/ING
 Create Workflow.xml File
<?xml version="1.0" encoding="UTF-8"?>
<workflow-app xmlns="uri:oozie:workflow:0.2" name="cs-wf-fork-join">
    <start to="fork-node"/>
    <fork name="fork-node">
        <path start="customer-node"/>
        <path start="sales-node"/>
        <path start="inventory-node"/> 
    </fork>
    <action name="customer-node">
        <sqoop xmlns="uri:oozie:sqoop-action:0.2">
            <job-tracker>${jobTracker}</job-tracker>
            <name-node>${nameNode}</name-node>
            <prepare>
                <delete path="${nameNode}/${examplesRootDir}/input-data/customer"/>
            </prepare>
            <configuration>
                <property>
                    <name>mapred.job.queue.name</name>
                    <value>${queueName}</value>
                </property>
            </configuration>
            <command>import --connect jdbc:mysql://localhost/final --table customer --target-dir ${examplesRootDir}/input-data/customer -m 1</command>
        </sqoop>
        <ok to="joining"/>
        <error to="fail"/>
    </action>
    <action name="sales-node">
        <sqoop xmlns="uri:oozie:sqoop-action:0.2">
            <job-tracker>${jobTracker}</job-tracker>
            <name-node>${nameNode}</name-node>
            <prepare>
                <delete path="${nameNode}/${examplesRootDir}/input-data/sales"/>
            </prepare>
            <configuration>
                <property>
                    <name>mapred.job.queue.name</name>
                    <value>${queueName}</value>
                </property>
            </configuration>
            <command>import --connect jdbc:mysql://localhost/final --table sales --target-dir ${examplesRootDir}/input-data/sales -m 1</command>
        </sqoop>
        <ok to="joining"/>
        <error to="fail"/>
    </action>
    <action name="inventory-node">
        <sqoop xmlns="uri:oozie:sqoop-action:0.2">
            <job-tracker>${jobTracker}</job-tracker>
            <name-node>${nameNode}</name-node>
            <prepare>
                <delete path="${nameNode}/${examplesRootDir}/input-data/inventory"/>
            </prepare>
            <configuration>
                <property>
                    <name>mapred.job.queue.name</name>
                    <value>${queueName}</value>
                </property>
            </configuration>
            <command>import --connect jdbc:mysql://localhost/final --table inventory --target-dir ${examplesRootDir}/input-data/inventory -m 1</command>
        </sqoop>
        <ok to="joining"/>
        <error to="fail"/>
    </action>
    <join name="joining" to="pig-node"/>
    <action name="pig-node">
        <pig>
            <job-tracker>${jobTracker}</job-tracker>
            <name-node>${nameNode}</name-node>
            <prepare>
                <delete path="${nameNode}${examplesRootDir}/intermediate"/>
            </prepare>
            <configuration>
                <property>
                    <name>mapred.job.queue.name</name>
                    <value>${queueName}</value>
                </property>
                <property>
                    <name>mapred.compress.map.output</name>
                    <value>true</value>
                </property>
            </configuration>
            <script>id.pig</script>
            <param>INPUT=${examplesRootDir}/input-data/clickstream</param>
            <param>OUTPUT=${examplesRootDir}/intermediate</param>
        </pig>
        <ok to="end"/>
        <error to="fail"/>
    </action>
    <kill name="fail">
        <message>Sqoop failed, error message[${wf:errorMessage(wf:lastErrorNode())}]</message>
    </kill>
    <end name="end"/>
</workflow-app>
  Create Id.pig File
customer = LOAD '/user/vm4learning/oozie-ingesting-example/input-data/customer/part-m-00000' USING PigStorage(',') AS (c_id:int,first_name:chararray,age:int,gender:chararray,city:chararray);
sales = LOAD '/user/vm4learning/oozie-ingesting-example/input-data/sales/part-m-00000' USING PigStorage(',') AS (c_id:int,item_id:int,date:chararray,status:chararray,quantity:int);
inventory = LOAD '/user/vm4learning/oozie-ingesting-example/input-data/inventory/part-m-00000' USING PigStorage(',') AS (item_id:int,p_name:chararray,price:int);
C1 = JOIN customer BY c_id, sales BY c_id;
C2 = JOIN C1 BY item_id , inventory BY item_id;
B = GROUP C2 BY city;
X = FOREACH B GENERATE group, SUM(C2.price);
STORE X into '$OUTPUT';

Copy the required libraries to HDFS

bin/hadoop fs -rmr /user/vm4learning/share/
bin/hadoop fs -put /home/vm4learning/Code/share/ /user/vm4learning/share/

Copy the data related files in HDFS

bin/hadoop fs -rmr /user/vm4learning/oozie-ingest-examples
bin/hadoop fs -put /home/vm4learning/Code/oozie-ingest-examples/ /user/vm4learning/oozie-ingest-examples

Start Oozie

bin/oozied.sh start
http://localhost:11000/oozie/

Submit an Oozie workflow

bin/oozie job -oozie http://localhost:11000/oozie -config /home/vm4learning/Code/oozie-ingest-examples/apps/cs/job.properties -run

The output should appear in the /user/vm4learning/oozie-ingest-examples/finaloutput folder in HDFS after the workflow is complete.

Submit an Oozie coordinator

Modify the start time and the end time in the /home/vm4learning/Code/oozie-ingest-examples/apps/scheduler/coordinator.xml. Make sure it is 1 hr back to the system time. The job will run every 10 minutes.

bin/oozie job -oozie http://localhost:11000/oozie -config /home/vm4learning/Code/oozie-ingest-examples/apps/scheduler/coordinator.properties -run

  • Initially the job will be in the `RUNNING` state and finally will reach the `SUCCEEDED` state. The progress of the work flow can be monitored from Oozie console at http://localhost:11000/oozie/.

  •  The output should appear as below in the 'oozie-ingesting-example/intermediate/part-r-00000' file in HDFS.




Wednesday, March 30, 2016

Which is the most difficult programming language to learn and why?

Xiaomi Launches 32-inch and 43-inch Mi TV 4A in India, Price Starting At ₹13,999

After launching the Mi TV 4 in India, Xiaomi has launched two new affordable smart TVs in India. The company has introduced a 43-inch ...