Develop Bugs

[07.aug.11][KERNEL]RAFPIGNA 2.0 OC [1.5ghz-Ext2/3/4-CIFS-UTF8-EAP-UV-EB-CLK]

RAFPIGNA KERNEL
Click to expand...
Click to collapse
1,5Ghz OC, Undervolted, Extended Battery Support and much more
​
This is my personal kernel, compiled for myself and for my builds, but some one asked to share it so...
I'm not a kernel expert and probably I can't give a lot of support on this, so don't expect anything
I mainly did this to fit some my needs in my builds, so I cannot guarantee that will work fine with others and that I will be able to fix issues.
Credits for the kernel development goes to the people that constaly work on it: specially Markinus e Danijiel but of course also Rajko, Cotulla, huyanu and all the other people involved.
A big thanks also to: Hastarin for his help and clear instructions to start.., ocm7 for the "night lesson" that gave my first compiled kernel, darkstone, crawlingcity
Use this kernel at your risk.
Speed is 998 as default, so standard for your phone. If you want to overclock you have to use an OC app.
Anyway DO IT AT YOUR RISK. I will not be responsible for damages to your phone!​
Main Features:
Based on master linux_on_wince_htc http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc and always keept updated to it
G-Sensor freeze patch and other small fixes
Patched with 1.5Ghz OC capability
Patched SMARTASS Governor to be more battery saver
Default speeds: 245 - 998 mhz
Default governor: interactive
Default undervolted to 925mV
SysFS interface to custom undervolt or overvolt (see post 2 for help), credit: -snq
Full cLK support, credit Cedesmith
Full support of two-way call recording, via external app (see here http://forum.xda-developers.com/showthread.php?t=993793 )
Patched for BT high-battery drain on GB builds (your rom must support it in init.rc! read here http://forum.xda-developers.com/showthread.php?t=1007774
Fully working HTC Headset support
Wi-Fi MAC address fix
Yaffs, Ext2, Ext3, Ext4, CIFS, UTF-8
RMNET as module
IEEE 802.1x/EAP authentication and Native Wifi-tethering (on GB/AOSP builds using the GB version)
Extended Battery Support (only original HTC EB 2300mAh) credits: Arne
My entire code, config, build script are stored on GIT. No unuseful diff files, no unuseful zips with configs.. just clone the git repo and you can see everything, launch the script and build your own clone.
For who cares, config and commits logs are also stored in the zip in the "devs" folder
Click to expand...
Click to collapse
Changelog:
My git repo: http://gitorious.org/~rafpigna/linux-on-wince-htc/rafpigna_linux_on_wince_htc
Code:
2.0 OC GB
Added two way call recording support (http://forum.xda-developers.com/showthread.php?t=993793)
Patched for high BT drain on GB builds (remember that to have this working, your rom must support it in init.rc! read here http://forum.xda-developers.com/showthread.php?t=1007774 )
Merged to master branch
2.0 OC
Added two way call recording support (http://forum.xda-developers.com/showthread.php?t=993793)
Patched for high BT drain on GB builds (remember that to have this working, your rom must support it in init.rc! read here http://forum.xda-developers.com/showthread.php?t=1007774 )
Merged to master branch
1.9 OC GB
[B]only for Gingerbread builds[/B]
Cleaned and tweaked Wifi drivers from tytung repo
Merged to master git
Added default UV to 925mv for more battery saving
Sysfs interface to custom control the UV parameters via shell or script
Added more cpu frequency steps, for improved smoothness and battery saving
Added Extended Battery support from Arne code. (HTC Original EB 2300mah)
Added multiport support
Added full cLK support including boot-to-recovery
Included again "01modules" in the zip file to avoid losing data.
1.9 OC
Merged to master git
Added default UV to 925mv
Sysfs interface to custom control the UV parameters via shell or script
Added more cpu frequency steps
Added Extended Battery support from Arne code. (HTC Original EB 2300mah)
Added multiport support
Added full cLK support including boot-to-recovery
Included again "01modules" in the zip file to avoid losing data.
1.8 OC NO SENSE
Merged with linux_on_wince_htc to apply last commits
http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc
[fixed netfilter errors and missing dependencies] Danijel
Added tytung AOSP wifi drivers and wpa_suplicant to enable IEEE 802.1x/EAP authentication and native wifi thetering on GB/NO SENSE builds
[B]Credit for this fix goes to TYTUNG[/B]
1.8 OC
Merged with linux_on_wince_htc to apply last commits
http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc
[fixed netfilter errors and missing dependencies] Danijel
1.7
(new temporary branch: NEWOC)
Added BFQ as default scheduler, TinyRCU, LZMA [from huanyu]
Tweaked Interactive governor [from huanyu]
Other small tweaks (see git)
1.6
Merged to master http://gitorious.org/linux-on-wince-htc/linux_on_wince_htc
[g-sensor calibration fix (no more facedown needed)] - Markinus
1.5
Fixed 245000 min frequency typo
1.4
Added no-oc on boot to avoid rebooting issues
1.3
Fixed low cpu values that causes drop of phone signal.
1.2
Tweaked Smartass governor
Set INTERACTIVE as default governor
1.1
Some cleanups
1.0
Added OC + Smartass governor
Click to expand...
Click to collapse
Download:
AT THIS MOMENT THE DOWNLOADS ARE ONLY FOR MAGLDR ROMS. IF YOU NEED CLK PLEASE CLICK HERE FOR A GUIDE ON HOW TO CONVERT. THANKS ARIF-ALI!
USING OTHER METHODS CAN CAUSE NO BOOTING, NO DATA OR OTHER ISSUES
Flash via ClockWord Recovery
I will not provide other formats
If you have issues flashing or something not works after flashing, check with your build chef if this zip is compatible with the partitions used by your build.
2.0 OC
This is working for all froyo/gb/aosp builds, but if you want max performance on Gingerbread, use the GB version
http://www.multiupload.com/H6TP0LFVJX
{
"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"
}
2.0 OC GB
This is working only on Gingerbread builds. Includes a wpa_suplicant file that will be pushed in your /system/bin folder to enable IEEE 802.1x/EAP authentication and native wifi tethering
http://www.multiupload.com/QV7AHSKTC9
Old versions:
1.9 OC
http://www.multiupload.com/AVBKLQSITQ
1.9 OC GB
http://www.multiupload.com/14RSYK5B28
1.8 OC
http://www.multiupload.com/OGY9NC4M75
1.8 OC GB
http://www.multiupload.com/SRW5CN4OIS
1.7
http://www.multiupload.com/LW7P00W69F
1.6
http://www.multiupload.com/ISZNS4LFH2
1.5
http://www.multiupload.com/NTBNV4EGGN
Click to expand...
Click to collapse
Donations:
I dont ask donations for this because mainly is based on the work from others and they deserves more than a "thanks". But since I put some efforts in this, would be nice if you can click on my "thanks" button to show you are thankful for this work
Anyway if you still want to offer me a coffe, it's appreciated.
Click to expand...
Click to collapse

Undervolting/Overvolting via SysFS
This is a risky operation.
You can burn your CPU. Do it at your risk.
I'm not responsible if you damage your phone. If you are doing this, is supposed you know what are you doing.
You can set the UV/OV values using some simple commands in shell or writing them in a file to push in your /system/etc/init.d folder that will be executed on boot.
File must be named like XXvoltages, where XX is a number that is not used by any other file in the folder.
Please find here an example file (credits: tyween) to restore on boot the voltage levels to standard one (1050mv)
If you want to change, just unpack the zip, change the 12vddlevels to your preferred one and re-pack the zip, to flash it via cwr or push the single file with adb or droid explorer or anything else.
http://www.multiupload.com/8CP9AF9UGO​
Advanced Instructions from -snq
usage:
query: (output: first column: frequency (kHz), second column: vdd* (mV))
Code:
cat /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
128000: 950
245000: 950
384000: 975
422400: 975
460800: 1000
499200: 1025
537600: 1025
576000: 1050
614400: 1075
652800: 1100
691200: 1125
729600: 1150
768000: 1175
806400: 1200
844800: 1200
883200: 1225
921600: 1225
960000: 1250
998400: 1275
1036800: 1275
1075200: 1275
1113600: 1300
1152000: 1300
1190400: 1300
incrementing/decrementing all levels by a specified amount* (mV):
Code:
echo '-25' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
echo '+25' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
adjusting the supply voltage* (second value, mV) at a specific frequency (first value, kHz):
Code:
echo '998400 1250' > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels
*: vdd values must be a multiple of 25 (enforced by the interface; the regulator doesn't accept other values - found out in the hard way)
please note that the values set through this interface will only be written to the acpu table - they will only become effective when the specific frequency is (re)set by cpufreq
i took the input parser from iscaela's code - thanks for it
do not apply this patch if you plan to use avs
to query the constraints of the regulator ("max_microvolts", "min_microvolts") or the voltage currently supplied to the cpu ("microvolts" (uV)):
Code:
grep '.' /sys/class/i2c-adapter/i2c-0/0-0048/regulator/regulator.0/*
Click to expand...
Click to collapse

cool will test

You might want to add in nice big caps no official extended battery support (I'm guessing it doesn't), won't be long until the requests flood in!!!
Sent from my DL DesireZ v3.4 final using Tapatalk

sorry but how do in install this via clock work ??

m_segura420 said:
sorry but how do in install this via clock work ??
Click to expand...
Click to collapse
Just open the recovery from the Magldr, choose the option update.zip and browse the file which should be on the root of your SD card. That's it. Reboot to Android.
Good to see a kernel developer! I will try this
Sent from my HTC HD2 using XDA App

Is this kernel also for SD builds or NAND only?

back to 1.5
i installed 1.6,waited 5',shutted down the phone,then again->on-rebooted 3 times....data corruption....
i have version 2.3 with ext4 1gb
going to wipe all and do fresh start with ext3 4kb
edit: after wipping only the ext part from ext4 to ext3,restored from CWM,updated the kernel,no more corruptions!!!
only issue ..its a little laggyyy,i think that 1.5 was faster...
edit2: back to 1.5...much better
1.6->to much lag,startup time very long,screen reaction not like 1.5,battery drenage BAD

Very nice kernel, I was on the brink of starting my own as I was waiting for the new proximity sensor/light sensor fixes to be implemented but yours is now on my HD2.
One thing, it did think my battery was at 0% until I pulled the charger and started charging again in which it then shot back up to 100%.

I have high battery drain on standby mode about 267mA with this kernel
i want to downgrade it to 1.5, can u pls give me the link of kernel 1.5?

with all the respect for raf...
here you go
http://www.multiupload.com/NTBNV4EGGN

Are you becoming a hacker?
Thanks, great.

i am using your DHD build, does it have this version of the kernal or i should update with this?

does this kernel support Extended battery ?

Some one is reporting higher battery drain then 1.5 but no changes are made to 1.6 except the g-sensor calibration fix.
I think that cause you have to reboot to install the kernel, you will always have an high battery drain on next boot with new kernel. Wait 10-20 minutes and you will see low battery drain. Actually I have 4ma in standby.

Nice try

calibrating the g sensor
boba23 said:
I can top that ;-) 3ma with markinus 1.71 build. great job raf, g-sensor cal works perfectly fine now, [email protected] .
boba
Click to expand...
Click to collapse
Hi, what did you use to calibrate the g sensor. I thought stock android did not come with any calibration tool

Thanks RAF.
i hope You will use that kernel for the next version of RafDroid.

Kazz88 said:
Hi, what did you use to calibrate the g sensor. I thought stock android did not come with any calibration tool
Click to expand...
Click to collapse
Markinus 1.71 is a DesireHD based build but with out HTC sense. It has the calibration tool
Sent from my HTC HD2 using XDA App

shree.cse said:
Markinus 1.71 is a DesireHD based build but with out HTC sense. It has the calibration tool
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
o i see. thank you. would anyone know the best way to calibrate a stock build with this fix. i dnt think apps from market would work

[MOD]^^^AOSP Modifier-Virtuous OC-I/OScheduler Setting ^^^

AOSP Modifier
Control Script Settings
Virtuous oc settings
Virtuous oc enable/disable
Set I/O Scheduler
Enable clean up on boot (Clears LOST.DIR and .trash on sdcard and clears dalvik and caches)
Tested on the latest MIUI Rom.
NEW
Set I/O Scheduler In the control script allows you to pick the default i/o scheduler and shows available i/o schedulers and current scheduler.
Must reboot before setting takes effect
The list shows which one is active with [ ] around the active one so it will look like this with sio:
0 performance
1 [sio]
2 conservative
...
Usage:
Flash zip file
Run terminal type "su" without the quotes
Then type "voc" without the quotes
Make your selections
You MUST enable virtuous oc before and freq settings will work and everything is remembered on reboot.
Enjoy​

Damn brother, 114 views and not one reply, it must be working on theirs too.

This is awesome! Thank you for posting this.
I got an error because my system was read only so make sure you're mounted as rw before you run this.
Sent from my HTC Glacier using XDA App

I need some testers anyone interested ? I'm gonna add my configurator to this device here is the post on it:
http://forum.xda-developers.com/showthread.php?t=1248809
It does ALOT and it should all work here too.
Lmk if anyone is interested in testing this.

[Q] Question about Calkulin's init.d Undervolt Scripts

Hey All,
I'm new here so sorry if this has already been asked. I was poking around the init.d scripts Calkulin has put up and I noticed that it doesn't seem to work. Here's the "4undervolt" script which you can find in /system/etc/init.d.
Code:
#!/system/bin/sh
#
# Created by Calkulin
# Epic 4G Touch -50mV v1.1
if [ -e /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table ]; then
UV_TABLE=`cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table | wc -l`
CPU_MAX_FREQ=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
STEPS_1600_200="1450 1350 1225 1125 1025 925 875"
STEPS_1704_200="1500 1450 1400 1350 1225 1125 1025 925 875"
if [ $UV_TABLE = "7" ] && [ $CPU_MAX_FREQ = "1600000" ]; then
echo $STEPS_1600_200 > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo "-50mV Undervolt Levels SET"
elif [ $UV_TABLE = "9" ] && [ $CPU_MAX_FREQ = "1704000" ]; then
echo $STEPS_1704_200 > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo "-50mV Undervolt Levels SET"
fi
fi
Well I just flashed 2.8.1 (I used to be on 2.5.1 with the same issue), and it seems like the UV_TABLE, which is supposed to be in /sys/devices/system/cpu/cpu0/cpufreq/, isn't there. This means that neither the if nor the elif is being taken, which basically means the script is having no effect.
Am I reasoning correctly? If so, it seems like it would affect a lot of people who think they're undervolting but really aren't. Could someone with more familiarity Android possibly take a look?
Also, is there a way for me to check the current voltage at the CPU?
Thanks!

If no one can help me, could anyone point me to somewhere I can get my question answered?
It seems like a lot of people could be having this problem if they're expecting the init.d scripts to work when they're really doing nothing.
Thanks.

Check the permissions of the scripts. Make sure they are executable

The permissions are rwxr-xr-x, so they do indeed seem executable. In fact I can run them from a terminal emulator and they don't print anything out. This also leads me to believe that while they're running, they have no effect.

parth750 said:
The permissions are rwxr-xr-x, so they do indeed seem executable. In fact I can run them from a terminal emulator and they don't print anything out. This also leads me to believe that while they're running, they have no effect.
Click to expand...
Click to collapse
Interesting. I'm running those scripts in Blazer ROM, and they work really well. Hopefully someone on Calk's can square you away

Well thanks for taking a look. I actually modified the script slightly, just to make sure I wasn't crazy, so that if the first if wasn't taken it would print "Script had no effect". I just ran the modified script, and it does print just that.
Maybe after one of Calk's kernel changes he lost init.d support? I'm running the stock Desperado - I guess it doesn't have support.

Ah, I figured it out. For the last several months, Calk has been running on Stock kernels repackaged by Rouge. This obviously means the UV_mV_table won't be there, which prevents undervolting. I flashed to the latest Hitman kernel and everything works like a charm!

parth750 said:
Ah, I figured it out. For the last several months, Calk has been running on Stock kernels repackaged by Rouge. This obviously means the UV_mV_table won't be there, which prevents undervolting. I flashed to the latest Hitman kernel and everything works like a charm!
Click to expand...
Click to collapse
So the stock 2.8.1 does not have undervolting enabled?
Sent from my Epic 4G Touch

Vandam500 said:
So the stock 2.8.1 does not have undervolting enabled?
Sent from my Epic 4G Touch
Click to expand...
Click to collapse
I can't remember which version is which but I believe there was one that required Tegrak to undervolt.
Sent from my SPH-D710 using xda premium

Vandam500 said:
So the stock 2.8.1 does not have undervolting enabled?
Sent from my Epic 4G Touch
Click to expand...
Click to collapse
Calkulin's ROMs from 2.5.1 to 2.8.1 (maybe more, I haven't checked) use a stock kernel, which means no undervolting and any undervolt zips you do flash will have no effect.
EDIT: Just ran through the changelog. Looks like he's been using a stock kernel since v2.0.1a.

I wasn't seeing much difference from flashing the -100 and -50 scripts on 2.8.1 so I switched to Hitman kernel, flashed the stock mV script, and use SetCpu instead, now it seems to drain slower.
Transmission sent from a Galaxy S II with XDA Premium

maybe one of you guys can answer this for me so i dont have to post a new thread as the search brings me to this thread for the question i have.
is it as easy as uninstalling setCPU and re-flashing a kernel to get back my stock undervolt settings? or do i have to reflash the ROM?
i am running the latest blazer 3.8 with gunslinger kernel

If you're using SetCPU to change voltages, and you don't remember stock voltages, you could always reflash your kernel. Make sure you uncheck SetCPU's "Set on boot" options first.
Team Rogue's Stock kernels feature init.d support, which means Calk's scripts would work... make sure you don't have a conflicting program installed, and that the correct permissions are in place for the folder and the scripts.

parth750 said:
Hey All,
I'm new here so sorry if this has already been asked. I was poking around the init.d scripts Calkulin has put up and I noticed that it doesn't seem to work. Here's the "4undervolt" script which you can find in /system/etc/init.d.
Code:
#!/system/bin/sh
#
# Created by Calkulin
# Epic 4G Touch -50mV v1.1
if [ -e /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table ]; then
UV_TABLE=`cat /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table | wc -l`
CPU_MAX_FREQ=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_max_freq`
STEPS_1600_200="1450 1350 1225 1125 1025 925 875"
STEPS_1704_200="1500 1450 1400 1350 1225 1125 1025 925 875"
if [ $UV_TABLE = "7" ] && [ $CPU_MAX_FREQ = "1600000" ]; then
echo $STEPS_1600_200 > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo "-50mV Undervolt Levels SET"
elif [ $UV_TABLE = "9" ] && [ $CPU_MAX_FREQ = "1704000" ]; then
echo $STEPS_1704_200 > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table
echo "-50mV Undervolt Levels SET"
fi
fi
Well I just flashed 2.8.1 (I used to be on 2.5.1 with the same issue), and it seems like the UV_TABLE, which is supposed to be in /sys/devices/system/cpu/cpu0/cpufreq/, isn't there. This means that neither the if nor the elif is being taken, which basically means the script is having no effect.
Am I reasoning correctly? If so, it seems like it would affect a lot of people who think they're undervolting but really aren't. Could someone with more familiarity Android possibly take a look?
Also, is there a way for me to check the current voltage at the CPU?
Thanks!
Click to expand...
Click to collapse
Based on my test, no init.d script was running at least on ICS. It's because there's something not working on the repacked kernel. There's workaround of this - check this out.
http://forum.xda-developers.com/showthread.php?t=1610741

[MOD] A100 Peformance Enhancing build.prop for CM9 / ICS 4.0.4

**Latest Working Revision is Rev-0.4 ** 07/28/12
**Now optional A500 build.prop for extra games/apps from Play Store**
**Thanks das_webos_transformer for testing 4.0.3 and submitting working tweaked 4.0.3 build.prop!! **
**UPDATE** Rev-0.4 For 4.1.1 Jelly Bean << NEW>>
This build.prop is specifically made for ICS and Jelly Bean - has been tested working and verified to improve performance. A500 mod now is working great.
I've been working on getting my A100 to smoking speed / performance and with my custom build.prop for ICS in combination with ezTerry's custom kernel, I think I have achieved the goal!
Yea Yea, So why another build.prop on xda? Well I was looking through the forums and noticed that there isn't much posted for ICS, there are HC tweaks, but the ones that ARE posted for ICS seem to fail.. I am confident that this build.prop will work as long as the person installing reads the instructions and information in this post thoroughly :good:
**EDIT 08/04/2012 - I was originally using the ezTerry kernel overclocked to 1.5 using the lulzactive governor, I am currently testing my own custom kernel that I haven't decided to release yet as I am still testing it myself before I publish - Before the build.prop, my AnTuTu Benchmark score was 6200, after the build.prop I get 7118, Both scores with ezTerry kernel and cm9 ; With stock kernel and stock rom score was <6000. So, that's just a benchmark.. -NO - The main thing is - you can actually feel the difference, and it is easily noticeable, so it's not just a benchmark thing! Here is what this build.prop does:
Enhancements:
*Faster Boot
*Home Screen stored in Memory
*WiFi Data rates increased
*WiFi Scan rate decreased to preserve battery
*Media and Image Quality increased
*Disable verbose kernel logging (consumes less memory/battery)
*HW Acceleration prioritized
*Increased Window Manager / GUI events per second
...Overall Performance is definitely noticeable!
*Optional* the A500 hack has been tested and working with games and shows extra apps in Play Store see notes below.
File naming conventions:
>>Please choose your android release version in #.#.# <<<
build.prop-#.#.#-supertweak-a100-revX.X.txt == Tweaked version keeping device recognized as an A100
build.prop-#.#.#-supertweak-a100-revX.X-A500 == Tweaked version tricking apps/system to think it is A500
build.prop-#.#.#-vanilla-a100-revX.X-A500 == A500 trick with no enhancements or tweaks
**Thanks to das_webos_transformer for testing making necessary changes for cm9 4.0.3 release!**
How to install:
*Download the appropriate build.prop file attached below that you wish to test (see above naming conventions)
*You must have root, and you must mount /System rw (use Root Explorer or similar tool)
*Rename the attached file to: build.prop
*Move the existing /System/build.prop to /System/build.prop.bak
*Move the new file to /System/build.prop
*Reboot to recovery - Wipe Cache - Wipe Dalvik - Reboot System <<Important!! It won't work if you don't do this step!
*Wait for System to upgrade applications and Start to Home Screen. (initial boot takes a while, don't worry after this it wont)
*Reboot again.. Enjoy the performance
**07/28/2012 - A500 build.prop for A100 device back up, tested and working with performance mods intact. Grab the file with revX.X-A500.txt at the end of the file name. This allows extra apps to show up in Play Store/Market and your device will be recognized as the A500 instead of A100. Please don't forget to Wipe Dalvik and Cache before booting. First boot will take a while to update the apps.
**07/28/2012 - If you used the Rev.03 file please update to Rev.04 there was a minor error in the previous build.prop relating to windowmgr max events per second, this had a big impact in the performance and should be fixed in Rev.04

linuxsociety said:
**Edit Please note that the original title of this thread said ICS 4.0.x, it should be ICS 4.0.4 (as it is now) - This build.prop is specifically made for 4.0.4 - this is very important as keys such as: ro.build.version.release=4.0.4 ro.build.id=IMM76L if you know what you are doing you can make minor alterations to fit your build and it will work, but you need to research and do this at your own risk if you aren't using 4.0.4 (hint: ICS 4.0.3 is IML74k) **
I've been working on getting my A100 to smoking speed / performance and with my custom build.prop for ICS in combination with ezTerry's custom kernel, I think I have achieved the goal! PLUS you *should* get all apps that the A500 gets in the Play Store, AND the responsiveness of the tablet is just lightening fast.
Yea Yea, So why another build.prop on xda? Well I was looking through the forums and noticed that there isn't much posted for ICS, there are HC tweaks, but the ones that ARE posted for ICS seem to fail.. I am confident that this build.prop will work as long as the person installing reads the instructions and information in this post thoroughly :good:
I am using the ezTerry kernel overclocked to 1.5 using the ondemand governor. Before the build.prop, my AnTuTu Benchmark score was 6998, after the build.prop I get 7494, Both scores with ezTerry kernel and cm9 ; With stock kernel and stock rom score was <5900. So, that's just a benchmark.. -NO - The main thing is - you can actually feel the difference, and it is easily noticeable, so it's not just a benchmark thing! Here is what this build.prop does:
Enhancements:
*A500 Market/Play Store compatibility
*Faster Boot
*Home Screen stored in Memory
*WiFi Data rates increased
*WiFi Scan rate decreased to preserve battery
*Media and Image Quality increased
*Disable verbose kernel logging (consumes less memory/battery)
*HW Acceleration prioritized
*Increased Window Manager / GUI events per second
...Overall Performance is definitely noticeable!
How to install:
*You must have root, and you must mount /System rw (use Root Explorer or similar tool)
*Rename the attached file to: build.prop
*Move the existing /System/build.prop to /System/build.prop.bak
*Move the new file to /System/build.prop
*Reboot to recovery - Wipe Cache - Wipe Dalvik - Reboot System <<Important!! It won't work if you don't do this step!
*Wait for System to upgrade applications and Start to Home Screen. (initial boot takes a while, don't worry after this it wont)
*Reboot again.. Enjoy the performance
** This has been tested with only 4.0.4 CM 9-20120708 A100 so far (see http://forum.xda-developers.com/showthread.php?t=1597102 ) testers please report results!**
**Note it is very important to know that this build.prop isn't the only thing boosting the performance of my A100 - ezTerry's Kernel OC'd @ 1.5ghz plays a big part in it too! You can find the kernel and instructions for flashing it here: http://forum.xda-developers.com/showthread.php?t=1703683 It is also important that you know that after you use this build.prop your device will register with all apps as an A500 Iconia and not a A100 so if that is an issue with some app you use then please take this into consideration. I will edit this post soon with a build.prop that enables the performance options and keeps the A100 recognized as an A100. I'm sure there will be people who want that also.
*More to come:
* I plan to clone the sources used in ezTerry's kernel and slightly modifying his config in an attempt to patch with CK/PF patches for mainline. I'd like to see the performance when using Brain F**k Scheduler (BFS) in combination with BFQ IO scheduler. These patches also have other features like l7, LinuxIMQ, which may be fun to play with on Android with networking apps (if they will even compile with arm toolchain) I'll keep everyone informed on my progress with this, but I'm saving that work for a rainy day.
Enjoy your A100
Click to expand...
Click to collapse
Have I already supercharger v6, sera compatiblly? Is it a script? That is what I have to install? I neither have kernel Ezterry, nor have intention of putting it with CM9. In all that you put the link, we will prove it ... a greeting and graces.

Fransis88 said:
Have I already supercharger v6, sera compatiblly? Is it a script? That is what I have to install? I neither have kernel Ezterry, nor have intention of putting it with CM9. In all that you put the link, we will prove it ... a greeting and graces.
Click to expand...
Click to collapse
Hi and thanks for checking it out, it isn't a script, it just replaces the file that already exists in /System/build.prop
The file that is attached is made specifically for ICS 4.0.4, you DO NOT have to have eZterry's kernel for this to work, I have tested it only with his kernel (which allows overclocking to 1.5ghz and the use of BFQ I/O scheduler) and had great improvements on my A100. I would like to see how it works for you with your current setup if you are on 4.0.4 If it doesn't work then you just replace /System/build.prop with the file you backed up named /System/build.prop.bak
Don't forget to wipe cache and wipe dalvik
Thanks again

If someone is viewing this thread that is using the stock OFFICIAL ICS 4.0.3 or 4.0.4 firmware could you please pastebin /upload/share your /system/build.prop ? I'd greatly appreciate it, there seems to be some values that have changed recently, and I need to adjust my build.prop in this thread accordingly to the official releases. Thanks again

linuxsociety said:
If someone is viewing this thread that is using the stock OFFICIAL ICS 4.0.3 or 4.0.4 firmware could you please pastebin /upload/share your /system/build.prop ? I'd greatly appreciate it, there seems to be some values that have changed recently, and I need to adjust my build.prop in this thread accordingly to the official releases. Thanks again
Click to expand...
Click to collapse
So in my case, since podras to see in the captures, I have lost performance. I have CM9. And I have never had blackouts or problems. Aviary the keyboard on screen, I use swiftkey and it has never trumped me. So after trumping the keyboard, suddenly salio the image of take-off of the CM9 and was restarting the tablet. you eat it has happened to me. Now I have returned to my original build.prop. A greeting, I leave the captures you of antutu in order that you see, if I can help you in some kind of mas...
my build.prop
{
"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 build.prop

Fransis88 said:
So in my case, since podras to see in the captures, I have lost performance. I have CM9. And I have never had blackouts or problems. Aviary the keyboard on screen, I use swiftkey and it has never trumped me. So after trumping the keyboard, suddenly salio the image of take-off of the CM9 and was restarting the tablet. you eat it has happened to me. Now I have returned to my original build.prop. A greeting, I leave the captures you of antutu in order that you see, if I can help you in some kind of mas...
Click to expand...
Click to collapse
Francis88: thanks for testing the build.prop, I am sorry to see you had a slight performance decrease in your score. There are many things that could have impacted that score. Did you wipe the caches before you ran the benchmark? Do you have any other performance mods intact? What CPU governor was you running with the tests? the same cpu frequency with both?
Was this ran using a stock kernel? Which build of CM9 did you use?
Could you please put your original build.prop on a pastebin site and give the link here so we can see the differences? Thanks!

Francis88: please use the Rev.04 I think the reason your original build.prop out performed the one you got here has been resolved, there was a minor error in the Rev.03 file that you grabbed. Sorry for the inconvenience bro. Thanks
If anyone here is using a custom build.prop that makes their a100 register as an A500, please let me know if Angry Birds loads for you. I have been trying to resolve the issue with the a500 customization that prevents some games/apps from loading on my CM9 4.0.4 rom. If you have the A500 build.prop customization working and loading games like Angry Birds, can you please provide your build.prop so I can take a look at what may be causing this issue for me ** Edit - <<Solved in Rev.04

The proof is in the puddin'
I just wanted to post these 3 different results so people can see the difference it makes. All 3 runs were controlled, with no background apps, same CPU governor (lulzactive), same frequency (1500mhz), etc.
Rev0.4 Tweaked A100 (not A500) Results with AnTuTu Benchmark:
Rev0.4 Tweaked with A500 mod:
Default build.prop from ICS CM9 (no optimizations):

all I did was change it to work for 4.0.3. I don't know any of the changes for ics, I learned and still learning on froyo and a little cm7. But the changes required for this took about 1 minute.
Not sure how to post an upload on xda. So https://www.box.com/shared/24e5b156fbf12858d946
Also added linpack score.
sent from my ICONia

Uploaded with ImageShack.us
New result. Better good
Enviado desde mi A100 usando Tapatalk 2

Fransis88 said:
https://skydrive.live.com/redir.aspx?cid=b6039d5a2d5945e7&resid=B6039D5A2D5945E7!6737&parid=B6039D5A2D5945E7!114&authkey=!AKcWuovSxOsq82Y[/IM
New result. Better good
Enviado desde mi A100 usando Tapatalk 2[/QUOTE]
you forgot to close the tried to manually view it by copying the URL but it says file no longer exists on skydrive. Glad to see you got better good results with Rev.0.4
Click to expand...
Click to collapse

Excellent results.
sent from my ICONia

Jelly Bean 4.1.x build.prop is in the OP - personally tested and verified by me.. I also have been putting some effort into doing some kernel optimization for Jelly Bean for all of those people who liked the ezTerry kernel back when it was fresh. So far I have done the following:
*patched the kernel with code for compatibility with Tiny HAL in Jelly Bean with backwards compatibility with ICS
*added all I/O schedulers including: bfq, cfq, deadline, and noop - default being 'deadline'
*built in support for CIFS/SMB file systems, NTFS (write)
*More cpu governors are built in including: interactive, ondemand, performance, powersave, userspace, lulzactive, and conservative
*Optional Overclock up to 1504mhz, scaling ranges included are: 216, 312, 456, 608, 760, 816, 912, 1000, 1200, 1408, and 1504 - default is set to factory 1000Mhz
I haven't released the kernel yet as I want it thoroughly tested before hand, and I want to be sure all source changes are fully documented. Kernel Sources are based off CM9 A100/A500 Kernel, Nvidia Android 2.6.39.4 Tegra, Nvidia Android 3.1 (Grouper) - Thanks to eZterry for the original kernel that made so many happy - I just took it into my own hands to bring things up to date with better compatibility with ICS and JB.
Sorry if this seems to be vaporware, just want everyone testing my build.prop to know that I am currently putting more time and effort into the development of a better kernel at the moment and WILL keep my projects linked. Before I do release any zImages or sources I want everyone to be well aware that once they use my kernel that they can NOT report issues of any kind to CM9/10 developers (on the project pages) as the use of any kernel other than the one obtained with your ROM makes your device unsupported by the developer of your ROM!! If you have any issues with JB, ICS, or any ROM you use this kernel with, then you will need to report it on my kernel thread (which I haven't yet made, but once I do a release I will have the thread ready)

I can confirm this does work on cm10. I'll test the market when I get on WiFi, I'm tethering from my phone currently....sprint 3g... from and older phone.....sigh
Also should note I am over clocked to 1.2ghz.
Also, @Linuxsociety i f you want I'll test your kernel, love that testing!
EDIT Market works Fine and games do play
sent from my sexy-a$$-iconia tab

guys when i try to download a build.prop i click on it and it opens the file.same with the QR.how can i download it?

labros1995 said:
guys when i try to download a build.prop i click on it and it opens the file.same with the QR.how can i download it?
Click to expand...
Click to collapse
You need to save the download link instead of open it, if you are using your tablet try long pressing the link and look for an option for "save target" Not sure exactly how your browser on the tablet works, i usually download them to my PC and then
Code:
adb push /path/to/downloaded-build.prop /sdcard/
Then on the tablet I move the /sdcard/downloaded-build.prop to /system/build.prop (after backing up the original build.prop to /system/build.prop.bak) <You have to be rooted and /system has to be mounted as RW to do this, I recommend Root Explorer. Be sure that your downloaded file has the same permissions as the original build.prop.
Hope this helps

the problem is that it doesn't ask for download or open.when i click it just opens the txt

labros1995 said:
the problem is that it doesn't ask for download or open.when i click it just opens the txt
Click to expand...
Click to collapse
In dolphin, just long press the file link, click 'save link', then rename it build.prop

Romman0 said:
In dolphin, just long press the file link, click 'save link', then rename it build.prop
Click to expand...
Click to collapse
or when it opens as text, just save as build.prop fom the text editors menu.

It worked guys.Thanks a lot

[SCRIPT] Governor Tweaks | Increase performance

Hi everybody
Ones again I am here to guide you to increase there performance of you device.
To make it smooth n lag free.
Well, it took a whole week to complete these scripts so please shower this thread will positive views.
This Scripts are strictly for GALAXY Y only. Do not try it in any other device.
The following scripts attemps to make your phone battery dures more time or your phone more responsive and smoother by modifiing some governor's parameters.
It will set CPU min freq at 234 MHz and max at 832 MHz, the governor in the script name, BFQ scheduler and apply tweaked tunables for battery or performance.
Steps of Install
Download Script Manager
Download the script and placed it in the root of your sd-card
Open SManager >> explore to the scripts >> select the one you want to integrate >> check script >> root >> set at boot [set at boot is optional]
In arguments, write b or p within you want battery or performance optimisations
Click save
Click Run
Downloads :
1.Interactive-governer.sh
2.Conservative-governer.sh
The following scripts are tested and working on the following kernel :
1. Merruk kernel
2. Savie's kernel
Credits:
Pending....
Please test it on other kernels and report me, I will add you in Credits.
More scripts are comeing soon.
I will be not responsible if you brick your device or dead sd card or anything happen to your device.
Please give me credit if anyone mirror my work.
Dont forget to hit Thanks.
What Doesn't Kill Makes Me AWESOME

Governor for over-clocked devices are coming soon.
What Doesn't Kill Makes Me AWESOME

Downloading and trying...
Sent from my GT-S5360 using Xparent Cyan Tapatalk 2