National Conference on Competition & IPR in ICT, Telecom & Mobile Sets

praskrishna — 2016-05-30T01:50:19Z

Rohini Lakshané and Anubha Sinha attended this conference held at Vigyan Bhawan in New Delhi on May 18, 2016. The event was organized by CMAI.

This was a specific conference dedicated to Make in India especially Mobile, Telecom and role of Competition v/s IPR. The speakers were from CCI, Industry and Legal luminaries. There is a need to arrive at balance between Competition and IPR. The conference was aimed to address the issues of IPRs v/s competition, role of SSO in standard settings, SEP’s contentions, basis of FRAND negotiations and need to recommend to Government to form an appropriate policy that is suitable for Make in India.

The conference focused on the need to discuss these issues with all the stakeholders and come out with appropriate status on the date and its relevance on Make in India and appropriate recommendations to the government. Further details of the conference can be accessed here.

For more details visit https://cis-india.org/a2k/news/national-conference-on-competition-ipr-in-ict-telecom-mobile-sets

Sub$-100 Phones: Browser Compatibility Tests

rohini — 2017-02-16T16:47:02Z

This post documents the results of browser compatibility tests conducted on six out of eight specimen mobile phones being studied under the Pervasive Technologies project. These phones are Internet-enabled and cost the equivalent of USD 100 or less in India. Rohini Lakshané and CIS volunteer Dhananjay Balan carried out the tests. Intern Shreshth Wadhwa provided assistance.

Names and descriptions of mobile phones under study: Annexure 1
How the phones under study were chosen: Section 3.2: Criteria for choosing the mobile phones

Research Question:

What technical standards are browsers pre-installed in the eight test phones compatible with?

This question partially answers research question #2 in Methodology: Patent Landscaping in the Indian Mobile Device Market, that is, what patents pertain to [technical] capabilities commonly found in networked mobile devices sold in India for USD 100 or less?

Method:

We conducted tests on all browsers pre-installed, that is, installed by the manufacturer, on six mobile phones to understand their extent of compliance with technical standards for the web. All browsers were tuned to their default settings and no plugins or extensions were installed in them. The tests could not be run on two phones for reasons stated in "Limitations".

For Android v4.0 (Ice Cream Sandwich) and higher versions, we set up a local host and automated all the tests by using a script. The local host was set up to expose sample HTTP endpoints. We tested all browsers through this server.

A Shell script was used to acquire screenshots of the results of the tests:
#!/bin/bash

adb shell screencap -p $1
adb pull $1

We collected screenshots of devices with Android versions below v4.0 by capturing the framebuffer since the shell command was introduced in v4.0.

Script: Github - https://gist.github.com/dbalan/e58f51b713bfd6d711fd02061e27ca90 or Download as .zip.

Android version numbers, where applicable, can be found in the “User Agent” row of the test results. We took photos of the screens for the rest of the devices.

Standards and capabilities tested:

Browser Network Support

HTTP/1.1
HTTP/2
SSL

Acid Tests

Acid tests 1, 2, and 3 (http://www.acidtests.org) were run on all phones.

Acid 1 tests for compliance to the CSS 1.0 standard; Acid 2 for HTML 4, CSS 2.1, PNG, and data URLs. Acid 3 for SVG, HTML, SMIL, Unicode, DOM, ECMAScript (Javascript), and CSS 3, among other parameters. Here is the full list of specifications tested by Acid 3: http://www.webstandards.org/action/acid3/x

Image Formats

JPEG
GIF
PNG

Results

View as .ods; View as .xls

Reading the results:

User-agent string

Example 1: Micromax Canvas Engage A091
User-agent: Mozilla/5.0 (Linux; Android 4.4.2; Micromax A091 Build/A091) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.114 Mobile Safari/537.36

Mozilla/5.0: Mozilla Firefox browser, version number
This is a user-agent token.

Linux: Linux kernel

Android 4.4.2: Operating system, version number

Micromax A091: Device ID

Build/A091: Build number.

This is a customised Android build by Micromax. (Build numbers of stock Android 4.4.2 are KOT49H and KVT49L).

AppleWebKit/537.36: WebKit, version number. WebKit by Apple is a component of a layout engine that renders web pages in browsers. It is based on KHTML.KHTML: HTML layout engine developed by KDE. Licensed LGPL.

like Gecko: A browser that behaves like a Gecko browser

Chrome/34.0.1847.114: Chrome for Android browser, version number

Mobile: Either mobile browser or mobile device, or both

Safari/537.36: Apple Safari browser, version number

Example 2: Opal Cyher-Shot NX900
User-agent: Dorado WAP-Browser/1.0.0/powerplay/2

Dorado WAP-Browser/1.0.0: User agent key, version

This is a WAP browser for mobile phones based on a Java engine.

Observations:

Browsers pre-installed on phones of Indian brands comply with all technical standards and capabilities tested for. All of these phones -- Intex, Lava and Micromax -- also run on the Android operating system. In the case of failed tests, the results are the same or similar for most mobile phones. For example, Opera Mini 7.5 on Intex Aqua N15 and on Micromax Canvas Engage A091 scored 97/100 in the Acid3 test. This is in line with the results released by Acid for Opera Mini 7.5 and also by the Browserscope project for profiling web browsers.

Awang, Yestel and Opal are brands from China or Hong Kong. The only pre-installed browser on Awang A808, an Android v2.3 (Gingerbread) phone, also cleared all tests but one. It scored 95/100 in the acid3 test, which is the case for the Firefox browser on most Gingerbread phones. The browsers on non-Android phones Yestel and Opal failed the tests for Acid1, Acid2, Acid3 and HTTP2, which indicates that while these phones are technically Internet-enabled, their users do not enjoy many of the benefits of the modern web.

Screenshots or photos of results:

View photos and screenshots
The name of the file is in the format: <name of browser>_<name of format/ acid test with number>.<file extension>
In the case of default browsers, <name of browser> appears as “android”.

Limitations:

Eight phones were under study. However, one of the phones (HiBro) did not contain a pre-installed browser. The only way to access the Internet on this phone was through pre-installed apps such as Facebook.

The operating system of Kechaoda K16, which was Java-based, did not yield to the script used for running the tests. It had one pre-installed WAP browser. Both these phones were excluded from the tests.

Screenshots could not be obtained for the results of tests of two phones, Opal Cyher-Shot NX900 and Yestel Q5S+. We took photos of their screens instead.

For more details visit https://cis-india.org/a2k/blogs/sub-100-phones-browser-compatibility-tests

Centre for Internet and Society