At the core of your Android smartphone, whatever the version, there is a file the properties of which are more than interesting as it allows anyone to make your device show everything, and more. Would you like to change your smartphone’s name ? It’s easy.
Would you like to force the Play Store to open the doors of the Samsung applications ? No problem.
Would you like to turn your Android into a 4.4.2 version (fictitious) ? No sweat.
That and many other things like change the size of the Dalvik cache, change the default language, the launcher when you want to restore the defaults, the quality of your pictures, the frequencies of your wifi connection, and so on…
The Build.prop is a little text file that you can easily modify once you’re root on your device. It is indeed located at the root of the Android system, more precisely in the /System file.
The latter is not too error-sensitive so you’ll be able to configure without help quite a lot of things without taking too many chances, be it bricking it or falling into an unescapable Bootloop. Just be a little cautious – try not to stray on unknown paths, have a plan b on hand. 😉
You don’t need that much, actually. The two main things are the root rights and a file navigator which you’ll be able to use as a text editor. We’ve been talking for a few tutorials about ES File Explorer. It wil be the ideal candidate.
A few words on the Build.prop structure
To begin with, remember this file is loaded when your device is started for the first time. It will remain in memory in the cache so that it’s not loaded every time, therefore each time you do a manipulation, you should empty the cache and the dalvik cache for the latter to become operational.
There are two distinct parts about the Build.prop – the command line and its value. For instance, this is what you’ll see when the line indicates that the smartphone is a Zopo :
ro.product.brand=ZOPO → ro.product.brand is the command line, ZOPO is the variable
If you want to modify a datum, you’ll simply have to replace the variable’s value with the one you’re looking for. Continuing with the device’s brand, you’ll often see Shanzhai (counterfeit) smartphones such as Milais in Antutu wih ‘alps’ instead of ‘MIlais’. Thanks to that little manipulation, you’ll be able to do yourself justice very easily. 😉
Should you want to access Samsung’s play store, you’ll have to modify two data ; the serial number and the device’s manufacturer, for example like this :
ro.product.model=GT-i9500 (this is the Galaxy S4)
Be careful about the difference between ‘brand’ and ‘manufacturer’. If Zopo is the brand, ZWX is the manufacturer.
Other possible applications
Modify your Android version :
ro.build.version.release=4.2.2 that you’ll be able to change into 4.3 or 4.4.2 or even 5.0 without taking any chances.
Although it doesn’t seem like it, I’ve just given you one of the keys to the rigging often met on somewhat underground Chinese devices. It’s something I’ve already seen for myself on Star devices, such as an Android 4.0 ICS which, by sort of waving a magic wand, was turned into a 4.1.2 Jelly Bean. Will wonders never cease.
Change default language to French :
ro.product.locale.language=fr instead of zh
ro.product.locale.region=FR instead of CN
That was about the Build.prop’s main part, which is your smartphone’s informative nerve center.
There is a somewhat denser part called Additional_Build_Properties. The latter will allow you to modify some of the more technical aspects of your smartphone. Values here are very often 0 and 1. 0 means OFF, 1 is for ON. Others values, like 2 and 3, may also pop up ; they mean ON+option. You’ll have to search Google to know which options are present on your command line.
Remember too that you can add commands which haven’t originally been implemented in the Build.prop. Here’s an example that will help your friends and acquaintances when they get mixed up with 06XXXXXXX and +336XXXXXXX phone numbers.
This is a particular case as the variable does not mean ON+option but the number of figures you have to take into consideration after the 0. Here we type 9 but it will also work with 8.
A few last examples :
How to remove an Android debug call when you plug your device with an USB connection to a PC :
How to disable your camera’s shutter sound :
Don’t forget to save your modifications when you leave the text editor, otherwise these will not be acknowledged.
There are other techniques besides a live file access editing ; you can copy the /System/build.prop file in your PC then edit it with Notepad++, for instance. In that case, don’t forget to install the rights back in the rw-r-r mode (see our previous tutorial). Software like Build.prop Editor, and a few others, do the job for you but the interesting thing about these short tutorials is that they help you to discover your device and manage the nitty-gritty. Still, if you think the easy way is more tempting, don’t hesitate to use these applications. There are quite a lot of them at your disposal.
See you soon, and enjoy !
Today, the JTGeek is testing the THL T200C.
√ 8×1.7GHz, octa-core MTK6592 Cortex A7 processor
√ 6.0in HD touch screen
√ 2Gb RAM + 16Gb ROM + micro SD card (32Go max.)
√ 13.0Mp Sony IMX 135, F2.0 rear camera
√ OTG, NFC, GPS, 3G, etc.
On the sciphone Shop Here >> THL T200C
ZTE is probably today’s most ambitious smartphone manufacturer. The Chinese Dragon, as the company has been dubbed, is the world’s fourth telephony service provider and it seems it wants to storm the whole world with its evermore performing technology. We have to admit the Shenzhen manufacturer packs quite a few selling points.
ZTE will probably be the first Chinese manufacturers – or at least one of the first – to launch on the market a smartphone (ZTE Grand Memo 2 for example) which will be compatible with the all-new, high-speed 4G LTE network. Yet today we’ll have a closer look at an altogether different kind of technology, namely the promising 4G hotspots, which many of you are not yet quite familiar with. Our thanks to Hotwire for the info. Hotwire is ZTE’s new official communications manager. Their press release will help us sum up – unfortunately without illos – the performances of the ZTE Flare .
Even if we don’t know exactly how the ZTE Flare will work, we’re positive is a mobile and compact Wifi router which will offer you the maximum comfort you can expect from Data connections on cat 6 4G LTE frequency bands (2,300MHz and 2,600MHz) up to a downstream rate of no less than 300Mb/s… This feat will be made possible thanks to a new, fourth-generation Qualcomm modem called Gobi 9×30 (currently the fastest in the world). This device has been designed to run with any laptop PC or smartphone.
Yet, a 4G LTE, 300Mb/s Hotspot would be but a flash in the pan if it didn’t have a good, adequate Wifi. The latter, a classical 802.11 b/g/n, really labors to exceed 150Mb/s though it’s supposed to reach 540Mb/s. This is when one of Qualcomm’s new chips goes into action ; the Qualcomm Vive 802.11ac, which is dual-band 2.4 and 5GHz EEE 802.11ac/a/b/g/n 2×2 MIMO and will offer a significantly good connection for the 4G LTE network, and this with up to 32 simultaneously connected devices.
If you want to know what such a device will look like, we can show you (see pic above) the ZTE MF91S router and its 2,300mAh battery array or (see pic below) the 2,800mAh ZTE MF93D. They’re currently the manufacturer’s fastest Hotspots, with a 100Mb/s output.
If you’re interested in this Hotspot 4G ZTE Flare, know that it will go on sale as early as Q3. We don’t know yet what its price will be though we think this should smart a little as the current MF91S costs about 300€. 😉
Today the JTGeek will test the handsfree Bluetooth stereo helmet which allows you to listen to and manage your calls and enjoy music.
— Talking time: Up to 13 hours
— Music playing time: Up to 13 hours
— Standby time: Up to 240 hours
— Charging time: 1 hour and 15 minutes
— Working range: 10 meters
Following our latest tutorial, GLG’s video today gives you info on the upcoming 4G frequencies and how they will work on Chinese smartphones.
See you next Wednesday with a new tutorial hosted by GLG.
As we told you a few days ago, IOcean is coming on strong in 2014 with three new octa-core models, an X7S which is only an X7 Elite in an octa-core version. We also had a recent look at the 5.7in X8 which we think is not devoid of charm. Last but not least, here’s the ‘small’ the IOcean G7, the make’s XXL smartphone with its broad screen and its 6.44in Full HD OGS slab. The IOcean G7 will be a direct competitor to the UMI Cross which will as a result age a lot despite the NFC, its sole remaining main asset.
Yet the IOcean G7 will not only be a big device, it will also pack a lot of power, at least as much as its rivals running with Mediatek’s 8×1.7GHz, octa-core MT6592 processor, a 2Go RAM and a 16Go ROM. It’s also to be fitted with a microSD support (up to 32Go). The whole will be powered by Android 4.2.2 and a 3,500mAh battery array. Nearly the legal minimum for this high society.
The IOcean G7 has of course other specifications ; a 13Mp main rear camera (F/2.0 focal-plane shutter and LED flash plus 5Mp front).
What will probably interest you the most is that the G7 will have Dual SIM and will be compatible with the 3G WCDMA (frequency band for France will be 900-2,100MHz) while remaining GSM Quadriband. This device has definitely been made for our French and European lands.
How will the G7 feel in the palm of your hand ? Its dimensions are 175×90.5, it’s only 8.9mm thick and weighs 7.58oz (215g). Not bad. The G7 will be available in black and white very soon. We still do not know its official price though we think it should cost about 230€.