24 Peachy Free Linux Games (Part 2 of 4)

Linux has an ever-expanding library of thousands of free games, many of which are released under an open source license. A good selection of these titles are entertaining, highly addictive, offer captivating gameplay, and are most importantly, great fun to play. Identifying entertaining and challenging games is something that we have a passion for.
LXer Linux News

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Node.js integrates with M: a tutorial, part two

M database and node.js

In part one of this tutorial, I introduced the integration between the hierarchical data structures of the M database and the hierarchical structures of the Node.js language.

Here, in part two, I focus on the fact that this integration is equivalent to incorporating persistance storage in the Node.js language using a data model similar to JSON structures. This built upon a proven database that is known to deliver high performace for demanding applications.

read more

opensource.com

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

The Devil’s in the Cloud, Part III: The New Dark Ages

When the New Year’s Day sun rose in Europe and the United States, the reality of what had happened was hidden to almost all. Only a hundred or so targets had been struck, and the smoke from the ruins that remained was already dissipating. What people did immediately realize was that certain things that they were used to working now did not.
LXer Linux News

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Node.js integrates with M: a tutorial, part one

M Language and Databse

We have talked recently about the significance of integrating the Node.js language with the powerful M database, particularly in the space of healthcare applications.

The efficiency of Node.js combined with the high performance of M, provides an unparalleled fresh approach for building healthcare applications.

Here is how you can try this today:

read more

opensource.com

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Common Basic Android Terminal Commands Every Android Owner Should Know – Part 2 of 2

Those of you who read through the first part of the Common Basic Android Terminal Commands Every Android Owner Should Know post are aware that we covered five basic terminal commands device owners should know. Just to recap these were the: adb devices command, the adb push command, the adb pull command, the adb reboot command and the adb reboot – bootloader and reboot recovery command. This article discusses  the remaining five terminal commands namely:  the fastboot devices command, the fastboot OEM unlock command, the adb shell command, the adb install command and finally the adb logcat command.

 

6. The Fastboot Devices Command

The Android Debug Bridge (adb) no longer works when users are working on the bootloader. As such Android users that find themselves not booted in to their devices with the debugging tools not active to communicate with have no alternative but to use the fastboot command in place of adb. Fastboot is generally the most power tool available for the Android device however it can be typically observed that most Android devices do not come with this function enabled.

Android Fastboot

If your device happens to be fastboot enabled it is important to ensure that there is communication between the two. This is where the fastboot devices terminal command comes in to play. All an android device users need to do is key in “fastboot devices” at the prompt so as to receive a serial number much like in the Android Debug Bridge (adb) devices command we coved in part one of this article. If it seems like things are not working and you happen to be a Windows users then the most probably reason for this is that you may have a driver issue. Under such a circumstance heading online to look for a solution in the numerous forums dedicated to offering this type of assistance is the best place to start when trying to sort things out.

 

7. The Fastboot OEM Unlock Command

The OEM (Original Equipment Manufacturer) unlock command which is considered by most users the holy grail of Android commands  and helps users do one thing and one thing alone – which is unlock  Nexus devices (or a HTC device using the official HTC RUU tool). For those of you out there using devices from different manufacturers this Android terminal command will not apply to you. Such individuals have to source for a different tool or method of unlocking things e.g. through the use of ODIN (a computer software program used by Samsung in installing different firmware on devices via USB), .sbf (system binary files) or RUU (ROM Update Utility).

This article includes the Fastboot OEM Unlock Command as one of the basic terminal command that every Android owner should know because even though you as an individual users may not need it, this terminal command constitutes an important part of Android openness. Google is not concerned with what phone and tablet buyers do with the devices they have bought and as such include a simple way to crack them open. This is something we don’t usually see from many tech companies and such constitutes the main reason why most people choose Android.

Using the Fastboot OEM Unlock Command is fairly simple. Once you have ensured that your device and computer are communicating with the fastboot devices command discussed above you have to do is key in “fastboot oem Unlock” at the prompt and press enter. This action will present you with options so make sure you read through them carefully and select wisely.

Tip: Using the “fastboot oem unlock” will erase everything on your device.

 

8. The Android Debug Bridge (adb) Shell Command

This command usually confuses a lot of Android device users because there are basically two ways to use the Android debug bridge (adb) shell command, these are:

  • where the user actually enters the device command shell from their terminal and
  • where the user sends a command to the device to run its own command line shell

Android Shell

Source:

This image above illustrates a scenario where a user is inside the device shell listing the folders and files on their device. Getting to the point illustrated above is fairly simple. All one needs to do is key in “adb shell” and hit enter. Once in, a user can escalate themselves to the root if they need to. It is important to point out and further stress that adb shell command users need to exercise extreme caution here particularly in the case of those individuals who are not familiar ash or bash shells since thing can quickly turn bad if not careful. For those of you who are not familiar, ash and bash are command shells a lot like those used by Mac and Linux computer users. They are nothing like DOS.

The second way to use the adb shell command is in conjunction with one the ash commands that Android devices can run. This method of employing the adb shell command is typically used for more advanced tasks such as running tasks, changing permission on files and folders etc. Using the command is easy – “adb shel <command>”. An illustration of this would be altering the permission on a file as such: “adb shellchmod 666/data/filename”. As mentioned above it is important to remember to be extremely careful when using these commands.

 

9. The Android Debug Bridge (adb) Install Command

While the adb push command enables users to copy file to their Android devices, the Android debug bridge (adb) install command actually installs APK (Android PacKage i.e. .apk) files. Using the adb install command is very similar to using the adb push command since users need to provide the path to the files they wish to install. What this means is that it is always simpler to drop the application you want to install in to your tools folder than taking the longer approach that requires you to keying in the path. Once this is done, the next step involves you telling your device to sideload (this means installing apps without using the official Android Market) as such “adb install AppName.apk”.

To update an application you should use the -r switch i.e. “adb install –r AppName.apk”. There is also the -s switch which allows users to try install apps on their SD card if their ROM supports it and the –i switch which enables users to forward lock the application (i.e. install to/data/app-private). There are a number of other advanced encryption switches however those are left for discussion in another article.

To conclude with the adb uninstall command allows users to uninstall applications by their package name as such “adb uninstall AppName.apk”. This terminal command has a switch of its own too which is the –k switch. Using the –k switch however only helps users to uninstall the application but retain all the cache and application data in place.

 

10. The Android Debug Bridge (adb) Logcat Command

To some Android device users the adb Logcat command is one of the most useful terminal commands out there. However this command just prints a heap of gibberish unless one fully comprehends what they are looking at. This command enable users to return the events written to different logs in the functioning of Android systems and as such offers invaluable data for system debuggers and application developers. Most Android device users will only run this command when requested by an application developer nevertheless it is still important for device owners to know how to appropriately use it.

In order for a device owner to view their log out put on a computer screen they simply need to key in “adb logcat” and press enter. Though things may scroll down quite fast and as such affecting the chances of users finding what they are looking for there are a number of ways in which this can be dealt with, these are through the use of filters or text output. Filter switches are used when application developers have placed tags in their apps and wish to view what event logs are indicating about it. If needed most developers generally tell users what tags to append to commands. The text output approach on the other hand comes in handier since it allows users to log to a .txt file on their computers to allow for easy reading or access later. This command can be used as such: “adb logcat>filename.txt”. Users can let this command run while they do whatever it takes to crash the system program or application they are debugging, once done the command can be closed by hitting the CTRL + C Keys. The full log file can be found saved in the directory a user is working from e.g. the tools folder. This is what should be sent to the developer.

It is important to remember that sensitive data may be contained in the log files and as such it is vital to ensure that you trust the individual you are sending them to. Alternatively users can simply open log files in text editors so as to view what information is included and edit it accordingly.

There are numerous other switches for the logcat command that savvy developers can choose between. Some of the switches include: radio logs or main event, rotate log files on user device or computers and verbosity logs that allow users to change the verbosity of log entries and so much more. Some of these methods are slightly advanced and require users to read through the Android developer documentation before use.

 

Sources:

github

XDA Forums

Android Central

Stack Overflow

 

The Droid Guy

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Samsung Galaxy S3 problems, questions and solutions – Part 3

We never thought that our articles about Samsung Galaxy S3 errors and solutions published a couple of days ago will keep us busy answering some of our readers’ questions. This is the third article dealing with most common problems Galaxy S3 owners have encountered. Follow links below for the first two parts:

  1. Samsung Galaxy S3 Errors you may encounter; solutions and workarounds provided — Part 1
  2. Samsung Galaxy S3 problems, solutions and workarounds – Part 2

galaxy-s3-brown

Galaxy S3 Proximity Sensor Error/Glitch

Reader’s Problem: Hello I’m having a problem with my Samsung Galaxy s3 with phone calls, it’s when some one rings me or sometimes happens when I call them that I can’t hang up calls when I’m finished my call, screen just goes back, can’t touch to relight up screen and no buttons will work anywhere on phone. When other end is hung up around 5 seconds delay, then phone lights back up and is normal again. Probably sounds silly but hope you can help. Cheers, Ben.

Explanation: Proximity sensors were added to smartphones to make them even smarter. In Samsung Galaxy S3′s case, this sensor comes into play during calls. If the device detects it is near the owner’s face, the display automatically shuts off while keeping the call active. There were a few reported cases of proximity sensor glitches in S3 and they happened during Ice Cream Sandwich days. While it is a simple glitch, it is annoying because owners would have to wait a few seconds before the phone becomes active again.

Solution:  Since it is a software-related problem, an update would fix this issue. Owners are advised to go to Settings => About phone => Software updates. The phone will then scan for updates and if there is one, owners can initiate without having much of a problem.

Workaround: Just in case an update is not available and owners cannot stand experiencing this glitch, they are advised to turn the proximity sensor off.

How to disable Proximity Sensor in Galaxy S3

Step 1: Tap on Phone icon to launch the Phone app.

Step 2: Tap on Menu key, left of the Home button.

Step 3: Choose Call settings option.

Step 4: Uncheck Auto screen off during calls option.

This is the most common workaround to keep the phone’s screen active during calls.

Set Specific Music Folder in Galaxy S3

Reader’s Problem: I read your help on problems with Galaxy S3 music player but I have another problem. When I play my music on shuffle the phone includes all sound recordings, not just the ones in music player. As I have a Birds of Britain app on my phone with 286 bird song recordings on it listening to music is hilariously interspersed with quacks,  tweets, whistles and warbles. Any thoughts? Thanks, Anna.

Explanation: Android’s stock music player detects all audio formats and adds them to the playlist. While applications’ data are saved in a specific directory unreachable by the music app, problems like this happen when owners make a backup or their apps. All data will be archived in the SD card without being compressed. Thus, the music app can now detect the audio files of the apps and add them automatically to the playlist.

Workaround: I, too, am waiting for the day that the Android stock music app can choose a specific music folder and not scan the device’s entire internal memory or SD card to find audio files. The most common workaround is to delete unwanted audio files from the playlist. But my advice is to use a third-party music app. For this problem, I highly recommend Mixzing application. It is a free app from the Play Store and users can specify which folder the app needs to scan for audio files.

Install Adobe Flash Player in Galaxy S3

Reader’s Problem: I have tried everything that I’ve been advised and nothing works. I had flash before, my husband also has it on his S3, but after Verizon did a hard reset, I lost it. And now unable to find a good link to install it back onto my phone. Could you please help? 

Explanation: It was in August last year that Adobe announced it would stop support for its Flash Player on Android. Consequently, manufacturers and carriers released updates that took away the support for the flash player. So, basically, this is a global problem. Good thing we the XDA Developers who always have solutions for problems like this.

Solution: You can either install apps from the Play Store that claim to support flash or you can follow the guide our friends at XDA Dev forums offer.

Unbrick Samsung Galaxy S3

Reader’s Problem: One of our readers said the electricity was cut off (consequently his internet was cut off, too) while he was updating his device. So, his phone was bricked. 

Explanation: It is not a rare case. In fact, many people have experienced this problem. The thing is, when the update process is interrupted and was completed, some system files are missing in the phone so the operating system couldn’t load completely. Fortunately, it is easy to unbrick Galaxy S3.

Solution: Owners need to flash the official firmware using the Odin tool. Just follow the steps below.

Step 1: Download Odin and launch it as Administrator.

Step 2: Download official Galaxy S3 firmware. If you’re in the U.S. and is under a network, choose one from these firmware packages: T-Mobile | AT&T | Sprint. You need to extract contents of these packages.

Step 3: Turn your Galaxy S3 off and boot it into the Download Mode: press and hold HOME and VOLUME DOWN buttons while tapping the POWER button.

Step 4: Connect your device to your computer. If the connection is good, one of the ID:COM boxes turns yellow. Otherwise, make sure all drivers are installed and repeat this step.

Step 5: Under the Option section in Odin UI, check Auto Reboot and F. Reset Time.

Step 6: Click on PDA button and browse through the directory you extracted contents of the official firmware and look for “.tar” file.

Step 7: Click on START button to begin flashing of the official firmware.

Step 9: Wait until your phone is automatically rebooted before you use it.

Galaxy S3 Shuts Off Occasionally

Reader’s Problem: Wife and I both have the galaxy s3 running verison 4.1.1, from time to time it will just shut down and kick off have to take the battery out to reboot.

Explanation: There could be plenty of reasons why Galaxy S3 behaves this way. Others complain their phone reboots by itself from time to time.

Solution: The first solution we can recommend on this problem is try to reset the device into factory settings. It may be a hassle to back up all your data but it’s worth a try. If it doesn’t work, try to check if there is an available software update. More often, updates bring a lot of bug fixes. Lastly, contact your provider and have your unit be replaced with a new one.

MailBag

Have other Issues with your Samsung Galaxy S3? please share with us either via email at mailbag@thedroidguy.com, or simply leave a comment below.

We have also answered a few user questions in subsequent posts:

Samsung Galaxy S3 Errors & Solutions Part I

Issues addressed in this article:

  • “No SIM” error
  • “Insufficient Internal Memory” error
  • S3 message app error
  • Sprint Galaxy S3 Error Code 97
  • WiFi authentication error
  • play store error
  • OTA update error
  • USB hardware ID error

Samsung Galaxy S3 Errors & Solutions Part II

Issues addressed in this article:

  • headphone issues
  • TouchWiz freezes
  • internet connection
  • mic volume issue
  • music problem

Samsung Galaxy S3 Errors & Solutions Part III

Issues addressed in this article:

  • sensor error
  • music folder
  • install adobe flash
  • unbrick phone
  • phone shuts off occasionally

Have Other Questions?  Answers may be in our How To section.

Samsung Galaxy S III for $ 0.01 (with contract)

Price Disclaimer
Prices are accurate as of less than 12 hours ago. Product prices and availability are subject to change. Any price and availablility information displayed on Amazon.com at the time of purchase will apply to the purchase of any products.

Amazon Image
The Droid Guy

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Android developers invited to take part in ‘BlackBerry 10 Last Chance Port-a-thon’ this weekend

Android Central

Porting and running Android applications on BlackBerry hardware is nothing new. Since the inclusion of an Android App Player in PlayBook OS 2.0, Android developers have had an additional outlet to which they can distribute their creations with minimal time and effort. Indeed, we first got our Android eye on things a little under a year ago at BlackBerry Devcon Europe.

Things in the BlackBerry camp are starting to kick up through the gears of late — they're having some kind of launch, if you hadn't heard — and the final push to have apps on BlackBerry 10 at launch is upon us. Having held 2 previous "port-a-thons," the folks at RIM reached out to us with word of the final app-porting event before the big launch. All kinds of app developers are invited to take part, including of course Android developers.

There's cash up for grabs for those taking part too, with no need to wait until users start buying your BlackBerry 10 apps after launch. Each approved app will net the developer a cool $ 100, up to a maximum of 20 apps. So, if you've a whole portfolio of Android apps to port across, by our math that's a cool $ 2000 you could make this weekend. Not bad. Not to mention the repeated promises of success for app vendors on the BlackBerry platform. 

Additionally, everyone who submits 5 or more approved apps will be entered into a random draw to stand a chance at receiving one of 250 limited edition BlackBerry 10 devices. One entry is received for the first 5 apps, with an additional entry for each subsequent approved app. 

To register for the "BlackBerry 10 Last Chance Port-a-thon" hit up the link below where you'll find everything you need to know. There's a few steps to take ahead of time, such as requesting signing keys and register as a vendor for BlackBerry World. 

BlackBerry 10 will launch to the world on Jan. 30. Our sister site, Crackberry, is all over it as only they can — to the point they have a launch campaign headquarters — so you're going to want to keep it locked there in the coming weeks. 

More: Register for BlackBerry 10 Port-a-thon, Crackberry


Android Central – Android Forums, News, Reviews, Help and Android Wallpapers

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

What Linux Users Are Saying About GNOME In 2012 (Part 1)

With the 2012 GNOME User Survey now officially over, here’s the start of the results. In this posting are the first (of two) batches of feedback that users supplied while filling out the survey. This year there were 4,494 people participating in the annual yet independent GNOME survey. Of the nearly 4.5k respondents, 1,950 of them also provided feedback with this first batch consisting of the first one thousand responses. The results from the survey in full will also be published this week.
LXer Linux News

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

What Linux Users Are Saying About GNOME In 2012 (Part 1)

With the 2012 GNOME User Survey now officially over, here’s the start of the results. In this posting are the first (of two) batches of feedback that users supplied while filling out the survey. This year there were 4,494 people participating in the annual yet independent GNOME survey. Of the nearly 4.5k respondents, 1,950 of them also provided feedback with this first batch consisting of the first one thousand responses. The results from the survey in full will also be published this week.
Phoronix

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Android development using jEdit part 1

While there are many good IDEs for android development like eclipse, NetBeans, intelliJ; sometimes one may want to use lightweight editor to create android apps and still don’t want to get into command line every time.
LXer Linux News

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Linux Essentials for Windows Administrators – Part 2

There’s no such thing as a homogeneous server environment. Windows administrators must learn basic Linux commands and navigation to support a contemporary network.
LXer Linux News

StumbleUponDiggTwitterFacebookRedditLinkedInEmail