What to Expect from Nokia’s May 14 Event (Lumia 928, 925, EOS) and How Afraid Should Android Be

Once upon a time the largest mobile phone maker and the most profitable player in the business, Nokia has had a nightmare couple of years following Symbian’s ceasing in 2010. In all honesty, it wasn’t the ditching of the OS that turned Nokia from hero to zero, but in fact the platform’s inability to keep up with the times and provide sturdy competition for Android and iOS.

Ever since 2010, the Finland-based giant has bled money fiscal quarter after quarter, reaching a critical point in 2012 when a $ 3 billion net loss was reported. But while a Phoenix-like sudden and spectacular rising from the ashes is nowhere on the horizon, there are reasons for Stephen Elop and his guys to be (fairly) optimistic.

Nokia-May-14

Nokia’s latest financial report, for Q1 2013, showed an encouraging 30% increase in handset sales, confirming the new Windows Phone-based Lumias (especially the 920) are starting to grow on people. But with operating losses still reported, the Finns need to step things up a few good notches before finding themselves way too deep in financial trouble to ever get back on their feet.

Is such a thing possible? Can Nokia recover some of the lost ground to Samsung or Apple? Can the company’s next flagship devices become a real threat for the Galaxy S4 or HTC One? We honestly have no idea what the future has in store, but we may be able to answer some of those questions come May 14 (next Tuesday).

That’s when Nokia will hold a special London press event, teased with two cryptic messages: “The Nokia Lumia story continues” and “See what’s next”. Naturally, the mystery is on as to what will be on display in the English metropolis next week, but here are our best current guesses and their chances of making Android tremble with fear:

Lumia 928

The thing about the smartphone market nowadays is that it’s fairly predictable in many ways, which can lead to boredom and disappointment for people that keep up with the news. Take the Lumia 928.

nokia-lumia-928

This is likely going to be a decent 920 follow-up (or better yet rehash), but it’s been around in the rumor mill for so long that it’s impossible to find one guy still enthusiastic about it. On the flipside, it appears Nokia has understood that too, so chances are the 928 was nothing but a well-concocted diversion to make us look away from the real May 14 stars.

If the 928 will after all be introduced in London next week, its shot at glory is astronomical. The thing will almost certainly come with a 4.5-inch 720p display, dual-core 1.5 GHz CPU, 1 GB of RAM and 2,000 mAh battery, which would have been enough to take on Android’s top-notch devices… a year ago.

Verdict: dud

Catwalk (aka Lumia 925)

Here’s where things get  interesting. Though the Catwalk is rumored to pack essentially the same specs as the 928, chances are it’s going to come with an all-aluminum body and an extremely slender figure (hence the “Catwalk” codename).

And let’s face it, several Android high-enders have a problem with catching the eye of tech aficionados with their somewhat bland designs. Also, unlike the 928, tipped to be a Verizon exclusive, the 925 or Catwalk is said to be a global device. In the US, it will most probably only come to T-Mobile, but we still think Nokia may be on to something here.

Verdict: possible stud

EOS

This big guy was always thought to get a release after the Lumia 925 and 928, but there’s an increasing wave of rumors coming our way of late saying it could be the surprise London show-stealer after all. And what a show we’ll have if this proves to be true, because the EOS is the highly anticipated 808 Pureview cameraphone follow-up.

Nokia EOS

Unlike the 808, the EOS, suspected to be an AT&T-exclusive in the US, will not be all about the camera. Granted, that should still be the main selling point, packing a 41 MP sensor and all that, but a fairly credible source told us at one point Nokia was planning to throw the EOS to the lions with… a quad-core processor.

That would be a first for the Lumia line and Nokia in general and a definite turning point for Windows Phone in its battle against Android. Other possible features include 2 GB of RAM, a larger than 2,000 mAh battery and a 4.5-inch screen, but for now this should be all handled with extreme care and looked at as a wild rumor.

Verdict: definite stud

Max (aka Lumia 625)

I’m sure you’re as baffled as me to hear Nokia may be planning a 4.7-inch mid-ranger (?!?), but the info comes from a rock-solid source, so, even if this fellow won’t be on display in London, it will probably come sooner or later.

But what’s the strategy here? Well, it’s very, very simple. Not everyone can afford high-end, uber-expensive smartphones and, as Samsung has proven in the past few years, there’s loads of money to be made in the entry-level and mid-range niches.

nokia-lumia-625

Yeah, but Nokia already has the Lumia 520 and 720 and they’re both pretty fresh. True, but let’s be honest, how many people do you know that own those things? I know zero. And that’s because, like it or not, the trend is “bigger is better”, even when it comes to budget-conscious handhelds.

Enter the 625, or Max, which rumor has it will come with a modest, but big-ass 4.7-inch WVGA screen, dual-core 1.2 GHz CPU, 512 MB of RAM, 2,000 mAh battery and LTE speeds. A cheap LTE phone with a ginormous display? Count me in.

Verdict: possible stud

What could go wrong?

With three out of four possible May 14 stars having definite stud potential, you could say the future looks bright for Nokia. Only it’s not that simple. First of all, because none of the information presented above is official.

Second, even with decent hardware and lucrative prices, Nokia still has the software problem to take care of. Or, you know, Microsoft. Whoever, but the fact of the matter is people don’t really like Windows Phone 8. It’s too minimalistic, it doesn’t have solid app and game support and some might even call its UI ugly.

And that, boys and girls, is why Android should not really fear Nokia. Yet. But maybe soon… I’ll be honest, I want Android to rule the smartphone world for decades to come, but the only way it’s going to thrive and drive forward is if it’s going to have solid competition. So bring it on, Nokia!

The Droid Guy

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

LLVM/Clang 3.3 Should Be Close To Building Linux Kernel

Developing are reaching a point where the mainline LLVM/Clang compiler in an “out of the box” configuration can compile the mainline Linux kernel with only a few patches against the kernel’s source tree. This summer’s release of LLVM/Clang 3.3 should be a big milestone…
Phoronix

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Intel’s Valley View Should Be In Shape For Linux 3.11

While the merge window on the Linux 3.10 kernel is not even open yet let alone the Linux 3.9 kernel, Intel and mobile enthusiasts already have a reason to look forward to the Linux 3.11 kernel…
Phoronix

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Why enterprises should get involved in the open cloud now

enterprises in the cloud

While startups, developers, and small businesses flock to behemoth public clouds like Amazon Web Services and Google Compute Engine that give them a profoundly efficient bang for their buck, bigger enterprises largely stick to paying the high cost for private clouds. They are wary of potential availability and security issues that, rightfully, could hamper (or cripple) their business. The perceived risk-reward of saving money by turning IT operations over to a public cloud hasn’t yet permeated through to big businesses.

read more

opensource.com

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Why your company should contribute to open source

cube talk

After almost three decades of development, open source software has firmly crossed over into mainstream use. Companies understand the unique value derived from software developed through open communities and are welcoming its use in mission critical settings throughout the enterprise.

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

Which open source software license should I use?

MPL GPL APACHE

I’ve recently been involved in several discussions that are variations on, “Which open source or free software license should I choose for my project?” Here is my way of looking at the large and growing collection of licenses in the wild. First, let’s make sure we all understand that I Am Not A Lawyer. This is not legal advice. Depending upon your needs and your comfort with risk around your software, you’ll want to confirm your legal choices with counsel in your jurisdiction.

read more

opensource.com

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Which open source software license should I use?

I’ve recently been involved in several discussions that are variations on, “Which open source or free software license should I choose for my project?” Here is my way of looking at the large and growing collection of licenses in the wild. First, let's make sure we all understand that I Am Not A Lawyer. This is not legal advice. Depending upon your needs and your comfort with risk around your software, you'll want to confirm your legal choices with counsel in your jurisdiction.
LXer Linux News

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Should Instagram automatically license photos under Creative Commons?

Instagram photo licenses

Should Instagram automatically publish photos under Creative Commons?

Instagram has undergone several big changes lately, most noteably taking away the ability to quickly view Instagram photos on Twitter. Instagram CEO Kevin Systrom described this update during the LeWeb Internet conference in Paris as Instagram’s evolution, and explained that the company would naturally change as it grew.

read more

opensource.com

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Kororaa 17: What Fedora should be

Let’s be realistic for a moment here. I believe that there is not a single Fedora user who doesn’t use repositories that conflict with Fedora’s policy and default selection ideology. Not even the most hardcore Fedora developers can use the completely useless system that Fedora is out of the box, without adding third party sources and pieces of proprietary software.
LXer Linux News

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Why You Should Always Use Nginx With Microcaching

Why You Should Always Use Nginx With Microcaching

Everybody knows how hard is to push out as much as possible from your
webserver(s). In my daily occupation as a hosting engineer that means I
fairly often get the same question, “Wow, cool website, but can it cope
with big-time traffic?”.

HowtoForge – Linux Howtos and Tutorials – Linux

StumbleUponDiggTwitterFacebookRedditLinkedInEmail

Python modules you should know: Pwtools

Next in our series of Python modules you should know is Pwtools. The package is used to generate and test passwords in Python programs.
LXer Linux News

StumbleUponDiggTwitterFacebookRedditLinkedInEmail