The Google summer code is on, check the link : http://code.google.com/soc/2008/ for more details.
Lot lot open code ..., lets see how much translates to useful code.
© yankandpaste®
Showing posts with label google. Show all posts
Showing posts with label google. Show all posts
Tuesday, March 25, 2008
HTC names Google phone 'Dream'
The mobile phone High Tech Computer (HTC) has been developing to run on the Android software from Google will be called "Dream," and it will have a large touchscreen and full QWERTY keypad, a person close to the situation said Thursday.
HTC may become the first handset maker in the world to put out a mobile phone developed around Android, but it faces stiff competition from Samsung, a separate source said. Samsung has stepped up its effort to put out a Google phone, the person said.
HTC's Google handset is just over 5 inches long and 3 inches wide, with a keypad underneath the screen that either slides out or swivels out. The aim of the keypad is for easy e-mail, note-taking, and writing Web addresses. Internet navigational controls are situated below the screen on the handset.
The handset will likely hit the market near the end of this year, the person said.
The company officially remained mum on the handset. "We cannot comment on this product," said Maggie Cheng, an HTC representative.
Last November, HTC became the first company to admit to developing a mobile phone based on Android, although Samsung, Motorola, and other handset developers are part of the group dedicated to furthering the software, the Open Handset Alliance.
Android, an open source software platform that includes an OS, is designed to take advantage of Internet services for mobility. The software could become a potent new rival to Windows Mobile and other handset operating systems. At the launch ceremony, Google announced that over 30 companies had joined the Open Handset Alliance.
from :http://www.infoworld.com/article/08/03/20/HTC-names-Google-phone-Dream_1.html
© yankandpaste®
HTC may become the first handset maker in the world to put out a mobile phone developed around Android, but it faces stiff competition from Samsung, a separate source said. Samsung has stepped up its effort to put out a Google phone, the person said.
HTC's Google handset is just over 5 inches long and 3 inches wide, with a keypad underneath the screen that either slides out or swivels out. The aim of the keypad is for easy e-mail, note-taking, and writing Web addresses. Internet navigational controls are situated below the screen on the handset.
The handset will likely hit the market near the end of this year, the person said.
The company officially remained mum on the handset. "We cannot comment on this product," said Maggie Cheng, an HTC representative.
Last November, HTC became the first company to admit to developing a mobile phone based on Android, although Samsung, Motorola, and other handset developers are part of the group dedicated to furthering the software, the Open Handset Alliance.
Android, an open source software platform that includes an OS, is designed to take advantage of Internet services for mobility. The software could become a potent new rival to Windows Mobile and other handset operating systems. At the launch ceremony, Google announced that over 30 companies had joined the Open Handset Alliance.
from :http://www.infoworld.com/article/08/03/20/HTC-names-Google-phone-Dream_1.html
© yankandpaste®
Tuesday, February 12, 2008
Nokia and Google - The next Team
Why ? Read headlines "Nokia and Google to Offer Google Search to Nokia Customers Worldwide". I know what you are going to ask - " You read about Google's Android vs Nokia " So do they compete ?
I believe most people may think so but look close :
Nokia took Trolltech ( the home of QT and KDE ). Google is a customer of QT. now Google is a customer of Nokia.
Second : Google's core is search and not Linux or Android.
Nokia's core is handsets not Maemo.
Android is only a platform for Google to reach Mobile.
Maemo is a platform for handset.
Once Nokia helps Google for more reach then why struggle with Android or Maemo ?
The new strategy is "all non core stuff be Open source".
WOW now, we have Android = Maemo = Linux.
Google happy because search reach, Nokia Happy because they can sell more handsets and
Linux - Android or Maemo does this make difference ? its all Linux man (not core stuff for their revenue stream - look at strategy ).
So expect now more with Nokia Google Team !!
I believe most people may think so but look close :
Nokia took Trolltech ( the home of QT and KDE ). Google is a customer of QT. now Google is a customer of Nokia.
Second : Google's core is search and not Linux or Android.
Nokia's core is handsets not Maemo.
Android is only a platform for Google to reach Mobile.
Maemo is a platform for handset.
Once Nokia helps Google for more reach then why struggle with Android or Maemo ?
The new strategy is "all non core stuff be Open source".
WOW now, we have Android = Maemo = Linux.
Google happy because search reach, Nokia Happy because they can sell more handsets and
Linux - Android or Maemo does this make difference ? its all Linux man (not core stuff for their revenue stream - look at strategy ).
So expect now more with Nokia Google Team !!
Tuesday, November 13, 2007
Google Jumpstarts Handset Developers With $10 Million Challenge
If announcing the Android mobile handset open source software development kit (SDK) wasn’t enough for Google (www.google.com) today, the company is putting up $10 million in cash prize money for Android developers.
The Android Developer Challenge is designed to support the developer community and spark innovation on the Android open mobile platform, announced last week in conjunction with the Open Handset Alliance. Cash prizes from $25,000 to $275,000, with applications picked by a panel of judges. Submissions for the first round of Challenge I will be accepted from January 2 through March 3, 2008, with the 50 most promising entries recognized by the end of March. Each of the first round entry winners will receive $25,000 awards to fund further development.
Round two of Challenge I is more complicated. The 50 entries get to apply again by May 1, 2008, with the top 10 getting $275,000 each, and the next 10 receiving $100,000. Awards for round two of Challenge one will be done by the end of May 2008. A Challenge II will launch after the first handsets built on Android become available in the second half of 2008.
A panel of technology and mobile experts selected from the Open Handset Alliance member organizations and the industry in general will judge all qualifying entries. Awards will be given to the developers whose applications leverage all that the Android platform has to offer in order. Finally, developers retain all intellectual property and other rights to their applications, so even if they don’t win an award, they can still make some money from their work.
By Doug Mohney
yankandpaste from :http://vonmag.com/editorial/web-exclusives/google-jumpstarts-handset-developers-with-10-million-challenge
Open handset alliance : http://www.openhandsetalliance.com/index.html
© yankandpaste®
The Android Developer Challenge is designed to support the developer community and spark innovation on the Android open mobile platform, announced last week in conjunction with the Open Handset Alliance. Cash prizes from $25,000 to $275,000, with applications picked by a panel of judges. Submissions for the first round of Challenge I will be accepted from January 2 through March 3, 2008, with the 50 most promising entries recognized by the end of March. Each of the first round entry winners will receive $25,000 awards to fund further development.
Round two of Challenge I is more complicated. The 50 entries get to apply again by May 1, 2008, with the top 10 getting $275,000 each, and the next 10 receiving $100,000. Awards for round two of Challenge one will be done by the end of May 2008. A Challenge II will launch after the first handsets built on Android become available in the second half of 2008.
A panel of technology and mobile experts selected from the Open Handset Alliance member organizations and the industry in general will judge all qualifying entries. Awards will be given to the developers whose applications leverage all that the Android platform has to offer in order. Finally, developers retain all intellectual property and other rights to their applications, so even if they don’t win an award, they can still make some money from their work.
By Doug Mohney
yankandpaste from :http://vonmag.com/editorial/web-exclusives/google-jumpstarts-handset-developers-with-10-million-challenge
Open handset alliance : http://www.openhandsetalliance.com/index.html
© yankandpaste®
Thursday, November 8, 2007
Google - It's Evil - with proof
yes, finally i am realizing the fact. I know there is lot questions why i think so ? or the best open source support company is that and you say its evil ?
lets looks on facts.
First of all, i accept its contributions to open source and i say its really valuable.
Now lets looks what google does,
First case : Google talk : yes its based on XMPP and the library they use (libjingle) is open source.
Fact : true but read the libjingle page :
"The current version of the libjingle code still uses the original internal protocol, which is slightly different from, and incompatible with, the Jingle specification. Nevertheless, it is close enough to Jingle that it is worthwhile learning the Jingle specifications. Similar "close but not identical" conditions exist for libjingle's audio content description (early version of Jingle Audio Content Description Format XEP-0167), ICE transport description (early version of Jingle Ice Transport XEP-0176), and raw UDP transport description (early version of Jingle Raw UDP transport description XEP-0177). Where this documentation refers to "Jingle" or one of its related extensions (in terms of how libjingle uses that protocol), it really refers to the original, internal protocol "
from http://code.google.com/apis/talk/libjingle/developer_guide.html
what this means ? The Old Microsoft evil : "Embrace, extend, and exterminate". Even google does not document their internal protocol. means giving free code is to spoil the standards and the whole work happened before.
accepting its evil ?
Second case : Look at the Android.
How many efforts on Linux mobile is existing ?
Please have a look :
http://tuxmobil.org/mobile_phone_linux_distributions.html
www.maemo.org
http://www.lipsforum.org/
Do we really need one more ?
This reminds me open source as APAC countries and the Non-open source as European and North American countries. In APAC, they fight each other always and they never think of a joint solution. They buy arms from the Eu and NA countries and spend the most part of their money which is supposed to be used for their development and finally make the EU and NA countries more rich. After effect :
The APAC are poor, undeveloped nations spending high on defense
EU and NA - Rich developed nations.
Google by applying the Evil factor it making the open source community more poor.
Do you now agree Google is Evil ?
© yankandpaste®
lets looks on facts.
First of all, i accept its contributions to open source and i say its really valuable.
Now lets looks what google does,
First case : Google talk : yes its based on XMPP and the library they use (libjingle) is open source.
Fact : true but read the libjingle page :
"The current version of the libjingle code still uses the original internal protocol, which is slightly different from, and incompatible with, the Jingle specification. Nevertheless, it is close enough to Jingle that it is worthwhile learning the Jingle specifications. Similar "close but not identical" conditions exist for libjingle's audio content description (early version of Jingle Audio Content Description Format XEP-0167), ICE transport description (early version of Jingle Ice Transport XEP-0176), and raw UDP transport description (early version of Jingle Raw UDP transport description XEP-0177). Where this documentation refers to "Jingle" or one of its related extensions (in terms of how libjingle uses that protocol), it really refers to the original, internal protocol "
from http://code.google.com/apis/talk/libjingle/developer_guide.html
what this means ? The Old Microsoft evil : "Embrace, extend, and exterminate". Even google does not document their internal protocol. means giving free code is to spoil the standards and the whole work happened before.
accepting its evil ?
Second case : Look at the Android.
How many efforts on Linux mobile is existing ?
Please have a look :
http://tuxmobil.org/mobile_phone_linux_distributions.html
www.maemo.org
http://www.lipsforum.org/
Do we really need one more ?
This reminds me open source as APAC countries and the Non-open source as European and North American countries. In APAC, they fight each other always and they never think of a joint solution. They buy arms from the Eu and NA countries and spend the most part of their money which is supposed to be used for their development and finally make the EU and NA countries more rich. After effect :
The APAC are poor, undeveloped nations spending high on defense
EU and NA - Rich developed nations.
Google by applying the Evil factor it making the open source community more poor.
Do you now agree Google is Evil ?
© yankandpaste®
Friday, November 2, 2007
Vancouver Transit
If you ever used translink.bc.ca for trip planning, i am sure u got angry with the slow response of the map. I tried it a couple of times and i was really mad of the response. The deadly slow response of the map site was a big problem.
Its nice to say now we can use Google transit for trip planning in Vancouver.
The link
Its fast :-)
© yankandpaste®
Its nice to say now we can use Google transit for trip planning in Vancouver.
The link
Its fast :-)
© yankandpaste®
Thursday, October 11, 2007
700MHz vs. WiMAX
While speculation runs rampant that Sprint may cut back or cancel its WiMAX deployment, AT&T (www.att.com) signaled it intends to do something in the RF “beachfront property” – 700 MHz spectrum.
Earlier this week, AT&T announced it would buy the largest current holder of 700 MHz licenses in the U.S., Aloha Partners. AT&T will pay $2.5 billion in cash for the licenses and will obtain 12 MHz of spectrum covering 196 million people. The licenses cover all of the top 10 markets in the US and 72 of the top 100 U.S. markets, with a focus on former UHF TV channels 54 and 59.
Aloha was in the process of conducting several market trials and all of the 700 MHz spectrum it has purchased will be available for use after the DTV transition date in February 2009; in some area UHF TV stations are still operating either on or near the spectrum that Aloha had the rights for.
The 700 MHz band is frequently described as “beachfront property” for its ability to propagate through buildings and other obstacles, as well as its longer range when compared to other spectrum in U.S. A major metropolitan area that would require many 2.5 GHz WiMAX transmission sites could be served by one or two 700 MHz sites, depending upon geography and transmission power.
Meanwhile, Sprint is being pressed by Wall Street investors and analysts to cut back or shut down its WiMAX rollout. The no-WiMAX-camp wants Sprint to focus on being a cellular company, but others point out that without new products, Sprint has little new to offer customers in a time where cellular phone sales have leveled off in the United States. Both Intel and Motorola have committed substantial resources to deploying WiMAX equipment and Intel has also invested substantial money into second-largest U.S. WiMAX provider Clearwire.
In the end, Sprint may have no other strategic choice than to continue with their WiMAX deployment because they may not have the resources necessary to engage in aggressive bidding in the final round of 700 MHz auctions scheduled in January 2008. Sprint could have a fully deployed 4G WiMAX network deployed, operational, and with paying customers in 2008, while the 700 MHz spectrum won’t be fully “clear” until the DTV switchover in 2009
© yankandpaste® from :
http://vonmag.com/editorial/web-exclusives/700mhz-vs-wimax
Orginal By Doug Mohney
Earlier this week, AT&T announced it would buy the largest current holder of 700 MHz licenses in the U.S., Aloha Partners. AT&T will pay $2.5 billion in cash for the licenses and will obtain 12 MHz of spectrum covering 196 million people. The licenses cover all of the top 10 markets in the US and 72 of the top 100 U.S. markets, with a focus on former UHF TV channels 54 and 59.
Aloha was in the process of conducting several market trials and all of the 700 MHz spectrum it has purchased will be available for use after the DTV transition date in February 2009; in some area UHF TV stations are still operating either on or near the spectrum that Aloha had the rights for.
The 700 MHz band is frequently described as “beachfront property” for its ability to propagate through buildings and other obstacles, as well as its longer range when compared to other spectrum in U.S. A major metropolitan area that would require many 2.5 GHz WiMAX transmission sites could be served by one or two 700 MHz sites, depending upon geography and transmission power.
Meanwhile, Sprint is being pressed by Wall Street investors and analysts to cut back or shut down its WiMAX rollout. The no-WiMAX-camp wants Sprint to focus on being a cellular company, but others point out that without new products, Sprint has little new to offer customers in a time where cellular phone sales have leveled off in the United States. Both Intel and Motorola have committed substantial resources to deploying WiMAX equipment and Intel has also invested substantial money into second-largest U.S. WiMAX provider Clearwire.
In the end, Sprint may have no other strategic choice than to continue with their WiMAX deployment because they may not have the resources necessary to engage in aggressive bidding in the final round of 700 MHz auctions scheduled in January 2008. Sprint could have a fully deployed 4G WiMAX network deployed, operational, and with paying customers in 2008, while the 700 MHz spectrum won’t be fully “clear” until the DTV switchover in 2009
© yankandpaste® from :
http://vonmag.com/editorial/web-exclusives/700mhz-vs-wimax
Orginal By Doug Mohney
Tuesday, September 4, 2007
gOOgle phOne
talks on google phone :-), says a five facts
The operating system will be a "mobile variant of Linux" capable of running Java Virtual Machines.
Second, all the on-board applications will be Java-based, including the music/video player.
Third, the user interface is based in Java, is "very responsive", features a "search box", and will be "typical of mobile phones."
Fourth, the web browser -- also in Java -- will have pan and browse.
Lastly, there was initially one prototype, but since then the mobile OS has been seen running on between 3 and 5 devices, all of which rock the QWERTY.
Our view : google phone will be a mobile device capable of surfing internet (may be WIFI or WIMAX or 1X or EVDO or GPRS ( we dont expect GPRS because of low speed).
It will not be the normal mobile phone and will be running a linux OS and capable of running all the google app including gmail, search, talk ( expect call out and callin from googletalk with a dial pad ).google apps, maps youtube videos and all other google applications. The main focus will be adv displays with content.
It's time of voip and web to common man, every body needs it.
© yankandpaste®
The operating system will be a "mobile variant of Linux" capable of running Java Virtual Machines.
Second, all the on-board applications will be Java-based, including the music/video player.
Third, the user interface is based in Java, is "very responsive", features a "search box", and will be "typical of mobile phones."
Fourth, the web browser -- also in Java -- will have pan and browse.
Lastly, there was initially one prototype, but since then the mobile OS has been seen running on between 3 and 5 devices, all of which rock the QWERTY.
Our view : google phone will be a mobile device capable of surfing internet (may be WIFI or WIMAX or 1X or EVDO or GPRS ( we dont expect GPRS because of low speed).
It will not be the normal mobile phone and will be running a linux OS and capable of running all the google app including gmail, search, talk ( expect call out and callin from googletalk with a dial pad ).google apps, maps youtube videos and all other google applications. The main focus will be adv displays with content.
It's time of voip and web to common man, every body needs it.
© yankandpaste®
Wednesday, June 27, 2007
Work Life Balance
was reading http://no2google.wordpress.com/2007/06/24/life-at-google-the-microsoftie-perspective/
The problem i see everywhere
Fresh out ppl :- time for proving them self - do do and prove ( a lot enthusiasm )
After 3 to 5 yrs :- I know the tech game , its all old tricks
After getting engaged/married :- life has a lot good things to enjoy, I am forced to sit to match with the fresh people ( confession time : i too made some body's life miserable )
After a Kid :- Life is beautiful , need money to live and pay the bills.
Kid growing :- good things , i have to prove now again, this is the time of achievement for my kid.
Late 40's - again confession
After 60's - life is beautiful again
May be i am wrong, don't know. But i used to see, a lot always does not understand the meaning of life and ends up in living for working than working for living.
May be let this be an eye opener.
tailpiece : Life cycle is repeating, ask your dad, he has gone through same.
© yankandpaste®
The problem i see everywhere
Fresh out ppl :- time for proving them self - do do and prove ( a lot enthusiasm )
After 3 to 5 yrs :- I know the tech game , its all old tricks
After getting engaged/married :- life has a lot good things to enjoy, I am forced to sit to match with the fresh people ( confession time : i too made some body's life miserable )
After a Kid :- Life is beautiful , need money to live and pay the bills.
Kid growing :- good things , i have to prove now again, this is the time of achievement for my kid.
Late 40's - again confession
After 60's - life is beautiful again
May be i am wrong, don't know. But i used to see, a lot always does not understand the meaning of life and ends up in living for working than working for living.
May be let this be an eye opener.
tailpiece : Life cycle is repeating, ask your dad, he has gone through same.
© yankandpaste®
Friday, June 22, 2007
Embrace, extend, and exterminate
Do you think "Embrace, extend, and exterminate" is microsoft specific ??
Embrace: Development of software substantially compatible with a competing product, or implementing a public standard.
Extend: Addition and promotion of features not supported by the competing product or part of the standard, creating interoperability problems for customers who try to remain neutral.
Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors that do not or cannot support Microsoft's extensions and create an obstacle to new competitors.
Interesting to find a document which describes the Voice mail call flow used by google talk.
http://www.scribd.com/doc/123347/Google-Talk-Voice-Mail-Call-flow
Looks this document is googletalk reverse eng:.As you know the libjingle protocol and Jingle are very similar, they are not the same, and are not interoperable.
tailpiece: corporate always carry their ego, and keen in their interests.They are not interoperable with public standards.
© yankandpaste®
Embrace: Development of software substantially compatible with a competing product, or implementing a public standard.
Extend: Addition and promotion of features not supported by the competing product or part of the standard, creating interoperability problems for customers who try to remain neutral.
Extinguish: When extensions become a de facto standard because of their dominant market share, they marginalize competitors that do not or cannot support Microsoft's extensions and create an obstacle to new competitors.
Interesting to find a document which describes the Voice mail call flow used by google talk.
http://www.scribd.com/doc/123347/Google-Talk-Voice-Mail-Call-flow
Looks this document is googletalk reverse eng:.As you know the libjingle protocol and Jingle are very similar, they are not the same, and are not interoperable.
tailpiece: corporate always carry their ego, and keen in their interests.They are not interoperable with public standards.
© yankandpaste®
Subscribe to:
Posts (Atom)
