Benchmarks

It seems somewhat silly to run performance benchmarks when most media outlets talk about high performance smartphones most of the time, but my point to consider is my old phone, and whether moving from quad core Krait 300 at 1.7GHz to a MediaTek quad core A53 chipset at 1.0 GHz but running a newer Android is better or worse. For some of the regular smartphone tests I don’t actually own the prerequisite hardware of our smartphone team, but here are some tests I was able to run, and the devices I had to hand at the time:

Devices on Hand for Testing
 
Cubot H1 MediaTek 6735P
HTC Desire 610 Snapdragon 400
HTC One Max Snapdragon 600
Huawei Mate S Kirin 935
Huawei Nexus 6P Snapdragon 810
Google Nexus 7 2013 Snapdragon S4Pro
Amazon Fire HD 6 (Limited) MediaTek MT8135
OnePlus X Snapdragon 801

JSBench

Google Octane

Mozilla Kraken

WebXPRT 2013 - Stock Browsers

WebXPRT 2015 - Stock Browsers

PCMark: Work Performance Overall

PCMark: Web Browsing

PCMark: Video Playback

PCMark: Writing

PCMark: Photo Editing

3DMark: Ice Storm Unlimited, Graphics

3DMark: Ice Storm Unlimited, CPU

3DMark: Ice Storm Unlimited, Overall

When we talk about Qualcomm’s Snapdragon 400 family or Intel's partnership with Rockchip partnership for Sofia and Atom, it makes me somewhat sad we don't have many new data points to compare to the MediaTek MT6735P inside the Cubot H1. However the one benchmark were all interested in is the battery life:

So let's put it this way - the H1 on a full charge breaks the Geekbench3 test to the point that it thinks you are cheating. Oops.

With the PCMark test it gets over 15hrs compared to the 6hrs of the Galaxy S6. When you have a large battery and not many pixels to push, with the right efficiency the device will last a night out with only 25% left in the tank in the way that high end smartphones do not. Anecdotally, as I'm writing this, I just spent a few hours in meetings across the other side of London - I spent 30 minutes each way on the tube with Evernote open and being used (albeit with no wireless or updates), and the battery went down from 38% to 33%. That's an hour of solid writing with black text on white for at most 5% of battery.

  
Initial use, first battery run down and more aggressive use

When I first started using the H1, the graph on the left was my battery usage estimation. Saying ‘approximiately 4 days left’ is almost unheard of, but with a regular 10% screen on time, the result was the graph in the middle, successfully predicting four days of battery. On the right is another example of my use, although a little bit more aggressive with some charging. Yes, I can confirm that there seems to be something wrong with those percentage calculations. But a quick charge in airplane mode for a few minutes gives a few percentage points of battery – while a lot of smartphones offer quick charging for the capacity to fill quickly, it still depends on the capacity drain of the SoC. It helps to have the best of both worlds. Of course, the downside of this is that it can take 3hrs and up to fully charge the H1. The H1 does come with a cable so you can charge other devices though, as 5200 mAh matches some battery packs.

The Feel, The Camera and Video Final Words
Comments Locked

116 Comments

View All Comments

  • Tushar11684 - Monday, January 4, 2016 - link

    I saw that most of the commenters here do not own Cubot H1, so, for a change, consider this comment from someone who owns this device and coincidentally ordered it on same date as of this review for 130€ (received it in 5 days during holiday season).

    Last one week, I played a lot with H1 and got (average on one full charge) more than 13 hours of screen on time. I mainly bought it to do home automation using Tasker, Google Now and AutoVoice. Slowly, I am thinking to switch to this phone permanently (currently, I am waiting for the nano-sim to normal sim adapter, so that I can use the nano-sim from my iphone 5s).

    For normal usage, there is no lag. everything I tried until now works except one thing. I want Google-now on screen off but until now, I was not able to make it work.
  • arigajoe - Friday, January 15, 2016 - link

    Just bought that thing. after afew minutes of using it I have to say that the typing experience on this phone is horrible ...its not responsive when typing ..I have to press again and again for one character to register..Ian try to get in touch with the guys at Cubot so that we get a patch/fix or something..
  • escoltajuverf - Friday, January 15, 2016 - link

    just a warning for those who purchase phones from this brand, they use cheap touchpanels, typing is difficult and gaming is a mess, not only this unit model but also most of their top lineup phones have touch screen issues
  • hp79 - Monday, February 1, 2016 - link

    I feel sorry for you. I mean you are a tech writer but you will be stuck on a sad device for the next two year. The company that made this phone should pay you well (I'm not implying you got paid or anything).

    Thanks for spending the time writing in detail the state of modern cheap phones. I know high end phones are way overpriced and I hope they go down in price even further. I have a Galaxy S6 but the battery is just too short. At least it charges quickly, otherwise I would have switched to something else already.
  • Asherlying - Wednesday, March 2, 2016 - link

    looks a pretty smartphone, but the resolution is a big fault, and I prefer the Cubot x17, which has a smaller battery, but the higher resolution and 3GB RAM is a big advantage considering the price.
    http://www.tinydeal.com/cubot-px347wp-p-156821.htm...
  • Asherlying - Wednesday, March 2, 2016 - link

    looks like an impressive smartphone, but the resolution is a big fault, I prefer the Cubot X17 more, it has 1080p resolution and 3GB, though the battery is smaller,
    http://www.tinydeal.com/cubot-px347wp-p-156821.htm...

Log in

Don't have an account? Sign up now