Showing posts with label Computers. Show all posts
Showing posts with label Computers. Show all posts

How To Install Android SDK for Windows, Mac and Linux: A Complete Guide & tutorial


Everything you need to get started with the Android SDK, and everything you need to know about installing it.


nstalling the Android SDK is far easier than it used to be, thanks to a new package from Google. One download gives you most everything you need to communicate with your phone via the USB port, using tools like adb and fastboot.

Let's begin.....

1. Getting started with the Android SDK

I told you this was pretty easy, and that there was just one file to download. Here it is. Download the SDK direct from Google by clicking here. Scroll down a bit and find the section marked "SDK Tools Only" and save it somewhere easy to get to, like your desktop. We'll be extracting it to a better location in the next step.
The file you downloaded is compressed. You'll need to be familiar with compressed files — and extracting them — to go any further. If you're not, stop here and spend the time to learn about them.
Extract your compressed file into the following location:
  • Windows: The root of your C: drive
  • OS X: Your home folder
  • Linux: Your home folder
Rename the extracted folder to "Android". This will make the rest of this guide, and your time with the SDK, much easier.

2. Prerequisites


You'll need a working version of Sun Java to run the SDK components. Advanced users may try alternatives like Open Java, but for this guide we're sticking with the official Sun Java from Oracle. Yes, that Oracle.

On a Mac, it's pretty easy because you'll already have it installed unless you uninstalled it. If you did, install it again — you should know how.

On Windows, head to the Oracle website and download the correct version (32- or 64-bit) for your computer. Again, if this gives you any trouble stop what you're doing and learn a bit more about your computer. If you can't install Java, maybe you're not yet ready to use the Android SDK.

On a Linux computer, you'll also need to install Sun Java from Oracle. You can find x86 and x64 binaries at the Java website. If you need more assistance, or want to use a package manager to install Java, you'll need to refer to the documentation for your particular distro.

Linux users will also have to make sure they have some 32-bit libraries installed if they are running a 64-bit version of the operating system. If you're using Ubuntu or an other Debian variant, install ncurses5 and stdc++6 through your terminal: sudo apt-get install lib32ncurses5 lib32stdc++6 
 
Packages for other distros, like SlackWare or Fedora should be available as well. See the documentation for your particular distro.

3. Setting your PATH


The PATH variable in your computer's operating system tells it where to look when you want to run a command from a terminal or the command line. For example, to run the adb command you either need to type and provide the complete path — ie the folder adb is actually in, inside the SDK folder — or have the location set in the PATH variable itself. It's a bit confusing, but the good news is that doing it is easier than explaining it.
For these directions to work, you will have to have extracted and renamed the SDK download folder as mentioned above, and to the correct location for this tutorial.

4. On Windows

You no longer can set the PATH in the autoexec.bat file or autoexec.nt file. You'll need to update the system Environment Variable settings instead. Here's how it's done on a Windows 8 machine:
  • Hit the Start key on your Keyboard.
  • Start typing the words Environment Variables.
  • As you type, you'll see the choice to Edit the system environment variables. Choose it.
  • In the Environment Variables window, select the PATH line item in the Systems Variables section, then click the Edit button.
Add the full path to the Android SDK tools and Android SDK platform-tools folders in the edit box, separated by a semi-colon. It should look something like this:
C:\Android\tools;C:\Android\platform-tools
For older versions of Windows, refer to the documentation that came with your computer for assistance on setting the PATH. And, again: If you've installed your sdk somewhere other than \Android, you'll need to adjust accordingly.

5. On OS X

You can set your PATH variable on a machine running OS X in your bash profile. Doing so is easy, and is all done in one file.
In your Home folder is a file named .bash_profile. Open it with any text editor.
You may see a blank file, or it may be full of other information. All we need to do is add a couple lines to the top of the file:
export PATH="$HOME/Android/tools:$PATH"
export PATH="$HOME/Android/platform-tools:$PATH"
(Did we mention that if your SDK is in another location, you'll need to adjust things accordingly? Good.)
Save the file, and reboot your computer so the new PATH is sourced properly.

6. On Linux

 
 Setting the PATH on a Linux computer is almost the same as on a Mac, you just edit a different file.
Using your favorite text editor, open the ~/.bashrc file. It will probably exist and have multiple entries. If you get an error that the file does not exist, simply create a new file and save it as ~/.bashrc when finished.

You'll want to add the following two lines to the END of the .bashrc file:

export PATH="$HOME/Android/tools:$PATH"
export PATH="$HOME/Android/platform-tools:$PATH"
 
Save the file, and reboot your computer so the new PATH is sourced properly.

7. Wrapping it up

 

If you made it this far, you have successfully installed the Android SDK and can now use tools like adb and fastboot. Pat yourself on the back and have a frosty beverage. We're going to talk a lot more about how to use these tools in future articles, as well as making sure your phone is ready to go and connected.


Your Android is your oyster, and you'll need no sword to open it.
Read More »

How To Install Windows On Your Apple Mac When All Other MethodsFails



What won’t work

During the course of my Windows install venture I figured out at least 6 ways which didn’t work. They all have their eureka moments, but don’t work out in the end.


1. Cleaning the superdrive

Apparently you can drape something like a lens cleaner over a thin business card, stick the thing into the slot and get to work on it. The business end of the drive is at the bottom so if you wiggle it just right, and you’re lucky, you could be successful in cleaning the thing. You can also try blowing some compressed air into it.

If you were successful in doing so you can basically skip this guide and install via Basecamp, well done!
 
2. Bootable USB via bootcamp

The only snag with this was that I didn’t have this option. Apparently this is only available for computers without an optical drive. There is a way in which you can enable this pretty easily though. This is something we will need to do further on as a part of our installation, but it still doesn’t work on its own.

When I saw the option, I promptly clicked on it and let Bootcamp create a startup USB for me. It worked at first, but then refused to even acknowledge it in the boot menu. I tried this with and without Bootcamp drivers and I even tried checking the "Install Windows" options which would automatically start the process for me.

I was a bit downcast but I thought: hey, let’s create a bootable USB in Windows! I found a Windows laptop and created an USB using Rufus. Of course, it didn’t work, it wasn’t seen by the boot manager. I went back and used the Windows 7 USB/DVD Download Tool which was made by Microsoft. Still nothing. Changed another pen drive. Nope. Sigh.

3. Firmware update

Good news, my iMac model has a firmware update, and what’s more, this update has to do with "booting" stuff (is luck finally on my side?). I downloaded and installed the firmware update and after a terrifying BIOS beep, everything was back to the good old not working ways.

Oh well, at least my firmware is updated.

4. rEFInd Boot Manager

After reading a whole lot of forums I saw that using rEFInd, an alternative boot loader may help.

Once installed and loaded on startup it "saw" the USB, however, while it was able to access the drive, I always receive a "No bootable disk found" message. This was weird since the message obviously came from the boot device, why is it looking for (maybe) a CD? Try as I may, rEFInd was not the answer, although just like Bootcamp, it is a part of the final solution.
 
5. Using an external drive

Nope. This was the second thing I tried but it didn’t even see the CD. Once I had rEFInd installed I tried again; the CD showed up in the boot manager, but it refused to boot from it. All I got was a horizontal cursor and nothing more. One thing I didn’t try was an Apple-made external drive but while it’s possible that (for some unknown reason) this would work, I have read that it doesn’t.

6. Virtual machines

I remember from using Parallels that it can use a Bootcamp partition, allowing me to use the bootable partition as a virtual machine. I had a feeling this wouldn’t work, but it was worth a shot. Parallels (and other virtualization apps) can’t install Windows as boot partitions. They can use them once created, but only if created separately.

Again, virtual machines will be a part of our solution, but not THE solution.
What does work

Technically, it is a specific series of operations that works. My source for it is Yes, This Big – a huge thank you to them for figuring out the final solution.

Here is the simplified rundown of the solution:

    Force Bootcamp to create a bootable disk
    Create a custom virtual machine with VMware (the trial version is sufficient)
    Modify the virtual machine and install Windows onto the Bootcamp partition
    Delete all the files and copy them, from the USB key
    Boot into the Bootcamp partition using rEFInd and Install Windows normally
    Curse Apple a little bit for making this so difficult

Let’s take a look at the specifics of all these steps, by the end of which you will have a nice little Windows install!
 
1. Force Bootcamp to create a bootable disk

If you don’t have this option enabled, you’ll need to edit some files.

You’ll need your computer’s (1) Boot ROM version and (2) Model Identifier which can be found in System Report. (Open up Spotlight, with Cmd + Space, and type "System Information".)

Here’s a sample of what you will see:


Head on over to the Applications/Utilities folder, right-click "Boot Camp Assistant.app" and choose "Show Package Contents".

Go into the "Contents" folder and make a copy of "info.plist" somewhere, just in case. Next, open the original "info.plist" file in a text editor, and search for "USBBootSupportedModels" – it should be somewhere at the bottom.

Look up your model identifier and add it as a string, something like this

   
<key>USBBootSupportedModels</key>
<array>
 <string>Your Model Identifier</string>
 <string>MacBook7,1</string>
 <string>MacBookAir3,2</string>
 <string>MacBookPro8,3</string>
 <string>MacPro5,1</string>
 <string>Macmini4,1</string>
</array>

Next, find the section labeled "DARequiredROMVersions" and add your Boot ROM Version in a similar fashion:

   
<key>DARequiredROMVersions</key>
<array>
 <string>Your Boot ROM Version</string>
 <string>IM41.0055.B08</string>
 <string>IM42.0071.B03</string>
 <string>IM51.0090.B03</string>
 <string>IM52.0090.B03</string>
 <string>IM61.0093.B01</string>
 <string>MP11.005C.B04</string>
 <string>MB11.0061.B03</string>
 <string>MBP11.0055.B08</string>
 <string>MBP12.0061.B03</string>
 <string>MM11.0055.B08</string>
</array>

You can now save and close this file.

Open Bootcamp and wonder at the appearance of the "Create a Windows 7 or later version install disk". Click all the checkboxes and let Bootcamp do its thing. You’ll need to supply it with an ISO image which you can generate with Rufus or the Windows 7 USB/DVD Download Tool.

Once Bootcamp is done, it won’t be able to install Windows. When it reboots, press the alt button until the boot manager comes up and boot back into OS X.

2. Create a custom virtual machine with VMware

Note: I’m pretty sure this can be done with other virtualization software as well but I don’t know enough about this topic to go rogue. The trial version of VMware is more than enough for this task so you can get it done free either way.

Before we jump in, we’ll need to take a look at the disk identifier of our Bootcamp partition.

Using Spotlight to type "Disk Utility", click on the BOOTCAMP partition and press CMD + i. This will bring up a disk info window where you can find the Disk Identifier – make a note of it


Open VMware fusion and press CMD + N to create a new virtual machine. You’ll need to click "More options…" and select "Create a custom virtual machine". Then click Continue.



Now, select the operating system you are installing, click Continue and select "Create a new virtual disk" from the next menu. Click Continue and select "Customize Settings" from the bottom of the next screen; this will let you specify the location for the virtual machine. I selected my desktop for easy access – you can safely delete it once this is all over anyway. Finish up and close VMware.

3. Modify the virtual machine and install Windows onto the Bootcamp partition

Now, we’ll use some trickery to make VMware use our Bootcamp partition as the target location for the install.

To edit the settings for the virtual machine you’ll need to open up a terminal. Once ready, type "cd " (add a space at the end) and drag the icon of your virtual machine into the terminal and press Enter.

Now you’ll need to issue a command which will link the VM to Bootcamp, take care to replace [X] and [Y] with the correct values.

1     /Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk[X] [Y] win7_raw lsilogic

In the screenshot of my BOOTCAMP partition the disk identifier was disk0s4. The first number (0) would be X and the second (4) would be Y.

So in my case the command would be:
    
1    /Applications/VMware\ Fusion.app/Contents/Library/vmware-rawdiskCreator create /dev/disk0 4 win7_raw lsilogic

You won’t see any feedback from the terminal but if it worked, you should see a new file within the VM file.

Click on the icon for your virtual machine on the Desktop and click "Show Package Contents". This should result in a list of files – the new file you should be looking for
 "win7_raw.vmdk". 
 
The next step is to edit the "Windows 7 x64.vmx" file.

Open it in your text editor and search for the line starting with "scsi0.virtualDev" and edit its value to "lsilogic". Then search for "scsi0:0.fileName" and edit its value to "win7_raw.vmdk".



Open VMware and start the virtual machine. It will ask for your password because it needs to access the Bootcamp partition. You’ll need to install Windows from the iso file you created earlier. You may need to press CMD + A to open the settings and go to the CD/DVD section. Click Autodetect and choose the iso image and click enable.

Let the installer do its thing. You’ll need to format the Bootcamp partition using the drive tools because it won’t install on a FAT32 partition. Other than that, all should be well.
4. Delete all the files and copy them from the USB key

When the installation is complete, stop VMware and delete all files from Bootcamp.

OS X will still not be able to boot from the Bootcamp partition so we’ll delete everything we’ve done, and copy the files from our USB device (I’m not quite sure what’s happening here, I suspect that we are essentially using VMware to make the drive bootable, but we need a proper bootsector from our USB drive).

In any case, you may run into some problems while deleting because OS X may refuse to write the files on your NTFS drive. I used the Tuxera trial version to get this done (worked like a charm).

Now, copy all files from your USB key onto the Bootcamp partition.

5. Boot into the Bootcamp partition using rEFInd & install Windows normally

The last step is installing rEFInd. This is usually a simple matter of running a shell script, but with Yosemite, this has been complicated a bit.

Go to the download page and download the first option, the binary zip file and unzip it.

Open the terminal, type "cd ", drag the unzipped folder (it’s something like "refind-bin-0.8.3") into it and press enter. Type the following command:


1    sudo bash install.sh –esp

If you’re on Mavericks or earlier this should suffice, but if you’re on Yosemite, you’ll need to do some extra work. Yosemite users should go to "/Volumes/esp/EFI/refind/" and open the "refind.conf" file in their text editor. Find the line that has "dont_scan_volumes" in it. By default this line should be commented out, indicated by a hash sign at the beginning.

Uncomment the line and add two dummy values to it, mine looks like this:

1         dont_scan_volumes foo,bar

Once this has been done, reboot your Mac – it should use the new boot manager automatically. If it doesn’t reboot, hold down alt and select the "EFI Boot" option in the default boot manager.

Once in, select the Bootcamp partition and install Windows as usual. Once done it is a good idea to install the Bootcamp drivers. You can grab them from Apple and install them through your brand-spanking new Windows.

6. Curse Apple a little bit for making this so difficult

Seriously, Apple? There is no need for such complexity here.

First of all, if Macs do offer the opportunity of installing Windows in the first place, and the option to do it via a bootable USB that’s already built in, why hide this from some users just because they have a disk drive? Also, I’m pretty sure that the default boot manager not seeing boot devices is an artificial limitation, it has nothing to do with the Mac not supporting things.

But in any case, hopefully this article has helped some of you who were struggling with installing Windows on your Macs. I can finally play my Windows games from Steam which was kind of the goal of this whole enterprise in the first place!


   
Read More »

Inside the New Razer’s Blade Laptop Computer

For better and awesome performance Razer packs a full mechanical keyboard into a laptop.
If you want hardcore gaming performance, but need it in a system that's portable, if not completely lightweight, then Razer's new Blade Pro could be just the ticket. Razer is calling it the "desktop in your laptop," and they the company has a point.

On the inside, the system packs a quad core Skylake processor, an 8GB Nvidia GeForce GTX 1080 GPU, 32GB RAM, up to 2TB of NVMe SSD storage in RAID 0, Thunderbolt 3, and a 4K G-Sync capable screen. That's a machine that isn't giving much up in performance to most desktop PCs, so already justifies Razer's strapline... but it's the next thing they did that really makes this a laptop desktop.
The Blade Pro doesn't have the usual membrane keys found in laptops. It has a full mechanical keyboard, with switches—not rubber domes—beneath each key. OK, it's still a laptop, so it's a low profile mechanical keyboard with reduced key travel and chiclet style buttons. But it's a mechanical keyboard nonetheless (Razer also has a similar mechanical mechanism for its iPad Pro keyboard). And of course, being a Razer laptop, it's not just a mechanical keyboard. It's a mechanical keyboard that can be lit up with any color of the rainbow. Alongside it sits a giant touchpad.
All this hardware is packed into a unit that's actually surprisingly portable. It weighs 7.8lbs, and is about 0.9 inches thick. I remember a time not so long ago when regular laptops were fatter (and heavier) than that. My current mechanical keyboard is more than an inch deep, and the closest it has to a powerhouse computer is a USB hub!.


There is of course the small matter of the price; it's a little eye-watering. With 512GB of storage, it starts at $3,699/€4,199/£3,499.

Listing image by Razer
Read More »

Samsung unleashes high-end cylindrical desktop computer

Samsung  high-end cylindrical desktop computer

There’s a new black cylindrical desktop in town, but unfortunately for fans of the nearly three-year-old Mac Pro, this one isn’t from Apple. Samsung’s “ArtPC Pulse” desktop, revealed today via Amazon listings, isn’t quite the PC version of the Mac Pro, but that description isn’t far off.

The port layout in particular is distinctly Mac Pro-esque, though not as high-end. It has four USB Type-A ports, one USB Type-C port, an audio jack, an Ethernet port, an HDMI port, an SD card reader, and a power connector arranged vertically on its back. That power plug implies that, like the Mac Pro, the system saves some space on your floor with an internal power supply, which is a nice touch.

One major point of departure is the system’s top layer, which is apparently a 360-degree speaker from Harmon Kardon. The Mac Pro has an integrated speaker, but it’s definitely not a major selling point. Samsung is more interested in pushing the Pulse as an entertainment PC.

Aesthetic comparisons aside, the Pulse is aimed pretty squarely at the high end of the consumer market and not at the workstation market. Both models include quad-core Skylake Core i5-6400 and i7-6700 CPUs, which are solid performers but not replacements for the 6-, 8-, and 12-core CPUs that come with higher-end Mac Pros.

Fortunately, the pricing reflects that fact. The base model Core i5 Pulse costs $1,200, and the high-end Core i7 model costs $1,600. The base model includes 8GB of DDR4 RAM and a 256GB NVMe SSD, while the high-end system bumps that to 16GB of RAM and adds a separate 1TB 5400RPM HDD for additional file storage. Both models include a Radeon RX 460 GPU with 2GB of RAM, an entry-level card which should be suitable for 1080p gaming but not 4K gaming or VR. The Amazon listings don’t mention Wi-Fi or Bluetooth specs, though we assume that they’re included (there’s a button for Bluetooth pairing on the back of the machine above the ports). We’ll update the article if we can find out more.

Perhaps because it doesn’t have quite as much stuff inside it, the Pulse is lighter and slimmer than the Mac Pro—7.4 pounds and 5.5 inches in diameter compared to 11 pounds and 6.6 inches for the Pro. The Pulse's speaker setup makes it slightly taller at 10.7 inches (compared to 9.9 inches).
Samsung is also doing things right on the software side—the Pulse is a Microsoft “Signature Edition” PC, which means a relatively clean install of Windows 10 with few-if-any extraneous pre-installed apps. It’s a nice departure from the company’s Android phones, which come weighed down with Samsung apps that mostly duplicate the functionality of the mandatory Google apps.

Finally, the Pulse has an interesting feature that we won’t know more about until we see official Samsung product pages. You can apparently customize the system with “expansion modules” that help make up for the lack of space inside the case. The only module we’re aware of is the 1TB hard drive module, which comes with the $1,600 model, but we’re not sure what the modules look like, what they’ll be able to do, who can make them other than Samsung, or how many of them will be available.

The Pulse is one of a few different experiments the PC OEMs are doing right now. HP has also made a cylindrical-ish speaker-turned-PC in its Pavilion Wave, and that company’s Elite Slice takes the “modular” idea to its logical extreme. Tightly integrated systems like mini PCs and all-in-ones are one of the few segments of the desktop market that’s growing, so expect there to be more experimentation here as time goes on.

You can pre-order the Pulse now if you want, and it will actually be available on October 28

Read More »