People had to wait since the announcement was made in july, it got leaked today. LG is planning to release official update in few weeks.
Instructions how to install the update are here.
Finally! After many months of struggling with Microlog4Android, the first official release is here. The core is the original Microlog code, but it is re-written to take full use Java SE features. For example, no Vectors are used. This means that the logging is faster than it was in Java ME. One important addition is the support for SLF4J. This should make it easy to migrate if necessary. This might also be an addition to future versions of Microlog. This way it should be easy to share code between Java ME and Android. The most important appenders are there as well.
Please download it from here. As always, any feedback and comments are welcome.
iPad the ideal market dominated by home computer table, but he is shaking every day, every hour because there was a competition-level financial and even marginally better part is that Samsung are attacking Galaxy Tab.
To better understand why the super computers of the Samsung panel can do that. Here we will explore the advantages that super product ownership:
I have been working with Android development for quite a while now. So I decided to do something quite different; iPhone development.
It is like groping in the dark. After many years with Java and garbage collection, it feels a little awkward to manage your memory by yourself. The first encounter with garbage collection in Java was really awesome. After a couple of years as a Java developer, you realized that the garbage collector is not the answer to all of your memory problems. But still, you are not forced to think about memory management on a daily basis. All of a sudden you need to think about memory management on a more regular basis.
Eclipse has been the main tool in my Java toolbox for many years now. One might argue that IntelliJ or NetBeans is a better tool, but I have used Eclipse. Switching from Eclipse to Xcode is not easy. I miss the fabulous re-factoring support in Eclipse. There are many other small issues, but I am slowly and constantly learning new keyboard shortcuts in Xcode. I guess that I could be a better Xcoder in a while. The interface builder in Xcode is an invaluable tool. It is very easy to get nice looking iPhone UIs. It is very nice not having to worry about getting your XML files right. Making a good looking UI on Android can be frustrating and cumbersome. Of course you can get nice UIs on Android, but I find it easier to create one on iPhone.
Last but not least, the markets are a little bit different. Android market is open. Appstore is a little bit more closed. There is no quality control when submitting to Android market. As a consequence there is a lot of really bad Android applications. It is hard to find what you are searching for on Android market. The search seems to be case sensitive. Not good. Usually I install applications that is recommended somewhere. In most cases, there is a QR code available that I scan with the Android barcode reader. Really nifty application that makes installation on Android simple. The applications in Appstore is controlled by Apple and it seems that they are of better quality than Android applications. It must be pointed out that there are many high quality Android applications, but they are harder to find. As a developer in Sweden it is not possible to get paid for your Android applications, but you can get paid for your iPhone apps. When will this problem be solved?
Another thing that seems to be missing in the iPhone world is open source projects. The Java and Android world is full of open source. However there seems to be good hope for the iPhone world. I found this this list of open source applications for iPhone.
Of course there are many more differences. These are the most apparent differences from my perspective. At the end of the day I am a mobile software developer. Switching to iPhone gives me a new perspective of my world. I think that is a good thing.
It was just a week ago that LG announced the Optimus One and the Optimus Chic, and it looks like the former might be headed to Verizon as the Vortex.
Sharp has announced two phones for Chinese market; these smartphones will run on Tapas OS, which is based on Android. Tapas was announced a week back only by x-Google China president Kai-Fu Lee.
First of these two Tapas based phones, Sharp SH828U comes with a 3.5” WVGA screen, a 5MP Camera with AF and flash, Bluetooth, WiFi, microSD slot, and powered by a 600MHz Qualcomm MSM7227 processor.
While the other one – Sharp SH8118U will come with a smaller 3.2” inch touch screen, and same 600MHz Qualcomm MSM7227 processor with other basic specs.
Sharp SH828U will be available in China later this October at around $475 USD and Sharp SH8118U will sell for $335 USD around the same time.
Samsung Galaxy S Femme – The Pink Galaxy S for Women today landed in Taiwan. Well, it is not just a phone, it is a full deal. Samsung and AVEDA, a US based cosmetic company have started selling Galaxy S Femme pack, which includes a complete AVEDA traveling kit including several creams and cosmetics from the manufacturer, a travel kit voucher as well as a 4GB microSD card that included an AVEDA made software in order to help and advise women on which treatment their need to keep both their skin and hair young and beautiful along with a Pink Galaxy S phone.
China Telecom subscribers will soon have two cheap Android phones to buy. China Telecom has ordered 300,000 inexpensive Android phones from Huawei and ZTE to tap the growing demand of smartphones.
While, ZTE’s entry model smartphone N600 will constitute 80 percent of those handsets, the remaining 20 percent will be Huawei C8500 Android phones.
Both the Android 2.1 powered phones will be priced below 1,000 yuan ($148.9). Talking about the specs, Huawei C8500 is powered by 528MHz Qualcomm MSM7625 chipset, a 2.8 inch 320×240 capacitive touchscreen, 256MB RAM, 512MB ROM, a 3.2-megapixel camera, and a 1050 mAh battery.
ZTE N600 comes with a 600 MHz Qualcomm MSM7227 chip, a 2.8 inches 320×240 capacitive touchscreen, 256MB RAM, 256MB ROM, a 3-megapixel camera, and a 1000 mAh battery.
Pretty decent specs for $150 phones, both these smartphone will hit Chinese market early October during China’s National Day holiday that begins from 1st October.
It has been just over a month since we have first heard of the HTC Lexikon. It’s supposed specs were “pretty” impressive: MSM7630 Snapdragon processor, 512MB RAM, 4GB internal storage, 5-megapixel camera all inside this 3.8-inch display QWERTY slider. In standards of the next-gen phones we are seeing now, it’s nothing too ground breaking. However, it may just be coming to Verizon making it one of their best Android devices.
Another point of interest is that the ROM may have been leaked. The same website that provided us with the image above is also hosting the ROM for download. 911HTC has been a reliable source for rumors in the past so it looks like this may be the actual Lexikon ROM.
Samsung’s much hyped Galaxy Tab hasn’t even been released yet and people are already speculating on the future of the device. Many are reporting that the next update for the current Tab or the next model will be sporting Chrome OS instead of Android 2.2. It all depends on what Google has in store for Android 3.0 (Gingerbread) if it’s more tablet friendly then it would be the next update. However, if it is still not built with a tablet in mind, like Google has stated was the case for 2.2, then Samsung may consider Chrome OS.
What would Chrome OS mean for the Samsung Tab? First off, Users will be fronted with a very different experience. They will exchange a mobile phone like OS for one that feels more like an extension of a computer operating system. Chrome OS will also focus more on web based applications similar to Google Docs and stray away from downloadable apps.
In the end the preference will come to the end user. Right now the Galaxy Tab is capable of running Google’s upcoming Chrome OS. When it’s released it will be possible to replace the operating system with Chrome, but for the average user it may require professional help. Only time will tell to see the future of Chrome OS, Google 3.0 and the Android platform but we will be sure to let you know of any developments as they happen.
Source: http://www.feelandroid.com/2010/09/chrome-os-to-replace-android-on-samsung-galaxy-tab/
Editing Google Docs on a mobile device is not impossible, but it certainly is not a favourable way of working these days. Well that is going to change very soon as Google today announced their plans regarding Google Documents and the mobile experience.
The announcement was made during an event in Paris called Google Atmosphere (an event dedicated to cloud computing):
Second, today we demonstrated new mobile editing capabilities for Google Docs on the Android platform and the iPad. In the next few weeks, co-workers around the world will soon be able to co-edit files simultaneously from an even wider array of devices.On top of this announcement Google released a new verification system for business premium users of Google apps and also showed off some usage statistics. Apparently there are now 3 million businesses, and over 30 million users within businesses, schools, and organisations worldwide that depend on Google’s tools.
via [Adobe]
Today, a Security Bulletin has been posted to address a critical security issue (CVE-2010-2884) in Adobe Flash Player. This Security Bulletin affects Adobe Flash Player 10.1.82.76 and earlier versions for Windows, Macintosh, Linux, and Solaris, and Adobe Flash Player 10.1.92.10 for Android. Adobe recommends users apply the update for their product installation. This addresses the issue first mentioned in Security Advisory APSA10-03.
$
We are pushing out a series of updates via Android Market for TalkBack and the Eyes-Free Shell. Here is a brief overview of end-user visible changes.
Going by the principle of things should just work as expected , we have long resisted giving in to having a complex set of user preference settings for TalkBack and friends --- in my experience, if you introduce such a settings menu early on, we as software engineers tend to punt on all complex decisions by turning each question into a complex user-facing dialog. That said, it is now time to gradually introduce end-user settings for some aspects of the various accessibility tools.
Welcome new application AccessibilityPreferences to Android. What this application does:
TalkBack installs its user preferences under this tool. You can tweak a number of settings that affect TalkBack behavior including:
Over time, we'll add more settings here as appropriate --- but expect us to be conservative with respect to how many settings show up.
Here is a summary of updates to the Eyes-Free Shell:
Here is a summary of changes to TalkBack:
In addition, TalkBack introduces the ability to add application-specific plugins --- expect to see more advancement here in future releases.
If you're a developer of an AccessibilityService, you need to:
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.accessibilityservice.SERVICE_SETTINGS" />
</intent-filter>
Share And Enjoy,
Instead of changing the Rom to set proxy as I mentioned in the first post here is the application to make the proxy work in your Android phones.Still you have to root the phone.Rooting can be done using a single click as described in the tutorial in my previous post.