Manufacturer: Dane-Elec Hardware Type: External Hard Drive Model: So Speaky PVR Compatibility: Windows XP, Vista, 7, 8, 10 Downloads: 62,402,861 Download Size: 3.4 MB Database Update: Available Using DriverDoc: This page contains information about installing the latest Dane-Elec So Speaky PVR driver downloads using the. Dane-Elec So Speaky PVR drivers are tiny programs that enable your External Hard Drive hardware to communicate with your operating system software. Maintaining updated Dane-Elec So Speaky PVR software prevents crashes and maximizes hardware and system performance. Using outdated or corrupt Dane-Elec So Speaky PVR drivers can cause system errors, crashes, and cause your computer or hardware to fail. Furthermore, installing the wrong Dane-Elec drivers can make these problems even worse.

Recommendation: If you are inexperienced with updating Dane-Elec device drivers manually, we highly recommend downloading the. This tool will download and update the correct Dane-Elec So Speaky PVR driver versions automatically, protecting you against installing the wrong So Speaky PVR drivers. Solvusoft: Microsoft Gold Certified Company Recognized for best-in-class capabilities as an ISV (Independent Software Vendor) Solvusoft is recognized by Microsoft as a leading Independent Software Vendor, achieving the highest level of completence and excellence in software development. Solvusoft's close relationship with Microsoft as a Gold Certified Partner enables us to provide best-in-class software solutions that are optimized for performance on Windows operating systems. How is the Gold Competency Level Attained? To achieve a Gold competency level, Solvusoft goes through extensive independent analysis that looks for, amongst other qualities, a high level of software expertise, a successful customer service track record, and top-tier customer value.

As a Gold Certified Independent Software Vendor (ISV), Solvusoft is able to provide the highest level of customer satisfaction through delivering top-level software and service solutions, which have been subject to a rigourous and continually-audited approval process by Microsoft.

Amazon has stated the USB port on the Fire TV Stick is “for power only”. That’s not entirely accurate. I’ve discovered that connecting to the Fire TV Stick via ADB using a USB cable is possible and fully functional. Simply plug the Fire TV Stick’s USB “power” cable into a Mac or Linux computer, open a terminal window, run the command adb start-server, and then run the command adb devices to see that the Fire TV Stick is detected as a connected device. I was able to sideload apps and navigate the file system as you would expect with any ADB connected device. Due to the lack of drivers, I was not able to make this work with a Windows computer. I tried installing, but still had no luck.

Dane- Elec Drivers Download for Windows 1. Below is a list of our most popular Dane- Elec product support software drivers. Dane-Elec So Speaky 500Gb Multimedia External Hdd. Iomega External Hard Drive. Data Recovery Service Software When Did Laptops Start Using Sata Hard.

Currently there isn’t much you can do via ADB over USB that you can’t already do via ADB over Wifi, but this does confirm the USB port is alive. Having a functional USB port may lead to future abilities that have yet to be uncovered. Back in the early releases of Jelly Bean, Google introduced a new command to adb called “sideload.” Using the sideload command, and the newest version of adb from the Android SDK, one could update their Nexus device through stock recovery, without having to root or flash a custom recovery. It’s something we wish was there from day one, however, at least we have it now.

And I know that many of you feel that Nexus devices shouldn’t ever have a stock recovery and that they should be hacked on daily, but try to keep in mind that some like Nexus phones and tablets because of constant updates and a 100% stock version of Android. As someone that has a decent grip on drivers and adb, I have to admit that adb sideload has given me issues since it was introduced, which is why I have yet to fully write a guide about it. But with today’s Android 4.2.2 update becoming available, I decided to take a second look at the process and finally found some solutions to the issues that have taken hours away from my life.

One had to do with my device ID not registering through the USB driver, requiring a manual edit of the “winusb.inf” file. The other was a Windows 8 security issue that wouldn’t allow me to install drivers that had not been signed, which is something that happens after you start manually editing driver files. So for those that keep it stock and still want to update early with the cool kids, this guide is for you. Below, you’ll find the instructions to adb sideload, with extra posts coming later that will help with some specific issues that I ran into.

*Instructions are for a Nexus device when connected to a Windows 8 PC. First, you need to install the latest Android SDK (or at least steal the newest adb.exe from it). [] *This isn’t a guide on how to get the SDK installed or basic adb. There are dozens of those out there. Plug in your device to your Windows machine.

Make sure USB Debugging is enabled. To test that you have adb up and running, and that your device is recognized, open a command prompt. *The best place to open a command prompt is from within the Platform-Tools in the SDK. Hold SHIFT and the right-click and choose “Open command prompt” 5. Type the following adb devices 6. You should get a serial number followed by “device.” 015d182f9a0aac28 device 7.

If you see something along those lines, your adb is working properly, for now. Download the update.zip from Google to your PC that you would like to install on your Nexus. Move the file into your Platform-Tools folder. Type the following: adb reboot bootloader 11.

Your device will now reboot to the bootloader. Use Volume Down on your device to until you see “Recovery.” 13. Select it with the Power button.

Your device will boot to an Android logo with a exclamation mark. To jump past this, press Volume Up and Power at the same time.

*Depending on the phone, you may have to press Volume Up first, then Power. On the Nexus 5, though, you press Power first, then Volume Up. You will now be in stock recovery. With Volume Down, highlight “apply update from ADB.” Press Power to choose it. Back to your PC, type the following command: adb sideload *I tend to rename update files to something simple when I get them. For example, the I renamed to JDQ39.zip, so my command was “adb sideload JDQ39.zip” 19. If your adb is working properly, you should see the file transfer to your device in adb.

*If you get nothing, it’s time to troubleshoot.. Once that finishes, your device will begin to update. Once it has finished, simply reboot and enjoy the update. Hope this helps. Anyone that has ever tried to mod their Android phone has come across users telling other users to run various different ADB and/or Fastboot commands.

The only problem is the average Joe has no idea what ADB and Fastboot are because, well, they aren’t your run-of-the-mill applications. I was completely lost myself when I first ventured into the world of Android. While yes, developer hubs like XDA-Developers do provide instructions on how to get ADB/Fastboot installed, there are so many convoluted guides out there, it is easy to throw one’s hands up in defeat. Hopefully this guide makes it simple and straightforward to get ADB and Fastboot installed on your computer. ADB stands for Android Debug Bridge, while Fastboot stands for, well, Fastboot. Without going into too many technical details (trust me you don’t want technical details), let’s just say they are two command-line tools used when modding/hacking Android phones.

You need ADB and Fastboot if you are one of those people that like to mod/hack your Android phone. While many mods/hacks are now becoming more main-stream-user friendly with GUIs (i.e. They no longer require users to use ADB or Fastboot), there are still times when users need to use ADB and/or Fastboot. (Anyone with a Google Nexus One or Nexus S knows what I mean.) While you may not necessarily ever use ADB or Fastboot (depends on what phone you have, and the type of developer support it gets), it is always nice to have them installed when the time comes that you do need them. In this guide, we will show you two methods on how to install ADB and Fastboot. The first method is the semi-automated method while the second method is the manual method. The first method is a easier to do and recommended for most everyone.

If, however, you can’t get the first method to work or you prefer more control, then method 2 is for you. Keep in mind, after installing ADB and Fastboot, you need to ensure you have installed the proper Windows drivers for your Android smartphone or tablet on your computer. You can download the Windows drivers for your Android smartphone or tablet from. To quickly and easily install ADB and Fastboot on your Windows XP, Vista, 7, and 8/8.1 computer (32-bit and 64-bit), do the following: • Download the latest ( ). • Right-click the file adb-setup-1.3.exe and choose “ Run as Administrator“. • Type “Y” and press Enter to install ADB and Fastboot, and set the environment variables.

Enter “N” if you don’t want to do the same and want to just install the drivers. • In the next step, enter “Y” to install the drivers for your device. Enter “N” to skip this step.

• Wait till the driver installation finishes up. That would take only some seconds. • To verify that you have successfully setup ADB and fastboot, open up a command prompt (press Windows key + R ->type in cmd ->OK) and enter “ adb version” (without quotes). If it returns something like “ Android Debug Bridge version x.x.xx“, then your ADB and Fastboot are all-ready. You are ready to rock!

To manually install ADB and Fastboot on your Windows XP, Vista, 7, and 8/8.1 computer (32-bit and 64-bit), do the following: The following guide is for Windows PCs only, but ADB/Fastboot can be installed on Linux and Mac OS X also. (You just do it differently for Linux/Mac OS X.) Also note that this guide was written on a Windows 7 computer. However, the guide will work on Windows 8/XP/Vista the same way; I don’t know about earlier versions of Windows.

• (11 MB) ADB, Fastboot, and other tools. • Note: The tools found in the download are provided by Google, found in.

I have simply extracted the tools and uploaded them for easy access, instead of telling everyone to download the whole SDK. You can get the same tools if you download the Android SDK directly from Google. • Extract the contents directly into your C: partition. You should now have a folder C: Android that looks something like this: • Press Win + R on your keyboard to bring up the Run dialog.

• Once the Run box is open, type in sysdm.cpl and hit OK: • Once you hit OK, the System Properties panel should open; click on the Advanced tab: • From the Advanced tab click on Environment Variables: • At the Environment Variables window find where it says Path under System variables, click on it, and click the Edit button: • When the Edit System Variable window pops up, type in;C: Android at the very end and hit OK: Make sure you type in exactly;C: Android (be sure to include the semi-colon at the beginning). • After clicking OK, close out all windows. You are done! Once you have them installed, using ADB or Fastboot is as easy as opening command prompt, typing in adb xxx or fastboot xxx (with xxx being the command you want to run) and hitting Enter on your keyboard to execute the command.

Take note, however, installing ADB and Fastboot is not enough to start using it with your phones. You need to install the on your computer – so your PC recognizes your phone – before ADB or Fastboot will be able to work with it. If you don’t have any drivers installed, you will get an error similar to the following: If you don’t have the proper drivers installed, read dotTech’s article on. Uninstalling ADB, Fastboot, and the other tools is as easy and undoing what you did when you installed. In other words, delete C: Android and all the files in it and remove the environmental variable you added earlier. You have installed ADB and Fastboot – now what? Now go look for guides on modding/hacking your phone.

A good place to start is reading dotTech’s. Another good place to look for Android hacking and slashing is. If you are lucky, the guides you find won’t require you to use ADB or Fastboot; but if they do, you are now prepared because you just installed them. Originally posted Jun 18, 2012. Updated Nov 16, 2012 to include newer version of ADB and Fastboot. Updated Feb 3, 2014 to include semi-automated method of installing ADB and Fastboot. Installing Linux from a USB mass storage device or logging into Live Linux Environment is a cool Idea.

Booting from a USB mass storage device is sometimes necessary, especially when the ROM media device is not working. Booting Windows from a USB mass storage device is not difficult, and with the availability of various software it has been just a few clicks away. Booting into a windows machine requires only three files, namely boo.ini, ntldr and ntdetect.com.

But booting into a Linux machine is a complex process which requires a whole lot of files and process in well defined execution manner. The booting process is complex but creating a boot-able usb media is very interactive and fun. • Unetbootin (An Open Source Project, freely available) • dd (Data Description) • Usb Mass Storage Device ( Pen Drive) • Linux Image in CD/ DVD/ ISO or Internet connection (Not recommended for large images) • Windows/ Linux Platform Use Apt/ Yum to get the required Unetbootin package or download the tar-ball from the below link for your platform. • Insert Your USB pen-drive into the Windows/ Linux machine and Launch Unetbootin, you will be greeted with a windows similar to. Check the content above the red line.

Type should be Usb Device, strictly and if more than one usb device is plugged in you need to know the name of exact Usb device you need to work upon. A wrong selection will lead to wipe your hard disk, so be aware.

You can browse to the stored disk image on your hard drive, from the Unetbootin window. Or alternatively download from the internet, in real time. Although it is a time taking process and may result into error, when larger image is downloaded. Click OK, and the process of downloading and/or extracting image will start. It will take time depending upon the size of download and/or the file size of ISO image. Once completed, click ‘ exit‘.

Plug out the usb storage device safely and plug it into the machine you want to boot. Restart it and set that usb storage device to boot first from the BIOS menu which may be F12, F8, F2 or Del depending upon you machine and build. You will be greeted with a window as below, from where you can boot into Live Linux Mode and/or Install on Hard Disk from there, directly. • Most of the processing is automated. • Easy to use. • Make it possible to create boot-able stick from windows/Linux.

• One wrong selection of disk and all your Data and Installation on primary HDD is wiped. Dd command originally was a part of UNIX, which is implemented in Linux. The dd command is capable of striping headers, extracting parts of binary files. It is used by the Linux kernel Makefiles to make boot images.

Dd if= of= bs=; sync The bite Size is generally “ some power of 2, and usually not less than 512 bytes i.e., 512, 1024, 2048, 4096, 8192, 16384, but can be any reasonable whole integer value. Sync option allows you to copy everything using synchronized I/O. Run the below command with modification depending upon your source and destination.

# dd if=/home/server/Downloads/kali-linux-1.0.4-i386.iso of=/dev/sdb1 bs=512M; sync It will take time to create the boot-able disk depending upon the size of ISO image and your RAM capacity. Don’t interrupt the boot stick creation, once the process is completed, you will get something like this in your terminal. 4+1 records in 4+1 records out bytes (2.5 GB) copied, 252.723 s, 10.1 MB/s Now safely eject the disk, plug it into the machine you want to boot with Linux, and Yup don’t forget to change the booting option in your BIOS, setting your flash stick to boot primarily. When USB is booted, You will be greeted with a window similar to. • Least possible error in making copy • No extra/ third party tool required • No room for error, an error and everything is wiped. • Non-interactive way.

• You should know, what you are doing, as you won’t get any manual/prompt/help at run time, you must be good in terminals. Remember, All the distro don’t allow Live Environment, but most of the today’s distro does. You will be able to log into a live Linux Environment only if supported. The above article do not aims at comparing the two method.

Before writing anything we gives hours in testing and executing the process to ensure you get 100% working solution. If you gets stuck at somewhere, feel free to contact us in comment section. For any damage to data/ disk, as a result of above method neither the Author nor Tecmint is responsible. That’s all for Now. I will soon be here again, with another interesting article, you people will love to read. Till then stay healthy, safe, tuned and connected to Tecmint. The mobile phone application AndroidTethering turns your Android phone into a USB Internet access point for PC (both Windows, Mac and Linux).

Does not require root access. For windows user: Please follow the instruction step by step: 1.Enabled USB debugging of your phone in settings–>applications–>development. 2.download the driver and adb to your laptop. Download adb tools and android usb driver from the following address: For x86 For amd64 3.unzip the zip file you downloaded to your computer. 4.connect your phone with your laptop through USB cable, and a dialog which prompt you install driver will shown to you, it will ask you where is the driver, just locate it to the folder which you download&unzipped.(if no window opened, it may caused by your PC have already installed the driver correctly, so just skip this step) For moto device, please install moto pc client in your computer, you can get it from moto website: For samsung device, you may need to install samsung pc suite first, you can get it from samsung website or search from google. 5.run the AndroidTethering PC client software to start service on your PC after you read the readme.jpg file to know how to use it. Download PC client from: 6.in your phone side, change port to 6544 in Settings and then start service of AndroidTethering.

7.start browsing Note:The adb and driver is based on the Google’s sdk. The real Android SDK is more than 150Mb. So I made a subset of it that is just 3Mb which contains adb and the driver to save money of the traffic. If you want to download the real google’s sdk, you can download it from ***************************************************************************** For windows user who can NOT use AndroidTethering PC Client application in PC.

1.Enabled USB debugging of your phone in settings–>applications–>development. 2.download the driver and adb tools to your laptop. Download adb tools and android usb driver from the following address: For x86 For amd64 3.unzip the zip file you downloaded to your computer. 4.connect your phone with your laptop through usb cable, and a dialog which prompt you install driver will shown to you, it will ask you where is the driver, just locate it to the folder which you download&unzipped.

5.set the proxy of your browser with host “localhost” and port “8080” This page will tell you how to change proxy in your browser. 6.double click connect.bat file in the folder which you unzipped, then a window will shown, and you can see the successful log in it, if you install the driver correctly. 7.start service of AndroidTethering 8.start browsing ***************************************************************************** For Mac user: 1.Please download the android sdk for Mac to your Mac, and make sure your phone can connect with Mac correctly, you can get it from: 2.use the adb command in the tools of the sdk folder, “./adb forward tcp:8080 tcp:8080″, 3.change the proxy setting of browser with host “localhost” and port “8080″. This page will tell you how to change proxy in your browser. Now, open your Safari–>preference–>advanced–>proxies and change settings–>check the “web proxy(http)” and in the right side, input web proxy server: localhost:6544 4.start service of AndroidTethering in your phone side. 5.start browsing.

***************************************************************************** For Linux user: 1.Please download the android sdk for linux to your PC, and make sure your phone can connect with PC correctly, you can get it from: 2.use the adb command in the tools of the sdk folder, “./adb forward tcp:8080 tcp:8080″, 3.change the proxy setting of browser with host “localhost” and port “8080″. This page will tell you how to change proxy in your browser. 4.start service of AndroidTethering in your phone side. 5.start browsing. Recently, I s aw so many friends asking online for WhatsApp requests or how to use it. It's kinda frustrate me a little, because WhatsApp doesn't have a version in Windows Mobile 6.5 that I own, and I have spent my money for something else, not for a new Android phone. So, I just got an idea.

Why can't I use it on my PC? Since it uses internet(Edge/3G) to chat anyway, it is possible to use a PC to do the same thing. Then, I started asking around about how the software works. S eems WhatsApp need s also a mobile phone number to register and as a redundancy when offline. If it's just that. It's now possible to do.

Requirements: Let's start. (for those who are familiar with setting up Android Emulator, you can skip to step 6.) 1. Install Android SDK. Driver License Place In Memphis Tn On Shelby Drive on this page. The default installation path is at 'C: Program Files (x86) Android' but it seems to have a little trouble after installation because it is difficult to type a path name with ' '(space) in between.

I recommend to use 'C: Android' for installing path, or use a DOS command 'makelink' to create a link from 'C: Android' to the installation path. I won't cover the installation process here. After finish installing, 'SDK Manager' program would popup, if not, open it from Start-->All Programs-->Android SDK Tools-->SDK Manager. This tool is for managing which version of Android will be installed in the system.

You can choose to install all the Android versions available, but it would be a long time for downloading. I recommend installing only what is needed. For this tutorial, I'll use only Android 2.3.3 API 10. When the SDK Manager finish updating and installing, it's time for setting up our emulator. First off, go to the 'Virtual devices' tab on the left, and hit 'New.' Yea~~ WhatsApp on Windows 7 UPDATE (): I saw many people have problems on installing WhatsApp on Emulator. My first thought is I think WhatsApp changed its code to disable us from using their app on Emulator, which is true.

I just tried again today and it does not work. The new freshly download file's size is 4.75 MB, but the original file I did while doing this tutorial is just 4.29 MB (version 2.6.7722) So, what can we do about it? I think from now on, we cannot use WhatsApp on Android emulator anymore. But if you 'really' want to try it on the emulator, here is the how-to: • I uploaded the APK installer (from the time I wrote this tutorial) to here: • Download the file and put it in the folder that easy to remember. (I put it in D: ) • start the emulator so we can communicate with it via command line • use command prompt (cmd.exe as in step 8.

Above) and go to the folder contains 'adb.exe' (usually is at C: Program Files (x86) Android android-sdk platform-tools) • run command 'adb install d: WhatsApp.apk' (without quotes), where d: WhatsApp.apk is where the downloaded file is. Then wait until it completed. Oracle JDK7 itself is not hosted in the PPA because that's not allowed by the new Java license (which is also the reason why it has been removed from the official Ubuntu repositories); the package in the PPA automatically downloads Oracle Java JDK 7 from its official website and installs it on your Ubuntu / Linux Mint computer, just like the flashplugin-installer package does.

Please note that this package is currently in alpha and is offered without any guarantees, so it may or may not work! Use it at your own risk! The package should support proxies just like the flashplugin-installer does, but it may fail if your ISP or router blocks some non-standard ports because Oracle uses quite a few redirects for the Java 7 binary download links. If the download fails because of blocked ports or because you're behind a firewall, use the manual Oracle Java 7 installation method (link in the beginning of the post). Update: our Oracle Java 7 installer now supports ARM. Oracle Java 7 supports ARM v6/v7 Hard Float and Soft Float ABI. Update 2: Oracle Java 8 (stable) was released.

For how to install it, see: This package provides Oracle Java JDK 7 (which includes Java JDK, JRE and the Java browser plugin). However, you can't only install Oracle JRE - the PPA only provides the full Oracle JDK7 package. Important: Ubuntu 13.10 and older versions are no longer supported by Canonical: there will be no security updates and they don't allow uploading new packages to Launchpad PPAs! Canonical has been developing Ubuntu for Devices for a while. Unfortunately, it hasn't exactly been easy to play around with it.

However, if you've wanted to try it (and own a recent Nexus device), it's never been easier to dual boot. Recently, Canonical announced an —which allows you to run Ubuntu and Android side by side—that makes it easier to update (the name for the phone and tablet version of Ubuntu) directly on your device itself. This means that not only can you try out Ubuntu without ruining your phone, but you can see all the sweet new changes as they happen without much fuss. Sounds like a win-win for tinkerers. Disclaimers: Ubuntu for Devices is still in a Developer Preview right now.

As such, it is probably not feature complete enough to be your daily driver. Hence why we're dual-booting.

Naturally, you should expect some bumps in the road. Additionally, Ubuntu uses HTML5 for its apps, but many 'apps' on the platform are actually just the regular mobile sites. Even some of the included ones (like Twitter). At the time of this writing, some 'apps' prompt you to install an Android app when you first run them. Don't do this. Ubuntu is not built on Android and Android apps won't run on it.

Attempting to install them—or even opening a link to the app—can break things. To get started installing Ubuntu Dual Boot (and subsequently Ubuntu itself), here's what you'll need: • A Nexus 4, Nexus 7 (2013), or Nexus 10: These three are currently the only. If you don't have one of these phones or tablets, you can check out the list of unofficially supported devices in the user-ported section.

Our guide, however, will focus on these three. They must also be running Android 4.4.2, so if you haven't updated yet, now's a good time. • Root access: Before you install Ubuntu, you'll need to make sure your phone or tablet already. Fortunately, the three Nexuses we're looking at can all use the. If you're not rooted first, take care of that and come back. • An Ubuntu installation (Not a Live CD): In order to install Ubuntu Dual Boot, you'll need desktop Ubuntu installed on your computer. Unfortunately, the Live CD version won't allow you to install the necessary components.

However, if you have around 25GB of free on a spare drive, you can. • ADB: You're going to need ADB installed to set up dual boot (and to root your device, if you haven't yet). Fortunately, in most modern Linux distros, you can do so with a simple command. In Ubuntu, open up a terminal and enter the following: sudo apt-get install android-tools-adb • Around 2.7GB of free space on your device: Ubuntu for Devices is going to need about 2.7GB of space for the OS and related files. If you're low on space, clear some out before you begin.

Once you've got everything set up, you're ready for the main event. Canonical has created a (relatively) simple script to install the requisite dual boot app on your Android device. Once you've covered all your bases in the last section, fire up Ubuntu and perform the following: First, you'll need to enable USB debugging on your phone or tablet, if it's not already.

Here's how to do so: • On your tablet, open the Settings app and select 'About tablet.' • Tap 'Build number' seven times to enable developer mode. • Go back to the main Settings menu. • Tap the newly-accessible Developer options. • Enable USB debugging. Once that's complete, connect your tablet to your computer with a micro USB cable. Next, download the Ubuntu Dual Boot installer script from to your home directory.

Then follow these instructions: • Open a Terminal window (Ctrl+Alt+T). • Run the following command to make the script executable: chmod +x dualboot.sh • Execute the script by running this command:./dualboot.sh Note: In my tests with a Nexus 7 on a clean Ubuntu install, the script got caught in a loop attempting to execute a curl command (as seen below). If this happens to you, close the Terminal window, open a new one, and run the following command to install the package: sudo apt-get install curl This will install the necessary component. Once that's done, run the dual boot installation script again. The script will run automatically and reset your device several times. Once it's done, your phone or tablet should boot back up to the Android home screen. From there, open the new Ubuntu Dual Boot app from your app drawer.

Then: • Tap 'Choose channel to install.' • Select a download channel (Canonical recommends 'utopic').

• Tap 'Grant' when asked for superuser access. • Once Ubuntu is finished downloading and installing, tap Reboot to Ubuntu. You now have Ubuntu running on your phone or tablet. Now you just need to access it. Unlike many other dual boot solutions, you don't choose which operating system you want at startup.

Instead, once you've booted into Android, open the Ubuntu Dual Boot app and tap 'Reboot to Ubuntu'. Your device will then restart into Ubuntu. No matter which OS you're in, however, a hard reset will always boot to Android. This is usually performed by holding down the power button for about ten seconds. There's also a Dual Boot app in Ubuntu for switching back to Android if you prefer. You can also update Ubuntu from either the Ubuntu Dual Boot app in Android, or from the system settings in Ubuntu.

However, both methods require you to be in Android to actually install the update, so it's probably best to just boot into Android first when it's time to update anyway. Last Updated on October 13, 2014. Tu Mujhe Soch Kabhi Hd Video Song Free Download.

Hey Guys, as you know the Smartphone market is dominated by Android OS – which itself is an operating system designed / based on the linux kernel, but unfortunately the Android Emulators for Linux itself are quite less as compared to windows counterparts 🙁. So let’s have a look on the 5 best Android Emulators for Linu x to run android apps and play android games on Linux -Ubuntu,LinuxMint,Fedora,ArchLinux etc 1. Genymotion Genymotion – This is probably the Best Android emulator when it comes to Linux Platform due to some unique abilities present only in genymotion, Features of Genymotion are — • It allows us to easily Download pre-configured Android Images of various Android Versions and various Android device images such as Nexus 7,Galaxy S2,Galaxy S3 etc directly on our emulator. • It also allows us to configure the amount of resources e.g RAM,harddisk to be allocated to the Android device / Emulator. Great feature if limited on hardware resources.

• Genymotion directly supports networking through ethernet /Wi-Fi, emulates your connected connection directly so it use internet directly in the emulated android. • ADB Support and it also supports OpenGL hardware acceleration so your Android device works fullscreen and thus enhancing your experience while playing android games on your Linux! • It Also supports drag and drop file transfer to the emulated SD Card 🙂, supports Gyroscope,Light and accelerometer sensors too. • You need an account on Genymotion Cloud – to Download and deploy Genymotion android device — •. Note – Oracle Virtual Box must be installed on your Machine for Genymotion to work!, installing Virtual Box On Linux is covered at the end of this post 🙂 • Installation instructions for installing Geanymotion on Ubuntu/Archlinux are. 2.Andro VM AndroVM is the Parent Project of genymotion – nevertheless it still works and works awesomely!

And the best thing about Andro VM is that the android machine is deployed offline on your PC unlike Genymotion where it is deployed on your PC through cloud, thus you can use Andro VM to install Android Emulator on your linux even offline • another striking feature of Andro VM is that it supports hardware OpenGL rendering through Virtual Box. • Virtual Box must be installed on your Linux OS for Andro VM to run, check end of the post for Virtual Box installation tutorial. • AndroVM supports Net Sharing from guest to host, the internet sharing as well as Installation tutorial for Andro VM is available here at their blog — >• AndroVM can be downloaded for both 32bit and 64-bit Linux Kernels from here –>.

Andy Android Emulator by Andyroid.net – Andy OS • Although, yet in Beta at the time of writing this article – ANDY OS Android Emulator is pretty much exciting and the best Android emulator for Linux., being a beta tester i have the access to pre-release features of ANDY, hence i have given it the 3rd place, it could easily been the first one though! • Features of ANDY emulator include Google Play Store support inbuilt, none of the emulator has this feature inbuilt even for Windows builds! • Multi-Touch support 🙂 the word explains it all!

• Use your phone as a controller for controlling / playing the games, the picture alongside explains it 🙂 • Access the installed apps directly from the Desktop environment! • OpenGL hardware acceleration, Camera and Microphone all features supported! • You can download the beta version for Linux or the Windows build for Andy from here –>The link will automatically redirect you depending on your OS — • You might want to check out this new emulator which runs directly inside Google Chrome Browser – 4. Official Android SDK – Android Emulator / AVDs • The Official Android SDK/ Android emulator by Google, has a lot of fans though not me 😛 and is used by default by mostly anyone who wants to develop apps for Android • This Android emulator supports all the functions including SD Card support, file transfer et • It also supports physical keypad which none of the Android emulators support!! • Being developed by Google Engineers you are assured of the quality of product and safety!

• The Setup of this emulator is the thing which doesn’t impress me much though 🙁 • An easier setup guide to • The required SDK / ADT bundle for Android emulator and plugins can be. Jar of Beans – Wine Compatible! • Although Jar Of Beans was developed as an Android Emulator which was Portable for Windows,it can be run through Wine. • It has all the basic support such as APK install, SD Card supports and supports installation of Play Store too. • but already Wine being a kind of Emulation environment we wont encourage usage of Jar of Beans on Linux • For using Jar of beans for Linux, extract the exe contents of the Jar of Beans.exe file which can be downloaded from here –>, and then by runnint the jarofbeans.exefile with wine. • Installing VirtualBox on Linux • As, we mentioned we need to install virtual box on linux before using Genymotion/AndroVM/ANDY, the eaiest method to install virtualBox on linux is • Installing the dependencies by executing “ sudo apt-get install dkms” in terminal, and then by executing “ sudo apt-get install virtualbox-4.3″ in the terminal!

That’s it virtual box will be installed! • If it doesn”t get installed you may want to Update: You might love it to check out the New Firefox OS on PC – If you have any doubts/queries/suggestions Feel free to Comment, we will try our Best to Please you Thanks! Devices listed below can be controlled via IR with the addition of a Simple Blaster (available with or ). A Simple Service subscription is required for IR control using third-party adapters. Devices not listed below may be learned from your original remote using the Simple Blaster. Devices in blue updated 1/26/17. Devices listed below can be controlled via Serial (RS-232) with the addition of a Simple Blaster (available with or ). Serial control also requires a Simple Cable – Serial cable.

Configuration of serial port settings, such as baud rate, should be performed via the Simple Blaster Settings web page on the adapter prior to usage. The Simple Cable – cable can be configured into all modes and genders. Certain cases, most notably Samsung TVs with EX-Link, require an attachment to convert the DB9 end of the cable to another connector such as 3.5mm that should be attached to the Simple Cable – Serial cable. See below for information on the type of cable your device needs. (Additional device support can be added to Roomie by advanced users. See for more information.).

USB_ModeSwitch is (surprise!) a mode switching tool for controlling 'multi-mode' USB devices. More and more USB devices (especially high-speed WAN stuff, based on cell phone chipsets which are able to change their USB connection mode) have their MS Windows drivers onboard; when plugged in for the first time they act like a flash storage and start installing the driver from there. After installation (and on every consecutive plugging) the driver switches the mode internally, the storage device vanishes (in most cases), and a new device (like an USB modem) shows up.

Modem maker 'Option' calls that feature 'ZeroCD (TM)' since it eliminates the need for shipping a separate driver carrier. In the beginning, nothing of this was documented in any form and there was hardly any Linux support available. On the good side, most of the known devices do work in both modes with the available Linux drivers like 'usb-storage' or 'option' (an optimized serial driver, the Linux standard for high-speed 3G modems). That leaves only the problem of the mode switching from storage to modem or whatever the thing is supposed to do. Fortunately there are things like human reason, USB sniffing programs and 'libusb'.

It is possible to eavesdrop the communication of the MS Windows driver, to isolate the command or action that triggers the mode switching and to reproduce the same thing under the rule of Linux or the BSD variants. USB_ModeSwitch makes this process easy to handle by taking the important parameters from a configuration file and doing all the initialization and communication stuff, with heavy help from 'libusb'. It is mainly used automatically - via udev events and rules - to do the switch without any user interaction. But it can also be run as a command line tool, usually when trying to make unknown devices work with it. This tool is part of most major distributions; you should not be having to install from the source packages here unless you run into problems and need the latest version. Please read the information on this page carefully before you go around posting questions! If you encounter a new device, it really helps to understand the principle of what is happening, which in turn makes it easier to find out about the switching command and to add a new config entry.

For hints about doing your own sniffing see paragraph below. Important: For a working installation you need both program and data package! Changes and updates to the configuration data may happen more often than new program releases; most of the knowledge about devices is contained in these files. That's why it is provided separately.

• Download (md5: 38ad5c9d70e1bdc2b1e568), the source code release dated from 2017-01-17; a Debian package should be available soon at the. • Download the package (2017-02-05, md5: 0cc107cd0c4c83df0d9400c999e21dfd). It contains the device database and the rules file, including full paths. You need program releases from 2.4.0 upward because of updated parameters/functions. • To compile the program, install (formerly on ) if it's not on your system yet. In most distributions there is most likely a package named 'libusb1-dev' or 'libusb1-devel' (or similar).

Older versions were based on libusb-0.1.12 but since version 2.0.0 only libusb1.x is supported. As a small complication, there was a compatible fork of libusb1 called 'libusbx' around for a while (). If you have an Android Tablet with USB host port and at least Android version 2.2, you can try the ', available only on Google Play. It includes USB_ModeSwitch and PPPD, making it relatively easy to go online with your modem stick or your phone, even on WiFi-only devices. For later Android versions, use ' which does not need kernel modem drivers anymore. If you are a system integrator (package maintainer) you can use this XML file to check for new releases:. The maintainer of the USB_ModeSwitch Debian package has set up a PPA providing the most recent release; see his for the link.

If you have an earlier version installed, de-installation is recommended ('make uninstall'). Several file locations changed in 1.1.0, old ones might be orphaned if not taken care of. If you have a version after 1.1.0 you can just update and overwrite all existing files. Unpack the source file of the program (who might have thought!). In the newly created directory run as root or superuser: # make install This installs a small shell script for udev, the larger wrapper script, a config file, the man page and the freshly compiled binary. Important: if you install this way, you will need the 'tcl' package for the large dispatcher script.

There are more ways to install which do not depend on that package. Refer to the included README for further install options! Now do the same procedure for the data package. It will install the config files in '/usr/share/usb_modeswitch' and the udev rule file in '/lib/udev/rules.d'. The earlier '/etc/usb_modeswitch.d' is now reserved for custom config files (new or changed).

You are set already; if your device is known, you should be able to just plug it and use it. If it doesn't work right away we'll find out why. For manual use - when testing and analyzing - you just need to install the binary program. Work with the command line interface or use a custom config file with the -c parameter. See also the next paragraph,. In most cases, you will be able to use your device without any interaction except plugging it in.

If you think your device is supported, but things are not working out as they should, turn on logging first as described in. For testing, debugging and taming new devices from the wild, you can use the binary part of USB_ModeSwitch in manual mode. There are two ways for that: using a config file or using the command line. Run 'usb-modeswitch -h' to list the command line parameters. If any of them except -W, -D, -I and -q are used, a config file given with -c is ignored and all mandatory parameters have to be provided on the command line. See also the included man page.

To work directly with a specific configuration, use one of the little files in '/usr/share/usb_modeswitch' or create one yourself. Then give the path and file name to usb_modeswitch with the -c option.

For a complete reference have a look into the. Together with the existing config files you should be able to get a good overview about the handling of a device. Important: USB_ModeSwitch - like all programs using libusb - has to be run as root (or with 'sudo') when calling it manually. Otherwise strange error messages turn up and things won't work. When trying out switching commands and strategies, it's probably easier to work at a root shell for a while ('sudo bash' or 'su -').

The automatic approach consists of several components working together, listed in the logical order of usage: • /lib/udev/rules.d/40-usb_modeswitch.rules - the udev rules starting the wrapper if a known device ID (vendor/product) is recognized. To add a trigger for a new modem for which you have a working config file, append a line with its USB ID as seen in the existing entries. If the switched device provides standard serial ports, a second rule calls the wrapper again and adds a symbolic link to the correct connection port (see below) • /lib/udev/usb_modeswitch - a shell script forking to the real wrapper script. Since version 1.1.6 the script is fully compatible with the 'dash' shell used in Ubuntu as well as with older 'bash' variants. Recent versions make use of upstart or systemd features in order to detach the usb_modeswitch run from the udev process • /usr/sbin/usb_modeswitch_dispatcher - this is doing additional device checking and then using the binary to switch with the selected device config file. If no drivers are taking care of the device after the mode switch, the dispatcher will try to load and bind the 'option' serial driver, in order to make the device usable. • /etc/usb_modeswitch.conf - a global config file to enable extensive logging when troubleshooting, or to disable switching alltogether (mostly to access the install part of devices) • /usr/share/usb_modeswitch - a folder containing the individual setup information files per device, named according to the IDs and possibly further identity tokens (to resolve known ambiguities).

If your device ID shows up in one of the file names, chances are your device is supported even if the model or brand does not match. • /etc/usb_modeswitch.d - a folder for customized config files.

You can put new or modified config files here; they will take precedence over the collection of configurations in /usr/share/usb_modeswitch. • /usr/sbin/usb_modeswitch - the binary program effectively doing the switch.

This is designed to be independent of kernel or system specifics, and should be portable to non-Linux platforms, wherever libusb is available. After switching and driver-loading, it is the responsibility of the system to discover the new (mostly serial) device. Current releases of NetworkManager (or its ModemManager component) are usually quite good at making use of wireless modems. Even newer models that don't use PPP interfaces anymore are recognized and integrated seamlessly. There may be issues with older versions of these programs which may run into touble when trying to auto-detect USB modems and how to use them.

If you are stuck with an older system, try disabling NM and MM. Good results were reported by working with wvdial, UMTSmon and several tools providing a user interface to PPP like kppp; some of these programs may require a bit of basic knowledge though. Starting from version 1.1.2, usb_modeswitch will add a symbolic link to the correct port with interrupt transfer if the device provides standard serial ports. The link will have the name /dev/gsmmodem, with a number appended if more than one device is attached.

You can use this name with connection helpers like wvdial. Note that in many cases you may have to edit the configuration file manually. If you managed to get a new or badly supported device to switch correctly in manual mode, you can add a udev rule and a config file yourself. But please report it back to share it!! Very important note: Personally, I could not test the vast majority of supported devices; the list here - as well as the necessary data - relies on reports from third parties (people, that is). So it may happen that you hit sudden obstacles even with your device listed here.

That said, the user base of this little tool has grown considerably, so that any data related problems are generally surfacing quite soon. There are hitherto three known methods for initiating the switching process: • sending a rarely used or seemingly weird standard storage command (equivalent to those of SCSI) to the storage device ('eject' for example) • sending one or more vendor-specific control messages to the device • actively removing (detaching) the storage driver from the device (only some early devices) Again, if you don't find the name of your device in the list, it may still be supported. The important thing is that you find your device's USB ID in the config file folder. Have a look into the latest data package (See ).

Here is an earlier list of devices (not updated anymore), together with the respective contributors:. Note: if you still need support after having followed the advice on this page, please use the forum! E-mail may be used for device/config contributions only - no support questions! Known issues: • Automatic serial driver assignment will work with the 3G-optimized driver only for kernels from 2.6.27 and up. If you have an older kernel and your modem is not recognized by any driver after mode switching, then the generic 'usbserial' driver is used as a fallback.

• There is a problematic handling of devices with ID 19d2:2000 in kernels 2.6.26 to 2.6.28. This affects mostly ZTE devices and makes the 'usb-storage' driver ignore the ID. In turn this will prevent proper initialization and may cause switching to fail. There is no other way around this than compiling your own kernel with some tiny edits. See Kernel related issues below for details. For debugging of the automated system integration, edit (as root or su) /etc/usb_modeswitch.conf in a text editor and change the line EnableLogging=0 to EnableLogging=1This gives you a verbose output of the hotplug activity to /var/log/usb_modeswitch_. If you're next to certain that you have the right values for your device, followed all the hints (see ), and USB_ModeSwitch seems to do something run after run but to no effect, there are most likely system issues involved.

The first suspects are existing system rules for modems which handle things not quite correctly. If you own a device with the unswitched ID of 05c6:1000, it may get a wrong switching command in older systems. There are four different types of switching devices, all with that same ID; in the big distributions they were all treated alike as a model from 'Option' (the manufacturer) which is wrong in four out of five cases. There are even cell phones with that ID which wrongly get the same treatment when connected to an USB port. To fix problems like that you can try to remove rules files from '/lib/udev/rules.d' which contain calls to 'modem-modeswitch'. USB_ModeSwitch will do additional checks beside the USB ID and treat all known ambiguous devices in the right way. For example, it will leave unknown devices with the 05c6:1000 ID alone.

Annother notorious candidate is again 19d2:2000. It may be switched O.K. By an existing rule, but there is no driver loading if your model is new and its ID is not yet added to the 'option' module. Disable the rule running 'eject' and the ID will be handled by usb_modeswitch. In some newer kernels, certain devices (some Option, some Huawei, some ZTE as mentioned above) get a special treatment in the usb-storage code to enable switching right away. You would not need USB_ModeSwitch anymore for these specific devices; on the other hand you have no choice of accessing the 'CD-ROM' part of your device.

Plus, there were cases when the special treatment brought no results and furthermore prevented USB_ModeSwitch to work properly afterwards (happened with ZTE devices, error '-2'). In case of trouble, look into 'unusual_devs.h' in the 'drivers/usb/storage' folder of your kernel source. If your default ID (vendor and product ID of the storage part) can be found there and you get errors when running USB_ModeSwitch, try first to blacklist 'usb-storage'. If that helps, you should consider rebuilding your kernel with the entry in 'unusual_devs.h' deactivated. The only thing that will happen is that usb-storage works in the default way afterwards.

I found a in the Russian Gentoo wiki to do exactly what I just suggested for the ZTE MF626. By the way, at one point there was an agreement among USB developers to keep all future mode switching code out of the kernel drivers if the neccessary steps can be taken in 'user space'. Annother way of influencing the kernel behaviour is the parameter 'delay_use' of 'usb-storage' which sets the time in seconds after plugging when the storage device will actually be used (and probably automounted). The default value is 5; this might affect the switching result under certain conditions. To change the default add in /etc/modprobe.conf: options usb-storage delay_use=1 (or 10, or other) If you are running a not-quite-fresh system (with a kernel below 2.6.27), you may run into incompatibilities between versions of 'udev', the device manager. If you get no indication of the usb_modeswitch components doing anything at all (no log files), follow these steps: • Check if there are other files alongside '40-usb_modeswitch.rules' in the folder '/lib/udev/rules.d'.

If this is not the case, move the file to the folder '/etc/udev/rules.d'. • If there is still no action, see if other files in '/etc/udev/rules.d' contain the string 'ATTRS'. If this is not the case, edit the file '40-usb_modeswitch.rules' and replace all occurences of 'ATTR' and 'ATTRS' with 'SYSFS'. Save the changes and see if something happens when you plug in again.

• In particularly tough cases of 'non-action', it might be necessary to analyze udev's actions; this is done by editing '/etc/udev/udev.conf' and change the logging level to 'debug'. USB_ModeSwitch comes quite handy for experimenting with your own hardware if not supported yet. The first step would be to try widely used switching methods from known devices, like the 'eject' sequence found in the BandLuxe configuration '1a8d:1000'. If you have a hint that your device may be made by Huawei originally, try the sequence from '12d1:1446'. Don't worry, it's almost impossible to break anything by experimenting with possibly wrong sequences. Just make sure you re-plug your device after each attempt! If all this has no effect you can try this approach: Note the device's Vendor and Product ID from /proc/bus/usb/devices (or from the output of 'lsusb'); the assigned driver is usually 'usb-storage'.

Then spy out the USB communication to the device with the same ID inside M$ Windoze, with the on-board driver installed. The device must be switched there too, and you want to log that moment. I recommend this tool: 'SniffUSB' ().

This is the short version. There is a very good case example from Mark A. Ziesemer here: Please post any improvements, new device information and/or bug reports to the!

If you don't need support you can also send me an old-fashioned - and at your demand confidential - e-mail (see below). Copyright (C) 2007 - 2017 • Josua Dietze (usb_admin at this domain) Please use only the forum for support questions! For other messages like tested new device configurations or personal/confidential stuff you can mail me directly.

Command line parsing, decent usage/config output and handling, bugfixes added by: TargetClass parameter implementation to support new Option devices/firmware: Created with initial help from: Config file parsing stuff borrowed from: Hexstr2bin function borrowed from: A special 'Thank You' goes to • Lars Melin, maintainer, who tirelessly traces and collects new device configurations from around the electronic universe, then lists them for me to make updates and corrections so much easier!! Code, ideas and other input from: • Aki Makkonen • Denis Sutter • Lucas Benedičič • Roman Laube • Luigi Iotti • Vincent Teoh • Tommy Cheng • Daniel Cooper • Andrew Bird • Yaroslav Levandovskiy • Sakis Dimopoulos • Steven Fernandez • Christophe Fergeau • Nils Radtke • Andrei Nazarenko • Filip Aben • Amit Mendapara • Roman S. Samarev • Chi-Hang Long • Andrey Tikhomirov • Nicholas Carrier • Adam Goode • Daniel Mende • Leonid Lisovskiy • Vladislav Grishenko • Lubomir Rintel More contributors (device specific) are listed in the. Thanks to everyone at the too! Sometimes it takes a considerable reservoir of patience on the road to success. 3 - 10, 3 -SOLNCEVO BLACK HAWKS, 4 () - -Hakuna Matata - -BarsA Plus - ' -4 -Volltage - - (), 5 - () - RUSVOLLEY 2.0 - ' - ' ' - - -, 6 - CSK Akado - -Maximus VolleyPlay-II - -, 7 - 2 - MIX - () Gazec - - ' 'Z' () - --3 Strong Volley - ' ', 8 - Dream Red Volley - ' Union Jack -Cuba Libre - - Nuris_2.0 -, 9 -2 -CSK Akado - -Lucky Break (Venta Sport) - ' -Veni Vidi Vici NonSTOP - - - - -LANDOR - - ' Team --LG - №6, 10 ' - ' - 2 - Plus -1 -Stella --2 -, 04.11 C () (, ultet) (Na, ( ) ( 'Butovo Bulls',,,, ) (,,, ()) ( 2.0) (-2) ( ') (Z-Coach Team, -, ) ( (.

() (Lucky Break) () (Drink Team, ) (Union Jack) (team) ( Alex) (,, ',,, -) (Pilsner Urquell, RUSVolley) (, ), 05.11 (-1 ) () - (,, ) ( ', ') () ( ) ( Plus) () (Sunny Wind (), VolleyUP, -2) (,, ) (-) (Liberty, ) () ( ') (, 675) ( ) (CONTRAIL, ITon), 06.11 (-,,, -4, ) (, ) (-LG, ) ( ) ( ) (Arsport,,, ') (Legion,, New Style) ( ) (, -) (WalkaWay,, (Venta Sport),,, ()) (-) ( Alex) (-2) © Copyright c.