Break new score in Antutu 25160.

- Stock JWR ROM with Krait optimizations.
- AOSP kernel (jb-mr2-release) with undervolting -175 and some -150 and overclock to 1.8ghz.

All self-compiled directly from Google source and Code Aurora using Linaro toolchain.

This post has been edited by cowithgun: Aug 15 2013, 05:07 PM

Have not been able to use my Nexus 4 till fully discharge lately. It's connected to my notebook from time to time testing new voltage and stuff. But since I have the max freq set to 1.7ghz, and using the same VDD as before 4.3 (-175 from 4.2 stock), I am expecting similar battery life or better (because 4.3 has less wakelock).

I only tested pushing to 1.8ghz today since I am using the VDD from Snapdragon 600 SOC.

I am expecting similar performance since both SOC are almost identical except for larger memory bandwidth in S600. As of now, 1.8ghz seem stable but need to test further. Next step is to reduce the voltage and test it again. Need to continue doing so until I get the min voltage that can get it stable before I push to 1.9ghz.

Got some ideas I want to implement today...

if everything goes well, and my Nexus 4 not toasted, i should be able to push beyond 25k Antutu score today...

Here is my battery life with max Freq set to 1.8ghz, some light browsing, mostly idle.



PS: oh ya, SOT is 26mins.

This post has been edited by cowithgun: Aug 16 2013, 11:09 AM

refer to first page on how to download and compile your own AOSP kernel. my kernel has been customized so deeply with my Nexus 4 that it may not work on other phone. for example, each freq and its vdd is tailor made to suit my phone. another example, i tweak the OnDemand CPU governor and disable JellyBean to take control of my max freq.

i dont normally reply to question like this.. but i m making exception since today is friday...

stop being such as @sshole. just becoz u are having some problem with your nexus 4 does not mean others have similar problem. did it ever occurs to u that no one is replying because they dont have this problem and not sure what is wrong.

and in forum, no one is obligated to answer anything. ask nicely, may be, just MAY BE someone willing to help you with YOUR PROBLEM.

Managed to push Antutu to 24k on default clock speed @ 1.5ghz.



Too bad that I can't push beyond 25k in 1.8ghz... but i know what i must do in the future...

wont work. N4 only support band 4 (1700/2100). Malaysia only support 3 and 7 (1800/2600).

Look up for Malaysia:

http://en.wikipedia.org/wiki/List_of_LTE_networks

Just got back from PC Fair... omai~ I really like Huawei Ascend P6! Phone is really slim and even the bezel is so narrow.

The IPS display is even better than my Nexus 4! I wonder why, so I did a bit of checking. It turn out that P6 is even brighter than Nexus 4. Nexus 4 screen is bright at max 608cd/m2, a lot better than most phone (Samsung S4 just 404cd/m2)... but P6 is at 670cd/m2... I dont know why, I am always attracted to bright screen...

Tested the "Emotion UI"... kind of OK, but I still like pure Android.

ps: price is only RM1399!



This post has been edited by cowithgun: Aug 23 2013, 08:30 PM

Things that visible to user:

- Bluetooth Smart Ready
- OpenGL ES 3.0
- Dial pad - Autocomplete
- New camera UI

Things not so visible to user:
- Faster UI with merge and re-organize (http://www.youtube.com/watch?v=vQZFaec9NpA)
- Restricted profile (Not just for tablet, you can access some of its feature: http://googlesystem.blogspot.com/2013/08/a...ermission.html)

Due to some of its internal improvement, I managed to get Antutu score to 24k at default clock speed. No overclock. Beat my previous 1.7ghz overclock score which as at 23k.

Smart people that done enough research always end up buying nexus 4.. Hehe

This post has been edited by cowithgun: Sep 1 2013, 01:51 PM

I am still on stock ROM! seriously, best in stability and smoothness.

if you charge your phone on daily basis, even stock kernel and rom should be good enough.

quad core technically consume more, so starting with NVidia Tegra 3 (first quad core CPU for mobile), kernel already implement auto_hotplug which allow kernel to decide to use only more core when needed.

qualcomm's S4 pro implement it slightly differently using mpdecision - a userland process that something similar. however, since it's not open source, many custom developers decided to removed that and implement the hotplug.

so, even in stock kernel and ROM, it's not that bad.

all stock ROM are using OnDemand CPU governor. in term of power saving this CPU governor is second only to Powersave and sometimes Conservative. most custom ROM using Interactive which may make the phone more responsible, but cannot match the power saving of OnDemand. (On side note, Interactive CPU Governor may not be best for Nexus 4 or any Jellybean android since Project Butter is more effective than CPU governor. it will automatically boost CPU freq on touch.)

there are other settings such as larger data buffering, low memory killer settings, io scheduler, etc that custom ROM may implement to conserve power, but in my testing, they are soooo minor. so custom ROM offer little in power saving nowadays.

custom kernel offers more nowadays. with custom kernel, you can do under-volting. typically allow your CPU to run at same speed (or higher) at lower voltage. other than that, you also can implement lower lowest brightness etc.

although i m still using Stock ROM (with some customization), i m using a custom kernel for power saving and lower heat. ohh... ya, custom kernel allow me to calibrate Nexus 4 screen too, which LG and Google really do not do justice for the IPS screen.

this news give me a good laugh nice one.

look like Oct kitkat release is possible...

everyone thought it's key lime pie becoz of this:

it was actually leaked from Google's employee:

http://www.ibtimes.com/android-50-key-lime...re-photo-915145

anyway, "Key Lime Pie" _was_ the choice before Google get the acknowledge from Nestle to use KitKat:

"Lagerling also confirmed that his team did originally consider "Key Lime Pie" as a potential name for Android after Jelly Bean, but the issue was "very few people actually know the taste of a key lime pie."

http://www.engadget.com/2013/09/03/android-kit-kat/

8GB Nexus 4 is sold out at Google Play and it won't be coming back, new Nexus handset on the way?

http://www.engadget.com/2013/09/03/8gb-nexus-4-sold-out/

personally, i think -25 is safe. it's so small.

the right way to do undervalting is to test for its stability after you undervolt it since every chip is different. start small, increase it bit by bit and test for stability again.

don't worry if you chip will burn, undervolting will not cause that. overclock may.

worst case that can happen is your phone crash or cannot boot. in that case, use Custom Recovery to restore your boot.img (the kernel).

custom recovery partition is a separate OS of its own, so, your under volt will not affect it.

dont be afraid to try. (but make sure you have proper backup before you begin)

evert chip has its own potential. manufacturer set the default value for all. it is up to you to discover the true potential of your chip.

oh ya, my way of testing stability including running

1. Antutu stability test
2. Idle test - use the phone for a day or two
3. Use camera and turn on all other devices

if your undervolting survive all these, your chip is capable with the lower voltage.

ps: ahh... i forgot, i undervolt by changing the kernel directly... for most people, it should be even easier, just use your under volt tool and test it. dont make it apply at boot and you are good... i think... never really use those tool.

This post has been edited by cowithgun: Sep 5 2013, 11:02 AM

I like stock android. Can change wallpaper if I want to. Lol.

What's really get into my nerve is the fact that most custom ROM comes with deodex apk to allow customization.

With deodex apk, especially framework.jar, your phone boot slower, app load slower, all because you want easy customization.

With today's fast phone, you probably will not notice.

But I just don't like the idea of moving backward, Google invented optimized Dex (odex), but people remove it...