Database Info

Config Internal Mem Killer

Has any hero users actually got this working and is it making things better?
http://forum.xda-developers.com/showthread.php?t=622666

did you read the thread???
its a working tweak, you just have to do it yourself. But some are working on an app.

coffe34 said:
did you read the thread???
its a working tweak, you just have to do it yourself. But some are working on an app.
Click to expand...
Click to collapse
Yeah I have it on mine but I don't really notice a difference. I think it's because I'm running AOSP though which doesnt dip me too low in mem. If I was running sense I would probably notice it more.

More importantly are any of the developers planning on putting this code into there next rom, so we can just flash the new rom and already have our internal task killers configured for optimal performance?

Yup, I've added this to Fresh 1.1 and there's definitely a noticeable improvement. It's quite snappier and less laggy. I went back and forth to stock settings and more aggressive settings to test it out and can notice the difference after loading a few apps.
I haven't tested it out on any AOSP builds yet but plan to do so when I get some time.

black7 said:
Yup, I've added this to Fresh 1.1 and there's definitely a noticeable improvement. It's quite snappier and less laggy. I went back and forth to stock settings and more aggressive settings to test it out and can notice the difference after loading a few apps.
I haven't tested it out on any AOSP builds yet but plan to do so when I get some time.
Click to expand...
Click to collapse
black7 what settings are you running? I'm currently at: 1536,2048,4096,5120,8192,10240
haven't had much time to play with it yet. Wondering what you are finding works best on Android 1.5

coffe34 said:
did you read the thread???
its a working tweak, you just have to do it yourself. But some are working on an app.
Click to expand...
Click to collapse
Yep I read it but wanted to tripple check before I started messing around with scripts, I'm confused with the editing, but I'm gonna have a go at it. Just wanted to see if it was worth the effort.

Ok, so after looking and searching I can't seem to find this answer so hopefully someone may be able to point me in the right direction. I have updated the values of the memory killer, and I even followed the instructions to pull, edit and push the compcache.sh file back but after rebooting I still get the stop values when I run the command
# cat /sys/module/lowmemorykiller/parameters/minfree
This is my edited file...
/system/xbin/insmod /system/lib/modules/lzo_decompress.ko
/system/xbin/insmod /system/lib/modules/lzo_compress.ko
/system/xbin/insmod /system/lib/modules/xvmalloc.ko
/system/xbin/insmod /system/lib/modules/ramzswap.ko disksize_kb=131072
/system/xbin/swapon /dev/block/ramzswap0
echo "10" > /proc/sys/vm/swappiness
echo "1536,3072,4096,21000,23000,25000" > /sys/module/lowmemorykiller/parameters/minfree
Its not a big problem cause I can do it manually everytime I reboot, but I would like to have it initialize on its on at startup but something is not correct. Anyone have an idea of where I went wrong?

All I can say is... HOLY MONKEY!! Works great on 1.6. I uninstalled taskpanel and this thing is seriously screaming!

swaze said:
Ok, so after looking and searching I can't seem to find this answer so hopefully someone may be able to point me in the right direction. I have updated the values of the memory killer, and I even followed the instructions to pull, edit and push the compcache.sh file back but after rebooting I still get the stop values when I run the command
# cat /sys/module/lowmemorykiller/parameters/minfree
This is my edited file...
/system/xbin/insmod /system/lib/modules/lzo_decompress.ko
/system/xbin/insmod /system/lib/modules/lzo_compress.ko
/system/xbin/insmod /system/lib/modules/xvmalloc.ko
/system/xbin/insmod /system/lib/modules/ramzswap.ko disksize_kb=131072
/system/xbin/swapon /dev/block/ramzswap0
echo "10" > /proc/sys/vm/swappiness
echo "1536,3072,4096,21000,23000,25000" > /sys/module/lowmemorykiller/parameters/minfree
Its not a big problem cause I can do it manually everytime I reboot, but I would like to have it initialize on its on at startup but something is not correct. Anyone have an idea of where I went wrong?
Click to expand...
Click to collapse
read the original thread again it says right in there that it will not be there after a reboot that you will have to go back in and do it again.

wtphoto said:
read the original thread again it says right in there that it will not be there after a reboot that you will have to go back in and do it again.
Click to expand...
Click to collapse
If you put the values in compcache.sh will it re echo the values on reboot? It seems to be doing that on my phone.

ljmeli said:
Actually putting it in compcache.sh will re echo the values on reboot.
Click to expand...
Click to collapse
Right, the original thread clearly shows the steps to make it initialize on reboot, but its not working for me for some reason.

It isn't working for me either. I edited compcache.sh exactly as shown and it isn't working for me. I also tried creating a new file and placing the command in it and having that run on startup, no luck there either.

I'm surprised this thread isn't more popular. This is the best tweak ever.

I pulled compcache.sh and added
echo "1536,3072,4096,21000,23000,25000" > /sys/module/lowmemorykiller/parameters/minfree
pushed it back rebooted and its still in compcache.sh

notrock said:
I pulled compcache.sh and added
echo "1536,3072,4096,21000,23000,25000" > /sys/module/lowmemorykiller/parameters/minfree
pushed it back rebooted and its still in compcache.sh
Click to expand...
Click to collapse
Huh? It's supposed to still be in there...

Tikerz said:
Huh? It's supposed to still be in there...
Click to expand...
Click to collapse
I know. I thought the OP was saying it wasn't on his.

The "right" way to do this is use the perl scripts from Lox (I believe) and edit the init.rc in the ramdisk. I can't post links, but search the forums for them.
The line that provides the default values is in this file and you can simply change the numbers. For a quick and dirty hack you need to be using MoDaCo's init.rc and have his script in the file tree.
Don't edit the ramzswap file in windows without a true text editor and don't change the file permissions if your using linux.
I've built this into the Gumbo Kernel and started a dev thread here to work on getting it in the init rc natively as a first step in our own community kernel, but like i said, can't post links.

gbhil said:
The "right" way to do this is use the perl scripts from Lox (I believe) and edit the init.rc in the ramdisk. I can't post links, but search the forums for them.
The line that provides the default values is in this file and you can simply change the numbers. For a quick and dirty hack you need to be using MoDaCo's init.rc and have his script in the file tree.
Don't edit the ramzswap file in windows without a true text editor and don't change the file permissions if your using linux.
I've built this into the Gumbo Kernel and started a dev thread here to work on getting it in the init rc natively as a first step in our own community kernel, but like i said, can't post links.
Click to expand...
Click to collapse
Curious, will the Gumbo kernel work with the AOSP builds, specifically 1.6? I was trying to add this to my init.rc but couldnt get it to work with Droid Explorer, and for some reason adb wasnt recognizing push to the / directory.

katmandu421 said:
Curious, will the Gumbo kernel work with the AOSP builds, specifically 1.6? I was trying to add this to my init.rc but couldnt get it to work with Droid Explorer, and for some reason adb wasnt recognizing push to the / directory.
Click to expand...
Click to collapse
No it wont. I've already requested some files from some one currently running it though. Details in other thread.
You can't write to / . That's why you can't just push init.rc in. It comes from the ramdisk image.

[HOW-TO] Enabling Wireless N on Evo- Android Eclair 2.1

THIS IS FOR ECLAIR 2.1 DO NOT USE THIS IN A FROYO 2.2 ROM. SINCE THE 2.2 UPDATE WIRELESS N IS SUPPORTED OUT THE BOX. NO NEED FOR THIS HACK IN FROYO 2.2
edited by toastcfh to avoid mishaps
Update: Thanks to Calkulin there are now flashable zips on my blog post as well as just the driver. Just flash them like any other update.zip file.
So the Evo's WiFi chip supports Wireless N technology, which allows for faster throughput on your WiFi connection. To use this you obviously need a Wireless N capable AP or router. Basically, for some reason (I am going to assume battery life?), HTC decided to disable the wireless n capability of this chip but this can be fixed. Since we don't have the source for the driver we need to use a hex editor. Note, if using AOSP wireless n will already be enabled using the AOSP driver. But if you are using a Sense rom then you will need to do the following. Also I am including a download link with the driver that you can just push if you don't want to get dirty with a hex editor. Anyway, here we go:
1. Download a hex editor (I just googled hex editor and downloaded this one: http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm)
2. Go into a command prompt or shell and perform:
Code:
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko.old
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko
This will pull the file and make a backup in case you need to replace the backup.
3. In your hex editor open the file you just pulled. Now, in two spots HTC added 'nmode' in here to disable Wireless N. All we have to do is modify this string to be any other 5 character string and wireless N will be enabled. I did a search and replace and replaced 'nmode' with '-----' (Note: Do not include the single quotes).
4. Save the file.
5. Perform the following in a command prompt or shell:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
Now wireless N should be enabled on your device. If not, restart it and try. If you ever want to restore your original just perform the following:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb push bcm4329.ko.old /system/lib/modules/bcm4329.ko
.
Below is the download link for the already modified wireless driver.
http://objectunoriented.com/android/?p=35

I downloaded the file and pushed it to my phone. I restarted the phone and once it came back up it connected on 802.11n. So far been working perfectly.

Sounds good, will try when I get home. But I have to say I was expecting this after I heard that the incredible is getting a patch to enable wireless n.

wow. clever little patch. im excited to try this! hopefully will at least allow better throughput if not also better signal with wireless n! thanks!!
on a technical side note, any reason why your /system is mtdblock3 while mine is mtdblock4?

cant wait to try this.... thanks

good stuff! gonna try this.

joeykrim said:
wow. clever little patch. im excited to try this! hopefully will at least allow better throughput if not also better signal with wireless n! thanks!!
on a technical side note, any reason why your /system is mtdblock3 while mine is mtdblock4?
Click to expand...
Click to collapse
That's just the command I used when I mounted the system directory as writeable when I had my Hero. Should it be 4 instead of 3?

liquidhaste said:
Sounds good, will try when I get home. But I have to say I was expecting this after I heard that the incredible is getting a patch to enable wireless n.
Click to expand...
Click to collapse
I have actually had this working for maybe a week now in my latest Superersonic rom but since I haven't had time to fix the root problem with that rom I just decided to post this seperately.

most of the power issues/concerns with wireless-n are targetted at the AP/Router i think... wondering if anyone has been seeing a drop in battery power though.

poporo said:
most of the power issues/concerns with wireless-n are targetted at the AP/Router i think... wondering if anyone has been seeing a drop in battery power though.
Click to expand...
Click to collapse
That was just an assumption. I had nothing to back that up lol

Here is the mod in zip format to make it easier, restore is also attached

Calkulin said:
Here is the mod in zip format to make it easier, restore is also attached
Click to expand...
Click to collapse
Hey thanks for doing this for me. I completely forgot to do this lol
Updated blog post with these update zips btw. Thanks again.

Probably a dumb question but im guessing since you have provided us with a zip file we can just flash it now??? And even dumber question this will still work with wireless g routers right?

awesome bro. Thanks.

rustyman14 said:
Probably a dumb question but im guessing since you have provided us with a zip file we can just flash it now??? And even dumber question this will still work with wireless g routers right?
Click to expand...
Click to collapse
Correct. Thanks to Calkulin you can now use the zips he provided (downloadable here or on my blog post) to flash instead of using adb.
And yes this will still work with a/b/g routers.

chuckhriczko said:
That's just the command I used when I mounted the system directory as writeable when I had my Hero. Should it be 4 instead of 3?
Click to expand...
Click to collapse
never used the hero, but this makes sense. on the EVO, pretty sure its mtdblock4.
would you be okay if i add this to the update.zip builder im putting together with credit going to you and a link to this thread?

joeykrim said:
never used the hero, but this makes sense. on the EVO, pretty sure its mtdblock4.
would you be okay if i add this to the update.zip builder im putting together with credit going to you and a link to this thread?
Click to expand...
Click to collapse
No problem bro. I'd be honored. My work is your work. Anything any of us do on here should be freely used by anyone else assuming proper credit is given.

Should have brought my laptop to work today, oh well will give it a go tonight. Can't wait!

jwhitney83 said:
Should have brought my laptop to work today, oh well will give it a go tonight. Can't wait!
Click to expand...
Click to collapse
You can download the files through your phone's browser and flash through that as long as you NAND unlocked everything. Just make sure you copy Calkulin's update.zip files to the root of the sd card after downloading.

Calkulin said:
Here is the mod in zip format to make it easier, restore is also attached
Click to expand...
Click to collapse
You are freakin awesome!

[CDMA] Cellular South CDMA Desire Hacks [Update: 6 OCT 2010]

Just like our USCC friends, I'm currently working on several mods for Cellular South's release of the Desire. I'll keep this post updated with new developments.
Linked is a custom boot.img from our stock ROM with apps2sd support. You will still need to download and flash the latest Darktremor apps2sd release and format your SD card accordingly.
How to flash?
Place the dphase-apps2sd-signed.zip file on the root of your sdcard and flash it as a zipped update.
Download Link (Cellular South, also confirmed working with Alaska Communications):
http://dphase.net/desire/dphase-apps2sd-signed.zip (2.3 MB)
MD5 checksum: 70df556ceb6891cbdcc3801d807d58af
US Cellular stock boot.img with apps2sd support
http://dphase.net/desire/dphase-USCC-apps2sd-signed.zip (2.3 MB)
MD5 checksum: e11b6f40b26811e252f0579f0ed5861c
Latest Darktremor apps2sd:
http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.1-adv-signed.zip
------------------------------------------------------------------------------------------
Zipaligned and PNG optimized system apps:
Code:
% du -sh original optimized
62M original
42M optimized
As you can see above, I've zipaligned and optimized the images in the system apps, which shaved off 20MB from total files size. This should lead to faster load times.
To install, untar the optimized archive to the directory of choice and boot to recovery. Mount the /system partition then do the following command with adb from within the directory holding the apk's (adb should be in your binary path, if not, fix that to make life easier in the future):
Code:
adb push . /system/app
You'll then see, for example:
Code:
push: ./DCSImpl.apk -> /system/app/DCSImpl.apk
push: ./HtcDialer.apk -> /system/app/HtcDialer.apk
push: ./EnhancedGoogleSearchProvider.apk -> /system/app/EnhancedGoogleSearchProvider.apk
... (etc)
Link:
http://dphase.net/desire/system_app_optimized.tar.gz (40MB compressed)
MD5 checksum:
2dc5fe2683e657006d2a8026c4ac32dc

reserved for later use

So what exactly does this accomplish? Is it basically adding apps 2 sd to the stock 2.1 rom? Any chance it will run on my US Cell desire?

Yes, adds apps2sd support to the stock rom. The latest a2sd will automagically move portions of /data over once it sees a properly formatted card.
In theory, this should work on USCC, but ymmv.

It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash

con247 said:
It is likely I won't get time tonight, but if I do, I'll be sure to give it a shot. I would like to get a2sd without a full reflash
Click to expand...
Click to collapse
If it doesn't work, we'll grab your existing boot.img and I can tweak it.

Updates posted, please test and enjoy.

dphase said:
If it doesn't work, we'll grab your existing boot.img and I can tweak it.
Click to expand...
Click to collapse
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.

con247 said:
That is the link to my boot.img
If you have time, if you could tweak that one, it would be great. If not, I'll give yours a shot tonight.
Click to expand...
Click to collapse
I've modified your boot.img and placed a link in the first post.

dphase said:
I've modified your boot.img and placed a link in the first post.
Click to expand...
Click to collapse
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Just booted and WOW look at all that new Space!!! Time to get more apps

seesser said:
A Big Thanks I am testing it now. I had to remember to change the MD5 information otherwise you get a fail.
Also You have to remember to run the apps2sd after the restore otherwise you will not boot!
Click to expand...
Click to collapse
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.

How do you change the MD5 of the file

dphase said:
Yes, I recommend installing apps2sd, formatting card, then applying new boot image.
Click to expand...
Click to collapse
I guess I did it a little differently. I already had the sd card partitioned so I just took a backup swapped the boot.img and edited the MD5 with note++. Restored the modified backup and then ran the apps2sd.zip and rebooted.
I did it this way just in case something went wrong I could restore the backup that I didn't modify.
Going to try out that app optimize next.
Thank again.

This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte

bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
Hello and yes I was running that rom but did not like that friend Stream did not have twitter. with that rom you still had to tell the phone to move the files (a little bit of command line codding). With this boot.img and apps2sd on my stock rom backup I went from 15mb to 71mb so this one works great right out of the box.
I Explained how I did it from a backup of my stock rom up a few lines hope this helps.

I too am a little lost on this push of the app optimize. Could you explain it a little more? I have done a little adb shell programming but am lost with your directions.
Thanks,

bytethegroove said:
This might be a noobish ?
but couldnt I just use a custom recovery and flash this as a rom?
or do I still have to push stuff?
im a lil confused coming from winmo
Right now im running blitz's apps2sd 2.1 sense rom
but not sure im seeing any benifit from the apps2sd....although I do see somethings being moved...wondering if seesser had tried blitz's rom...
are u seeing more space with the above method?
and what do I change the md5 to?
thanks
byte
Click to expand...
Click to collapse
No, none of this can be flashed as a rom.
I'm not sure why anyone is changing MD5's, I included those so one could verify there was no data corruption during the download.

fixed. no worries..

con247 said:
I keep getting an MD5 mismatch after I edited the nandroid.md5 to the one in the original post
Click to expand...
Click to collapse
There is zero reason to edit that. Are you trying to use nandroid to flash the image? If so, that's the wrong answer.

con247 said:
fixed. no worries..
Click to expand...
Click to collapse
Did you restart the phone after you modified the MD5? I had that problem also until I restarted the phone and It worked after that.

[Guide] SQLite3: Dramatically Improve Entire Phone

So I've used the sqlite vacuum/re-index feature of V6 SuperCharger blindly without knowing what it does getting a placebo effect sort of thing, and I started doing some research on it and realized that this feature has started getting stripped out of a lot of stock roms and what not on android devices and that basically it makes it wayyyy easier for the system to index and sort out system/app files a lot of it was over the top for me but I figured there could be no negative effects to this at all.
So long story short I downloaded SQLite Installer from the market
Restarted and everything on my phone has been quick and painless it's been up for 6 hours now since the restart and have yet to have any lag/problems.
here's my set up:
Tweaked 2.0
0504 PBJ Kernel
OC'd to 1.2ghz (SIO i/o and Interactive governor)
don't know if it is placebo affect once again and I'd love to get some more veteran knowledge on this but I LOVE MY PHONE NOW
As I am a new member here I cannot post links but go to my thread at rootzwiki[dot]com/topic/25072-sqlite3-phone-is-snappier-than-ever/ and read the instructions there and download the easily flashable .zip file with the included detailing script.
happy flashing
p2kmafia

I just flashed so ill report if results are the same for me
Sent from my SCH-I510 using XDA

good lookin. there were positive results in my rootzwiki thread.

RFS or EXT4?
and is this the app: https://play.google.com/store/apps/details?id=ptSoft.util.sqlite3forroot

It would be fairly easy to run before and after database benchmarks in an app such as AnTuTu Benchmark. That would show if there are any real gains to be had.
Looking at the script, it essentially just re-writes all of the databases on the phone (via a VACUUM/REINDEX combo). Logic would state that if you have badly fragmented databases, which would manifest as things like degredation of performance over time, then this should make your phone a bit snappier.
[edit: I ran before and after tests (average of 3 tests). There was no appreciable difference between the tests. Now, the test results may not reflect real world results for two reasons: 1. I have no idea how the database I/O test in AnTuTu actually tests (what database, etc) and 2. I received errors when the script was attempting to vacuum databases ("error: unable to open file"), though the re-indexing worked fine.
End result? The test essentially means nothing and all we can go off of is anecdotal evidence. However, whether it's a placebo effect or not, this process simply can't harmfully impact your phone. As such, results should be anything from no change in response to some response increase.
Yeah, I know. A whole lot of typing that essentially says nothing. Sorry!]

jco23 said:
RFS or EXT4?
and is this the app: play.google[DOT]com/store/apps/details?id=ptSoft.util.sqlite3forroot
Click to expand...
Click to collapse
yes that's the app but check out my rootzwiki thread the flashable zip file adds the detailing script to your sd card that you'll need if you feel your device slowing down.
Cilraaz: thanks for testing this out. the error opening files might have to do with a bad install. keep the detailing script and try the app in the playstore for the install or reflash the zip

p2kmafia said:
Cilraaz: thanks for testing this out. the error opening files might have to do with a bad install. keep the detailing script and try the app in the playstore for the install or reflash the zip
Click to expand...
Click to collapse
I re-installed from Play and have tested my copy of sqlite3. It is a working copy. I also didn't flash the zip. I downloaded the zip, extracted the shell script, and manually placed it on my SD card. I've run the vacuum command manually as well, and received the same error.

I don't know what to tell you. I just re-ran the detailing script and I don't receive those errors, but if you know it is installed correctly/is vacuuming it shouldn't be a problem. I wish I knew more about this software to help out. I just discovered it helps a lot haha.

Cilraaz said:
I re-installed from Play and have tested my copy of sqlite3. It is a working copy. I also didn't flash the zip. I downloaded the zip, extracted the shell script, and manually placed it on my SD card. I've run the vacuum command manually as well, and received the same error.
Click to expand...
Click to collapse
Are you using script manager to run the script? And if so are you running with root privileges?
Sent from my SCH-I510 using xda premium

Endless2232 said:
Are you using script manager to run the script? And if so are you running with root privileges?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
Script manager as root. Command line as root. The entire script and individual manual vacuums. Same result on all. Maybe I'll boot into CWM and run a fix permissions to see if that does anything.

Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Sent from my SCH-I510 using xda premium

Endless2232 said:
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
hey endless I just checked my sqlite3 and it has all 9 checks across the board. should I change them as well even though i'm not experiencing any problems?

p2kmafia said:
hey endless I just checked my sqlite3 and it has all 9 checks across the board. should I change them as well even though i'm not experiencing any problems?
Click to expand...
Click to collapse
No, you're fine.

So i did everything in the instructions and i have one little question. Do i keep the script running in the background?
Sent from my SCH-I510 using xda premium

Crap7126 said:
So i did everything in the instructions and i have one little question. Do i keep the script running in the background?
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
No. Once you've flashed/installed SQLite3 it runs by itself it's not a script. the detailing script is a run once kind of thing that you run if you feel your phone slowing down/lagging. I usually run it anywhere from once every 2 days to once every 3 or 4.
I also have an auto cache clearing app that I use that helps with lag so you don't get the two mixed up.

p2kmafia said:
No. Once you've flashed/installed SQLite3 it runs by itself it's not a script. the detailing script is a run once kind of thing that you run if you feel your phone slowing down/lagging. I usually run it anywhere from once every 2 days to once every 3 or 4.
I also have an auto cache clearing app that I use that helps with lag so you don't get the two mixed up.
Click to expand...
Click to collapse
Failed for me.
Sent from my SCH-I510 using xda premium

deafptl4ever said:
Failed for me.
Sent from my SCH-I510 using xda premium
Click to expand...
Click to collapse
what failed for you? i'd love to help out but need a little more information

Endless2232 said:
Check the permissions of sqlite3 in system/xbin using root explorer. Read and execute should have all three checkboxes checked and write should have owner checked.
Click to expand...
Click to collapse
If this was in regard to my issue, it's of no consequence. The sqlite3 executable was running fine, as evidenced by the fact that there were no errors in executing sqlite3 (the REINDEX command ran without problem). The permission issue would be with the database files themselves, though root should have no permission issues on r/w partitions like data and dbdata, or wherever sqlite3 is trying to write the temporary database during the VACUUM process. The VACUUM process actually reads data out of the database file, stores it in a temporary file, and then overwrites the original file with data from the temporary file. This eliminates "blank" data and fragmentation within the database files, which is why you see a slight performance increase and smaller database footprint.
Does anyone know where that temporary db file is stored by sqlite3?

Cilraaz said:
Does anyone know where that temporary db file is stored by sqlite3?
Click to expand...
Click to collapse
Unfortunately my expertise stops at how it works/why it works I just found out that it helps my phone and that's it

This def made my phone much snappier. My only question is, when i run the script i get a constant error, "error mountind database". Not really sure whato do (if anything) since it has made the phone quicker regardless.
Sent from my SCH-I510 using XDA

[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.