Advertisment
Browsing this Thread:
1 Anonymous Users
LucaRocchi
- Started insulating
- Joined: 2012/8/31 20:29
- From Milan, IT
- Group: Registered Users Webmasters
- Posts: 2228
- Posted on: 2013/12/11 10:51
Motorola MotoG
#1
Available from tomorrow here in Italy, 199€ 8GB version.
Dimensions: 129.9 x 65.9 x 11.6 mm (5.11 x 2.59 x 0.46 in)
Weight: 143 g (5.04 oz)
Display: AH IPS
Display size: 720 x 1280 pixels, 4.5 inches (~326 ppi pixel density)
Protection: Corning Gorilla Glass 3
OS: Android OS, v4.3 (Jelly Bean), planned upgrade to v4.4 (KitKat)
Chipset: Qualcomm Snapdragon 400
CPU: Quad-core 1.2 GHz Cortex-A7
GPU: Adreno 305
RAM: 1GB
More spec
I don't like try stuff at D1, but sounds very interesting..there are products with same price/perfomance ratio?
No LTE, but who cares..specially for where I live.
LucaRocchi
- Started insulating
- Joined: 2012/8/31 20:29
- From Milan, IT
- Group: Registered Users Webmasters
- Posts: 2228
- Posted on: 2013/12/15 8:51
Re: Motorola MotoG
#3
Quote:
rewarder wrote:
I couldn't live with a smartphones that has "only" 1GB memory.
uhhm maybe, I mean is personal and depends from your usage..and from what you were using before.
In other words, I had XperiaRay (=Desire, same HW), single core, +2y old and 512 mb ram (384 available (?)). MotoG is not supertop smartphone but from single to quad is unbelivable experience
Beyond the perfomance, this side is quite interesting for me:
I'm around 40th hour and I have still battery.
Attach file:
(81.15 KB)
LucaRocchi
- Started insulating
- Joined: 2012/8/31 20:29
- From Milan, IT
- Group: Registered Users Webmasters
- Posts: 2228
- Posted on: 2013/12/16 11:51
Re: Motorola MotoG
#5
Yes and according to our chart, is fast like a N4 
rewarder
- Webmaster
- Joined: 2004/7/5 10:54
- From Zürich CH
- Group: Registered Users Webmasters
- Posts: 3193
- Posted on: 2013/12/16 11:53
Re: Motorola MotoG
#6
Quote:
LucaRocchi wrote:
Yes and according to our chart, is fast like a N4
I guess I really have to change that benchmark ...
LucaRocchi
- Started insulating
- Joined: 2012/8/31 20:29
- From Milan, IT
- Group: Registered Users Webmasters
- Posts: 2228
- Posted on: 2014/1/15 8:06
Re: Motorola MotoG
#7
Update last night to 4.2.2For enable ART, just keep tapping on Android version for enable developer submenu and enable ART
LucaRocchi
- Started insulating
- Joined: 2012/8/31 20:29
- From Milan, IT
- Group: Registered Users Webmasters
- Posts: 2228
- Posted on: 2014/1/15 8:07
Re: Motorola MotoG
#8
Update last night to 4.2.2For enable ART, just keep tapping on Android version for enable developer submenu and enable ART
LucaRocchi
- Started insulating
- Joined: 2012/8/31 20:29
- From Milan, IT
- Group: Registered Users Webmasters
- Posts: 2228
- Posted on: 2014/1/16 7:38
Re: Motorola MotoG
#10
Quote:
rewarder wrote:
Can you help me with what ART is?
ART is the new runtime from Google that aims to boost up the performance of your device. It's available only with 4.4 KitKat and (I guess) still ongoing project.
You can enable it: go to "Settings> Developer Options> Select Runtime" and choosing ART. The sys will reboot and rebuild your OS for the new runtime. No data lost, only more space taken from apps and a device potentially more fast.
Quote:
ART vs Dalvik / AOT vs JIT Android apps are deployed in Dalvik bytecode, which is portable, unlike native code. In order to be able to run the app on a device, the code has to be compiled to machine code. Dalvik is based on JIT (just in time) compilation. It means that each time you run an app, the part of the code required for its execution is going to be translated (compiled) to machine code at that moment. As you progress through the app, additional code is going to be compiled and cached, so that the system can reuse the code while the app is running.
Since JIT compiles only a part of the code, it has a smaller memory footprint and uses less physical space on the device. ART, on the other hand, compiles the intermediate language, Dalvik bytecode, into a system-dependent binary. The whole code of the app will be pre-compiled during install (once), thus removing the lag that we see when we open an app on our device. With no need for JIT compilation, the code should execute much faster. Except for the potential speed increase, the use of ART can provide an important secondary benefit. As ART runs app machine code directly (native execution), it doesn't hit the CPU as hard as just-in-time code compiling on Dalvik. Less CPU usage results in less battery drain, which is a big plus for portable devices in general.
Source
Honestly? I don't see any difference