Author |
K700 / K500 Firmware Overview |
vee Joined: Jun 22, 2004 Posts: 435 From: Zagreb, HR PM |
@mwarner
as I already said I have this firmware on my phone for few days, so it is real ... no major changes noticed yet. here are Jbenchmark results:
jBenchmark - 2550
jBenchmark2 - 130
jBenchmark3D - couldn't run, phone woul reboot or freeze always when initialising Texturing Test... 
[ This Message was edited by: vee on 2005-04-02 10:49 ] |
|
hazart Joined: Nov 09, 2004 Posts: 187 From: London, U.K. PM, WWW
|
@vee
Exactly the same thing happened to my K700 running JBenchmark3D. I'm on R2AE033. |
firewired Joined: Nov 26, 2002 Posts: 85 From: Manila, Philippines PM |
so is the new firmware true or not?
I also have the R2A version and I don't have the multiple character search in my phone book. |
mwarner Joined: Dec 23, 2003 Posts: > 500 From: Warwickshire, England PM, WWW
|
@vee
Yeah, I added the firmware to the first post yesterday when I saw that you had it installed. You being a trustworth source and all .
Could you let me know the software versions for this firmware, i.e. LCD, Camera and ITP info? Thanks!
I have added your JBenchmark results to the first post - thanks for that!
[ This Message was edited by: mwarner on 2005-04-02 13:44 ] |
T68 MMS Joined: Jun 01, 2002 Posts: 162 From: Philippines PM |
Recently, I updated my firmware to R2AE033 using update service online. I lost my t9 enlgish and other language pack.. What do i do to restore them? |
vee Joined: Jun 22, 2004 Posts: 435 From: Zagreb, HR PM |
@T68MMS
Master Reset
@hazart
well seems like some problem, the results on jbenchmark.com are with R2AA firmware... don't know if that makes any difference
@mwarner
R2AL02 prgCXC125821_EU_1_C
LCD SW versions
Main Display
Current: 200406041
Camera SW versions
Camera
Current: 3.10
ITP SW version
CXC 125 813 R1T
Customization
CDA102286/9 R2A
cxc125822 R2AE033
EMEA_2
[ This Message was edited by: vee on 2005-04-02 16:39 ] |
T68 MMS Joined: Jun 01, 2002 Posts: 162 From: Philippines PM |
@vee. are you sure about this?
What's the difference between 3.9 and 3.10 camera version anyway? |
hazart Joined: Nov 09, 2004 Posts: 187 From: London, U.K. PM, WWW
|
@T68 MMS
Here is a complete camera driver revision history (official):
// Revision history:
//
// Rev. 3.10 - Changed default flicker compensation mode from 50 Hz to automatic.
//
// Rev.3.9 - Same as 128.13, except for the following additions:
// (1) A line added that changes when the last byte is read when vsync goes low for snapshot. This
// apparently solves the problem with being thrown out of the application occasionally.
// (2) Removed $f FE 02 $f 80 00 00 $d0010 in WAIT_FOR_SS_READY=$d0010 since it is not needed.
// (3) Changed the seq_ss_start from seq_ss_start=FE 02 $f 80 10 00 $f FE 00 $f 04 02 00 $f #WAIT_FOR_SS_READY;
// to seq_ss_start=FE 00 $f 04 02 00 $f #WAIT_FOR_SS_READY $f FE 02 $f 80 10 00;
// This allows you to decrease the frame rate during snap without any changes of the image brightness.
// (value $f FE 02 $f 50 03 00 in the init)
//
// test of ss-sync change
//
// Rev.128.13 - Modified seq_ss_start so that auto black level compensation is not shut off when taking a snap.
// This almost solves the problem with getting thrown out of the application when taking a snapshot.
//
// Rev.128.12 - Added a new sequence to cam_power_off. This makes sure the RESET pin is set to low
// at power off.
//
// Rev. 128.11 - Tried new workaround of problem with slow snapshot and problem with AE and AWB
// not converging when moving camera quickly. Changed back to old antivignetting
// tables since the new ones made the center of the image look pink/magenta. New
// brightness settings for property 0.
//
// Rev.3.5 - Optimized delays when locking frame rate
//
// Rev.3.4 - Changed fixed video frame rates from 7.5 to 10 fps.
//
// Rev.3.3 - Problem with zoom x 4 for sizes 90 and A0 solved
//
// Fixed frame rate in VR now set already when choosing the size.
// Calling property 7 will not have any affect for sizes 40, 80, 90 or A0
//
// Removed viewfinding size id:s 21, 22 and 23
//
// Size id 40 and 90 have fixed frame rate 7.5 fps
// Size id 80 and A0 have fixed frame rate 5 fps
//
// Problem with using size id A0 solved: Sequence name had to be in lower case
//
// Increased frame rate in snapshot mode
//
// Modified gamma table to get better image quality
//
// Fixed a bug that caused sharpening not to work
//
// New antivignetting tables
//
// Increased gain in lowlight mode in order to enhance light sensitivity
//
//
// Rev.3.2 - Discovered and fixed problem with slow viewfinder seen in previous
// versions
//
// Fixed frame rates for videorecording at 10 and 5 fps added
//
// Complete patch inserted:
// ADCM2700 Patch Release 2.0
// Problems addresses by this revision:
//
// Module_Issues.51 - AVE code initialization
// Module_Issues.67 - SCL exposure incorrect
// Module_Issues.70 - Anti-vignetting and zoom
// Module_Issues.73 - Vertical flip doesn't work
//
// Module_Issues.60 - Double-row FPN w/ fast clocks
// Reprograms the flex timing controller
//
// Module_Issues.75 - Analog ref ignite too short
// Reprograms the ref ignite pulse to be longer
//
// Module_Issues.88 - Reinit auto functions
// Sets the AF_init_done flag so the Reinit_AF
// control bit will work properly
//
// Module_Issues.104 - White doesn't saturate
// Fixed with sensor white balancing
//
// Module_Issues.110 - Output incompatible w/ video chip
// Overrides the single frame snapshot limitation by
// copying OUTPUT_CTRL_S to OUTPUT_CTRL w/o clearing bit 12
//
// Rev 3.1 - Enabled I2C reads
// Added polling of register 4 to ensure that the first
// snapshot frame is grabbed and not the last viewfinder
// frame.
//
// Rev 3.0 - Changed snap method: Multiple snap patch now implemented
//
// Lower frame rate to 7.5 fps for snapshot (in seq_init)
// Updated frame rate settings
//
// Changed the Multiple Patch code due to Bug inside
// Address 0x4A9e is now 0x0182 instead of 0x0183
// At the beginning, the write to register 186 disables the
// patch mechanism, the patch is then loaded, and the the
// patch is enabled by writing to register 186 at the end
// of the patch.
// The actual number of frames you will get is the value of
// register 0x012e minus one.
//
// Added size id:s 80, 90 and A0.
// Reinserted vf sizes 11, 12 ...etc.
//
// Removed I2C reads because of problem in platform to read from I2C
//
// Rev 2.4 - Removed an error in the delay code introduced in version 2.3 that seems
// to solve the problem with corrupt snapshots.
//
// Rev 2.3 - Inserted a small delay before snapshot. This partly solves the
// problem with corrupt snapshots
//
// Rev 2.2 - Inserted 256ms delay in seq_vf_start. Fixes crashes when starting
// viewfinder. (No VGA size viewfinder)
// - Replaced polling of config registers with a 256 ms delay,
// since I2C read is not safe.
// - Removed ping, since I2C read is not safe. Fixes problem of beeing
// thrown out of the camera app when starting vf.
//
// Rev 2.1 - Corrected supsizes section. Changed from 15 to 10 fps for video rec
//
// Rev 2.0 - Changed snapshot method.
// No longer uses snapshot bit in camera.
// Continues images are sent even in snapshot mode,
// making retries possible
//
// - Reduced frame rate when zooming
// - 15 fps for all unzoomed vf-sizes
// - 8 fps for VGA snapshot
//
// NOTE! All changes to frame rate must be done when
// setting property 6 (zoom)
//
// Rev 1.8 - VF synch signal |
celltech Joined: Apr 26, 2004 Posts: 203 PM |
K5/700 Latest Firmware
K500/K700 O2 Trade SW R2AN001 - MEA
Affected products:
K500
K700
Description:
Two O2 trade sw's has been released.
K700 O2 Trade [EN, FR, DE, ST, ZU, TR] R2AN001
K500 O2 Trade [EB, FR, DE, ST, ZU, TR] R2AN001
[ This Message was edited by: celltech on 2005-04-03 16:24 ] |
gbrooks3 Joined: Jun 02, 2003 Posts: > 500 From: OTP RED CID36 PM, WWW
|
yes that was uploaded around 25/2/05
Because the platform sends bogus messages while charging, that is why!!!..But why this change of heart?..We sense a charger connected, oops, we will not shut down after all!!!..*********************** UI BASIC, HOLD YOUR HORSES
|
rodmond Joined: Jul 12, 2004 Posts: 4 PM |
Anyone from the Philippines with a k700i firmware version higher than R2L?
About two weeks ago, I tried SEUS and I'm still getting R2L001... |
Sebby Joined: Dec 12, 2004 Posts: > 500 From: London, UK PM |
@ rodmond
I don't mean to insult your intelligence, but are you sure it's R2L and not R2AL you got from the SEUS?
[addsig] |
rodmond Joined: Jul 12, 2004 Posts: 4 PM |
@ Sebby
No problem about the clarification. It's still R2L001. |
hazzard Joined: Dec 30, 2004 Posts: 1 PM |
Yeah me too i just used it right now and thats all i got.
|
caff Joined: Jun 14, 2002 Posts: > 500 From: Australia PM |
So R2L is still the latest software from SEUS ???
|
|