[ROM] Archos ICS - Custom Rom - Overclock Edition !

Hi everyone !!!

I made ​​this Custom Rom ( Overclock Edition ) to improve performance in our Archos tablet !..... if I could .... will leave you to appreciate.....

This Custom Rom should be work for all Archos G9 ....but you need activate SDE menu !

Update 13/05/2012 : ICS Firmware 4.0.6(4.0.3) - Overclock Edition !
**********************************************************************
Custom Rom & Custom Kernel => ICS Firmware 4.0.6 - Overclock Edition , based on ultimate update archos/kernel/system ( 4.0.6 update ) !

This Custom Rom is permanent ROOT, include busybox and module tun.ko for enable VPN !

ICS@4.0.6_OC - include :

• - Omap 4430 1GHz stock => overclock max. 1.24GHz ;
• - Omap 4430 1.2GHz stock => overclock max. 1.44GHz ;
• - Omap 4460/70 => overclock max 1.74GHz;
• - module tun.ko ;
• - enabeled /init.d to run scripts ;
• - root;
• - "busybox";
• - new bootanimation ;
• - app add : Terminal Emulator, Root-Browser, CPU Tuner, Root Check Basic, Play Books;
• - app update : Maps, Street, Gmail, Music2, Google+, Market Play;
• - remove update (software) notification ;

Download :

- archos.ext4.update => in archive "archos_406_oc.zip" => https://hotfile.com/dl/155806528/f429faa/archos_406_oc.zip.html
- zImage & initramfs => in archive "kernel_406_oc.zip" => http://www.2shared.com/file/CvHkZHLC/kernel_406_oc.html Mirror : kernel_406_oc.zip

Install :

- copy archos.ext4.update in /mnt/storage/ ;
- go to SDE -> "D.E.M." -> Flash Kernel & Initramfs -> copy here zImage & initramfs.cpio.lzo -> OK! -> wait to install .....
- after everything was installed - please reboot your device !

Overclock Frequency :

TI OMAP 4430 1GHz Stock , Overclock -> 1.06GHz; 1.12GHz; 1.18GHz; 1.24GHz;
TI OMAP 4430 1.2GHz Stock, Overclock -> 1.26GHz; 1.32GHz; 1.38GHz; 1.44GHz;
TI OMAP 4460 1.5GHz Stock, Overclock -> 1.56GHz; 1.62GHz; 1.68GHz; 1.74GHz;

Click to expand...

Click to collapse

First release - 10/04/2012 : ICS Firmware 4.0.5(4.0.3) - Overclock Edition !
**************************************************************************
This version ICS@4.0.5_OC Edition , is a minimalist version .... it was removed some applications unnecessary .

This Rom is rooted and include busybox , no extra apk ( you can downloaded from market play ) , and you can overclock with SetCPU or other app .

For TI OMAP 4430 now we have : 300, 600, 800 , (MHz) and... 1; 1.06; 1.1; 1.12; 1.18; 1.2; 1.24; 1.28; 1.32 GHz / For TI OMAP 4460/4470 : overclock with : 1.56; 1.62; 1.68 GHz

ICS@4.0.5_OC - include :

- Omap 4430 overclock until 1.18GHz/1.32GHz ;
- Omap 4460/70 overclock until 1.68GHz;
- module tun.ko ;
- enabeled /init.d to run scripts ;
- "su" and "Superuser";
- "busybox";
- bootanimation ;
- activate vibrator and adjust_audio - is needed to confirm if it works ...;

For install ....download "fast_ics_oc.zip" => https://hotfile.com/dl/152251241/ef27ecd/fast_ics_oc.zip.html ; => http://www.4shared.com/zip/Bg7Ela_U/fast_ics_oc.html => http://www.2shared.com/file/sHkKDCoh/fast_ics_oc.html
- unpack fast_ics_oc.zip , copy archos.ext4.update -> Internal Sorage ..... and into SDE
-Flash Kernel and Initramfs , copy zImage and initramfs into it ! Reboot and wait to install...

Tested [ TI OMAP 4430 1.2GHz Stock ] with Quadrant Standard ( 1.32, 1.28 GHz) - the result is always more than 2500 . ( max. was 2578)
Tested [ TI OMAP 4430 1.2GHz Stock ] with AnTuTu Benchmark (1.32GHz) - the result is always more than 6500 . ( max. was 6759)

Do not overclok your device for long periods of time ! Overclocking , may damage your device !
Archos 101 G9 1.32GHz =>


If device does not respond ....press power 10sec. and select a lower frequency !

Overclock settings :
TI OMAP 4430 : 1.2 GHz -> Stock Voltage (1.388mV) ; 1.24GHz -> 1.392mV ; 1.28GHz -> 1.396mV ; 1,32GHz -> 1.400mV
TI OMAP 4460 : 1.56GHz -> 1.400mV ; 1.62GHz -> 1.400mV ; 1.68GHz -> 1.400mV
TI OMAP 4470 : 1.56GHz -> 1.398mV ; 1.62GHz -> 1.398mV ; 1.68GHz -> 1.398mV

***UPDATE*** 12/04/2012***

Now work for all TI OMAP 44xx with stock freq. 1GHz ; 1.2GHz ; 1.5GHz

TI OMAP 4430 1GHz Stock , Overclock -> 1.06GHz; 1.12GHz; 1.18GHz
TI OMAP 4430 1.2GHz Stock, Overclock -> 1.24GHz; 1.28GHz; 1.32GHz
TI OMAP 4460 1.5GHz Stock, Overclock -> 1.56GHz; 1.62GHz; 1.68GHz

Click to expand...

Click to collapse

Please download "fast_ics_oc.zip" and change zImage with this .... => http://www.2shared.com/file/myHbERv3/zImage.html

If you feel that high overclock frequency leads to underclock the device , so please choose your overclock max. frequency = immediately preceding value of overclock max. frequency !

One of the properties of kernel -> low frequency at boot : ( it means that your device will run underclocked until you change freq. with Cpu Tuner ! )

- TI OMAP 4430 Freq. Stock 1GHz => On Boot 1GHz;
- TI OMAP 4430 Freq. Stock 1.2GHz => On Boot 1.1GHz;
- TI OMAP 4460/4470 Freq. Stock 1.5GHz => On Boot 1.2GHz;

Click to expand...

Click to collapse

Android CPU governors explained

1° OnDemand
2° Performance
3° Powersave
4° Conservative
5° Userspace
6° Interactive
7° Hotplug


1°: OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.

OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.

This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.

2°: Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).

3°: Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.

4°: Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.

The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.

5°: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.

6°: Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.

Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.

However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.

Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.

7°: Hotplug Governor:
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."

Obviously, this governor is only available on multi-core devices.

Thanks for your help LeTama, gen_scheisskopf !

regards,
Surdu Petru

android.i.am said:

Thanks surdu_petru,
Just installed this & so far so good - I'll report more feedback with further usage...

FYI, on my 80 G9 Classic, Quadrant scores are:
stock 1GHz = 2103
oc 1.24GHz = 2432

BTW, can someone explain the "governor" setting in various CPU control apps? Do I just leave it as the default "ondemand"? what's different when you change that to "hotplug", or "interactive", or "performance", etc.? Thanks.

Click to expand...

Click to collapse

Hi !

Android CPU governors explained


1° OnDemand
2° Performance
3° Powersave
4° Conservative
5° Userspace
6° Interactive
7° Hotplug


1°: OnDemand Governor:
This governor has a hair trigger for boosting clockspeed to the maximum speed set by the user. If the CPU load placed by the user abates, the OnDemand governor will slowly step back down through the kernel's frequency steppings until it settles at the lowest possible frequency, or the user executes another task to demand a ramp.

OnDemand has excellent interface fluidity because of its high-frequency bias, but it can also have a relatively negative effect on battery life versus other governors. OnDemand is commonly chosen by smartphone manufacturers because it is well-tested, reliable, and virtually guarantees the smoothest possible performance for the phone. This is so because users are vastly more likely to ***** about performance than they are the few hours of extra battery life another governor could have granted them.

This final fact is important to know before you read about the Interactive governor: OnDemand scales its clockspeed in a work queue context. In other words, once the task that triggered the clockspeed ramp is finished, OnDemand will attempt to move the clockspeed back to minimum. If the user executes another task that triggers OnDemand's ramp, the clockspeed will bounce from minimum to maximum. This can happen especially frequently if the user is multi-tasking. This, too, has negative implications for battery life.

2°: Performance Governor:
This locks the phone's CPU at maximum frequency. While this may sound like an ugly idea, there is growing evidence to suggest that running a phone at its maximum frequency at all times will allow a faster race-to-idle. Race-to-idle is the process by which a phone completes a given task, such as syncing email, and returns the CPU to the extremely efficient low-power state. This still requires extensive testing, and a kernel that properly implements a given CPU's C-states (low power states).

3°: Powersave Governor:
The opposite of the Performance governor, the Powersave governor locks the CPU frequency at the lowest frequency set by the user.

4°:Conservative Governor:
This biases the phone to prefer the lowest possible clockspeed as often as possible. In other words, a larger and more persistent load must be placed on the CPU before the conservative governor will be prompted to raise the CPU clockspeed. Depending on how the developer has implemented this governor, and the minimum clockspeed chosen by the user, the conservative governor can introduce choppy performance. On the other hand, it can be good for battery life.

The Conservative Governor is also frequently described as a "slow OnDemand," if that helps to give you a more complete picture of its functionality.


5°: Userspace Governor:
This governor, exceptionally rare for the world of mobile devices, allows any program executed by the user to set the CPU's operating frequency. This governor is more common amongst servers or desktop PCs where an application (like a power profile app) needs privileges to set the CPU clockspeed.

6°: Interactive Governor:
Much like the OnDemand governor, the Interactive governor dynamically scales CPU clockspeed in response to the workload placed on the CPU by the user. This is where the similarities end. Interactive is significantly more responsive than OnDemand, because it's faster at scaling to maximum frequency.

Unlike OnDemand, which you'll recall scales clockspeed in the context of a work queue, Interactive scales the clockspeed over the course of a timer set arbitrarily by the kernel developer. In other words, if an application demands a ramp to maximum clockspeed (by placing 100% load on the CPU), a user can execute another task before the governor starts reducing CPU frequency. This can eliminate the frequency bouncing discussed in the OnDemand section. Because of this timer, Interactive is also better prepared to utilize intermediate clockspeeds that fall between the minimum and maximum CPU frequencies. This is another pro-battery life benefit of Interactive.

However, because Interactive is permitted to spend more time at maximum frequency than OnDemand (for device performance reasons), the battery-saving benefits discussed above are effectively negated. Long story short, Interactive offers better performance than OnDemand (some say the best performance of any governor) and negligibly different battery life.

Interactive also makes the assumption that a user turning the screen on will shortly be followed by the user interacting with some application on their device. Because of this, screen on triggers a ramp to maximum clockspeed, followed by the timer behavior described above.

7°: Hotplug Governor:
The Hotplug governor performs very similarly to the OnDemand governor, with the added benefit of being more precise about how it steps down through the kernel's frequency table as the governor measures the user's CPU load. However, the Hotplug governor's defining feature is its ability to turn unused CPU cores off during periods of low CPU utilization. This is known as "hotplugging."

Obviously, this governor is only available on multi-core devices.

Update ICS Firmware 4.0.6 - Overclock Edition !

HI !

NOW -> for all those who want this rom , I made an Update to Firmware 4.0.6 !

Work in update ....I'll release soon ....( today ! )

raised.fist said:

will there be an update to 4.0.6?

current version runs perfectly on my 1GHz model.

Click to expand...

Click to collapse

Hi!

YES, once the archos will update kernel source code in /gitorious/ -for firmware 4.0.6, now source code is just for 4.0.5 !

Pesach85 said:

Could you publish your sources? It may help me overlock my OMAP4430 device with 3.0.21 kernel

I'm interested especially on /arch/arm/plat-omap folder and /arch/arm/mach-omap2 folder

Cheers

Click to expand...

Click to collapse

Hi !

...sorry but I have no source ...( was removed from my PC ) !
- but it's no hard to do , just take a look here !
Good luck ! :good: