Database Info

MMS sending size? 300 vs 600 Kb

I tried a few of the ROMs here on my Tilt already. I noticed on a couple of them that the sending size for the MMS was set at the old 300Kb limit. I often send stuff that is right at the 600Kb limit and want to keep that limit.
I noticed on a few of the cooked ROMs the limit was 300Kb, and I couldn't figure out a way to change it, even going through configuration and settings.
So, my questions are as follows (and, yes I did search)-
Is there a way to change it that I'm just not seeing (short of maybe a regedit?)?
What ROM are you running, and what is your sending limit? (this is the one I came up with no answer at all for when searching)
Could this have to do with a particular MMS install .cab file? (similarly I didn't see an answer for this one. Lots of cab links, but no specs on the limit)
Thanks!
EDIT: Dangit, I put this in the wrong forum. I meant to put it in the Kaiser forum.

over2land said:
I tried a few of the ROMs here on my Tilt already. I noticed on a couple of them that the sending size for the MMS was set at the old 300Kb limit. I often send stuff that is right at the 600Kb limit and want to keep that limit... Is there a way to change it that I'm just not seeing (short of maybe a regedit?)?
Click to expand...
Click to collapse
By "short of a regedit" do you mean you DON'T want to edit the registry? You may find a cab for ARCSoft or whatever MMS client you're using that has the larger sending size limit. But it would probably be quicker to just change it manually by editing the registry. Check this post for the Hermes, most likely it will work on the Kaiser also.

Set MMS Send Limit to 600 kb
over2land said:
I tried a few of the ROMs here on my Tilt already. I noticed on a couple of them that the sending size for the MMS was set at the old 300Kb limit. I often send stuff that is right at the 600Kb limit and want to keep that limit. . .
Click to expand...
Click to collapse
hotmail said:
. . . it would probably be quicker to just change it manually by editing the registry. Check this post for the Hermes, most likely it will work on the Kaiser also.
Click to expand...
Click to collapse
@over2land: I have been wondering about this also!
@hotmail: Thanks for your reply - I changed registry items per your post in the Hermes thread and now have 600 limit. I didn't find any registry keys with title of Wap1SendLimit_x - so I just changed the SendLimit keys, and also changed the ReceiveLimit keys, and Voila! good to go!

hotmail said:
By "short of a regedit" do you mean you DON'T want to edit the registry? You may find a cab for ARCSoft or whatever MMS client you're using that has the larger sending size limit. But it would probably be quicker to just change it manually by editing the registry. Check this post for the Hermes, most likely it will work on the Kaiser also.
Click to expand...
Click to collapse
If regedit is the only way to do it, I'll do that. Right now I'm back on the ATT OE ROM and radio, since I'm on ATT, it works for me. I get the 600Kb limit. But, the cooked ROMs are typically faster and have more storage, so at some point I'll end up going back to a cooked ROM.
I was hoping that there was some setting going through the phone's UI that I could change. Even though I've regedited every phone I've had, I'm not 100% on regediting this one just yet.
I am using ARCsoft... I was hoping to avoid having to DL every .cab I can find for that limit. I was figuring if people posted their cabs or thier ROMs with the 600Kb limit, then someone like myself who didn't want to necessarily reg edit the phone would have some recourse.

I think I have a cab that's got the 600k mod in it. if you want it, let me know.

RR ATT settings cab
http://forum.xda-developers.com/showthread.php?t=415585 , it changes the Media Net settings a bit, just take note of the OG settings to input after install

http://www.4shared.com/file/69575927/74bdbf1e/Raiisaks_Kaiser_3MB_MMS_limit.html
http://www.4shared.com/file/69575931/84c52b6a/Raiisaks_Kaiser_600k_MMS_limit.html
over2land said:
I tried a few of the ROMs here on my Tilt already. I noticed on a couple of them that the sending size for the MMS was set at the old 300Kb limit. I often send stuff that is right at the 600Kb limit and want to keep that limit.
I noticed on a few of the cooked ROMs the limit was 300Kb, and I couldn't figure out a way to change it, even going through configuration and settings.
So, my questions are as follows (and, yes I did search)-
Is there a way to change it that I'm just not seeing (short of maybe a regedit?)?
What ROM are you running, and what is your sending limit? (this is the one I came up with no answer at all for when searching)
Could this have to do with a particular MMS install .cab file? (similarly I didn't see an answer for this one. Lots of cab links, but no specs on the limit)
Thanks!
EDIT: Dangit, I put this in the wrong forum. I meant to put it in the Kaiser forum.
Click to expand...
Click to collapse

I'm guessing the 3mb limit does not apply to AT&T's network? Or do they support a 3mb file going out?

BerettaFreak said:
I'm guessing the 3mb limit does not apply to AT&T's network? Or do they support a 3mb file going out?
Click to expand...
Click to collapse
Not sure about ATT but I installed this cab and went into the MMS settings and changed the limit to 3mb but I've only sent out a 1mb file or so over the Tmobile network. Works good

Does it cost more to send a larger mms?

Harsesis said:
Does it cost more to send a larger mms?
Click to expand...
Click to collapse
No standard text messaing rates apply

daddy_yankee1980 said:
Not sure about ATT but I installed this cab and went into the MMS settings and changed the limit to 3mb but I've only sent out a 1mb file or so over the Tmobile network. Works good
Click to expand...
Click to collapse
i've installed the .cab , where did u change the limit? in the registry?

Hello,
how can I revert the setting to 300kb back?

kiltbaq said:
i've installed the .cab , where did u change the limit? in the registry?
Click to expand...
Click to collapse
I'm stuck here too... anybody???

For the 3MB one, and in the same post is the 600kb one. Post also includes a .gif on how to.
http://forum.xda-developers.com/showpost.php?p=2309317&postcount=39

[dev][sqlite3] 21/Jan, how to disable sync in sqlite3 without pragma

WARN:The following steps only for developers. The following changes may cause instability or even cause the phone can not be used.
Android phones as the underlying database using sqlite3. sqlite3 writes efficiency is very low, because the sync feature turned on by default, and fsync() must be performed after each insertion, the resulting system efficiency is low, and the disk life is reduced.
I try to disable sync feature by default in exchange for greater IO performance and reduce disk consumption. While doing so may result in data integrity problems, but I still like to use it because most of the sqlite insert action can be completed within a few seconds, not too much to consider issues such as sudden power-down.
After modified, the time of insert 2000 records to sqlite3 db, from 1m11s reduce to 2s.
Attachment is my sqlite3 patch, it is for CM or AOSP.
For SenseROM, I can not simply replace libsqlite.so from AOSP, so I do hexedit with it.Do follow modify for SenseROM libsqlite.so:
replace
c6 f7 66 fd 03 20 78 72
with
c6 f7 66 fd 01 20 78 72
replace
cc f8 0c 00 03 20 a3 68
with
cc f8 0c 00 01 20 a3 68
replace
5f fa 81 fc 83 f0 01 06
with
5f fa 81 fc 01 23 00 26
EDIT(2011/01/07 23:40):
replace
5f fa 81 fc 83 f0 01 06
with
5f fa 81 fc 01 26 00 bf
replace
23 72 00 23 66 72 02 26
with
26 72 00 23 63 72 02 26
EDIT(2011/01/10 16:45):
HD WWE RUU 1.72.405.3 patched libsqlite.so:http://www.multiupload.com/N9FLJYAC77, not test!
EDIT(2011/01/10 22:24):
HD WWE RUU 1.72.405.3 patched version v2 as attachement
patch file upgrade to V2
EDIT(2011/01/21 10:59):
add auto repaire script for mms/sms db corrupt. If you met data loss with my sqlitemod, then place this script to /system/etc/init.d/, and chmod 755 to it.
this script will be check your mms/sms db at boot time, and auto fix it if found table loss.:View attachment 03repairesmsdb.txt

Patched libsqlite.so for SenseROM.
I got libsqlite.so from Pays 1.1+Z HD rom.

Sounds intressting. I like the idea of modding sqlite more than loop.
Loopfile is double flush (flush loop + flush file) and direct loop mount causes random reboots.
Ill test it it when i have time.
EDIT: you don't mind if i'll use it for my rom (as optional addon)
EDIT2: By the way, ... did you try 1.72 base of HD rom. Its really fast and sqlite3 is also newer version?

but won't cause this (micro)-lags like any other kind of disk-buffering?
The 2000 insert statements will go in 2s because they are still in RAM.
After a while of doing nothing and / or suddenly needing more RAM, the changes will (finally) be written to disk, causing the system to be unresponsive for the duration of the write.
If I receive or send a new sms / text for example, there are a few records inserted. With sync on, it might take a fraction longer, but the changes are there and the user 'understands' it. There is some activity.
Without sync-ing, all those little changes add up until suddenly they need to be really written and the system lags for a full second or so because it needs to write them all at once.
And what are the moments when there are a lot of database writes during normal use anyway?
Another example: I'm restoring my sms messages with SMS Backup & Restore. I've got a lot of messages, so it takes a while. This is normal. Now, with syncing (default) it takes a while, but when the app says it's done... it's really done. Switching back to your homescreen and launching another app will go smoothly.
With syncing off, the restore operation will complete sooner, but the moment you start another app (or even go back to your homescreen) more RAM is needed and the changes will be written to disk, causing a simple tap to launch an app to feel laggy or sluggish because the latest changes from the restore operation are written to disk (which the user understands to be done already).
Buffering like this helps a lot if something needs to be written while concurrently something else is constantly reading. The write-changes are kept in memory so the disk I/O is completely free for the reading operations. When they are done, the write-changes can actually be commited to disk, and won't interfere with the read operations. On a multi-tasking desktop computer, this is normal.
But when will something like that be needed / happening on a smartphone?
Thinking about the user experience, when a special process is running (restoring backups, installing an app, etc..) the user expects / understands that it takes a moment. The user surely does not want that operation to complete quickly, only to have a lagging keyboard 5 secs afterwards, right?
Thinking about 2000+ inserts is nice, but I really don't see when a situation like that occurs on an Android phone, and I much rather have operations be really done than interfering later on.

I think you are wrong.
With Android applications, the database operation is non-persistent, normal step in app is:
1.open db
2.do read/write
3.close db
with step3, the data in cache will be flush to disk. so user will not notice any sudden lag, always smooth.
With SYNC-ON, the db operation like this:
1.open db
2.1. write a record/do a transcation
2.2. fsync()
2.3. write a record/do a transcation
2.4. fsync()
.....
3.close db/fsync()
with SYNC-OFF, operation like this:
1.open db
2.1 write a record/do a transcation
2.2 write a record/do a transcation
....
3. close db/fsync()
So, no-sync can significantly save IO time.
dipje said:
but won't cause this (micro)-lags like any other kind of disk-buffering?
The 2000 insert statements will go in 2s because they are still in RAM.
After a while of doing nothing and / or suddenly needing more RAM, the changes will (finally) be written to disk, causing the system to be unresponsive for the duration of the write.
If I receive or send a new sms / text for example, there are a few records inserted. With sync on, it might take a fraction longer, but the changes are there and the user 'understands' it. There is some activity.
Without sync-ing, all those little changes add up until suddenly they need to be really written and the system lags for a full second or so because it needs to write them all at once.
And what are the moments when there are a lot of database writes during normal use anyway?
Another example: I'm restoring my sms messages with SMS Backup & Restore. I've got a lot of messages, so it takes a while. This is normal. Now, with syncing (default) it takes a while, but when the app says it's done... it's really done. Switching back to your homescreen and launching another app will go smoothly.
With syncing off, the restore operation will complete sooner, but the moment you start another app (or even go back to your homescreen) more RAM is needed and the changes will be written to disk, causing a simple tap to launch an app to feel laggy or sluggish because the latest changes from the restore operation are written to disk (which the user understands to be done already).
Buffering like this helps a lot if something needs to be written while concurrently something else is constantly reading. The write-changes are kept in memory so the disk I/O is completely free for the reading operations. When they are done, the write-changes can actually be commited to disk, and won't interfere with the read operations. On a multi-tasking desktop computer, this is normal.
But when will something like that be needed / happening on a smartphone?
Thinking about the user experience, when a special process is running (restoring backups, installing an app, etc..) the user expects / understands that it takes a moment. The user surely does not want that operation to complete quickly, only to have a lagging keyboard 5 secs afterwards, right?
Thinking about 2000+ inserts is nice, but I really don't see when a situation like that occurs on an Android phone, and I much rather have operations be really done than interfering later on.
Click to expand...
Click to collapse

melethron said:
Sounds intressting. I like the idea of modding sqlite more than loop.
Loopfile is double flush (flush loop + flush file) and direct loop mount causes random reboots.
Ill test it it when i have time.
EDIT: you don't mind if i'll use it for my rom (as optional addon)
EDIT2: By the way, ... did you try 1.72 base of HD rom. Its really fast and sqlite3 is also newer version?
Click to expand...
Click to collapse
my sqlite3 mod is against loop.
The main purpose of loopfile/loopdevice is speedup fsync() in sqlite3, But the normal file operations have been affected. So I directly modify sqlite3. The benefit is MTD db access can be speedup, too.
Anyone can use my MOD.
I use 1.32.832.6(HK RUU), because I don't like WWERUU include too many language, this will lead apk too large.
Offical new version sqlite3 must be disabled nosync for stability.

ownhere said:
my sqlite3 mod is against loop.
The main purpose of loopfile/loopdevice is speedup fsync() in sqlite3, But the normal file operations have been affected. So I directly modify sqlite3. The benefit is MTD db access can be speedup, too.
Anyone can use my MOD.
I use 1.32.832.6(HK RUU), because I don't like WWERUU include too many language, this will lead apk too large.
Offical new version sqlite3 must be disabled nosync for stability.
Click to expand...
Click to collapse
I dont have a problem with large apks. I deodexed my rom and complete system will fit in mtd4+5 then. Apart from that: the 1.72 base is REALLY MUCH faster. As soon as HK RUU 1.72 is available i recommend you use that one. You'll love it.
About the fsync if db is closed. When will it be closed then? After the app is closed?

melethron said:
I dont have a problem with large apks. I deodexed my rom and complete system will fit in mtd4+5 then.
About the fsync if db is closed. When will it be closed then? After the app is closed?
Click to expand...
Click to collapse
Most apps close db after db operation. I try reboot 10+ times in 30 mins, no FC or data loss.

Ok. Still a bit risky but its really good to have this optional. Great work .
Sent from my HTC Desire using XDA App

great work!
patch for miui, flash from recovery.
the binary is slightly different,so I made this patch.

_bryan_ said:
great work!
patch for miui, flash from recovery.
the binary is slightly different,so I made this patch.
you can also extract libsqlite.so from the zip and replace it with rootexplorer.
Click to expand...
Click to collapse
Not sure if replacing it "on the fly" is a good idea. Might cause issues if sqlite is runnin while it is replaced.

melethron said:
Not sure if replacing it "on the fly" is a good idea. Might cause issues if sqlite is runnin while it is replaced.
Click to expand...
Click to collapse
yes，you are right.

so we need to put it in rom before flashing, right??
i will try on oxygen 1.4 and will post benchmark

madman_cro said:
so we need to put it in rom before flashing, right??
i will try on oxygen 1.4 and will post benchmark
Click to expand...
Click to collapse
tried it. dont see any lags, and to be honest dont see any improvments. will test some more

madman_cro said:
tried it. dont see any lags, and to be honest dont see any improvments. will test some more
Click to expand...
Click to collapse
Do you even use data2sd. In most cases there aren't lags if /data/data is on nand but there is if it is on sd-ext.

melethron said:
Do you even use data2sd. In most cases there aren't lags if /data/data is on nand but there is if it is on sd-ext.
Click to expand...
Click to collapse
no i dont use it . i only use a2sd

madman_cro said:
no i dont use it . i only use a2sd
Click to expand...
Click to collapse
Don't think you'll notice the difference then.

madman_cro said:
so we need to put it in rom before flashing, right??
i will try on oxygen 1.4 and will post benchmark
Click to expand...
Click to collapse
I'd say you can inject it in recovery mode. No need for flashing

Answer to this here (the discussion there went off topic).
Loop is not intended to mount a "real" filesystem. It is made to mount stuff like *.iso or *.img. Loop is only a "workaround" to skip fsync. Loop is simply abused to achieve a fsync skip. Skipping it directly in sqlite has following improvements over loop:
1. Less RAM: needed because there is no "loop" cache needed then.
2. Less I/O: Only one flush because there is no need to "double flush"
3. Less cputime/battery: Also because no double flush.
4. Less time to set it up: No setup needed for a loopfile.
5. More safety: Faster flush and the partition can be journaled without speed decrease (ext3/4 instead of fat)
About 5: You may still loose data on a powerloss because it is not yet synced but you wont have corrupted data because half written data will be fixed on a ordered journal.

ownhere said:
replace
c6 f7 66 fd 03 20 78 72
with
c6 f7 66 fd 01 20 78 72
replace
cc f8 0c 00 03 20 a3 68
with
cc f8 0c 00 01 20 a3 68
replace
5f fa 81 fc 83 f0 01 06
with
5f fa 81 fc 01 23 00 26
EDIT(2011/01/07 23:40):
replace
5f fa 81 fc 83 f0 01 06
with
5f fa 81 fc 01 26 00 bf
replace
23 72 00 23 66 72 02 26
with
26 72 00 23 63 72 02 26
Click to expand...
Click to collapse
are these values the same in sqlite hd 1.72....
i can not find them...after c6 f7 66 it say can not find...if i open it in a hex editor
edit: or anyone can give me a patched version for 1.72..?
thx for answers...with kind regards...Alex

[Q] Original Sidekick Notifications and Ringtones

The old sidekicks are out of commission so I do not see where this would be a problem. Does anyone have the original Sidekick ringtones available? Specifically Dangerous Girl or the "Danger" ones.

dude seriously..... u shouldve just stayed with the old one -.-

Can't stay with the old one and still have internet. I think my wife would have. I had to pull it from her hands. I finally got an Iphone in her hands but that was hard for both of us. I couldn't get her to settle on an android device. I have the Inspire, one of the best phones i've ever had. She wants the ringtones though from it and I didn't have a developer key from Danger where i could get them. If it were even possible.

I've been searching around on google for a good half an hour and haven't found anythng except a few youtube clips. All we need are the audio files to convert to an mp3 and the rest is easy. We could also download the videos from youtube and rip the audio that way.

gearhead27 said:
I've been searching around on google for a good half an hour and haven't found anythng except a few youtube clips. All we need are the audio files to convert to an mp3 and the rest is easy. We could also download the videos from youtube and rip the audio that way.
Click to expand...
Click to collapse
I actually thought about that. And then I thought about running them through Audacity for quality improvement. I just was hoping beyond hope that someone would have one. I tried to re-open a thread on another forum but no one has responded. The person had some of the effects, just none of the tones.

I found a post with these files. (not allowed to post links yet!)
Dated 12/2008 on Android Community
New Message.zip‎ (25.2 KB, 4606 views)
Attention.zip‎ (18.5 KB, 1244 views)
Blue Flute.zip‎ (36.1 KB, 802 views)
AIM.zip‎ (44.3 KB, 1127 views)
Bell Tree.zip‎ (58.0 KB, 556 views)
Bird Call.zip‎ (25.5 KB, 471 views)
Default Beep.zip‎ (24.5 KB, 639 views)
Ding-A-Ling.zip‎ (38.8 KB, 473 views)
Evil Overlord.zip‎ (33.6 KB, 485 views)
Frogs.zip‎ (25.1 KB, 427 views)
Future Ring.zip‎ (74.3 KB, 578 views)
Siren.zip‎ (43.7 KB, 497 views)
Wah-Wah.zip‎ (42.7 KB, 530 views)
not sure if files still work, but worth a try!!!

ncmacasl said:
I found a post with these files. (not allowed to post links yet!)
Dated 12/2008 on Android Community
New Message.zip‎ (25.2 KB, 4606 views)
Attention.zip‎ (18.5 KB, 1244 views)
Blue Flute.zip‎ (36.1 KB, 802 views)
AIM.zip‎ (44.3 KB, 1127 views)
Bell Tree.zip‎ (58.0 KB, 556 views)
Bird Call.zip‎ (25.5 KB, 471 views)
Default Beep.zip‎ (24.5 KB, 639 views)
Ding-A-Ling.zip‎ (38.8 KB, 473 views)
Evil Overlord.zip‎ (33.6 KB, 485 views)
Frogs.zip‎ (25.1 KB, 427 views)
Future Ring.zip‎ (74.3 KB, 578 views)
Siren.zip‎ (43.7 KB, 497 views)
Wah-Wah.zip‎ (42.7 KB, 530 views)
not sure if files still work, but worth a try!!!
Click to expand...
Click to collapse
Hey good to see you here! I too wondered about the ringtones from the original Sidekick but I never had a developer key but that's okay.

here is the link: http://androidcommunity.com/forums/f8/sidekick-new-message-sound-file-9870/#post106592 files are included (also several from the AIM app later in the same thread)

A developer's key wouldn't help much with getting ringtones off the Danger powered Hiptops.
We would need an inside source that had access to "hands on" development at Danger to get the actual files that the Hiptop used. The original sound files were stored as Beatnik .RMF files--although the device did support up to 17 seconds of audio with a compessed 16-bit, 11kHz, IMA (4:1) WAV files.
Even if you could dump perfect originals, you wouldn't be able to use them on Android. Google did not license Beatnik's compression technology and the development community has moved toward XMF--an open format for MIDI triggered audio.
The best way to get the sounds now is to plug the device directly into a computer and record the sounds directly. That would require taking a few extra minutes to crop and clean up the recordings, but it should work.

orange808 said:
A developer's key wouldn't help much with getting ringtones off the Danger powered Hiptops.
We would need an inside source that had access to "hands on" development at Danger to get the actual files that the Hiptop used. The original sound files were stored as Beatnik .RMF files--although the device did support up to 17 seconds of audio with a compessed 16-bit, 11kHz, IMA (4:1) WAV files.
Even if you could dump perfect originals, you wouldn't be able to use them on Android. Google did not license Beatnik's compression technology and the development community has moved toward XMF--an open format for MIDI triggered audio.
The best way to get the sounds now is to plug the device directly into a computer and record the sounds directly. That would require taking a few extra minutes to crop and clean up the recordings, but it should work.
Click to expand...
Click to collapse
Doing this as we speak.

Does anybody have an original Sidekick or Color Sidekick? I traded mine in as I upgraded and the oldest device I own is a Sidekick 2.
It would be nice to have the sounds from the original device.
Sent from my SGH-T839 using XDA App

orange808 said:
Does anybody have an original Sidekick or Color Sidekick? I traded mine in as I upgraded and the oldest device I own is a Sidekick 2.
It would be nice to have the sounds from the original device.
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Sidekick Slide is what I got.

The files I shared from the Android community seem to be from the original Sidekicks.
I have also posted the files here on my SugarSync account (similar to DropBox):
https://www.sugarsync.com/share/bt8m248oxzcbv

Also, I have a CSK, a Sidekick 2, & a Sidekick LX (2007)

@Orange, LOL I see you accessed the folder already!! let me know what you think!

Nice work. Thanks.
I'll go ahead and rip the SKII audio, icons, and make a Danger checkerboard wallpaper.
I'll throw them on sugarsync when I'm done.
Sent from my SGH-T839 using XDA App

My thanks to those who have posted the sounds from the old Sidekicks. I rooted my Sidekick and put one of the tones on the internal memory at /system/audio/notifications/. I can set it as my chosen tone in the messaging app, but it doesn't play after I copy it. Also, I noticed the pre-loaded sounds are in .ogg format. Should ÷ convert the mp3 to ogg and retry? Or, should it work either way?
Sent from my T-Mobile Sidekick 4G.

Thank you!
Thank you for everyone's hard work!! The original sidekicks will be greatly missed, in my opinion. I haven't had a chance to play with the 4g yet, but my wife is still having withdrawls!

Sidekick II backgrounds
Here's the Sidekick II classic "checkboard" wallpaper background.
Pull the wallpaper size to fit the entire image before you apply it.
The icon images will probably need to be resized. They also don't look quite right without the blue dot behind them. But, they seem to fit the rest of the Android theme better like this...

is that the hi-def version? looks a bit low-res or was that on purpose?

Help Please...profile picture emergency...

Not worth the effort but really want a profile picture for xda account. Have resized several images but none will upload. Just keeps saying upload failed. :crying: This is a big problem and will be thanked massively.

Hmm that is a bit strange. I had no trouble uploading an avatar on here. You should make sure that the maximum size of your custom image is 80 by 80 pixels or 19.5 KB (whichever is smaller). If your image fits those parameters then it might be your browser that's causing some trouble. Try uploading it using another one.

[HOW TO] Calibrate your touchscreen (chinese tablets - YG A701, Pioneer A700 etc)

Hey guys,
So a couple of weeks ago i've bought a chinese tablet that came with Android 2.3.3. As you might have guessed, the calibration app didn't work and basically i've spent hours and hours reading about how to manually calibrate the screen. At first, i thought it would've been a simple thing to do... but no.
So if any of you out there have experienced any problems with the calibration of your tablet, i have a solution. You just have to follow these steps:
1. Make sure you have the ADB drivers installed. (Install the SDK, run the program - SDK Manager.exe - and then scroll down until you find the "Extras". Select Google USB Driver, download and install them.)
2. Root your device using SuperOneClick. (To do this, turn on the device until the home screen appears, then run SuperOneClick). The program is attached at the end of this post.
3. Run the calibration script i also attached. It's in the "Calibration" folder.
4. You should be partially done.
Basically the file responsible with the calibration of your screen is pointercal (no extension) and it is found in /data/data/touchscreen.calibration/files/. When you try to calibrate your screen using the default app, you're going to end up with the wrong values for the pointercal file. For these devices, there should be 20 pointercal values, not 6-7.
BAD EXAMPLE
22865 15 -804946 -267 18625 -1193918 65536
GOOD EXAMPLE
45 175 602 60 625 360 31 397 325 240 50 50 750 50 750 430 50 430 400 240 (these are actually the values of my tablet).
Unfortunatelly, every tablet is different so you'd have to change some of the values in the pointercal file. I have found out that the first ten values are XY pairs, the last ten are needed to calculate the actual position of the touch input. So basically you'd have to modify the first ten values until you have a nice calibrated screen.
These values match the corners of your screen :
45 175 - Top left corner
602 60 - Top right
625 360 - Bottom right
31 397 - Bottom left
325 240 - Center
Remember these are XY values!
There is no standard, so modify them with any text editor, runt the calibration script, restart your device and see what you've got. If you don't have a nice calibrated screen, try again. I have also included a modified version of build.prop, which makes the screen a lot more sensitive and there are overall improvements.
I really hope this post helps somebody. I also hope i didn't make many English related mistakes :silly: I'm not a native speaker so i apologize.

Nice sharing bro.Some of devices not include calibration setting by default.So this tutorial is useful for those device's owner.
Sent from my LT22i using xda app-developers app

How would I run this on Xperia S? How do I run a script?