Develop Bugs

Quadrant score 2234 with rooted stock FW I9000ZSJF7 [EDITED 10AUG 1714HKT new tool]

tested for about a week without problems
no data2sd required (actually mod to sd is not needed), no more lag, smooth scroll/zoom in and out in default browser with a web page contains more than 170 images, much faster cache for browser, market and other apps retrieval and listing
if u guys r interested, pls let me know and i'll post it here later tonite (HKT). i'll ONLY tell u what i did and how to do that, but WONT show u a step by step guide, since a typo may brick ur phone, sorry about that. however, experienced linux users will know how. i think it's better for them to write scripts and run automatically for all users
and, hopefully, experts here can have better solutions to this dirty trick to speed up this laggy phone
EDIT: 8 aug 2250HKT
ok, here's how:
- create an empty file with dd (i chose -b 4096 -m 1)
- mount it to loopx and format it with ext2 (busybox)
- create mount points and create links, eg
mount -o rw,noatime,nodiratime /dev/loop0 /dbdata/dbdataimage
then mv files and folders to /dbdata/dbdatimage
so, instead of reading /dbdata/databases/com.1.2.3, it will be linked to /dbdata/dbdataimage/databases/com.1.2.3
- finally write a script to mount them on boot by replacing playlogos1
simply speaking, is to run on an ext2 file block in rfs, and that's all for the trick!!
WARNING:
- i did it for /cache, /dbdata and /data only
- empty files, folders, and sym links will be deleted by the system under /cache
- dont reboot the phone when u've temporarily moved /dbdata/databases to a slow partition like /data
personally, i moved /data/data and /data/dalvik-cache to /dbdata and moved browser and market cache files to /cache
PS E&OE
enjoy!
EDIT2:
no need to try ext3/4, they'll slow down ur phone, i've tried them already
EDIT3 09 aug 0033HKT:
it's not for the benchmark only, instead, it has very good effects on ur phone's io
for the loop device:
busybox mknod /dev/loop0 b 7 0
busybox losetup /dev/loop0 /dbdata/dbdata.img
busybox mkfs.ext2 /dev/loop0
then mount it
and, here's my mount output:
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,nodiratime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/loop0 /dbdata/dbdata1 ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop2 /cache/cache1 ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop2 /cache/market ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/loop2 /cache/browser ext2 rw,noatime,nodiratime,errors=continue 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block//vold/179:9 /sdcard/sd vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-
1,shortname=mixed,utf8,errors=remount-ro 0 0
EDIT4 09 aug 0039HKT:
- no need to deal with /data
- the major thing is /dbdata/databases
- it wont have impact when u connect it to ur pc/kies since kies only deal with /sdcard and /sdcard/sd only, which both r out of my concern
- to see the improvement, simply do a dd and u'll see the difference
EDIT5 09 aug 2212HKT:
a simple tool added for phone test (windows only)
pls go to
http://forum.xda-developers.com/showthread.php?t=748596&page=38#373
EDIT6 10 aug 1714HKT:
new test tool (test4me v1.11) updated
test4me 1.11 updated, changes:
- will look for busybox under /system/bin/ also
- will look for playlogos1, if not found, will look for other mods
pls go to
http://forum.xda-developers.com/showthread.php?t=748596&page=38#373
PS for questions regarding other similar fixes, pls refer to the author. I cannot/will not comment on others job. Thx
http://a.imageshack.us/img32/7803/201008060404passedreboo.png
http://a.imageshack.us/img42/3750/device1r.png

ykk_five said:
tested for about a week without problems
no data2sd required (actually mod to sd is not needed), no more lag, smooth scroll/zoom in and out in default browser with a web page contains more than 170 images, much faster cache for browser, market and other apps retrieval and listing
if u guys r interested, pls let me know and i'll post it here later tonite (HKT). i'll ONLY tell u what i did and how to do that, but WONT show u a step by step guide, since a typo may brick ur phone, sorry about that. however, experienced linux users will know how
http://a.imageshack.us/img32/7803/201008060404passedreboo.png
http://a.imageshack.us/img42/3750/device1r.png
Click to expand...
Click to collapse
Yes, very interested

very very interested! pls post the details, thanks!

sounds cool, hope to read here what you did soon =D

Yes. Very interested.
Sent from my GT-I9000 using XDA App

Count me in!

maybe we can use it for other firmwares too! Im interested.

want that! what languages are included?

Impressive.
.
Waiting.

hm. curious what you did. you say "stock firmware" but from the pictures it looks like you use your own kernel?! more info plz

2234?!
I'm guessing you succeeded in changing the whole phone over to EXT4 + other tweaks?
I'm interested.

Sounds awesome - can't wait for more infos

yah @ could be achieved by OC ...

RyanZA said:
I'm guessing you succeeded in changing the whole phone over to EXT4
Click to expand...
Click to collapse
I've been mulling this one over in my head for the last few weeks, but I don't have nearly enough technical knowledge to even start getting it sorted - I was worried about how Odin/recovery would treat the ext4, and whether it would be able to flash firmwares at all after doing so...
Anyhow, nice work OP, looking forward to the explanation

whats the magic potion your phone drank for this hype?

RyanZA said:
2234?!
I'm guessing you succeeded in changing the whole phone over to EXT4 + other tweaks?
I'm interested.
Click to expand...
Click to collapse
I thought about that too, but naah, it's just a dream

tids2k said:
yah @ could be achieved by OC ...
Click to expand...
Click to collapse
Can't be achieved with an OC, since quadrant is mainly graphics/IO - cpu is a smaller part

Would love if you could post what was done to achieve this. After all, the whole point of XDA is to be a community where everyone can share and build off each other's achievements and discoveries with a legion of willing testers prepared to take the risk of bricking their phone. =)
Amazing work to get that score! Congrats, and looking forward to when this will be able to be developed into a released rom / kernel / method.

Argh double post. Ignore this. =)

Can't say I'm not interested.

[HOWTO] Convert ext4 partitions to No-Journaling mode

WARNING: This procedure is risky and may result in loss of data.
This is a follow up to findings made in this thread: http://forum.xda-developers.com/showthread.php?t=819580
Many people have been asking for an ext2 lagfix. You can get something similar but (arguably) better: ext4 with no journaling. Ext4 no-journal performs as fast or faster than ext2 because of performance improvements made in ext4.
Quadrant comparison for ext4 /data-only lagfix:
ext4 scores about 1500, ext4 no-journal scores about 1650.
This should work with existing kernels that support ext4 lagfixes. It's tested on a ULFK kernel (SpeedMod).
WARNING: Turning off journaling makes your data more susceptible to getting corrupted, although the risk is small.
Disclaimer: No promises that this will work for you, or that it won't corrupt your data. Try this at your own risk.
Step 0: You start off by applying an ext4 lagfix. If you are already using an ext4 lagfix, you can skip this step.
For ULFK kernels, this is either:
- "Voodoo" ext4 /data
- No-RFS advanced ext4
After the lagfix has been successfully applied and your phone is up and running properly, then you can proceed to convert the ext4 partitions.
Step 1: Make a backup of your data, using CWM (recommended). If anything goes wrong, you can restore the backup later.
Step 2: Download the tune2fs file attached to this post (works for FROYO roms only), and copy it to /data as /data/tune2fs:
adb push tune2fs /sdcard/
adb shell
# su
# cp /sdcard/tune2fs /data/
Procedure if your kernel has ro.debuggable enabled:
Step 3: If your kernel has ro.debuggable enabled, then boot your phone into recovery mode. Then run adb in root mode:
adb root
(wait for adbd to restart)
adb shell
Copy tune2fs to the /tmp folder.
# cp /data/tune2fs /tmp/
If you don't have ro.debuggable enabled, "adb root" will give you an error. Go to Step 3A in the next section.
Step 4: Now in ADB shell, find out which partitions are ext4:
# mount | grep ext4
mount | grep ext4
/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl10 on /dbdata type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl11 on /cache type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
In this example, the 3 partitions are:
/dev/block/mmcblk0p2 (/data)
/dev/block/stl10 (/dbdata)
/dev/block/stl11 (/cache)
Repeat Steps 5 to 9 for every partition you want to remove the journal from.
The next steps show the procedure for /dev/block/mmcblk0p2 (/data).
Step 5: Unmount the partition:
umount partition_mount_point
for example:
# umount /data
Step 6: Check if there is a journal:
# /tmp/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" in the features. It means this partition has a journal.
Step 7: Fsck the partition:
# e2fsck -f /dev/block/mmcblk0p2
Step 8: Remove the journal:
# /tmp/tune2fs -O ^has_journal /dev/block/mmcblk0p2
(this is a capital "O"!)
Step 9: Check if the journal was removed:
# /tmp/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" is NOT there.
Done for this partition.
Step 10: After you've remove the journal from all the partitions you wanted to, shutdown the phone by pressing the power button.
DONE. You only need to do this procedure once and it'll "stick" until the next time you re-format the partition.
--------------------------------------------------
Procedure if you don't have ro.debuggable enabled:
Step 3A: If you kernel does not have ro.debuggable enabled, then you can try doing this using normal adb with su while the phone is running. But this is much more risky.
To lower the risk, do this right after booting, wait for the Media Scan to complete.
adb shell
# su
Step 4A: Now in ADB shell, find out which partitions are ext4:
# mount | grep ext4
mount | grep ext4
/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl10 on /dbdata type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl11 on /cache type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
In this example, the 3 partitions are:
/dev/block/mmcblk0p2 (/data)
/dev/block/stl10 (/dbdata)
/dev/block/stl11 (/cache)
Repeat Steps 5A to 8A for every partition you want to remove the journal from.
The next steps show the procedure for /dev/block/mmcblk0p2 (/data).
Step 5A: Check if there is a journal:
# /data/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" in the features. It means this partition has a journal.
Step 6A: Fsck the partition:
# e2fsck -f /dev/block/mmcblk0p2
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)?
Answer yes.
Step 7A: Remove the journal:
# /data/tune2fs -O ^has_journal /dev/block/mmcblk0p2
(this is a capital "O"!)
Step 8A: Check if the journal was removed:
# /data/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" is NOT there.
Done for this partition.
Step 9A: After you've remove the journal from all the partitions you wanted to, shutdown the phone by pressing the power button. Reboot the phone and hope everything works.
DONE. You only need to do this procedure once and it'll "stick" until the next time you re-format the partition.

Nice one!
Going to try this tomorrow!
__________________________
Device: GT-I9000 16GB
Rom: Doc's V8 Nude&Raw v3
Kernel: Hardcore's Speedmod K9A - 500 Hz
Modem: JPP
Lagfix: No RFS, ext4-ext2, no binds
Tweaks: I/O Sched, Kernel VM Management, Kernel sched

Please ignore.

danzgrace said:
http://www.mjmwired.net/kernel/Documentation/filesystems/ext4.txt#364
Data Mode
=========
There are 3 different data modes:
* writeback mode
In data=writeback mode, ext4 does not journal data at all. This mode provides a similar level of journaling as that of XFS, JFS, and ReiserFS in its default mode - metadata journaling. A crash+recovery can cause incorrect data to appear in files which were written shortly before the crash. This mode will typically provide the best ext4 performance.
* ordered mode
In data=ordered mode, ext4 only officially journals metadata, but it logically groups metadata information related to data changes with the data blocks into a single unit called a transaction. When it's time to write the new metadata out to disk, the associated data blocks are written first. In general,
this mode performs slightly slower than writeback but significantly faster than journal mode.
* journal mode
data=journal mode provides full data and metadata journaling. All new data is written to the journal first, and then to its final location.
In the event of a crash, the journal can be replayed, bringing both data and metadata into a consistent state. This mode is the slowest except when data needs to be read from and written to disk at the same time where it outperforms all others modes. Currently ext4 does not have delayed allocation support if this data journalling mode is selected.
Click to expand...
Click to collapse
Applying writeback mode is the best option.

danzgrace said:
Applying writeback mode is the best option.
Click to expand...
Click to collapse
Hi danzgrace. Those options you quoted are for journaled modes. data=writeback is still a journaled mode.
This procedure is for non-journaled mode (none of the above). Its faster than all of the above because there is *no* journal.

hardcore said:
Hi danzgrace. Those options you quoted are for journaled modes. data=writeback is still a journaled mode.
This procedure is for non-journaled mode (none of the above). Its faster than all of the above because there is *no* journal.
Click to expand...
Click to collapse
Yes. Just stumbled upon lots of docu about ext4 and you are right about the performance gain when there's no journal involve but kind of risky.
https://ext4.wiki.kernel.org/index.php/Ext4_Howto#.22No_Journaling.22_mode

danzgrace said:
Yes. Just stumbled upon lots of docu about ext4 and you are right about the performance gain when there's no journal involve but kind of risky.
https://ext4.wiki.kernel.org/index.php/Ext4_Howto#.22No_Journaling.22_mode
Click to expand...
Click to collapse
It should be no more risky than ext2. Been using it for a few days now and so far so good.

danzgrace said:
Yes. Just stumbled upon lots of docu about ext4 and you are right about the performance gain when there's no journal involve but kind of risky.
https://ext4.wiki.kernel.org/index.php/Ext4_Howto#.22No_Journaling.22_mode
Click to expand...
Click to collapse
But its not much more risky because writeback journal does not prevent data loss - it just removes the need of a filecheck after unclean unmounting. Data still can be lost or?
Sent from my GT-I9000 using XDA App

Can you implement this tweak in speedmod kernel?
Sent from my GT-I9000 using XDA App

IMO, keeping the journal, with the default data=ordered option, is a good safety vs. speed compromise.
However, have you tried fiddling with the commit= mount option? The default commit interval is 5 s - this could be what's detrimental to battery life (a wake every 5 seconds). Maybe upping this to 60, or even more, seconds? I myself wouldn't care if it were 5 minutes on a phone, but upping it to one minute should already show a significant battery life increase.

corgar said:
Can you implement this tweak in speedmod kernel?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Not that easy because I have to modify the recovery executable. Maybe at a later stage.

AnnihilatorSC said:
IMO, keeping the journal, with the default data=ordered option, is a good safety vs. speed compromise.
However, have you tried fiddling with the commit= mount option? The default commit interval is 5 s - this could be what's detrimental to battery life (a wake every 5 seconds). Maybe upping this to 60, or even more, seconds?
Click to expand...
Click to collapse
I'm not sure if this has any effect when there's no journal. But I guess it's worth a shot.

I hope there is a way to do this in a script and apply by update.zip in recovery. Please tell me this can be done...
In general use, just how much faster does this feel? I'm asking because regular ext4 does not feel much faster in general use than RFS using speedmod. Back when I was using JM8 + OCLF, k-9 Email was so much faster.

hardcore said:
I'm not sure if this has any effect when there's no journal. But I guess it's worth a shot.
Click to expand...
Click to collapse
It doesn't. But I aim to hang on to the journal.
You could try releasing a SpeedMod revision which mounts all ext4 fs's with commit=60. If you do, i'll be sure to report the battery life - the effect should already be obvious to me after a night on battery (I currently lose about 20% battery overnight - no-rfs advanced ext4, w/ defaults).

hardcore said:
I'm not sure if this has any effect when there's no journal. But I guess it's worth a shot.
Click to expand...
Click to collapse
I guess commit=60 or more and journal_async_commit, can save us a lot of battery power.

you can change the commit options by remounting the disk.. in adb or terminal with root..
mount -oremount,data=writeback,journal_async_commit,... /dev/block/... /data (for example)
you will lose it at phone reboot, too - but good for testing

bilboa1 said:
you can change the commit options by remounting the disk.. in adb or terminal with root..
mount -oremount,data=writeback,journal_async_commit,... /dev/block/... /data (for example)
you will lose it at phone reboot, too - but good for testing
Click to expand...
Click to collapse
not unless it was on your playlogos hack.

danzgrace said:
journal_async_commit, can save us a lot of battery power.
Click to expand...
Click to collapse
I sincerely doubt journal_async_commit would bring about better power utilization. Maybe a slight performance increase, but nothing significant. Personally, I wouldn't enable that option.

danzgrace said:
not unless it was on your playlogos hack.
Click to expand...
Click to collapse
SpeedMod and ULFK supports init scripts, without the playlogos hack.
Just name the script E_something.sh and place it in /system/etc/init.d/
For example /system/etc/init.d/E_startup.sh

hardcore said:
SpeedMod and ULFK supports init scripts, without the playlogos hack.
Just name the script E_something.sh and place it in /system/etc/init.d/
For example /system/etc/init.d/E_startup.sh
Click to expand...
Click to collapse
Thanks for the info. imho. I feel more safe putting the script on /data partition so if it fails I just factory reset rather than putting it on /system dir.

[Q] Can someone help with "out of memory"?

After several random unexpected reboots CWM titanium SU and several other apps force close and / or won't even open, wireless tether disappeared, couldn't boot into recovery at all. pulled battery (several times) and had to reboot to recovery in adb then able to restore a backup still no wirelss tether and random fc's. Now I can't install any apps from sd card.
Read and tried several othe posts and scoured the nets a bit.... there should be plenty of room and apps can install from market but "insufficient memory" from sdcard???
export PATH=/data/local/bin:$PATH
$ $ su
# busybox df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 155188 0 155188 0% /dev
df: /mnt/.lfs: Function not implemented
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
tmpfs 155188 0 155188 0% /mnt/asec
/dev/block/stl9 257872 219300 38572 85% /system
/dev/block/stl10 496440 89756 406684 18% /data
/dev/block/stl11 167120 99396 67724 59% /cache
/dev/block/stl11 167120 99396 67724 59% /data/dalvik-cache
/dev/block/vold/179:1
15443968 11224512 4219456 73% /mnt/sdcard
/dev/block/vold/179:1
15443968 11224512 4219456 73% /mnt/secure/asec
/dev/block/dm-0 16612 14484 2128 87% /mnt/asec/com.rovio.angrybirds-1
#
Sent from my Twin Jets EPIC using XDA App

Ok after more work, I used terminal emulator /cd/sdcard/download method to install to system/app then titanium to uninstall from system directory. After that I had no issues using es file explorer to find and install wireless tether.
Still would like to hear any ideas as another side effect of whatever happened is I can no longer use three finger method to boot recovery..... and that scares me a bit
Sent from my Twin Jets EPIC using XDA App

Not enough free space when installing applications from play store on ICS with a2sd

I have just discovered how to fix a problem of insufficient space when you have a device with low internal storage running ICS and a2sd or similar and I thought I would share it with you as I could not find the answer online.
So the old way of creating a symlink from /cache/download would not work and anyway I have my cache on a2sd so it looks like the play store moved it's download location so I poked around to find that the play store now stores downloads at /data/data/com.android.providers.downloads/cache (I don't have my /data/data on sd as I find it unstable).
So all we need to do is link somewhere ie /cache/download to /data/data/com.android.providers.downloads/cache. In your favorite terminal emulator / ssh / other method
Code:
rm -r /data/data/com.android.providers.downloads/cache
mkdir /cache/download
ln -s /cache/download /data/data/com.android.providers.downloads/cache
hope that helps somebody

I was forever having problems with low storage on my old wildfire but now have a sensation. Will try this on the missus phone though.
Thanks
Sent from my HTC using xda app-developers app

Insufficient Storage
Thanks for your post, this is the closest thing I've found to a solution, but I'm not a developer and I'm having this issue with my newly rooted Samsung S3 (AT&T). I used this file: TeamEpic-Root-from-Recovery-v5 with Odin V 3.04.
Is there any way you could either help me fix this or point me in the right direction?? Please?
Bazzawill said:
I have just discovered how to fix a problem of insufficient space when you have a device with low internal storage running ICS and a2sd or similar and I thought I would share it with you as I could not find the answer online.
So the old way of creating a symlink from /cache/download would not work and anyway I have my cache on a2sd so it looks like the play store moved it's download location so I poked around to find that the play store now stores downloads at /data/data/com.android.providers.downloads/cache (I don't have my /data/data on sd as I find it unstable).
So all we need to do is link somewhere ie /cache/download to /data/data/com.android.providers.downloads/cache. In your favorite terminal emulator / ssh / other method
Code:
rm -r /data/data/com.android.providers.downloads/cache
mkdir /cache/download
ln -s /cache/download /data/data/com.android.providers.downloads/cache
hope that helps somebody
Click to expand...
Click to collapse

ROM?
DreamingWillow said:
Thanks for your post, this is the closest thing I've found to a solution, but I'm not a developer and I'm having this issue with my newly rooted Samsung S3 (AT&T). I used this file: TeamEpic-Root-from-Recovery-v5 with Odin V 3.04.
Is there any way you could either help me fix this or point me in the right direction?? Please?
Click to expand...
Click to collapse
Ssounds like you have rooted properly, but your ROM along with any Kernel mods or tweaks is the key. Clear caches and data from GP also.
Search the forums because a lot of people have had this issue, me included.
One application is "Marketfix", works for some people....

Fly-n-High said:
Ssounds like you have rooted properly, but your ROM along with any Kernel mods or tweaks is the key. Clear caches and data from GP also.
Search the forums because a lot of people have had this issue, me included.
One application is "Marketfix", works for some people....
Click to expand...
Click to collapse
Yeah, it rooted just fine, that was easy! (Did it before on my Captivate). Thanks for the suggestion on the Market!! Hopefully, I can get that going today....it's a challenge because I can't download the app from the market because I get the error of "insufficient storage available".....I'm going to try a few things...I've already cleared cache and uninstalled several apps with the same result. The last thing I can think of to do is wipe it clean and try to install that app first. If that doesn't work....well I'm not sure what to do. I'll keep you posted. Thanks again for your help.

got it!
Hi,
Thank you so much for your help and to everyone who makes these things easy for those who have no idea what the hell they are doing (like me!)
The "marketfix" app worked great!

sandvold ics 0.15, htc desire, data++, a2sd
i tried the script. it doesn't solve the problem. the rom continues to delete the dir /cache/download and after a reboot i had a system.media continous crash. needed to restore a nandroid to solve the problem
so, because on the htc desire with data++ table, cache partion is only 5MB, i changed the script:
rm -r /data/data/com.android.providers.downloads/cache
mkdir /sd-ext/download
ln -s /sd-ext/download /data/data/com.android.providers.downloads/cache
it seems to work, but i need some more testing.

I have HTC Desire with JB 4.1.2 from vijendrahs, stock hboot, a2sd (y,n,y).
This are my FSs:
Code:
[email protected]:/ # df
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 207072 48 207024 0% /dev
tmpfs 207072 0 207072 0% /mnt/asec
tmpfs 207072 0 207072 0% /mnt/obb
/dev/block/mtdblock3 256000 232636 23364 91% /system
/dev/block/mtdblock5 151168 129920 21248 86% /data
/dev/block/mtdblock4 40960 1304 39656 3% /cache
/dev/block/mmcblk0p2 1548096 540404 1007692 35% /sd-ext
/dev/block/mmcblk0p2 1548096 540404 1007692 35% /data/app
/dev/block/mmcblk0p2 1548096 540404 1007692 35% /data/app-private
/dev/block/mmcblk0p2 1548096 540404 1007692 35% /data/app-asec
/dev/block/mmcblk0p2 1548096 540404 1007692 35% /data/dalvik-cache
/dev/block/dm-0 13316 11096 2220 83% /mnt/asec/com.touchtype.swiftkey-2
/dev/block/vold/179:1 6252544 1440464 4812080 23% /storage/sdcard0
/dev/block/vold/179:1 6252544 1440464 4812080 23% /mnt/secure/asec
/dev/block/dm-1 18428 17064 1364 93% /mnt/asec/se.maginteractive.rumble.free-2
/dev/block/dm-2 8196 6216 1980 76% /mnt/asec/com.google.android.apps.currents-2
/dev/block/dm-3 14340 12656 1684 88% /mnt/asec/com.djinnworks.linerunnerfree-2
/dev/block/dm-4 5128 3248 1880 63% /mnt/asec/com.quoord.tapatalkxda.activity-1
I did the link of cache directory: ln -s /sd-ext/download /data/data/com.android.providers.downloads/cache
The problem of upgrade for Whatsapp and Facebook still remain for insufficient space. Anyone can help me?
Edit: just update Google Play Book, 5,95MB, without problems

I FOUND A FIX I FOUND A FIX !!!!
for those of you who are using a nexus or something or any other phone on which clearing dalvik cache etc doesnt work try this..
go to this location /data and find app-lib
this folder has a total storage of 6.62 GB (on my phone)
find any unwated folders and your done
i had installed MC4 and when i uninstalled it com.gameloft ..whatever was still in this folder and it was consuming a lot of staorage so when i cleared it up all updates and installs were working

I'm an idiot
Damn...
I had this issue and didn't even have enough space to download the marketfix thing, but then i hit me, that I had just changed the Apps2SD through ROM Toolbox to sd card and that was causing the problem cause i haven't formatted my SD card yet.
That fixed the issue for me.

thanx

Have you guys tried Link2SD? It is able to link everything to a 2nd partition on your SD card. Has saved me tons of frustration and memory!

how to install apps on system / app on android 10 OOS10?

after upgrading to OOS 10 I can no longer install an application on / system, whenever I restart the device the folders disappear, how can I fix this?

Gleivisson said:
after upgrading to OOS 10 I can no longer install an application on / system, whenever I restart the device the folders disappear, how can I fix this?
Click to expand...
Click to collapse
Which method and/or software do you use to install? Perhaps it is not aware of system partition no longer being mounted on /system for 10. Also, there us not vary much room left in /
Code:
[email protected]:~# cd /system
[email protected]:system# df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/dm-0 3047900 2838328 193188 94% /

Dior DNA said:
Which method and/or software do you use to install? Perhaps it is not aware of system partition no longer being mounted on /system for 10. Also, there us not vary much room left in /
Code:
[email protected]:~# cd /system
[email protected]:system# df -k .
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/dm-0 3047900 2838328 193188 94% /
Click to expand...
Click to collapse
I would like to install an anti-theft application on the system

Gleivisson said:
I would like to install an anti-theft application on the system
Click to expand...
Click to collapse
can you be more precise about which application
also, have you rooted OOS 10?
good luck !