Database Users

Galaxy-S Stalling Issue?

After having some major speed issues using Touchdown on my new Vibrant, I was directed to this thread discussing issues with the way Samsung stores app data on the phone. Apparently the app data is stored on the internal SD vs. NAND and that is considerably slower. Here are the two methods to fix:
*Both Methods require ROOT*
*Method 1 limits the space of app data, which can possibly cause issues*
*Method 2 requires writing a new Kernel, which comes with it's own possible issues*
*READ THE THREADS!*
Method 1: http://android.modaco.com/content/s...298/got-the-stalling-problem-rooted-try-this/
Method 2: http://android.modaco.com/content/s...ed-real-fix-for-the-stalling-lagging-problem/
Hopefully this will be helpful moving forward with the development of this phone!
Note: I have used method 1 which moved the app data from the SD space to the NAND space which significantly increased the speed of my phone, but PLEASE read the links and associated discussion. You are limited to 130MB app space on NAND, which can be limiting depending on which apps you use. Method 2 purports to fix this limitation...
How to check how much app memory you are currently using:
Code:
adb shell
su
cd /data/data
busybox du -h|busybox grep M
How to apply Method 1:
Code:
adb shell
su
busybox cp -rp /data/data /dbdata
mv /data/data /data/data.bak
ln -s /dbdata/data /data/data
reboot
How to undo Method 1 (no loss):
Code:
adb shell
su
busybox cp -rp /dbdata/data /data/data.tmp
rm -r /data/data
mv /data/data.tmp /data/data
reboot
How to undo Method 1 (restore to point of application):
Code:
adb shell
su
rm /data/data
mv /data/data.bak /data/data
reboot

Awesome, thanks for doing the parsing and putting out a procedure. Works great. No more lag.

Thanks, just tried it out on mine.

BE WARNED you will run into issues if your application data goes over 130MB. There is a better way to do this which includes a custom kernel with ext3/4 support and symlinking to the ext partition instead of the small NAND space.
Find it herehttp://android.modaco.com/content/samsung-galaxy-s-s-modaco-com/313365/updated-real-fix-for-the-stalling-lagging-problem/
I havent felt the need to perform either of these ATM. Please warn people of the consequences especially if your just telling them "Hey this will make your phone faster!" I do notice its explained in the article you linked from but not everyone will read that and then when they start having issues they will have no idea what to do. For those that completed this method you might want to revert it and go a better route. 130MB isnt enough room.

Agreed...I figured people would read the link, but you never know. Will update accordingly. THX!

I am trying test out method 1 but I keep getting stuck. I type in cp -rp /data/data /dbdata into adb but it comes back with cp: not found. Any ideas what I am doing wrong here?

Add busybox before the cp command; i.e.: busybox cp etc...

Krycek said:
Add busybox before the cp command; i.e.: busybox cp etc...
Click to expand...
Click to collapse
Thanks, figured it was something simple like that. Still new to this Android stuff after years of custom WinMo roms and hybrid Blackberry roms.

i'm a little sketchy about applying method 2...will installing a modified kernal have an effect when samsung rolls out the update for 2.2?

I concur, but that is also probably the "right" way to do it. The nice part about method 1 is it is easily reversible. I will update post 1 in a minute with how to check what your current usage is to see if you are close to the 130MB limit.

Thanks, just checked my usage and was only using 21MB thus far. I figure the 130MB limit should suit me fine until Samsung issues a fix. It looks like the European devices already have a new firmware that speeds it up quite a bit so probably won't be too much longer here in the US either.

Im not going to do either. Im going to wait for an official fix.

I'm about to get a vibrant; if you can get parted installed wouldn't it be fairly simple to just unmount and partition the internal SD card into fat32 and ext3/4, and then maybe just update fstab? (parted lets you resize existing partitions to make room for new ones, but I'm not sure if the Samsung firmware uses fstab or something else, coming from a MyTouch here).

anomalous3 said:
I'm about to get a vibrant; if you can get parted installed wouldn't it be fairly simple to just unmount and partition the internal SD card into fat32 and ext3/4, and then maybe just update fstab? (parted lets you resize existing partitions to make room for new ones, but I'm not sure if the Samsung firmware uses fstab or something else, coming from a MyTouch here).
Click to expand...
Click to collapse
i doubt it...it's the reason you need to install the modded kernal so that it recognizes the ext3 or ext4 partition. without it the partition is useless. i personally wouldnt use method 2 as there is no way to revert as of now.

Man i dont understand wtf is going on. Im usually good with adb and whatnot but I cant seem to get su permissions. I type "adb shell" and it goes thru. But when I type "su" it comes back 'permission denied'. Of course, I applied the update.zip to get my phone rooted. Superuser works and I have my rooted apps working.
Anyone have any ideas?!

I'm not infront of my PC atm, but try this.
adb mount
adb shell
su
If mount doesn't work try remount.
Let me know if this works for you, once i'm home I can double check.

Already tried that. I have a Nexus One and adb remount works on that but for this phone it says 'remount failed: No such file or directory'

Digitalthug said:
Man i dont understand wtf is going on. Im usually good with adb and whatnot but I cant seem to get su permissions. I type "adb shell" and it goes thru. But when I type "su" it comes back 'permission denied'. Of course, I applied the update.zip to get my phone rooted. Superuser works and I have my rooted apps working.
Anyone have any ideas?!
Click to expand...
Click to collapse
You might have already tried this, but make sure the phone is unlocked (at home screen) when you run the su command from your workstation... superuser will then prompt and you can allow it to run.
I've noticed that if the screen is locked it won't prompt and just give the permission denied message.
Sent from my Vibrant (with lag fix and loving it)

just did method 1 and the difference is incredible. as far as method 2 goes, will custom roms have this ability from the get go or do we need the official samsung update?

I just want to confirm that this fix works for the US version of the Galaxy S (Samsung Vibrant) right?

[Q] ADB Question

Ok. So im touching up on my ADB. Messing around trying to transfer files and what not. Now when I try and push and file from my pc to my sdcard it errors me out saying Read-Only File System.
Command im doing is
adb push C:\Android\android.jpg /sdcard/android.jpg
Any ideas where im going wrong here? I have full root access, When I:
adb shell
su
I do not get permission denied... So dont get why this is happening.
Edit: Just looked more into it. I can push to the phone. Just not to the sdcard. I pushed to /data/local for giggles and it worked. Only gives me read only when pushing to the /sdcard.
Thanks for any info.

just tried mine and it worked fine. I first tried it with pushing a file from my sdk dir, and tried it with pushing a file from another directory on the drive. worked both times, not sure what to tell you.
p.s. I'm running the desire z rom

Yeah for some reason its only on the sdcard I cant write to.. USB Debugging is checked. Anyone have the slightest idea as to why I'm unable to write to my sdcard with this Read-only File system error?

Anyone know the shell command to mount the sd card as rw? Been trying to figure this thing out but it has me in a puzzle.
[G2/HTC Vision]

luis86dr said:
Anyone know the shell command to mount the sd card as rw? Been trying to figure this thing out but it has me in a puzzle.
[G2/HTC Vision]
Click to expand...
Click to collapse
Are you making sure that you don't have media mounted? That would screw up /sdcard. For me, it's "umount /media/*; eject /dev/sde" then on the G2 disable USB storage, wait for it to remount the SD card.
If that still doesn't work, what does "adb shell mount" tell you?
Normally, like with /system, it's "busybox mount -o remount,rw /system", but I've never seen /sdcard mounted readonly, unless there are I/O errors (it's mounted to remount ro on failure). Have you tried rebooting your phone?

luis86dr said:
Ok. So im touching up on my ADB. Messing around trying to transfer files and what not. Now when I try and push and file from my pc to my sdcard it errors me out saying Read-Only File System.
Command im doing is
adb push C:\Android\android.jpg /sdcard/android.jpg
Any ideas where im going wrong here? I have full root access, When I:
adb shell
su
I do not get permission denied... So dont get why this is happening.
Edit: Just looked more into it. I can push to the phone. Just not to the sdcard. I pushed to /data/local for giggles and it worked. Only gives me read only when pushing to the /sdcard.
Thanks for any info.
Click to expand...
Click to collapse
Is it possible that you are writing the command wrong? I noticed the slash is opposite on the second half of your command code.
C:\Android\android.jpg /sdcard/android.jpg
Click to expand...
Click to collapse

Figured it out. Had usb storage on. So it wouldn't push turned it off and I was able to push. Thx foe the info
[G2/HTC Vision]

[Q] Help!!! I think my device is bricked...

Hello everyone.... i really think i bricked my device and i would love for someone to help me... i Have been searching the forum since yesterday morning and i cant seem to find anything that works... well first off i am rooted (s-off) i used the gfree method because setting up adb wasnt going to well for some reason... but im stuck in bootloop mode or whatever and when i hold down power and the vol down button it recognizes the pd15dimg.zip file but when i do the update i get an error check out the first pic below... then when i put it in recovery mode i get another error check out 2nd pic... then when i to to load the pd15dimg.zip manually from the choose zip file directly from the root of the sd card i get another error check out third pic... as u can see im on cwm 3.0.2.4 and the rom i was originally using i dont remember the name but it was gingerbread...can someone plz help?? any help will be appreciated. thnx

I had this same issue 3 weeks ago. But I wasnt getting those partition errors with the PD15dimg.zip. I would first suggest downloading another one to make sure the one you got wasnt corrupted. But before I figured out to do the pd15dimg trick, the nice fellas over on Cyanogenmods Shoutbox were helping me out with a different method. You have the engineering bootloader, which is great news for you. I did not. Do you have a nandroid backup on your SD that you can copy over to your computer?

i didnt do a nandroid back up but i did a back up threw the rom manager i had... is that useful?

curlz187 said:
i didnt do a nandroid back up but i did a back up threw the rom manager i had... is that useful?
Click to expand...
Click to collapse
Hmm. Maybe, I'm not sure what that backs up, do you know what folder that went into? Find it and post whats in there

the folder is on the root of my sd card... its call clockworkmod... i click that then i see two folders one of which is named back ups. i click that and it has tsome some files in it such as android_secure.img boot.img cache.img data.img nandroid.md5 recovery.img and system.img

curlz187 said:
the folder is on the root of my sd card... its call clockworkmod... i click that then i see two folders one of which is named back ups. i click that and it has tsome some files in it such as android_secure.img boot.img cache.img data.img nandroid.md5 recovery.img and system.img
Click to expand...
Click to collapse
Perfect! Alright, PM now and I'll help you with the rest alright?

Ok just did it

does anyone else have any insight on this subject?

Once you get fail-pu you can't do anything as you need to send it back they have to replace the motherboard. Fail PU means failed partition update at this point once its corrupted you can't reformat it since we are using SLC-EUDA low level format which is 1 time.

TmpUsr said:
Once you get fail-pu you can't do anything as you need to send it back they have to replace the motherboard. Fail PU means failed partition update at this point once its corrupted you can't reformat it since we are using SLC-EUDA low level format which is 1 time.
Click to expand...
Click to collapse
the original file i used was corruted JDV28 sent me another file and it starts the update but idk how long its suppose to take because its been updating for bout 15 mins now

Well PD15IMG.zip can be corrupted and even if you get a good radio/rom image and verify it the problem you will run in to is when you try to write to the partition. Fail PU means failed partition update where you can't write radio, recovery and system. I was leaning on to gfree but I need another phone to fully hack it as I was massing with the emmc block last time but atm I don't have any other phones. Best solution is soon as you see the errors on recovery you should push and manually flash recovery partition and replace it.

TmpUsr said:
Well PD15IMG.zip can be corrupted and even if you get a good radio/rom image and verify it the problem you will run in to is when you try to write to the partition. Fail PU means failed partition update where you can't write radio, recovery and system. I was leaning on to gfree but I need another phone to fully hack it as I was massing with the emmc block last time but atm I don't have any other phones. Best solution is soon as you see the errors on recovery you should push and manually flash recovery partition and replace it.
Click to expand...
Click to collapse
how do i do that?

Terminal said:
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
cp /sdcard/flash_image /system/bin [hit enter]
flash_image recovery /sdcard/recovery.img [hit enter]
Click to expand...
Click to collapse
adb said:
adb devices [hit enter]
adb push boot.img /data/local/boot.img [hit enter]
adb shell [hit enter]
su [hit enter]
flash_image boot /data/local/boot.img [hit enter]
rm rm /data/local/boot.img [hit enter]
Click to expand...
Click to collapse
Like I said depends on how deep the issue is you can't revert it. But try it anyways. You will need image which you can get from dev section.

im not connected threw adb had problems setting it up b4... but after i did the update now my screen only turns black? idk what happened it was updating i leave for a min now it seems unusable

I had the same issue, couldn't recover it so I sent it back.
Sent from my HTC Glacier using XDA Premium App

partitioning issues most likely = game over unless your running the engineering boot. thats the bottom line i think with everyone thats running into these issues..

[Q] Honeycomb Keyboard

I'm kinda new to android
I've started to delete useless apps through Titanium Backup(acer staff,games etc) , and exidently deleted smth connected with honeycomb stock keyboard.
Now every time when i want to use stock keyboard, pops up a messege "The application Android keyboard (process com.google.android.inputmethod.latin) has stopped unexpectedly. plz try again".
Ive tryied to reset factory data but it wont helped. Is thera any solution for this problem? if there no, plz tell how to completely reset tablet) ive read "system Images " thread but i didn understand some things
here is my recover steps: (for a500 which is bricked)
for a500 is normal:
root it
put the system.img into a500
connect to the computer with adb and follow the codes:
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
then reboot
Click to expand...
Click to collapse
connect to the computer with adb and follow the codes:
su
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
what that means)

You might very well have ruined your tablet.
I'm not a developer or coder so I can't make any sense of the code you posted but if a reset didn't fix it then you've certainly deleted something important. Hopefully someone has some ideas.
If not, then maybe you can return it? And next time, don't delete something unless you know what it is you're deleting.

ok ive recovered from image, but now wifi is not working , what should i do?

There are posts about having to change file permissions to fix wifi. Search this forum, there are a few.
edit - linked post
http://forum.xda-developers.com/showthread.php?t=1074449&highlight=wifi+permission

yeah ive read this but i dont know how to move that files to system folder on devide, wifi is down , so i cant download any file managing apps from market and theres no any file managers on stock Rom

If you've got the adb working, you can use the command mv to move the file.
I'm not sure of the exact path involved, but for example. the file is in /mnt/sdcard/filetobemoved and needs to go into /sytem/lib/modules
mv /mnt/sdcard/filetobemoved /system/lib/modules
That'd put it in the location you need. To change the permissions, you'd use the command chmod
chmod 655 /system/lib/modules/filetobemoved
The 655 is an octal(0-7) representation of the file's permissions. I'm not sure what permissions it needs, but you could try 655 as a start unless someone else knows for sure.
if you want, hit me up on msn, I can try to walk you through it: [email protected]

Glebaka said:
ok ive recovered from image, but now wifi is not working , what should i do?
Click to expand...
Click to collapse
Ah *phew* Good to hear.

gammaRascal said:
Ah *phew* Good to hear.
Click to expand...
Click to collapse
lol How'd he get in that shape to begin with? Any idea what exactly it was he deleted that bonked his system?

muqali said:
lol How'd he get in that shape to begin with? Any idea what exactly it was he deleted that bonked his system?
Click to expand...
Click to collapse
No clue. I really should start reading up on HC app development and at least familiarize myself with that environment.
I haven't rooted yet cause I'm e'scarded to.

ahh i cant replace that files , somehow installed astro manager(through docsttogo) but i cant remove/replace/rename that files in system/lib/modules it says i dont have permission to do this.
tryed in connectbot type "mv /mnt/sdcard/filetobemoved /system/lib/modules"
got this "failed on '/system/lib/modules/filename' - cross-device link"
im rooted what if

Glebaka said:
ahh i cant replace that files , somehow installed astro manager(through docsttogo) but i cant remove/replace/rename that files in system/lib/modules i dont have permission to do this.
tried connectbot tryied "mv /mnt/sdcard/filetobemoved /system/lib/modules"
got this "failed on '/system/lib/modules/filename' - cross-device link"
im rooted
Click to expand...
Click to collapse
type mount and paste/retype the line that has /system in it. It might be mounted read only.
or try the cp command in place of mv
edit - also, the filetobemoved is just an example. I think one of the filenames is bcm4329.ko but I'm not sure. so /system/lib/modules/bcm4329.ko would be the full path

ah im total noob tried cp instead of mv it said permission denied .
t
ype mount and paste/retype the line that has /system in it. It might be mounted read only.
Click to expand...
Click to collapse
i didnt get that (
edit - also, the filetobemoved is just an example. I think one of the filenames is bcm4329.ko but I'm not sure. so /system/lib/modules/bcm4329.ko would be the full path
Click to expand...
Click to collapse
yeah thats i know)

Are you logged into the tablet using adb's shell? I've only used that once on a different tablet, but iirc the commands are standard Unix/Linux commands. Someone correct me if I'm wrong but aren't you already logged in as superuser like this? You don't need to 'sudo' or 'su' to switch over do you?
I'm not familiar enough with this specific environment to figure out what might be keeping you from placing those files in that location. The command to check the partitions mount options is
mount
It should return a bunch of text, one line of which is gonna be the /system partition. If it's ro(read only) then you can't write to it and would need to remount it.

yeah it looks like it is "ro"
ive got /system ext4 ro
how to remount)

My knowledge of adb is limited as well. All I know is that I can connect to it, type: adb devices (in the command prompt) to make sure it sees my tab then 'adb push filename.extension /directory/structure' to force files... Conversly, I think adb pull filename.extension /directory/structure will grab files on the tab if you know what they are called and where they are located.

Glebaka said:
yeah it looks like it is "ro"
ive got /system ext4 ro
how to remount)
Click to expand...
Click to collapse
what was the /dev/block/mtdblock for /system?
there is a number after it...for example /dev/block/mtdblock1
mount -o rw,remount -t ext4 /dev/block/mtdblock1 /system
would remount it read/write, provided that it is mtdblock1, change the number depending on what your device has.

yeah now /system have "rw", but it anyway refuses to copy using mv(failed on '/system/lib/modules/filename' - cross-device link"
) or astro manager

Glebaka said:
yeah now /system have "rw", but it anyway refuses to copy using mv(failed on '/system/lib/modules/filename' - cross-device link"
) or astro manager
Click to expand...
Click to collapse
If cp won't put it there either, I'm out of ideas. Maybe ask in the other thread how they were able to copy/move the file and set the permissions?

I know it may not be really classy, but how about downloading an .apk That will let you mount the drive, to an sd card in a computer then transfer that to the Acer. (If it's an extreme case and nothing else will work..not condoning piracy, but don't know what would work...)
or is it possible to copy the system data from a Titanium backup and send it over so he can restore the missing files?

This following step I can't be responsible for it's safety. It looks safe to my eyes, but proceed having been forewarned. I did some research and you might be able to use dd to get the file there.
dd if=/mnt/sdcard/filname of=/system/lib/modules/filename

[SOLVED] Using Terminal Emulator to write to system

Not sure if this will help anyone else, but I searched forever trying to figure out how to write into the system folder using Terminal Emulator on the Note 3 to no avail. I found a slew of posts that said to type "mount -o rw,remount /system" to achieve this. When I used this command it didn't return any errors so I assumed it worked, however no files ended up being copied and pasted to the location I wanted. I found numerous other examples that were supposed to enable writing to the system as well, but none of them worked. I finally figured out how to get it to work on my Note 3 by typing "mount" in terminal emulator and noticing that at the very beginning of the string that was returned was "rootfs". So if you are wanting write to your system using Terminal Emulator on the VZW Note 3 here is what ended up working for me:
Code:
mount -o remount,rw rootfs
to return to read only enter:
Code:
mount -o remount,ro rootfs
I wanted to figure this out because a bug in TWRP v2.6.3.0 maimed my efs partition and bricklooped my phone. Even flashing the Stock Developer tar by Beans wouldn't bring it out of the brickloop. I was able to get out of the brickloop by following this thread, but even though my phone booted up and the IMEI # was correct, my /efs folder was missing in action. This caused odd things to happen like my lock screen not functioning and the power button instantly turning the phone off instead of bringing up the power menu. I discovered this was because the phone was placed into something called "factory mode" and that to fix it you needed to edit some files in the efs folder, which were completely missing on my device. Member js0uth graciously sent me his efs folder from his Developer Note 3 and when I copied it to my phone it began to function normally again (big shout out to js0uth!). However, this folder was completely deleted once again after a reboot. So now you can see why I was looking for a way to copy these files using Terminal Emulator. I ended up making a Tasker profile with the Secure Settings plugin that automatically copies the files from my ext SD card to my system folder on boot of the device. In order to mount, copy/paste the files while retaining the correct permissions from the folder that js0uth sent me, and unmount the system I had the set up my Secure Settings command as follows:
Code:
mount -o remount,rw rootfs;cp -Rpf /storage/extSdCard/efs/* /efs/;mount -o remount,ro rootfs
So now I have a livable workaround for my problem until I can discover a way for the phone to rebuild my own /efs folder.
Edit: See radionerd's post for a permanent fix to this issue and be sure to hit thanks under his name if it helps you.

I did the same to my DE. Corrupted EFS about a month ago after a few flashes using TWRP 2.6.3.0. Boot loops for 28 hours of hell until I followed your tracks to the trick that deleted my corrupted EFS folder, and created a new empty folder. I guess this would wipe out IMEI, Mac, and more in models that store phone specific data in EFS. We lucked out I've read that our phones have that info in a few other folder not EFS
Since wiping EFS I have run stock ROM, CM11, and now bean V6. I didn't see the factory mode popup until recently. I noticed that the screen will flash when leaving or entering cell service.
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Thanks for documenting your steps to recovery.
radionerd

radionerd said:
My corrupted EFS was 3MB. I'm curious what's the size of the EFS folder from js0uth?
Click to expand...
Click to collapse
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
radionerd said:
Were you able to enter the factory mode on string? something like this?
Code:
# echo -n ON > /efs/FactoryApp/factorymode
this is from an S3
Click to expand...
Click to collapse
Setting the Factorymode folder to ON is actually what disables that mode. Seems backwards I know, but when it's set to OFF (or if the folder is completely missing as in my case) that warning message will display. If that folder is intact on your phone then you should be able to use a string to disable or enable Factorymode.

It got worse before it got better
bodieism said:
It's 1.04 MB. Sorry for taking so long to respond. I thought I had it set up to send instant emails for replies to this thread, but apparently I didn't.
No worries, I went from an annoyance of no lock screen to bricked for over 6 weeks. This happened after trying to do an EFS backup.
I've learned a lot since back then, My DE is back 100%, EFS is repaired. I think we ran the same script which actually points to the wrong mount in our phones. It brought us out of bootloops, but efs was pointed to block12. Qualcom snapdragon Note-3's use mmblk0p11 to load /efs.
If you still have to load the tasker script, I think I figured out an easy fix to rebuild your original efs folder.
I would backup mounts first, delete /efs folder. Then run the original script, but this time change from 12 to 11.
Code:
adb shell
su
mke2fs /dev/block/mmcblk0p11
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p11 /efs
Bet that would do the trick
Here is my thread
Click to expand...
Click to collapse

^ That did do the trick! :good:
Phone is back to 100% working order :highfive: