Database Info

SD Card Speed Fix!! IMPLEMENT INTO CM7 PLEASE

http://forum.xda-developers.com/showthread.php?t=921530
THIS WORKS on the Aria. BIG DIFFERENCE!

akira02rex said:
http://forum.xda-developers.com/showthread.php?t=921530
THIS WORKS on the Aria. BIG DIFFERENCE!
Click to expand...
Click to collapse
I just tried this, and it appears that the tweak to the file makes a difference in speed tests.
I'm trying to get my hands around how to actually test it in real-world situations.
So for CM7 - this would definitely be a nice addition to this already excellent ROM...

akira02rex said:
http://forum.xda-developers.com/showthread.php?t=921530
THIS WORKS on the Aria. BIG DIFFERENCE!
Click to expand...
Click to collapse
This should have been posted in the CM7 thread. Why start a new one?
Here is a flashable zip that will add the fix to an init.d script and will survive reboot. It checks to see if the value is 4, and if so changes it to 128. You have to apply it after each new rom flash.

This can be tested with adb pull.
Pull it with the setting at 4. pull pack the cm rom to a local folder. you will get speed stats. after the first pull, set the param to 128. pull again.
syntax from adb: adb shell echo 128 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
from terminal - just skip the adb.
one note, I tried this on my Aria - it broke adb transfers. Then I tried it again and it worked.
Before I add this to CM, I want to make sure it's reliable.

The gallery loads even faster.
Sent from my Liberty using XDA App

attn1 said:
This can be tested with adb pull.
Pull it with the setting at 4. pull pack the cm rom to a local folder. you will get speed stats. after the first pull, set the param to 128. pull again.
syntax from adb: adb shell echo 128 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
from terminal - just skip the adb.
one note, I tried this on my Aria - it broke adb transfers. Then I tried it again and it worked.
Before I add this to CM, I want to make sure it's reliable.
Click to expand...
Click to collapse
Im at 128 with the update.zip I posted above, and I can adb pull and push to my hearts content. I am on nightly 18 BTW.

bkmo said:
Im at 128 with the update.zip I posted above, and I can adb pull and push to my hearts content. I am on nightly 18 BTW.
Click to expand...
Click to collapse
the correct way is to add it to init.rc - that's when I had a failure. but the failure is not consistent.

bkmo said:
This should have been posted in the CM7 thread. Why start a new one?
Here is a flashable zip that will add the fix to an init.d script and will survive reboot. It checks to see if the value is 4, and if so changes it to 128. You have to apply it after each new rom flash.
Click to expand...
Click to collapse
On cm, if you want to preserve an init script, you can do anyone of the following:
Save it in /sd-ext/userinit.d/
Save it as /sd-ext/userinit.sh
Save it as /data/local/userinit.sh
Use cm's backuptool, it runs on rom installation. Just save its path (without the leading "/system/") into /system/etc/custom_backup_list.txt
Code:
etc/init.d/04sdcardspeedfix

Apparent improvement
Just flashed the above posted zip on CM7 Nightly 18 - seems to be a dramatic improvement, at least in stats, on my cheapie class 6 card:
before update: Write 5 / Read 6
after update: Write 4 / Read 12
I did not conduct this test at all scientifically - just ran one speed test before and one after the update, so take it for what it's worth I guess...just figured I'd share.

attn1 said:
the correct way is to add it to init.rc - that's when I had a failure. but the failure is not consistent.
Click to expand...
Click to collapse
I have it running as an init.d script and cannot make it fail. I do see this tweak posted in a lot of different forums.

Looks like this thread is now dead. This has been commited to cm7.

bkmo said:
Looks like this thread is now dead. This has been commited to cm7.
Click to expand...
Click to collapse
I dont quite understand. This last change set it back to 4? We still gotta manually change it? Or that's just the MIN value?

Darius_bd said:
I dont quite understand. This last change set it back to 4? We still gotta manually change it? Or that's just the MIN value?
Click to expand...
Click to collapse
The last commit is making a correction for the nand flash after the sd commit changed all memory readahead to128.

.
Gotcha, thanks for the clear up

bkmo said:
The last commit is making a correction for the nand flash after the sd commit changed all memory readahead to128.
Click to expand...
Click to collapse
Correct! The changes will be built in tonight's nightly.

Have anyone who can build boot.img already flashed the new kernel files? Is Wi-Fi broken? Or just me?
Sent from my Liberty using XDA App
EDIT: sorry... my bad, it's my typo of modules folder

[Q] I need help on zipalign.

What is zipalign, what are the benefits of zipalign and how do i do this?
Thank you

60 views but 0 replies
Someone help me please

just use the search option

EdisDee said:
just use the search option
Click to expand...
Click to collapse
I find just one thread with the same question and that thread also has only 2 posts and the person who made the thread posted saying he found the answer but never mentions what the answer is.

I found something about placing a file in the init.d folder but the file was not specified so if anyone has the file in their init.d folder could they copy it to their sd card, upload it to dropbox or any other file share website and share it with me please.

Help please

I know this is bloody perfect forum but sometimes you just need to jump out for a while. It's easier.
"The Android SDK includes a tool called zipalign that optimizes the way an application is packaged. Running zipalign against your application enables Android to interact it more efficiently at run time and thus has the potential to make it and the overall system run faster. We strongly encourage you to use zipalign on both..."
source: http://developer.android.com/resources/articles/zipalign.html
Enable? Nor sure. Kyrillos has it by default. I don't remember about others...
EDIT: Remove ".TXT" and place in /etc/init.d (or /system/etc/init.d). I belive it should be enoguh but can't say for sure. I only hope Kyrillos will not mind, it is from his 8.1 rom. Or hillbeast who edited it to work with hybrid.

mrvek said:
I know this is bloody perfect forum but sometimes you just need to jump out for a while. It's easier.
"The Android SDK includes a tool called zipalign that optimizes the way an application is packaged. Running zipalign against your application enables Android to interact it more efficiently at run time and thus has the potential to make it and the overall system run faster. We strongly encourage you to use zipalign on both..."
source: http://developer.android.com/resources/articles/zipalign.html
Enable? Nor sure. Kyrillos has it by default. I don't remember about others...
EDIT: Remove ".TXT" and place in /etc/init.d (or /system/etc/init.d). I belive it should be enoguh but can't say for sure. I only hope Kyrillos will not mind, it is from his 8.1 rom. Or hillbeast who edited it to work with hybrid.
Click to expand...
Click to collapse
I did what you said. I am rebooting the phone now and hopefully your help is sufficient

Smonic said:
What is zipalign, what are the benefits of zipalign and how do i do this?
Thank you
Click to expand...
Click to collapse
Download "ADB Mask Controller"
install it, connect your phone with USB debugging enabled.
Make sure the connection is detected by the application, click on the refresh button beside SEARCH Option in the program.
in the first screen, you will find option "Push Zipalign" Do that.
Go to the screen titled "Zipalign"
select the optioin you want to use zipalign for user app or system app or both.
Caution : Use this tool judiciously, it has many advanced features used by ROM developers mainly. Like pushing an app to system, removing bloatware, Sql LIte, and many many more.....A wrong step may force you to reflash your ROM.
Hope it helped.

umangsagar said:
Download "ADB Mask Controller"
install it, connect your phone with USB debugging enabled.
Make sure the connection is detected by the application, click on the refresh button beside SEARCH Option in the program.
in the first screen, you will find option "Push Zipalign" Do that.
Go to the screen titled "Zipalign"
select the optioin you want to use zipalign for user app or system app or both.
Caution : Use this tool judiciously, it has many advanced features used by ROM developers mainly. Like pushing an app to system, removing bloatware, Sql LIte, and many many more.....A wrong step may force you to reflash your ROM.
Hope it helped.
Click to expand...
Click to collapse
I clicked on 'push zipalign' a number of times and then clicked on zipalign data/app but nothing happens. It says zipalign not found. Push zipalign and try again or sth like that. I've rebooted my phone and i'm trying now,

Check if you have /system/bin/zipalign. If not try to put it there manually.
ADB controller might have problems mounting your /system r/w and it is read-only. Maybe you can mount it r/w and then try with controller (just guessing, though).
And you'll need to have the S03_zipalign made by kyrillos and hillbeast in /system/etc/init.d (or just /etc/init.d) posted earlier. For what I can tell it zipalign's all apps from /system/app and /data/app.

mrvek said:
Check if you have /system/bin/zipalign. If not try to put it there manually.
ADB controller might have problems mounting your /system r/w and it is read-only. Maybe you can mount it r/w and then try with controller (just guessing, though).
And you'll need to have the S03_zipalign made by kyrillos and hillbeast in /system/etc/init.d (or just /etc/init.d) posted earlier. For what I can tell it zipalign's all apps from /system/app and /data/app.
Click to expand...
Click to collapse
I second that esp rw option, its already there in ADB Controller. U can manually browse as instructed above. Its not that difficult, I am sure u will be able to do it well, reply here if u still get probs even after taking all steps as directed in my previous post and the post i quote above.

umangsagar said:
I second that esp rw option, its already there in ADB Controller. U can manually browse as instructed above. Its not that difficult, I am sure u will be able to do it well, reply here if u still get probs even after taking all steps as directed in my previous post and the post i quote above.
Click to expand...
Click to collapse
Thanks for the help. I'll go back and thank the posts
Anyway i decided not to do any tweaks because i always end up flashing a different ROM anyway, I'm weak when it comes to flashing ROMS
It's like an addiction

Smonic said:
Thanks for the help. I'll go back and thank the posts
Anyway i decided not to do any tweaks because i always end up flashing a different ROM anyway, I'm weak when it comes to flashing ROMS
It's like an addiction
Click to expand...
Click to collapse
hahhahahha...this tweak is not that difficult to implement..and i guess pretty safe...agree totally to the last line

I thought I'd give this a go. I've moved the first file on the previous page to system/etc/init.d and the second file on the top of this page to system/bin. Is this sufficient?

you mean to say you have s03_zipalign in /system/etc/ini.d and zipalign file posted above as /system/bin/zipalign ??
i guess this should do for you .. awaiting to hear if u succeeded.

umangsagar said:
you mean to say you have s03_zipalign in /system/etc/ini.d and zipalign file posted above as /system/bin/zipalign ??
i guess this should do for you .. awaiting to hear if u succeeded.
Click to expand...
Click to collapse
It's working fine. The apps load up fast and i'm happy Thanks!

[Q] Setting liveoc values on boot.

Hi i was wondering if what is the proper way to use an init.d file. I want to set my liveoc value to 105 on boot using an init.d file. I edited the line below in an init.d file using a file manager with root rights.
echo 105 > /sys/class/misc/liveoc/oc_value
but somehow it does not work. do i need special permissions for this??

There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz

frutelaken said:
There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz
Click to expand...
Click to collapse
yupp its great!! i'm using it in the mean time. but i really want to know the proper way to go about using init.d files. if someone could help that would be greatly appreciated!!

Hey guys, So how I would use script manager? I want to the same of running the script at boot so liveoc starts at reboot! Thanks!
Sent from my Google Nexus S using Tapatalk

frutelaken said:
There's an app called "Script Manager" that lets you create scripts and have them executed at boot
Greetz
Click to expand...
Click to collapse
yes its great try it "Script Manager" hope you like it sory for my bad eng

idelgado782 said:
Hey guys, So how I would use script manager? I want to the same of running the script at boot so liveoc starts at reboot! Thanks!
Sent from my Google Nexus S using Tapatalk
Click to expand...
Click to collapse
I just learned all this.. so here's my take.
You simply put your script to the /init.d subfolder in /system/etc
There's one more essential step, you'll see all the scripts named with "01, 02" etc. I named mine as "58liveoc" as another post in Dec section recommended. Keeps it out of the way of system scripts and tweak scripts for kernel.
make sure you have " #!/system/bin/sh" at the top and have voltages and Max frequently set before echo for live_oc
see live oc thread for some demo scripts, backup your device!!!!
---------- Post added at 02:43 PM ---------- Previous post was at 02:36 PM ----------
Almost forgot match permissions of file to that of existing ones... should be rwxr-x--- also change owner to 0 root and group 2000 shell.... did it all using root explorer

ecksion said:
I just learned all this.. so here's my take.
You simply put your script to the /init.d subfolder in /system/etc
There's one more essential step, you'll see all the scripts named with "01, 02" etc. I named mine as "58liveoc" as another post in Dec section recommended. Keeps it out of the way of system scripts and tweak scripts for kernel.
make sure you have " #!/system/bin/sh" at the top and have voltages and Max frequently set before echo for live_oc
see live oc thread for some demo scripts, backup your device!!!!
---------- Post added at 02:43 PM ---------- Previous post was at 02:36 PM ----------
Almost forgot match permissions of file to that of existing ones... should be rwxr-x--- also change owner to 0 root and group 2000 shell.... did it all using root explorer
Click to expand...
Click to collapse
oh wow!! hmmm ok i'll give it a shot. thanks for the help. cheers.
edit: i tried what you told me and did it exactly but its still not setting my live oc on boot. is there something else i am missing??

tinselttown said:
oh wow!! hmmm ok i'll give it a shot. thanks for the help. cheers.
edit: i tried what you told me and did it exactly but its still not setting my live oc on boot. is there something else i am missing??
Click to expand...
Click to collapse
OK.. Im sure we can figure it out here
So step 1 you're using a kernel that supports live oc
Step 2 script has been copied from SD to init.d and then permissions and group set(not sure if those stick when copy/pasting)
Step three I guess is renaming it
And step 4 is the script itself...
Are you using one of the preset scripts?
If not.. what values? Voltage/Max/min/oc/gov's
When I screwed mine up my phone would crash left and right
..
Hmm... oh make sure "run on boot" is unchecked in SM for said script... reboot and CPU frequency. Should all be set as desired....
Lemme know? I'm not an expert but if you've got the time Im happy to help

does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks

xtracrispy said:
does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks
Click to expand...
Click to collapse
I think its best to use multiples of 5. That being said I think its capped at 125. Also it requires higher voltages the higher you set it. If you want a 200 MHz bus you can use trinity kernel its compiled at 200 and keeps lowest possible voltages while giving overclock aswell

wait hang on...
I always thought it was a double pumped bus, so 100 base close = 200 bus, the trinity kernel's not actually 2x faster bus than anything else, is it?

xtracrispy said:
does anyone know if you need round numbers for this to work?
or will something like 113 be such an odd multiplier that it breaks
Click to expand...
Click to collapse
yupp it works for odd numbers but like ecksion said its better to use multiples of 5.

ecksion said:
OK.. Im sure we can figure it out here
So step 1 you're using a kernel that supports live oc
Step 2 script has been copied from SD to init.d and then permissions and group set(not sure if those stick when copy/pasting)
Step three I guess is renaming it
And step 4 is the script itself...
Are you using one of the preset scripts?
If not.. what values? Voltage/Max/min/oc/gov's
When I screwed mine up my phone would crash left and right
..
Hmm... oh make sure "run on boot" is unchecked in SM for said script... reboot and CPU frequency. Should all be set as desired....
Lemme know? I'm not an expert but if you've got the time Im happy to help
Click to expand...
Click to collapse
ok i have done step 1-3 correctly. about the script i am using the one that is written for my phone, i just changed the liveoc value. is it a must to include all the steps?? can i just set the oc values and not set the stuff i don't want to change?? because currently i have only that line included in the script. i also have a test script inside init.d which does not execute as well which makes me believe that the scripts in init.d aren't being run on boot.

[TWEAK] How to get more RAM and speed up responses!

I was browsing at the Android Software and Hacking General thread and I just found this. I tested this on my phone and I think I got 10 - 20MB of free RAM. I'm still not sure if this will work for you, but you can give it a try..
According to the OP..
This is not useful in odexed ROMs & devices with 1GB or more RAM. However, this will give a performance boost in deodexed ROMs as much as odexing system & data apps. This is an alternative for odexing. It's not that you can't apply this tweak on an odexed ROM but rather, it's useless to do so.
Click to expand...
Click to collapse
Advantages:
More free RAM.
Faster launch for system & user apps during the second launch.
Gives as much as of a performance boost as ODEX without odexing. Themer friendly.
Smoother app switching.
Disadvantages:
Might break some apps.
Click to expand...
Click to collapse
Here's the link to the original thread:
http://forum.xda-developers.com/showthread.php?t=1263119
Dont forget to give him your thanks if it works! And for me too
Credit goes to nibras_reeza
NOTICE:
Please don't use this tweak for those who already installed the CF-Root by ganeshbiyer, this tweak is already integrated to the kernel itself.

Silentkiller101197 said:
I was browsing at the Android Software and Hacking General thread and I just found this. I tested this on my phone and I think my I got 10 - 20MB of free RAM. I'm still not sure if this will work for you, but you should give it a try..
According to the OP..
Here's the link to the original thread:
http://forum.xda-developers.com/showthread.php?t=1263119
Dont forget to give him your thanks if it works! And for me too
Credit goes to nibras_reeza
Click to expand...
Click to collapse
I think this tweak in all ROM's

TheFrankenstain said:
I think this tweak in all ROM's
Click to expand...
Click to collapse
What do you mean buddy ??

Silentkiller101197 said:
What do you mean buddy ??
Click to expand...
Click to collapse
This tweak included in all custom ROM

yeah this tweak is present in every custom rom

yeah this tweak is present in every custom rom
Click to expand...
Click to collapse
This tweak included in all custom ROM
Click to expand...
Click to collapse
Oh I didn't knew that.. Sorry
But it is still useful for those who have a stock ROMs, right ?

ya, I'm using stock rom, and I just did this tweak yesterday...
and my "Go Keyboard" starting to act strange...
may be it doesn't like the tweak?

How strange ..
alex88510 said:
ya, I'm using stock rom, and I just did this tweak yesterday...
and my "Go Keyboard" starting to act strange...
may be it doesn't like the tweak?
Click to expand...
Click to collapse
not sure.. but this tweak has nothing to do with keyboard, ALTHOUGH according to the op, this can break some apps..
But you can still undo this tweak.. just go open up your Terminal Emulator or ADB shell and type these commands:
su
# setprop dalvik.vm.verify-bytecode true
# rm /data/dalvik-cache/*
# rm /cache/dalvik-cache/*
# reboot
Click to expand...
Click to collapse

alex88510 said:
ya, I'm using stock rom, and I just did this tweak yesterday...
and my "Go Keyboard" starting to act strange...
may be it doesn't like the tweak?
Click to expand...
Click to collapse
Did u find any improvements, other than the keyboard issue.. Concerned coz I'm on stock rom too..

sorry, I found that the keyboard problem is not cause by this tweak but its recent update.
About improvement, I did found that the apps are opening faster.

Hope somebody who's tried this tweak can help me..
In the first step in terminal emulator, the fourth line.
rm /cache/dalvik-cache/*
It said no such directory found.. Tried twice but the same thing..
Step 2- do I need to add both the following lines to system/build.prop
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v-n, o=v
I found the 2nd line already present in the build. prop.. So I just modified it without adding the 1st one...
Please tell me where I've gone wrong, I'm the first and second steps.. Cheers..

ivAnash said:
Hope somebody who's tried this tweak can help me..
In the first step in terminal emulator, the fourth line.
rm /cache/dalvik-cache/*
It said no such directory found.. Tried twice but the same thing..
Step 2- do I need to add both the following lines to system/build.prop
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v-n, o=v
I found the 2nd line already present in the build. prop.. So I just modified it without adding the 1st one...
Please tell me where I've gone wrong, I'm the first and second steps.. Cheers..
Click to expand...
Click to collapse
For the fourth line, which show no directory found, I just skip it and manually clear cache and dalvik-cache in the recovery.
for the step 2, I just modified it if it already existed.

alex88510 said:
For the fourth line, which show no directory found, I just skip it and manually clear cache and dalvik-cache in the recovery.
for the step 2, I just modified it if it already existed.
Click to expand...
Click to collapse
K.. For step 2 do u just modify one line which is there in the build. prop or add the other line too..

ivAnash said:
K.. For step 2 do u just modify one line which is there in the build. prop or add the other line too..
Click to expand...
Click to collapse
Modify one and add one.

[Q] Keyboard Dropping/Missing Keystrokes?

Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.

ged92781 said:
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
Click to expand...
Click to collapse
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom

ultraprimeomega said:
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
Click to expand...
Click to collapse
I wonder what the issue is that's causing it to show up on custom ROMs. Though, I've had it on the stock ROMs as well.

Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622

yogi2010 said:
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
Click to expand...
Click to collapse
Thank you!!!!!!!! I went ahead and dug into that thread. I do have that kernel already on my phone. I looked at the thread linked in that thread that gives a patch to adjust the timer delay and column delay in the kernel. HOWEVER, I'm not knowledgeable enough to apply that patch to my phone as it's given. Elsewhere in that thread, someone gave the commands to edit the settings manually through a terminal which I did through Android Commander on my PC and it worked wonders! Being the suspicious type, I guessed that the settings might not keep after a reboot. Unfortunately, that is the case and I had to reapply the settings after my phone finished restarting. So, I'll have to play with this a bit more to get it to keep, but thank you for showing me this!

You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.

yogi2010 said:
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
Click to expand...
Click to collapse
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?

ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
+1
I've noticed this problem and thought it was just me :$

I've had this happen as well as my screen thinking I was pressing it in one location when I wasn't even touching the phone. :s Had me at my wits end.
Sent from my SGH-T839 using xda premium

To those interested in the commands I used to fix the keyboard, see below. If you reboot your phone, these settings will go away and you will need to input these commands again. For a permanent fix, someone will need to add them to a kernel that can be flashed. To use these commands, your phone must be rooted. I've successfully used Android Commander to enter these commands from my PC while my phone is connected via USB.
The current timer delay may be read with:
cat /sys/devices/platform/s3c-keypad/timer_delay
The default is 5 if I remember correctly.
A new timer delay may be set with:
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
The default 300 µs column delay value may be read with:
cat /sys/devices/platform/s3c-keypad/column_delay
A new delay may be set with:
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
In either command, you may experiment with different values by changing the 1 or the 30 in either command to what you want. I believe the lowest is 1 and the max is 256 for the timer delay. If you damage your phone running these commands, that's on you. I'm just telling you what I did and feel worked for me. YMMV. Also, if you don't want to connect your rooted phone to your PC and want to use Terminal Emulator from the Play store, that will work too. You need to enter 'su' prior to running the above commands and grant the terminal super user permissions for the commands to take.

ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.

RicAndroid said:
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
Click to expand...
Click to collapse
Thank you!

ged92781 said:
Thank you!
Click to expand...
Click to collapse
You are very welcome! All done, BTW. Posting my updates now.

Permanent Fix(Manual way)
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)

SammaelAkuma said:
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
Click to expand...
Click to collapse
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?

RicAndroid said:
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
Click to expand...
Click to collapse
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.

SammaelAkuma said:
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
Click to expand...
Click to collapse
I'm using your commands, dude. I'm very into details....so thanks!

RicAndroid said:
I'm using your commands, dude. I'm very into details....so thanks!
Click to expand...
Click to collapse
Lol. No problem. And good luck with the custom rom cooking.