by admin

Native Android style in Qt 5.4

December 6, 2014 in C++, News, Programming, Qt by admin

qtvia blog.qt.digia.com:

As you might have heard, the upcoming Qt 5.4 release delivers a new Android style. This blog post explains what it means in practice for different types of Qt applications.

Qt Widgets

Earlier it has been possible to get native looks for Qt Widgets applications on Android with the help of Ministro, a system wide Qt libraries installer/provider for Android. In Qt 5.4, selected parts of Ministro source code have been incorporated into the Android platform plugin of Qt. This makes it possible for Qt applications to look native without Ministro, even though applications wishing to use services provided by Ministro will continue to do so. In other words, Qt Widgets applications will look native regardless of the deployment method; system wide or bundled Qt libraries. Read the rest of this entry →

by admin

Mile High Milestone: Tegra K1 “Denver” Will Be First 64-bit ARM Processor for Android

August 12, 2014 in Android, Hardware, News by admin

From nvidia.com:

Our 32-bit Tegra K1 mobile processor has been racking up praise for bringing amazing performance and true console-quality graphics to the mobile space.

It “handily beats every other ARM SoC” in GPU performance benchmarks, according to Anandtech. And “the GPU performance is what stands out with the Tegra K1, nothing else on the market today is really able to get even close,” according to PC Perspective. Read the rest of this entry →

by admin

Anatomy of a Qt 5 for Android application

July 25, 2013 in Android, Qt, Tutorial by admin

qt

There is a nice article by  on the digia qt blog explaining the anatomy of a Qt5 Android application.

Some of the areas discussed are a general overview of major parts composing a Qt5 Android application, a description of the Android application launcher and some insights about how QtCreator sets up the application and also some information about the Qt part of the entire puzzle.

Also, the entire startup of the application is described quite in detail and also the various deployment methods which can be used.

For more information and the entire article, please follow this link.

by admin

CyanogenMod 10.1.1 Released – fixes for vulnerabilities that can bypass check for a digital signature

July 12, 2013 in Android, Linux, News, ROM by admin

cyanogen-modGiven all the Android security topics in the news, we thought it prudent to issue a follow-up to the 10.1.0 general release, incorporating patches for various vulnerabilities that have since been identified.

t the time of this post, CyanogenMod 10.1.1 releases are building and mirroring to our download portal. The CM 10.1.1 build is purely a security bug-fix release on top of the previous 10.1.0.x code-base. While it does not carry any new features, it does address the following:

  • Bug 8219321 aka “MasterKey” exploit (also patched in CM 7 and CM 9 source)
  • CVE-2013-2094 (Linux kernel exploit)
  • CVE-2013-2596 (Qualcomm-specific exploit)
  • CVE-2013-2597 (Qualcomm-specific exploit)
  • General device bug-fixes

With the security nature of this release, all users on CM 10.1.0.x are encouraged to update once their respective build is available

 

Source: here.

by admin

Using Google’s repo tool with in own projects on BitBucket

April 12, 2013 in Code Snippets, Source Code, Tips & Tricks, Tutorial by admin

Using Google’s repo tool with in own projects on BitBucket

There are couple of ways to manage projects which are split in multiple repositories, of which the two most known are probably git submodule, git subtree, each with it’s own list of pros and cons. One such tool is Google’s Repo wich was created to manage the large Android project in a way which would allow easy replacement of modules, easy addition of new modules, access control, and so on. Some of the things which repo allows are checking out multiple projects from a manifest file, updating them, branching, sending changes from multiple different projects as a single changeset.

A more detailed description of the this command and various other information related to using repo with the Android project can be found here.

Let’s consider a project composed of two repositories, test/a and test/b stored on bitbucket. Once created, their URL will be something like:

git@bitbucket.org:[an user name]/test-a.git
git@bitbucket.org:[an user name]/test-b.git

where the ‘/’ in the project’s name was replaced with ‘-‘.

In order to be able to use Repo, you’ll need to download it from http://git-repo.googlecode.com, copy it to a suitable location and make it executable or from command line:

curl http://git-repo.googlecode.com/files/repo-[the last version] > repo
chmod a+x repo

Repo’s information about a project is stored in a manifest file, default.xml by default if no other name is specified. The file structure is rather simple. Bellow is a sample file for a hypotethical project hosted ob BitBucket []:

<?xml version="1.0" encoding="UTF-8"?>
 <manifest>
     <remote name="bitbucket" fetch=".."/>
     <default revision="refs/heads/master" remote="bitbucket" sync-j="4"/>
     <project name="test-a" remote="bitbucket" path="a>
     <project name="test-b" remote="bitbucket" path="b"/>
 </manifest>

As you can see, first at least one remote needs to be defined, which will be used to fetch the projects. The name should be something meaningful for you, while fetch should contain the URL to the repository from where the projects will be fetched. The reason why we specified “..” will be explained bellow.
Then we need to add a default revision definition for the remotes we defined, and then follow the list of projects. The defaults are useful since in case no revision is defined for a project, the default one will be considered.

In the project definition the path specifies the path where the given project will be cloned and will be automatically created if does not exists. The project name is the path and the name of the project, without the .git part, which will be appended automatically. The full URL of the project’s repository will be {the url provided to remote fetch}/{projec name}.

Once this file is created, we need to store it on bitbucket in a repository, for example test/repo, the repository URL being like:

git@bitbucket.org:[an user name]/test-repo.git

This being complete, the configuration part is done. Time to clone the project. For this, we need to create a folder, and inside that folder we’ll need to initialize repo by running this command:

repo init -u git@bitbucket.org:[an user name]/test-repo.git

This will download the manifest from the specified URL using git and create a .repo folder inside your folder, then will clone the project you specified after the -u flag and try to find and store the manifest file (default one being default.xml).

The reason why we specified the “..” for the fetch is as because in this case the it will be considered relative to the URL we specified at the init moment. Remember that earlier I said the project’s repository will be {the url provided to remote fetch}/{projec name} ? In our case {the url provided to remote fetch} will be git@bitbucket.org:[an user name]/test-repo, and in order to be able to specify an another project, we need to go one folder higher, which would mean relative path “..”. When composed together with the project name, we’ll end up with something like git@bitbucket.org:[an user name]/test-repo/../test-a.git which is same as git@bitbucket.org:[an user name]/test-a.git, the right path for our test/a project.

Once this is complete, we can download the projects by running

repo sync

which will clone all the configured projects. From here you can use the usual git commands to commit & push stuff in various projects or use the repo commands for the repo’s functionality.

Note: while git allows you to clone a bitbucket repository with ssh://git@…., it won’t work with repo. If you specify the repository for the manifest file, the repo won’t be able to find te repos of the configured projects.

More information about Repo’s commands can be found here

Source here.

PanoramaGL library Android update

February 28, 2013 in Android, OpenGL by Adrian Marius

The supported features in PanoramaGL version 0.1 are:

– Tested with SDK 2.x to 4.x

– Support for architectures ARM, x86 and MIPS.

– Supports OpenGL ES 1.x

– Supports spherical, cubic and cylindrical panoramic images

– Allows scrolling and continuous scrolling

– Supports scrolling left to right and from top to bottom using the accelerometer

– Allows to use the inertia to stop scrolling

– Supports zoom in and zoom out (moving two fingers on the screen)

– Supports reset (placing three fingers on the screen or shaking the device)

– Allows you to control the range of camera rotation in the x and y axis

– Support for view events

– Support for hotspots

– Support for sensorial rotation (Only compatible for devices with Accelerometer and Magnetometer)

– Support for simple JSON protocol

 

Please check

by admin

Samsung Galaxy Altius smartwatch screenshots leaked

February 15, 2013 in News, Rumors by admin

galaxy-altius-lg1 Screenshots purported to be from a forthcoming smartwatch from Samsung have emerged on a Korean messageboard. Spotted by Slashgear, the Samsung Galaxy Altius looks as though it will give users quick access to date and time, music playback controls, and email notifications. If accurate, the leak suggests that Samsung, like Apple, could well into the development of the next generation of wearable smart devices.

For more information and screenshots follow this link.

Android port of the Firebird Jdbc driver (Jaybird) 2.2.2 is released

February 15, 2013 in News by Adrian Marius

New version for Android Jaybird is released This is a port of the Firebird Jdbc driver (Jaybird)

You can check what is new in Jaybird 2.2.2 from the official announcement page

 

 

by admin

HP bids adieu to WebOS, Windows RT, and says hello to Android

February 15, 2013 in News by admin

android-200x150-200x150While HP still hasn’t made it official, sources are reporting that HP has decided that at least part of its tablet and smartphone future lies not with Windows or WebOS but with Google’s Android. Who’d thought it!?

Source: here.

 

 
Skip to toolbar