Database Info

Quadrant Benchmarks

Many of the kernels & fixes that have been posted have resulted in dramatic increases in Quadrant scores. Unfortunately, the standard (free) version will only show the final system score and not individual subsystem scores. My goal is to post a detailed summary of these fixes / kernels so that the individual subsystem improvements can be seen.

Summary
Stock
Total: 882 CPU:744 Mem: 1773 I/O: 700 2D: 297 3D: 894
Stock + 1.2 Ghz Overclock
Total: 1030 CPU:884 Mem: 2103 I/O: 743 2D: 370 3D: 1049
One Click Lag Fix (ext2)
Total: 2142 CPU:736 Mem: 1787 I/O: 6988 2D: 306 3D: 893

Stock + Root = 882
Stock firmware flashed from Odin3 One-Click and then rooted.
Total: 882
CPU: 744
Mem: 1773
I/O: 700
2D: 297
3D: 894
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

One Click Lag Fix (ext2) = 2142
One Click Lag Fix (ext2)
http://forum.xda-developers.com/showthread.php?t=749495
Total: 2142
CPU: 736
Mem: 1787
I/O: 6988
2D: 306
3D: 893

Stock + 1.2 GHz Overclock = 1030
Stock with 1.2 GHz overclock kernel
http://forum.xda-developers.com/showpost.php?p=7558178&postcount=38
Total: 1030
CPU: 884
Mem: 2103
I/O: 743
2D: 370
3D: 1049

Nice thread. Good information and links for the masses.

nice thread with detailed information + pictures.
Unfortunately, quadrant scores do not really mean anything, especially with the SGS phones.
In other words, quadrant scores do not scale with actual performance gains in real world usage. I, and many others, feel the NAND hack provides the fastest real world benefit, but still have near-stock Quadrant scores.

Very interesting. It sounds like the biggest and most useful improvement is 2.2's increase in CPU ability.

SlimJ87D said:
Very interesting. It sounds like the biggest and most useful improvement is 2.2's increase in CPU ability.
Click to expand...
Click to collapse
So imagine the insane quadrant score we'll be reporting when we get that CPU boost in addition to a final I/O fix to overcone RFS.

I know Quadrant benchmarks don't necessarily mean anything, but I thought this was cool:
Samsung Captivate: Android 2.1 Stock ROM + Ext2 Hack + 1.2 GHz overclock

That's pretty awesome.

Dolphin HD flies w/o any lag , here is my quadrant score
Samsung Captivate: Android 2.1 Stock ROM + Ext2 Hack + 1.2 GHz overclock

JH2 firmware, rooted, 100+ apps installed
Total: 891
CPU: 755
Mem: 1879
I/O: 608
2D: 306
3D: 908

Root + Stock Rom
Total: 857
CPU: 734
Mem: 1765
I/O: 572
2D: 300
3D: 913
Root + Stock Rom + SetCPU
Total: 866
CPU: 754
Mem: 1738
I/O: 625
2D: 309
3D: 906
SetCPU Settings
(I have not figured out how to overclock yet, so I am only using it to manage resources)
Default profile
Max 1Ghz
Min 800Mhz
scaling Conservative
Charging/full profile
Same as default but scales on performance
Battery <50%
Max 800Mhz
Min 400Mhz
scaling Ondemand
screen off
Max 200
Min 200
Scale powersave

andy2na said:
, and many others, feel the NAND hack provides the fastest real world benefit, but still have near-stock Quadrant scores.
Click to expand...
Click to collapse
Which fix is the NAND hack?

Overclocking Rogers Infuse 4G

Currently running stock (for Canada) Gingerbread 2.3.3 rooted with Infused V1 Kernel with Voodoo Lagfix enabled.
I've overclocked pretty much every piece of technology that would allow me to, so I figured why not my phone.
I know rooting this was the first step, now I believe I have to install a Kernel that supports OC/UV.
Will any of these Kernels work the same on my Rogers Infuse as they would on an AT&T Infuse?
I know the rooting process was different, but I'm not completely sure why.
Maybe because of the version of Android? Froyo on AT&T vs Gingerbread on Rogers?
I'm hoping to get a stable clock of 1.5Ghz & Ideally I would like to keep my stock ROM. If anyone would advise against going as high as 1.5Ghz, please feel free to let me know.
Also...
Any suggestions on an Overlcocking tool?
I was looking at Voltage Control or SetCPU app to do the job, any recommendations?
Does overclocking the CPU improve GPU performance as well?
I believe it's all integrated into one chip, but I'm not sure if they have the same clock. If not, is there any current method of GPU overclocking?
Thanks in advance guys, have always appreciated this forum back since my Windows Mobile 6.1 days.

Any gingerbread kernel can be flashed on our phones, I recommend INFUSION-GB, which has different versions with different clock speed settings. You can go to 1.6 no problem, and even undervolt a bit! Also, use voltage control. Flashing a kernel won't change your rom, but even if you were to flash a different rom (such as infused, which is based on stock Rogers) you can always get back to stock easily.
Sent from my SAMSUNG-SGH-I997 using XDA App

Any idea on the GPU overclocking?
Will changing there kernel effect the rogers logo at boot? Or is that rom based?
I'm familiar with over volting on PCs to get higher clock speeds. What's the purpose of under volting?
Sent from my SAMSUNG-SGH-I997R using XDA App

Undervolting help please.
What is a stable undervolting setup that has been proven by multiple users on the Infuse? Not looking for anything extreme, just something effective.
Anyone have any knowledge on GPU overclocking options?
Here's my current setup...
Kernel: Infusion-GB Core-A
Rom: Stock Rogers Infuse
Gingerbread 2.3.3
w/ - Voodoo lagfix
- 30fps camera mod
Overclocked to 1600Mhz
w/ - No undervolting
SetCPU profiles...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Info from SetCPU...
Kernel
Linux version 2.6.35.7-I997RUXKG3-CL366622 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2009q3-68) ) #Infusion-GB-CoreA PREEMPT Tue Oct 11 23:31:36 CDT 2011
Battery
Battery Temp: 38.0° C (100.4° F)
Battery Level: 30%
CPU
Frequency: 200000 kHz
Load Average: 1.15 1.17 1.36 1/576 16860
Processor : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 199.80
Features : swp half thumb fastmult vfp edsp thumbee neon vfpv3
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x2
CPU part : 0xc08
CPU revision : 2
Hardware : herring
Revision : 0030
Serial : 38314be08ee400ec
Time in State
1600000 362749
1200000 50032
800000 75224
400000 55332
200000 114986
100000 516004
Memory
MemTotal: 463188 kB
MemFree: 52260 kB
Buffers: 10072 kB
Cached: 151936 kB
SwapCached: 0 kB
Active: 253144 kB
Inactive: 94760 kB
Active(anon): 191056 kB
Inactive(anon): 2508 kB
Active(file): 62088 kB
Inactive(file): 92252 kB
Unevictable: 7004 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 76 kNo
Writeback: 0 kB
AnonPages: 192936 kB
Mapped: 55496 kB
Shmem: 664 kB
Slab: 13920 kB
SReclaimable: 4032 kB
SUnreclaim: 9888 kB
KernelStack: 4608 kB
PageTables: 12532 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 231592 kB
Committed_AS: 2093332 kB
VmallocTotal: 196608 kB
VmallocUsed: 83880 kB
VmallocChunk: 15188 kB
AnTuTu Benchmark Results...
(Up approx. 1000 over stock)
Sent from my SAMSUNG-SGH-I997R using XDA App

Just use voltage control and bump the voltage down, if it becomes unstable, turn it back up. Just don't set at boot until you're sure its stable and you'll be fine. Undervolting just saves battery. You can't damage the CPU from giving it less power, only more, so nothing to worry About.
Sent from my SAMSUNG-SGH-I997 using XDA App

It would seem to me that the Infuse, does not have a cpu temp sensor, just the battery temp sensor.
Please correct me if I'm wrong.
What type of max temps should I be looking for from the battery temp sensor?
Running Stability Test CPU+GPU I hit 52 degrees celsius after about 4 hours at 1600Mhz.
I am now undervolting...
I noticed that I can't undervolt the 1600Mhz, I would assume this is because the overclock needs at least the stock voltage, or something isn't being detected?
Without being able to undervolt the 1600Mhz. When running Stability Test to confirm the undervolting is working, should I be limiting the clock speed to 1200Mhz?
Sent from my SAMSUNG-SGH-I997R using XDA App

How to Edit Frequencies in Exynos4412?

I've built a custom kernel for my Galaxy Tab 10.1 The link is in my signature. When I wanted to add custom frequencies to it, there was a very informative post that told me how to edit the frequency table to make the new clock speeds on tegra2 come out right and also how to edit the voltage tables. At least on the tegra2 it involved editing tegra2_clocks.c where you had to change the pll_x frequency table, change the pll_x max speed, virtual cpu max speed, sku max speed, and add an additional frequency table for your new clock speeds. The voltage was done in tegra2_dvfs.c where you added changed the min/max voltages accordingly and added in your new frequencies there.
I have looked all over the internet for a similar guide for my I9300. The cpufreq-4x12 looks nothing like the tegra one. It appears that every frequency has an entry in clkdiv_cpu0_4412 (for the S3 at least) with dividers for cryptic values like "divcore" "divcorem0". I've tried doing a grep search in the kernel source and couldn't find those names mentioned anywhere. There also appears to be another clkdiv_cpu1_4412 with even more cryptic values which don't appear in grep either. Then of course, there's yet another cryptic table that each frequency seems to go to called "apll_pms". It appears as the voltages go to the asv tables but how you accommodate new frequencies is beyond me. The L0,L1.. etc labels don't appear to follow the conventions stated earlier where 1800MHz is labelled L0 at the top but L-2 later.
I realize that many experienced developers probably take this information for granted and I wouldn't be asking for this if it was available somewhere else. The documentation folder in the kernel doesn't provide any information either.
Please help a startup enthusiast As a beginner, I've typically answered similar how to questions on my own thread in the beginning, when other people were interested in how to get their hands dirty with modifications. (Although now, people just seem to be interested in the final product which is fine too.)

Each divider value represents the real divider minus 1. So a value of 7 divides by 8. Populate the divider talbes with new entries like that. The registers have a limit so see the register maps in /mach/regs-clock.h. The dividers divide the final CPU clock. What values you give the dividers is up to you to decide.
The CPU clock is decided by the PLL as you saw. PMS decides the PLL frequency. The source quartz runs at 24MHz. The frequency is calculated by (P * Xtal) / (M << S).
Example 500MHz: ((125<<16)|(3<<8)|(0x1)), the format is ((P<<16)|(M<<8)|(S)).
(P * Xtal) = 125*24 MHz = 3000MHz
(M << S) = 3 << 1 = 6
End result is 3000MHz / 6 = 500MHz.
That's all you need to know. Alternatively, just copy what other devs have already done. Be careful with the Lx levels when you add new ones, you need shift all the existing ones throughout the file.

AndreiLux said:
Each divider value represents the real divider minus 1. So a value of 7 divides by 8. Populate the divider talbes with new entries like that. The registers have a limit so see the register maps in /mach/regs-clock.h. The dividers divide the final CPU clock. What values you give the dividers is up to you to decide.
The CPU clock is decided by the PLL as you saw. PMS decides the PLL frequency. The source quartz runs at 24MHz. The frequency is calculated by (P * Xtal) / (M << S).
Example 500MHz: ((125<<16)|(3<<8)|(0x1)), the format is ((P<<16)|(M<<8)|(S)).
(P * Xtal) = 125*24 MHz = 3000MHz
(M << S) = 3 << 1 = 6
End result is 3000MHz / 6 = 500MHz.
That's all you need to know. Alternatively, just copy what other devs have already done. Be careful with the Lx levels when you add new ones, you need shift all the existing ones throughout the file.
Click to expand...
Click to collapse
I'm a bit confused by what M << S means. From lookig at the example it looks like the formula is: P * 24 / ( M * 2^s)? Also, I'm assuming the voltage tables don't have to be touched. Thanks so much for the information. And... what fun would it be if you did a straight up copy and paste? :cyclops:

Ummm that's a bit-wise left-shift operation. And yes you also need to add entries in the voltage table.

AndreiLux said:
Be careful with the Lx levels when you add new ones, you need shift all the existing ones throughout the file.
Click to expand...
Click to collapse
And in any other files that reference levels... Namely any that contains a level-based DVFS lock.
I think much of Samsung's newer code does frequency-based locks with a frequency-to-level lookup, but in older 4210 kernels, there were lots of locks that called out specific levels. Some of these locks were in throttling code. Levels go from high freq to low freq.
So if L2 was originally 800 MHz, and L2 is now 1000 MHz, and thermal throttling code locks to a minimum level (maximum frequency) of L2... Whoops, now the thermal throttling is broken.

Hi again,
For some reason, the exynos4 sources seem to be much more fussy than the galaxy tab 10.1 tegra2 sources I messed with in the summer. Right of the bat (with no modifications), it refuses to compile giving me issues in the file arch/arm/mvp/mvpkm/mvpkm_main.o. I haven't touched anything or made any changes yet. I downlaoded the latest sources from Samsung. I tried switching toolchains and I get 1 of 2 errors. With an older toolchain I get
/tmp/ccC3yZT8.s:4865: Error: unknown pseudo-op: `.arch_extension'.
With a newer toolchain I get an error about making a pointer to int conversion without a cast. Wow, truly unbelievable!!!??? I just want to make a baseline run, haven't touched a character of code and it refuses. I tried compiling CM10.1's kernel (also with no modifications) but for some reasons the graphics are Pentium 1 slow. ADB shell with logcat keeps saying hwcompser can't do vsync and it attempts to fake it.
I don't remember it being this hard on my galaxy tab 10.1. Am I missing something obvious?
---------------------added-----------------
I got cm sources compiling correctly. I think i forgot to undo previous experiments

AndreiLux said:
Each divider value represents the real divider minus 1. So a value of 7 divides by 8. Populate the divider talbes with new entries like that. The registers have a limit so see the register maps in /mach/regs-clock.h. The dividers divide the final CPU clock. What values you give the dividers is up to you to decide.
The CPU clock is decided by the PLL as you saw. PMS decides the PLL frequency. The source quartz runs at 24MHz. The frequency is calculated by (P * Xtal) / (M << S).
Example 500MHz: ((125<<16)|(3<<8)|(0x1)), the format is ((P<<16)|(M<<8)|(S)).
(P * Xtal) = 125*24 MHz = 3000MHz
(M << S) = 3 << 1 = 6
End result is 3000MHz / 6 = 500MHz.
That's all you need to know. Alternatively, just copy what other devs have already done. Be careful with the Lx levels when you add new ones, you need shift all the existing ones throughout the file.
Click to expand...
Click to collapse
I have been meaning to thank you for this, I have not seen this information elsewhere. Could you please briefly explain how to set the values in cpufreq_clkdiv? I have noticed different kernels have different values for the same frequency, and I don't know which one is correct for me.
Example:
/*
* Clock divider value for following
* { DIVCORE, DIVCOREM0, DIVCOREM1, DIVPERIPH,
* DIVATB, DIVPCLK_DBG, DIVAPLL, DIVCORE2 }
*/
Samsung source (I believe)
/* ARM L0: 1600Mhz */
{ 0, 3, 7, 0, 6, 1, 2, 0 },
Perseus:
/* ARM L0: 1600Mhz */
{ 0, 4, 7, 0, 6, 1, 7, 0 },​

ffolkes said:
I have been meaning to thank you for this, I have not seen this information elsewhere. Could you please briefly explain how to set the values in cpufreq_clkdiv? I have noticed different kernels have different values for the same frequency, and I don't know which one is correct for me.
Example:
/*
* Clock divider value for following
* { DIVCORE, DIVCOREM0, DIVCOREM1, DIVPERIPH,
* DIVATB, DIVPCLK_DBG, DIVAPLL, DIVCORE2 }
*/
Samsung source (I believe)
/* ARM L0: 1600Mhz */
{ 0, 3, 7, 0, 6, 1, 2, 0 },
Perseus:
/* ARM L0: 1600Mhz */
{ 0, 4, 7, 0, 6, 1, 7, 0 },​
Click to expand...
Click to collapse
I don't have any exact technical explanation behind the physical CPU blocks that those auxiliary dividers are clocking.
Personally I just fired up Excel and adjusted them in to what seemed to me a reasonable curve with the rest of the frequency clocks which Samsung provided. These are the values I put in Perseus.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You could probably adjust M0 again beyond 1800 MHz to be somewhat lower.

[INFO] [ROOT] [UPDATED] Celkon A85 Wiki By Kevin

Welcome Visitors XDA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Technical specifications:
• Name : Celkon A85
• Platform :Android OS
• Version : 2.3.9 Gingerbread*
• Brand Manufacturer : Spreadtrum
• Global Name : HSDroid (S5820i)
Hardware specifications:
Display:
Screen Type: LCD Capacitive *
Screen Size: 3.5” Capacitive*
Multitouch: YES*
Screen Resolution: 320 x 480 Pixels*
Display Type: HVGA*
Density: 165 dpi*
Body:
Dimensions: 110 x 56 x 8 mm (4.33 x 2.20 x 0.31 in)*
Weight: 125 g (4.41 oz)*
Memory:
On Board Memory: 681 MB*
System Memory: 240 MB*
Internal Memory (DATA): 140 MB*
RAM: 252 MB*
Cache Memory: 70 MB*
Threshold RAM: 24 MB*
Connectivity:
SIM: Dual SIM (Mini-SIM)*
Band: GSM 850/900/1800/1900 – SIM 1& SIM 2*
GPRS: Yes (Class-8)*
EDGE: Yes (Class-10)*
3G: NO*
WLAN: Yes (Wi-Fi802.11b/g/n)*
GPS: NO*
Bluetooth: Yes (V2.0)*
USB: Yes (microUSB v2.0)*
Camera:
Primary: 3.2 MP, 2048x1536 pixels*
Focus: Auto, Auto-Multi, Macro*
Flash: Yes, LED *
Video: Yes, 40 fps*
Secondary: No (Optional on some conditions)*
Processors:
CPU Type: ARMv7 Processor rev 1 (v7l)*
CPU Frequency: 1000 MHz (1 GHz)*
CPU Core: Single (1)*
CPU Manufacture: Spreadtrum*
CPU Tech Name: SP6820a*
CPU Features: swp half thumb fastmult vfp edsp neon*
GPU: Mali 300*
Sensors:
Accelerometer: Kionix KXTJ9 3-axis Accelerometer 5.0mA By Kionix, Inc.*
Light Sensor: cm36283 Light sensor 0.005mA By CAPCELLA*
Proximity Sensor: ROHM Light sensor 0.005mA By ROHM*
G-Sensor: MMC328X 0.003mA By MEMSIC*
Magnetic and Accelerometer Combo orientation Sensor 0.5mA By MEMSIC*
Features:
Messaging: SMS(Threaded view), MMS, Email and IM*
Browser: HTML, WAP*
Radio: Yes, Stereo FM Radio With RDS*
Software:
Android Version: 2.3.9 Gingerbread*
Kernel Version: 2.6.35.7*
Battery:
Technology: Li-ion*
Capacity: 1200mAh*
Stand-by: 10 Days (Dual-SIM)*
7 Days (SIM)*
Talk time: 7 h*
Price:
About 65 – 70 EUR*******
Common Issues:
As Celkon A85 is an budget smart phone it comes out of the box with variety of common and intresting problems.
Major problems encountered while usage are
1. Low Data Memory (140 MB)
2. Low Battery Capacity (1200mAh) Even it gives 10 days stand-by
3. Problem while setting wallpaper through gallery
4. Low Connectivity Issues
As it comes in global market around 60 - 70 EUR., it is very acceptable.
Suggestions:
1. Root your device (Celkon A85)
It helps in Managing the Internal memory and battery performance and life
I got 111 MB of free memory after rooting Celkon A85
(I will help you in obtaining and managing the free memory)
Install CWM on your device (Celkon A85)
(Link will be added soon)
It helps in flashing new firmfare.
For Wallpaper issues i suggest an application called "Wallpaper Wizardrill"
It helps in Scaling the required Image exactly to the resolution.
Other Software related problems can be rectified by Development of software and using various applications from Google Play(I don't suggest it.
*****************DEVELOPMENT PAGE OF CELKON A85 IS GOING TO START SOON*****************​
ROOT GUIDE
http://forum.xda-developers.com/showthread.php?t=2390591
Thanks to ravikanthchary for his effort

auiiir clear
Dear Bro where is the link for Cwm

HELP
Guys.....can someone help me by Giving some Custom ROM'S for this Celkon a85 ...... so i could enjoy extra features in it ..... i've successfully Rooted my Android also ..... U can also Give link For downloading ODIN Package
Can u help Guy's .........

[SPECS] Oppo F1 Specifications

Hi all
We have a general discussion thread, so this one is intended to focus on the specifications and design features of the Oppo F1. Feel free to compare hardware with competing devices.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Specifications:
Display - IPS LCD, 5.0 inches, 720 x 1280 pixels (~294 ppi pixel density)
Chipset - Qualcomm MSM8939v2 Snapdragon 616
CPU - Quad-core 1.7 GHz Cortex-A53 & quad-core 1.0 GHz Cortex-A53
GPU - Adreno 405
RAM - 3 GB RAM
Memory - 16 GB, microSD
Camera - 13 MP, f/2.2, phase detection autofocus, LED flash
Secondary Camera - 8 MP
Sensors - Accelerometer, proximity, compass
Connectivity - Wi-Fi 802.11 b/g/n, Wi-Fi Direct, hotspot, Bluetooth v4.0
Battery - 2500 mAh
Dimensions - 143.5 x 71 x 7.3 mm
Weight - 134 g
Color Availability - White/Gold
source: gsmarena

oppo F1 Specifications from oppo official website
http://www.oppo.com/en/smartphone-f1#section-product-specs
Dimensions/Weight
Height 143.5mm
Width 71mm
Thickness 7.25mm
Weight 134g
Basic Parameters
Color: Golden, Rose Gold
Operating System: ColorOS 2.1, Android 5.1
GPU : Adreno 405
RAM: 3 GB
Storage: 16 GB (Support microSD card, expandable up to 128 GB)
Battery: Non-removable battery with the minimum capacity of 2400mAh, the typical capacity of 2500mAh
Processor: Qualcomm Snapdragon 616 Octa-core
Display
Size: 5.0 inches
Type: IPS TFT
Resolution: HD (1280 by 720 pixels)
Colors: 16 million colors
Touchscreen: Multi-touch, Capacitive Screen, Gorilla Glass 4
Support for Gloved and Wet Touch Input
Camera
Main Sensor: 13-megapixel
Front Sensor: 8-megapixel
Flash: Flash
Aperture Rear: f/2.2
Sec: f/2.0
Other Features: 720p/ 1080p videos
Connectivity
Frequencies 3G Version:
GSM 850/900/1800/1900MHz
WCDMA 2100MHz
Asia-Pacific Version:
GSM 850/900/1800/1900MHz
WCDMA 850/900/2100MHz
LTE Bands 1/3/8
4G India Version:
GSM 850/900/1800/1900MHz
WCDMA 2100MHz
LTE Bands 1/3/TD-40
International Version :
GSM 850/900/1800/1900MHz
WCDMA 850/900/2100MHz
LTE Bands 1/3/5/7/8/20/28/TD-38/39/40/41
SIM Card Type: Dual-SIM: Micro-SIM Card and Nano-SIM Card
GPS: Supported
Bluetooth: 4.0
Wi-Fi: 802.11 b/g/n
OTG: Yes
NFC: No
Sensors
Distance sensor
Light sensor
G-sensor
E-compass
Battery
Non-removable battery with the minimum capacity of 2400mAh, the typical capacity of 2500mAh
In the Box
OPPO F1
Micro USB cable
Charger
Earphones
SIM ejector tool
Documentation
Case
---------- Post added at 05:18 PM ---------- Previous post was at 05:03 PM ----------
Some More Specifications
1. Gyroscope Sensor: I have seen in numerous reviews and oppo website also, they say that oppo F1 have only Accelerometer, proximity, compass, E-compass Sensors but no gyro. But after I bought the mobile I have seen that is equipped with Gyroscope Sensor named OEM pseudo gyro. This sensor is not accurate, but gets the job done. Many people ask for gyro because its needed for occasional VR.
2. It doesnt have secondary voice cancellation micropone
3. Capacitive Touch Keys Dont have backlight
4. Camera has full manual control.
5. Notification LED is present.

Optus model is f1f and snapdragon 615 processor clocked at 1.5.
Sent from my F1f using Tapatalk

"Hardware Info" Details
I have Extracted all info from "Hardware Info" App. Some Important Info are here.. download the attached text for details...
OPPO F1w (Android 5.1.1)
Model F1w
Manufacturer OPPO
Device F1f
Product F1w
Brand OPPO
Android Version 5.1.1 (Lollipop)
API Level 22
Build ID LMY47V
Fingerprint OPPO/F1w/F1f:5.1.1/LMY47V/1447645196:user/release-keys
Display (1280x720)
Size 1280x720
Refresh Rate 60 Hz
Default Orientation Portrait
Physical Size 4.97" (12.63 cm)
Logical Size Normal
Density 320 dpi (Extra High)
Pixels Per Inch X: 294.97; Y: 295.56
Processor (AArch64)
Processor AArch64 Processor rev 4 (aarch64)
Cores 8
Max Frequency 1497 Mhz
Instruction Sets arm64-v8a,
SIMD Instructions Not Supported
Memory (2877 MB)
System RAM 2877 MB
JVM Max Memory 256 MB
Internal Storage 10707 MB
External Storage 10657 MB (Emulated)
Back Camera (13 megapixel)
Summary
Max Picture Size 4160x3120 (4:3)
Zoom 6.06x
Autofocus Supported (Continuous)
Orientation 90°
Focus Areas (0, 0, 0, 0, 0)
Focus Distances Infinity, Infinity, Infinity
Focus Mode Auto
Focus Mode Values Auto, Infinity, Macro, Continuous Video, Continuous Picture, Manual
Max Focus Pos Index 512
Max Num Focus Areas 1
Min Focus Pos Dac 1023
Min Focus Pos Index 0
Front Camera (8 megapixel)
Summary
Max Picture Size 3264x2448 (4:3)
Zoom 6.06x
Autofocus Not supported
Orientation 270°
Sensors (9)
lis3dh-accel
Vendor STMicroelectronics
Range 156.8 m/s²
Resolution 0.01 m/s²
Power 0.01 mA
Delay 5000 μs
mmc3416x-mag
Vendor MEMSIC, Inc
Range 1228.8 μT
Resolution 0.048822813 μT
Power 0.35 mA
Delay 10000 μs
apds9921-light
Vendor avago
Range 60000.0 lx
Resolution 0.0125 lx
Power 0.2 mA
Delay On Trigger
apds9921-proximity
Vendor avago
Range 5.0 cm
Resolution 5.0 cm
Power 3.0 mA
Delay On Trigger
oem-orientation
Vendor oem
Range 360.0°
Resolution 0.00390625°
Power 1.0 mA
Delay 10000 μs
oem-pseudo-gyro
Vendor oem
Range 50.0 rad/s
Resolution 0.01 rad/s
Power 1.0 mA
Delay 10000 μs
Rotation Vector Sensor
Vendor AOSP
Range 1.0
Resolution 5.9604645E-8
Power 1.36 mA
Delay 5000 μs
Gravity Sensor
Vendor AOSP
Range 19.6133 m/s²
Resolution 0.01 m/s²
Power 1.36 mA
Delay 5000 μs
Linear Acceleration Sensor
Vendor AOSP
Range 19.6133 m/s²
Resolution 0.01 m/s²
Power 1.36 mA
Delay 5000 μs
Color Longshot
color.longshot
Oppo App2sd
oppo.app2sd.disabled
Oppo Black
oppo.black.gesture.proximitysensor.support
Oppo Breath
oppo.breath.light.support
Oppo Brightness
oppo.brightness.mode.automatic
Oppo Commcenter
oppo.commcenter.reboot.dialog
Oppo Dirac
oppo.dirac.support
Oppo Dirac_bluetooth
oppo.dirac_bluetooth.spport
Oppo Double
oppo.double.flinger.volume.support
Oppo Exfat
oppo.exfat.support
Oppo Eye
oppo.eye.protection.support
Oppo Feature
oppo.feature.15309
Oppo Filtrated
oppo.filtrated.app
Oppo Gallery
oppo.gallery.opencabc
Oppo Guard
oppo.guard.elf.support
Oppo Hw
oppo.hw.manufacturer.qualcomm
Oppo Inexact
oppo.inexact.alarm
Oppo Keyguard
oppo.keyguard.highvolume
Oppo Leather
oppo.leather.proximity.sensor.support
Oppo Memory
oppo.memory.auto.clean
oppo.memory.auto.deep.clean
Oppo Multi
oppo.multi.touch.camera.support
Oppo Otg
oppo.otg.connection.menu.support
Oppo Qcom
oppo.qcom.hotswap
Oppo Qualcomm
oppo.qualcomm.gemini.support
Oppo Quick
oppo.quick.shot.support
Oppo Screen
oppo.screen.hovering.support
Oppo Soundeffect
oppo.soundeffect.support
Oppo Support
oppo.support.single.partition
Oppo Sw
oppo.sw.solution.device
oppo.sw.solution.rom
Created with Hardware Info 4.2.6

Any dev. Working on oppo f1

Just got a 1.5GHz octa core F1 for my wife.
Nice phone, I think she will enjoy it, especially when I replace the ColorOS launcher, lol.

mine is 1.7ghz sd 616

Yeah the 32 GB model has Octa Core processor
Sent from my F1f using Tapatalk
---------- Post added at 07:29 PM ---------- Previous post was at 07:28 PM ----------
Is it have selling only in India?
Sent from my F1f using Tapatalk