How to Install Android 4.2.1 Jelly Bean on Galaxy Nexus I9250 with JPO40D Xylon Custom ROM
Step 2 - Connect and mount your Galaxy Nexus USB mass storage on your computer with original USB cable.
Step 3 - Copy and paste the Xylon ROM and Google Apps zip files to the root folder on your phone’s SD card.
Step 4 - Then power off your phone and boot into Bootloader mode.
Step 5 - Switch on the phone while pressing and holding Volume Up, Volume Down and Power buttons together until the device enters Bootloader mode
Step 6 - Follow the navigational instructions on screen. Now, select Bootloader and progress into Recovery.
Step 7 - In ClockworkMod recovery (CWM), wipe data first. Then navigate to Flash zip from SD card option and hit Power button to select it.
Step 8 - Tap the Power button again and click Choose zip from sdcard.
Step 9 - Use volume keys to navigate to Xylon ROM zip file and select it by tapping Power button. Confirm the ROM installation on next screen and the installation procedure will begin.
NOTE: Repeat this step for installing Google Apps as well.
Step 10 - Once Google Apps is installed, hit Go Back and reboot the phone by tapping Reboot System Now in the Recovery Menu. The phone will reboot and the first boot might take about 5 minutes to complete. So, leave it alone.
Android 4.2.1 JPO40D Xylon custom Jelly Bean ROM is now installed on your Galaxy Nexus I9250. Go to Settings About Phone to verify the firmware version installed.
[Source: Team Android]
To report problems or to leave feedback about this article, e-mail:
To contact the editor, e-mail:
The custom firmware, Slim Bean Beta 1 ROM, also brings a number of customization features to Galaxy S3. Apart from that, the Android 4.2.1 Jelly Bean exclusive features include multi-user support, gesture typing, new quick settings option, lock-screen widget, new camera app, photo sphere, improved Google Now, new daydream feature, miracast display and many more, according to Android Jinn.
The report states that the custom ROM in question is known for low file size and fast speedy nature. However, it is still under development and therefore the users might face some issues and bugs. All the issues are expected to be fixed as development progresses.
Here is a list of key features of the Slim Bean Android 4.2.1 Jelly Bean Beta 1:
- Dotted Battery Mod and color picker
- Battery bar mod
- Notification Background customization
- Notification row transparency
- Quick Settings option
- Network mode tile
- Profile Tile
- Dismiss on toggle
- Updated APN + SPN
- Wi-Fi name in notification drawer
- Power widget
- Device Parts
- Performance Settings (need to tap build number a few times)
- Cursor control using volume keys
- Disable full screen keyboard
- Alternate app chooser
- Clock styles and color chooser
- ADB over Wi-Fi
- Camera power shutter mod
- Wi-Fi country specific settings
- Notification IME selector
- SMS quick reply mark as read from notification
- All MMS features
- All Contacts feature
Below is a tutorial showing how to install Android 4.2.1 Jelly Bean on Sprint Samsung Galaxy S3 (SPH-L710) using Slim Bean Beta 1 ROM. Before going ahead, take a look at the preciosities that need to be aware of.
- Backup your data.
- The device must have at least 80 percent battery power.
- USB driver must be installed for Samsung Galaxy S3 (SPH-L710) in your PC.
- USB Debugging must be enabled.
- Backup your EFS Folder.
- Flashing this ROM on Galaxy S3 L710 will increase your binary counter.
- Don’t skip Nandroid backup as it’s very helpful if this custom ROM doesn’t work the way you wanted.
The users should also keep in mind that this tutorial is only for Sprint variant of the Samsung Galaxy S3. Therefore, it should not be implemented on any other Android device. In addition, IBTimes cannot be held responsible if anything goes wrong. The users should proceed at their own risk.
1. Slim Bean Beta 1 4.2.1 Jelly Bean ROM For Galaxy S3 L710 [Filename: Slim-4.2.1.Beta.1-d2spr-20121222-0812-OFFICIAL.zip]
2. Google Apps [Filename: Slim_Gapps.zip]
How To Install
Step 1: Connect your Sprint Galaxy S3 to PC using USB cable.
Step 2: Copy downloaded files to the SD card of your phone without extracting them.
Step 3: Disconnect USB and turn off your phone.
Step 4: Boot into ClockworkMod recovery in your Galaxy S3 by pressing and holding the Volume Up, Power and Home buttons together until the Samsung logo appears on screen.
Step 5: Leave the buttons and hold then again. You will get ClockworkMod recovery screen soon. Now browse between options in recovery using Volume keys while using Power key to select an option.
Step 6: Carry out a Nandroid backup of your existing ROM by selecting Backup and Restore, then on the next screen, selecting Backup again. Once back up is complete, go back to the main recovery menu.
Step 7: Now perform the data wiping task. To do so, select wipe data/factory reset, then select Yes on next screen to confirm your action. Wait for a few minutes till the data wipe is completed.
Step 8: Select install zip from SD card, then select choose zip from SD card. After that, locate the Slim-4.2.1.Beta.1-d2spr-20121222-0812-OFFICIAL.zip file and select it by pressing Power button (tap on it if using touch version).
Confirm installation by selecting Yes – Install _____.zip on the next screen. The ROM installation will begin.
Step 9: Once the ROM installation is done, repeat step 8 but choose the Slim_Gapps.zip file instead of ROM zip to install the Google apps package.
Step 10: After the installation is completed, go back to the main recovery menu and select reboot system now to reboot the phone and boot up into customized Android 4.2.1 Jelly Bean ROM Slim Bean Beta 1. The first boot will take time.
[Source: Android Jinn]
SMS quick reply and marks as read from notification
All MMS features
All contact features
To learn more about bugs and device-specific issues, head to the source page.
Galaxy Note users who wish to upgrade their devices with SlimBean Android 4.2.1 Jelly Bean custom ROM may follow the tutorial below. IBTimes UK reminds its readers that it will not be responsible for any damage to the device. Users are advised to verify the model number of their devices since the Jelly Bean ROM works only on the Samsung Galaxy Note N7000 but not on any other variant.
1) Download USB Drivers for Samsung Galaxy Note and enable USB Debugging Mode.
2) Back up all your important data.
3) Ensure the device is rooted and ClockworkMod (CWM) Recovery is installed.
4) Ensure the battery of the device has more than 80 per cent of charge.
Steps to install SlimBean Android 4.2.1 Jelly Bean ROM on Galaxy Note N7000
1) Download Slim Bean Android 4.2.1 Jelly Bean ROM on Galaxy Note N7000
2) Download Google Apps package
3) Connect your Galaxy Note to the computer using the USB cable and copy both the downloaded zip files to the SD card of your phone
[Note: Do not extract any file.]
4) Disconnect the phone from the computer. Then boot into ClockworkMod recovery by pressing and holding Volume Up, Power and Home buttons together until the Samsung logo appears. Then leave all three buttons for half a second and hold them again. You should see CWM Recovery soon. Alternatively, you may try for Recovery mode without key combination
5) In CWM Recovery, perform a Nandroid backup of your existing ROM which you can restore later. To do so select Backup and Restore; then select Backup again on the next screen. Return to the main recovery menu once the backup is completed
6) Now perform data wiping by selecting Wipe Data/factory Reset then select Yes on the next screen to confirm the action. Wait until the data wipe is complete
7) Using the Power button select ‘Install zip from SD card’; then again press the Power button to select ‘Choose zip from SD card’ and locate the Slim Jelly Bean ROM zip file which you have copied to the SD card. Select it using the Power button and confirm installation by selecting Yes on the next screen
After the ROM is installed, repeat the same procedure to flash the Google Apps package
9) Once the installation process is complete, return to the main recovery menu and select ‘Reboot System Now’ to reboot the phone and boot up into the customised Jelly Bean ROM. The first boot will take some time
Note: If you wish to return to your previous ROM, then boot into recovery, select Backup and Restore and restore your previous ROM by selecting it from the list.
SlimBean beat 1 custom ROM featuring Android 4.2.1 is now installed and running on your Samsung Galaxy Note N7000. Navigate to Settings About Phone to verify the software version running on your device.
[Source: Android Jinn]
To report problems or to leave feedback about this article, e-mail:
To contact the editor, e-mail:
1) Download USB Drivers for Samsung Galaxy Note 10.1 and enable USB Debugging mode.
2) Back up all your important data before proceeding.
3) Ensure the Galaxy Note is rooted and ClockworkMod Recovery is installed.
4) Ensure the device is factory unlocked.
5) The battery of the device should have more than 80 per cent charge.
Steps to install CM10.1 Android 4.2.1 Jelly Bean on Galaxy Note 10.1
2) Download Google Apps package
3) Connect the Galaxy Note to the computer using USB cable and transfer both the downloaded zip files to the SD card of your device
4) Turn off the Note. Now reboot into recovery mode by pressing and holding Volume Up and Power buttons together until the screen turns on. Then leave the Power button and continue holding the Volume Up button until you enter CWM Recovery
5) In recovery mode, perform a Nandroid back-up of your existing ROM, which you can restore later. To do so select ‘Backup and Restore’ and select Backup again. Once the action is completed, return to the main recovery menu
6) Perform data wiping by selecting Wipe Data/Factory Reset and confirm the action on the next screen. Wait until the data wipe is complete and return to the main recovery menu
7) Using the Power button, select ‘Install zip from SD card’ and again press the Power button to select ‘Choose zip from SD card’ and locate the Jelly Bean ROM. Select it using the Power button and confirm installation on the next screen
Once the ROM is installed, repeat the same procedure to install Google Apps package
9) Once the installation is completed return to the main recovery menu and select ‘Reboot System now’ in order to reboot the device and boot up into the customised ROM
CM10.1 based on Android 4.2.1 is now installed and running on your Samsung Galaxy Note 10.1 N8000. Navigate to Settings About Phone to verify the software running on your device.
[Source: Android Egis]
To report problems or to leave feedback about this article, e-mail:
To contact the editor, e-mail:
Step 1: Download the latest version of Liquidsmooth Jelly Bean ROM
Step 3: Copy both the ROM and Google Apps (GApps) zip files to the root folder on your phone’s SD card.
Step 4: Power off your phone and boot into bootloader mode. To do so, press and hold Volume down and Power buttons together until the display comes on. NOTE: Use Volume buttons to navigate and Power button to select an option in Recovery.
Step 5: Browse to the Recovery mode option and select it using the Power button to boot into CWM Recovery.
Step 6: Take a NANDroid Backup of your existing ROM so that you can restore it later if something goes wrong with the new ROM. To take a backup, select Backup and Restore and then hit Backup again. Return to main recovery menu once backup is done.
Step 7: Choose wipe data/factory reset and click Yes to confirm. Wait for the data wipe process to complete (it will wipe only installed apps and settings, but the files on the SD card will be left intact).
Step 8: Choose Install zip from SD card and then click Choose Zip from SD card. Browse to the location of ROM file you copied earlier and select it. Click Yes to confirm ROM installation on next screen.
Step 9: Once ROM is installed, click Choose Zip from SD card again, but select GApps file to install Google Apps as well.
Step 10: After GApps is installed, return to the main recovery menu and hit Reboot System Now to reboot the phone into Liquidsmooth ROM. The first boot may take about 5 to 7 minutes. So, leave it alone.
Updating to Newer Versions of the ROM:
The ROM will receive periodic updates as part of development progress. So, to install newer versions, download the latest ROM, copy it to the device, reboot to recovery, repeat step 8 to install the update and then reboot the phone.
NOTE: It is not necessary to reinstall Google Apps or wipe data once again while updating to a newer version, as it is required only when installing the ROM for first time.
Liquidsmooth Jelly Bean ROM is now successfully installed on your Nexus 4.
[Source: The Android Soul]
To report problems or to leave feedback about this article, e-mail:
To contact the editor, e-mail:
A year after unveiling Chromebooks to the world, Google and Samsung today are announcing two new devices, including the first “Chromebox” desktop PC. Google is also rolling out several major software improvements, including a new window manager for Chrome OS, better trackpad support, upgrades to a remote desktop access tool, and offline editing for Google Docs.
The new Chromebook has a slicker, more attractive design than previous models, and both the new laptop and desktop take a big step forward in memory and CPU. Instead of Intel Atom processors, Samsung’s latest Chrome computers use Sandy Bridge-based Intel Celeron CPUs, and double the RAM to 4GB. Both devices will be on sale online today and in Best Buy stores soon.
The Samsung Chromebook Series 5 550 has a 12.1″ display with resolution of 1280×800, starts up in about 7 seconds, weighs 3.3 pounds, is rated for six hours of battery life, and costs $449 for a WiFi-only edition and $549 for one with WiFi and 3G cellular access. Google says it’s about 2.5 times faster than last year’s models, while the Samsung Chromebox Series 3 will be 3.5 times faster. The Chromebox, which costs $329 and has roughly the same size and shape as an Apple Mac Mini, runs faster because with battery life not being a concern, it can use a higher-wattage version of the Intel Celeron processors.
The new Samsung Chromebook runs a dual-core Intel Celeron Processor 867 at 1.3GHz, compared to last year’s Chromebook which ran a dual-core Intel Atom N570 at 1.66GHz. The Celeron architecture is more advanced, and the laptop certainly seems zippy in our limited testing so far. We’ll have more to say on performance in an upcoming article, which will include some benchmarking. The Chromebox has an Intel Celeron B840 running at 1.9GHz.
The Chromebox has a good number of ports, including six USB 2.0 ports and two DisplayPort++ slots that are compatible with HDMI, DVI, and VGA. Chrome OS is optimized for screens up to 30 inches and can support multiple monitors, Sengupta said.
Oddly, the Chromebox has no SD card reader, but USB devices that can read SD cards are common anyway. The new Chromebook has two USB 2.0 ports, DisplayPort++ output, and an SD card reader. Both the laptop and desktop have a Gigabit Ethernet port. Because the laptop is quite thin, the Ethernet port opens up and juts out a bit to fit the cable.
While the computers are cheaper than any Mac and many Windows PCs, we still think they’re a bit pricey for devices designed to run just one application: the Chrome Web browser. But Chrome devices are fast, and extraordinarily easy to use. Google and its hardware partners haven’t revealed sales figures, and significant market share doesn’t seem to be forthcoming any time soon. However, Google is offering support packages to businesses and education customers ($150 for businesses, $30 for schools, in addition to the device cost) and says the Chromebooks are proving quite popular in educational settings.
Acer and Samsung both released Chromebooks a year ago, but Samsung is the only hardware maker doing so this time around. However, Chrome OS Director Caesar Sengupta says Google is working closely with Intel and expects to have “a few more OEMs shipping later this year.”
Samsung has done well in delivering strong hardware, with a very responsive trackpad. But ultimately, software improvements are needed to give Google any shot at gaining significant market share from Windows and Mac OS X. New features being rolled out today and over the new few weeks provide a good start.
Google used to allow offline editing of Google Docs through a Google Gears extension, but killed the project with the promise of delivering offline functionality natively through the browser. Offline viewing capabilities were brought back last September and editing is coming sometime in June, Sengupta told Ars. Any changes made while offline will sync with the Google server once a user gains an Internet connection.
“Offline viewing has existed for a while, but the Docs team is readying the release of offline editing,” Sengupta said. “We are using this internally at Google right now and we are going to gradually migrate users over the next several weeks.”
Offline editing of Docs will be available in all versions of the Chrome browser, not just the one for Chrome OS devices. No other browsers are supported just yet, but Sengupta didn’t rule it out as long as competing browsers use similar HTML5 technology. Google is using IndexedDB to store files locally when an Internet connection is severed.
Two other additions help on the offline documents and storage fronts. New viewing capabilities allow opening of Microsoft Word, Excel, and PowerPoint files in a browser tab, online or offline. The files can be viewed without Google Docs, although editing requires Docs. Chrome OS is also being integrated with Google Drive, the new cloud storage service with 5GB of free storage. Drive integration is built into the Chrome OS development release, and will hit the stable channel in mid-to-late June, Sengupta said. Because Chromebooks contain 16GB solid-state disk capacity, a user’s Drive files will be cached locally.
We recently posted an in-depth examination of Google’s new Aura interface for Chrome OS, a window manager that makes Chromebooks act a lot more like the Windows, Mac, and Linux computers people are used to. When Chromebooks first came out last year, they supported viewing of only one browser tab at a time so you couldn’t, for example, type in a Google Doc and view a separate webpage at the same time. Simultaneous viewing of multiple browser windows was added within a few months, and the more robust Aura interface hit the Chrome OS developer channel in April of this year.
Today, Aura becomes the standard interface for Chrome OS as part of an operating system update. For the first time, this provides Chrome OS a graphical user interface that exists outside of the browser, although it’s still very Web-centric. There’s an icon for a file manager, but for the most part the “applications” listed are links to websites. Users can still fill the whole screen with the Chrome browser simply by clicking a little box at the top right of the screen.
Although Aura is pleasing to the eye, it doesn’t change the fact that Chrome OS’s biggest limitation is still its limited usefulness when a user lacks an Internet connection.
As mentioned earlier, the Samsung Chromebook has a very responsive trackpad, easily recognizing tap-to-click, scrolling, and the two-finger click. We give Samsung much of the credit for this as its trackpads are generally good regardless of which OS is running, but Google says it has improved trackpad support on the software side as well.
“Our trackpad last year was a bit fiddly,” Sengupta said. With many Googlers using the Chromebooks internally, Google set out to analyze the problems that can be caused by differences in people’s thumbs and fingers and how they click. Google even used robotic thumbs and fingers to duplicate unique digits.
“Some people have thumbs that have a waist in the middle. They’re used to resting it on the trackpad and so they click with that and it looks like two different points,” Sengupta said. “We now know more about thumbs than we ever cared to know. We realize human beings come in different shapes and sizes.”
Improvements to trackpad support made their way into the open source Chromium OS as a new component.
One last software improvement announced by Google today is an upgrade to Chrome Remote Desktop, which we tested out last October and provides a remote desktop connection between two computers running the Chrome browser. This would let a Chromebook user access any Windows, Mac, or Linux machine, but it required a person on each computer to type in an access code, limiting its use for truly “remote” scenarios. Google says it is now launching a persistent connection, allowing a user to set up the remote desktop tool only once and have it be accessible from then on.
According to Google, more than 500 schools have purchased Chromebooks and are using them in curriculum. Newly announced customers include Dillard’s, which will deploy hundreds of Chromeboxes to retail stores; California libraries, which will use 1,000 new Chromebooks for patron checkout purposes; Mollen Clinics, which will deploy 4,500 Chrome devices to mobile immunization clinics at Wal-Mart and Sam’s Club stores; and Kaplan, which is using them in a New York City call center.
Google is hoping for a bigger push into businesses and schools with its $150 per-device support charge for businesses and $30 per-device for schools, which includes 24/7 phone support, a management console, and a hardware warranty. The support cost is in addition to the regular retail price of the devices. Google used to sell support to businesses and schools with a monthly subscription model. The new pricing is a one-time up-front cost with support for the lifetime of the device.
We don’t know many regular consumers buying Chromebooks, but Google has a compelling pitch for businesses with employees that use only Web applications, or are satisfied with accessing Windows programs through Citrix’s virtualization software. Call centers, back offices, retail stores, and other “non-mobile” scenarios are good for the Chromebook and Chromebox, said Rajen Sheth, Chrome for Business Group Product Manager.
Google has further optimized Chrome OS for businesses, allowing the devices to automatically configure applications, network settings, WiFi, VPN access, and organizational policies, Sheth said. Sheth believes businesses can take a Chromebook from a delivery truck and hand it directly to an end user without any IT involvement.
“To do that with a PC is almost impossible,” he said.
Article was updated to correct business and education pricing.
With hundreds of Android devices on the market, many users are curious about how they can root their phones to have full control of their phone. If you’re thinking about rooting your phone, let’s see how you can benefit from it, the pros and cons and even how you can do it for the phone you have now.
What is rooting?
Rooting is a procedure where the user can gain access to the operating system of the phone. For a second, picture your phone as a desktop computer. If you were to log on your desktop computer as a guest, you wouldn’t have a lot of options, would you? When you root an Android device, this is going to give you the freedom of changing anything in the system that the default system generally doesn’t allow you to do. In desktop terms, you’ll now gain access as an administrator user. Rooting is very similar to the iPhone jailbreaking situation.
Will I lose data and apps?
One of the biggest concerns that Android users have is if data and apps will be destroyed. Thankfully, all of your apps will stay intact. In fact, you probably won’t see much of a difference since the rooting process will just shift a few files around. Yes, serious problems can happen, but it’s very rare.
Why should I root?
Rooting is a great way to have more freedom with your phone. Wouldn’t it be cool to change the colors on your wallpaper? What if you could download apps that make your Android faster? By pushing the restrictive permissions aside, you’ll have full control of your phone.
The Pros of Rooting
Freedom – While the Android already gives you freedom to download just about any app on the Android Marketplace, rooting will take you one step further giving you complete control. With a rooted phone, you’ll be able to disable permissions, use FTP clients, customize your home screen, over clock the CPU and tether your phone to treat it like a hotspot.
Backing Up Data – There are many great apps that work solely with rooted phones. One of the biggest reasons that people root is based on the backup functions. With certain apps such as Titanium Backup, users can click a button and backup their data from anywhere.
Moving Apps – The problem with a standard Android phone is that when apps are downloaded, it can take up a lot of internal memory. With a rooted phone, users can have move apps to the SD card and not have them eat up that memory.
Carriers – Don’t want to be locked in with the cell phone carrier that you have now? Rooting can give you the freedom of choosing any cell phone carrier that you want.
The Cons of Rooting
Warranty – One of the main reasons that people shy away from rooting their Android is because it can potentially void your service provider warranty. Keep in mind that most rooting processes can be reverted though if this were to happen. In certain circumstances, there have been reports where users have damaged their data due to rooting improperly. As long as you follow directions step-by-step, there’s no reason you shouldn’t have this kind of problem.
Data Loss – As touched upon earlier, you can risk the chance of losing all of your data and apps. To prevent this from happening, just make sure that you backup all of your data ahead of time. That way, if the worst case scenario does happen, you can restore all of your previous settings.
Buggy – Again, this is not common but some roots can cause the phone to be buggy and glitchy. This will solely depend upon what route you’ll take when rooting your phone.
How to Root
Rooting can be done through several applications that run directly on your desktop. One application in particular named SuperOneClick is by far the most popular application used by root junkies. This application can be run either on Windows or Linux operating systems. There are other software programs that can be used aside from SuperOneClick such as Unlock Root, Universal Androot and Z4Root. No matter what software you use, most work the same way with the instructions noted below.
Now, before we start with this process, there are some models that don’t work with this software. The phones that don’t work are listed below:
If your phone isn’t on that list, you can follow the directions listed below to successfully root your phone. If your phone is on the list, you’ll have to take extra steps. The best way to find these steps is by searching your model plus the word root via a search engine query. Be forewarned that you should do this at your own risk!
Your Android phone should successfully be rooted by now if you followed the prompts above. Now that your Android has been rooted, it’s recommended that you download apps so that you can successfully play around with your phone and files. Listed below are some apps that most download in order to manage files, execute scripts and manage apps. It’s highly recommended that you download the apps listed or find an alternative that performs the same job.
When rooting your phone, just make sure that you do your homework first. You’ll want to make sure that it is something that you’ll truly enjoy. Remember that even if you don’t like what you’re seeing, you can always change your phone back to the way it was. If you’re having a hard time with the instructions working above, or you’re finding that your phone doesn’t root, it probably means that your phone isn’t meant for that software package. Instead, it’s recommended that you search your exact phone model online to see exactly how you can root your phone. No matter what Android device you own, you can root it some way or another.
Article source: http://thedroidguy.com/2012/05/how-to-root-android-phones/
Palo Alto, CA (PRWEB) May 11, 2012
Originally set to launch August 2010, SOCIAL DASHBOARD’s Founder was diagnosed with stage 4 cancer and Stanford doctors gave him a week to live. They said if he lived he would never talk or work again. Against all odds the shy but resilient 40 year old Founder and SOCIAL DASHBOARD is back with a vengeance after enduring 2 years of chemotherapy, radiation and a full laryngectomy.
SOCIAL DASHBOARD replaces tabs with a turntable that accelerates functionality and increases stability. “Tabs” were the big thing a few years ago, but SOCIAL DASHBOARD powerful magic is its simplicity. With a social network interface more user-friendly than FACEBOOK and browser functions simpler than Chrome, SD’s launch is very exciting.
SOCIAL DASHBOARD’s top priority is user experience. SD eliminates the need to search for “who’s online,” classifieds and other resources because it’s all built into smart menus. One example of how SD eliminates confusing navigation of many websites into one user defined look-and-feel is three categories of live chat – friends, business and personals. In other words, it combines FACEBOOK, LinkedIn and Match.com. Similar functionality is applied to shopping searches grabbing content from Craigslist, Ebay, and so on. SD’s “RESOURCES” menu includes documents, photos, movies, shows and videos, a blog library, news content aggregation, etc.
“I was selected to test SD’s UI and was astounded by its logical simplistic approach. Technology CEO’s like myself and analysts simply overlooked the loophole, and I wish I would have thought of it. I believe SD is going to be the next best company in Silicon Valley and on the web. I guarantee every computer we have and millions of users will switch to SD. If my company could afford to buy SD before its launch, it is a no-brainer.” – CEO of [company name redacted]
SOCIAL DASHBOARD is the first web-based desktop-browser that dynamically and intelligently learns and makes suggestions to improve user experience. The more it is used the better the experience. It becomes an extension of the user. SD’s interface transfers its entire content and functionality between devices (ie. pc, laptop, pad or phone) so multiple devices act as a one big multi-screen.
SOCIAL DASHBOARD has investors’ attention. The most logical play is to do a deal directly with Facebook, Google or Apple. One thing is for sure, whoever owns http://www.socialdashboard.com will have the advantage because unlike Monopoly, everyone will land on SOCIAL DASHBOARD.
Article source: http://www.prweb.com/releases/2012/5/prweb9494387.htm
The My Tablet 7, a 7-inch Android tablet from Xtex, is gunning for the Kindle Fire, undercutting Amazon’s device with a $150 price tag and topping the Fire with some specs.
The My Tablet 7 may not be the best-looking tablet around but it comes loaded with the latest version of Android Ice Cream Sandwich, 4.0.3, and a 7-inch display with 800-by-480 pixel resolution, which is below the $200 Kindle Fire’s 1024-by-600 pixel display. The Xtex tablet also runs on a 1.5GHz processor under-clocked to 1GHz, while the Fire runs on a 1GHz dual-core chip. From here on, it gets better.
The $150 tablet runs on 1GB of RAM, double what’s inside the Kindle Fire, and also double the Fire’s built-in storage, starting at 16GB, and expandable via SD card with an additional up to 32GB. It’s also slightly lighter and thinner according to the manufacturer’s specs.
There’s a 2-mgepiaxel front-facing camera for video chats, notably missing from the Fire, but there’s no camera on the back. The tablet has, however, a variety of ports: there’s a full–size USB port, a mini USB port and a mini HDMI port that can output 1080p HD videos.
Battery life could make or break My Tablet 7, but no official battery tests have been performed. Xtex says that it under-clocked the CPU so that the 3200Mah battery can give between 5 and 6 hours of use, which is at its best still below the 7 to 8 hours you can get on a Kindle fire, given that you have Wi-Fi turned off (you can get substantially less with Wi-Fi on).
The Xtex My Tablet 7 is not a bad tablet for its price, if you are looking for something low-end for kids to play games on or watch videos and download apps. $50 extra would get you a slightly better screen and battery life with the Kindle Fire or the Nook Tablet, with their own app stores and content ecosystem.
But if you can get over the average screen and battery life, for $150 you can get a My Tablet 7 in black, white or pink. It’s not available yet in any stores, but it can be ordered online, with an estimated shipping time of 7 to 10 days.
Cheap and small Android tablets seem to be gaining momentum. Amazon sold more than 3 million Kindle Fires, more than any other Android tablet manufacturer, while Samsung is prepping its own small and inexpensive tablets. Even Google is working on its own cheap Android tablet, to sell it for under $200.
Before you download an Android app, a developer has to present you with a list of system-level resources the app needs to access in order to run. These are simply referred to as Permissions; the purpose of Android Permissions is to let you know exactly what information an app maker is harvesting from your device, so you can make an informed decision over whether or not you want to download it. And an app needs your permission to do even trivial tasks like connecting to the Internet or preventing your phone from going to sleep.
But according to Leviathan Security researcher Paul Brodeur, even an Android app with zero permissions can still extract plenty of data from your device. Leviathan created a proof-of-concept app (called “No Permissions”) and found three types of personal data the app was still able to see:
1. Files on an SD card
2. A list of all apps already installed on the device, and files associated with those apps (the /data/system/packages.list file)
3. Basic device information: the GSM and SIM vendor ID, the Android ID which associates an app with a device, and kernel version.
An obvious question you might ask is what No Permissions could do with this data, if it couldn’t even connect to the Internet (which would require the ubiquitous “Internet” permission)? Brodeur claims Zero Permissions could still make one network call without explicit permission, one that would allow the app to launch the browser. Theoretically, from there the developer would be able to create additional browser calls and transmit the data.
Before you do something dramatic like making a leap to iOS, another security researcher says Leviathan’s findings don’t pose much of a threat at all.
“None of these are flaws with the Android operating system, but with some specific applications that aren’t named,” researcher Daniel McCarney from the Carleton Computer Security Lab told me. ”Most of the findings are entirely supported behaviour. None of this is new research [or] a serious security risk for end users.”
Here’s what’s really going on:
Older versions of Android use an outdated partitioning system (FAT32) also used by many other operating systems, including Windows and MacOS. FAT32 is popular as it allows users to insert an SD card without formatting it into another operating system.
Furthermore in February, Google said it was exploring a Read permission for the SD card in a future release:
“As phones and tablets have evolved to rely more on built-in, non-removable memory, we’re taking another look at this and considering adding a permission for apps to access images. We’ve always had policies in place to remove any apps on Android Market that improperly access your data,” Google said in a statement.
2. App list: Yes, the permission-less app was able to pull a list file showing all the apps on your device. But McCarney said Google is not only aware, it has given developers an even easier way to get a list of installed apps (the PackageManager API).
“The use of this obscure file (packages.list) strikes me as a way to make the issue seem like a serious oversight or a vulnerability,” he said.
Jerry Hillebrand over at Android Central noted this list file doesn’t really pose a risk.
“Knowing what applications a user has installed is a great way to know what exploits may be useful to compromise their phone or tablet,” Hillebrand writes. “Knowing that an exploit exists it’s there means an attacker could try to target it. It’s worth mentioning that targeting a known insecure app would probably require some permissions to do so, though.”
3. Basic device information: Lastly, it remains to be seen whether a hacker with your GSM, SIM, kernel version, and Android IDs can actually identify who you are.
“This claim is entirely overblown,” McCarney says. “All their application is able to gain is the Mobile country code (MCC) and the Mobile Network code (MNC) of the phone. This information would tell you something akin to the fact that I have a Rogers mobile phone in Canada.”
There are a few precautions you can take, if this information still leaves you feeling uneasy.
1. Don’t store any personal information on your SD card.
2. Download one of our recommend Android security apps that will detect apps behaving badly.
3. Be sure to install updates to applications as they arrive. Typically if an app improperly stores secure data on the SD card, developers will fix this and issue an update.