yashsingh1/xdaforums huggingface dataset:
[Nook Color General] Ravynmagi:
I'm having this problem with Firefox too. I've uninstalled and reinstalled Flash via Titanium Backup (this actually worked with Firefox on my Android phone), but Firefox still won't play Flash, acts like Flash isn't installed. The default browser does play Flash though.

Any other tricks other than uninstalling and reinstalling Flash? Firefox doesn't seem to have an option to change the agent.
[Nook Color General] JdgM3NT4L:
Grab the Flash 10.2 that's floating around the forums. It is working great on my NC with the Customized Nookie Froyo 0.6.8.

Flash download

Stolen from the XDA XOOM forum. Original Thread Here

Thanks to XDA Members frankic for the original post and to Blades for following up with a working linky. If that link goes bad try the link to the XOOM forum.

Hulu even works somewhat ok (DolphinHD) after a little tweaking...
[EVO 4G Q&A, Help & Troubleshooting] oranium:
I'm using Ra 1.8 & did a nand back up today but I can't find the file anywhere .

Anyone ?

Can I change the file name to what ever I want ? That way I know what's what ?

Sent From One BadAss Evo On Myn's Warm 2.2 Rls 5 Steroids Via XDA App. ;-)
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
The file should be in a folder in the sdcard called nandroid. If you mount the phone to the pc, you can go into the same folder and rename it, just no spaces; periods, hyphens, and underscores are fine though.
[EVO 4G Q&A, Help & Troubleshooting] oranium:
I think I got screwed :(

I made a partition to my SD card & lost all info on it .

What can I do to restore it ?

Sent From One BadAss Evo On Myn's Warm 2.2 Rls 5 Steroids Via XDA App. ;-)
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Naw man, you're outta luck. Once you partition the sdcard, all the info is wiped,a nd if not backed up gone for good.
[EVO 4G Q&A, Help & Troubleshooting] sekigah84:
What he said. lol

But yeah as rox said. Nandroid folder on your SD Card. Rename the files, and pull off the ones you aren't going to use since they are massive backups (600MB ish).
[EVO 4G Q&A, Help & Troubleshooting] oranium:
Nooooooooooo I hate this **** , damn this

Thx for the reply though

Sent From One BadAss Evo On Myn's Warm 2.2 Rls 5 Steroids Via XDA App. ;-)
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Its happened to me once...so just in the future, backup the sdcard before you partion...it happens to all of us.
[EVO 4G Q&A, Help & Troubleshooting] oranium:
I will definitely going to copy my SD card to my pc after this B.S ;-)

Sux ass I gotta dl a lot of apps, ringtones ... again

BTW What's the best way to back up my SD ?

Sent From One BadAss Evo On Myn's Warm 2.2 Rls 5 Steroids Via XDA App. ;-)
[EVO 4G Q&A, Help & Troubleshooting] teh roxxorz:
Yea, unfortunately you do. And the best way is to mount to the pc, then copy and paste to a folder on your pc.
[EVO 4G Q&A, Help & Troubleshooting] Just_s:
You should definitely be using Titanium Backup so that you aren't constantly downloading all your apps from scratch every time. Also as soon as you have a good nandroid that you like, I would copy it to your pc. Sync Toy is an excellent free program to copy your SD to your pc.

Also, I know most people on XDA love Amon, but if you use ROM Manager with Clockwork it will be much simpler to name your backups as you wish right from the start. I also keep a PC36IMG.zip of AmonRA 2.3 on my SD which can easily be flashed by going into hboot (power+vol down) anytime I want the extra oomph of RA rather than CW.

If you happen to be running MIUI, you can also use the native backup to take a snapshot of most everything (not widgets, but pretty much everything else.) I think there might be other ROMs with built-in backup, but others will have to chime in for that.

Good luck, hope it doesn't happen to you again.
[EVO 4G Q&A, Help & Troubleshooting] BigJohn89:
If you haven't written to the SD card yet, you may be in luck. Google SD Card recovery, this happens quite a bit to people who accidentally format their digital camera cards. Believe it or not, formatting digital memory devices (SSDs, USB sticks, CF and SD cards, etc) actually removes very little data - most if it is usually quite recoverable (if the device has not been written to)...

BigJohn
[EVO 4G Q&A, Help & Troubleshooting] oranium:
Thx Bigjohn89 ;-)

What Sux ass is that I was impatient & had to bring all back to the way it was before so since last night my phone is working over time ;-)

But that's a good thing to know if I ever screw up again witch I don't think I will ;-)

Sent From One BadAss Evo On Myn's Warm 2.2 Rls 5 Steroids Via XDA App. ;-)
[Desire Android Development] SiL3nTKiLL:
very nice tut :)
[Desire Android Development] grooltor:
Everything went well for me on Cool Z v8 A2SD, thanks a lot!

Only one thing: you should edit the 2nd post just before the section I'm quoting, adding "adb shell mount /data" and "adb shell mount /sd-ext" before trying to move dalvik back to NAND, otherwise it won't work ;)
[Desire Android Development] nerdo:
Amazing.... just when you think thought of it all... a new bright idea pops up :D

Nicely done mate ;)
[Desire Android Development] ciukacz:
nice idea, if i understand this correctly this looks like something that could help with sd speeds.

because currently even a fast sd card with a2sd/data2sd/data2ext chokes when /sd-ext/dalvik is read and /sdcard being written to.

is that about right ?
[Desire Android Development] ClassicalDude:
@grooltor - thanks. I fixed it. I have a few more additions that will be incorporated soon, such as coolexe's idea to increase the cache partition.

@nerdo - thanks. Like all good ideas, it came in the shower.

@ciukacz - that's the idea, and it is working indeed. You can check out the rom I posted, or the newest iNsertCoin rom, which is based on this method. Every rom, including HD and Z roms, runs smoothly this way.
[Desire Android Development] GuestK0083:
Anyone tested this guide on Leedroid 2.3d? I'd do it, but i am currently overwhelmed by my final exams...
[Desire Android Development] ClassicalDude:
Worked perfectly on modaco r10. See no reason why it should not work on LeeDroid.
[Desire Android Development] danarama:
so this is basically a way of trimming up /system by relocating it and symlinking so you can reallocate the space using an alpharev table / Custom mtd layout?

Suppose for sense roms, that makes sense (forgive the pun). Cool
[Desire Android Development] ciukacz:
@ClassicalDude: thanks for the reply, i will definitely try that and post back.

however i am fairly new to all things android and need to read up before i try.
[Desire Android Development] wollyka:
Will try that on Al-Maisan ROM (Arabic version of Starburst) tomorrow and see how it will go.
[Desire Android Development] mexxxico:
I have a problem with Titanium backup... wan't have a download a busybox.
[Desire Android Development] ClassicalDude:
I did not encounter this problem, so I cannot help. Like it is said in the beginning of this thread - this process is for very advanced users, who know what they are doing, and who can google their way to a solution to such problems, or figure it out themselves. I will help as much as I can, but I will not do the research for you.
[Desire Android Development] ClassicalDude:
Thanks to baadnewz and coolexe, I added a section called "Fixing market downloads" to the first post. It's a very elegant way of placing market downloads into a temporary ram disk, which self-deletes after the app is installed.
[Desire Android Development] mexxxico:
ok,tnx. I'll tray to find a solution

swyped from my HTC Desire using XDA Premium App
[Desire Android Development] wollyka:
Just to report it works on Al-Maisan. (with modified boot.img for market fix too)

Thanks for the tut
[Desire Android Development] GuestK0083:
I've just tried this guide on Leedroid 2.3d, here's my experience:

After sticking closely to the Guide in the 2nd post, i am getting LOADS of FCs as i boot up the device. Sense crashes, the IME crashes...everything fcs immediately.

I analysed everything but i've entered the correct commands...

So maybe the integrated A2SD script is the problem? I've cleaned it from all content saying "app-private" and "dalvik cache", as advised in the 2nd post.

#!/system/bin/sh
#
# Apps2SD using symlinks and bind mounts
# shade@chemlab.org (cyanogen)
# Adapted by Teknologist

#Removed this as there is no /etc/sysctl.conf as of now in MCR
/system/bin/strt

# execute any postinstall script then kill it
if [ -e /dev/block/mmcblk0p2 ];
then

# mount and set perms
busybox mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sd;
busybox chown 1000:1000 /system/sd;
busybox chmod 771 /system/sd;

# clean up any old symlinks, create data directories
for i in data;
do
if [ -h /data/$i ];
then
rm /data/$i;
fi;
if [ ! -d /data/$i ];
then
mkdir /data/$i;
busybox chown 1000:1000 /data/$i;
busybox chmod 771 /data/$i;
fi;
done;

# don't allow /data/data on sd because of upgrade issues - move it if possible
if [ -d /system/sd/data ];
then
busybox cp -a /system/sd/data/* /data/data/;
busybox rm -rf /system/sd/data;
fi;

# move apps from internal memory to sdcard
for i in app;
do
if [ ! -d /system/sd/$i ];
then
mkdir /system/sd/$i;
fi

busybox chown 1000:1000 /system/sd/$i;
busybox chmod 771 /system/sd/$i

if [ -d /data/$i ] && [ ! -h /data/$i ];
then
busybox cp -a /data/$i/* /system/sd/$i/;
busybox rm -f /data/$i/*;
fi;
done;

# symlink app dirs - they must be on the same filesystem
for i in app;
do
if [ -d /data/$i ] && [ ! -h /data/$i ];
then
busybox rm -rf /data/$i;
busybox ln -s /system/sd/$i /data/$i;
fi;
done;

# clean up old whiteouts
for i in local misc property system tombstones data;
do
if [ -h /system/sd/$i ]; then rm -f /system/sd/$i; fi
done;

# please don't put odex files in the app directory people!
# it causes dexopt to crash when switching builds!
busybox rm -f /system/sd/app/*.odex

setprop cm.a2sd.active 1;

echo "+++ Apps-to-SD successfully enabled";

else

# replace symlinks with directories so we can boot without sd
for i in app;
do
if [ -h /data/$i ];
then
rm -f /data/$i;
mkdir /data/$i;
busybox chown 1000:1000 /data/$i;
busybox chmod 771 /data/$i;
fi;
done;

setprop cm.a2sd.active 0;
fi;

sync;
[Desire Android Development] ClassicalDude:
Your a2sd script is fine. Probably some other small thing you did not notice.
[Desire Android Development] kluzik1:
how much internal memory would I have on cool z v8 after applying all those steps? :)
[Desire Android Development] ClassicalDude:
Why don't you back up, try, and let everyone know?

EDIT: Actually, no. I take it back. Please don't be offended, but a user who asks such a question is probably a user who is not experienced enough to go through this procedure in the first place. I am only giving a fair warning - don't expect support if things don't work out.
[Desire Android Development] kluzik1:
I'm not offended ;) just curious :) I've checked already 160 with moving dalvik cache and 246 leaving dalvik cache on ext ;) will try to test both of them and see :)

Thank you for this amazing tutorial :)
[Desire Android Development] ClassicalDude:
Very welcome! I was simply a little taken aback, because most of the time questions that start with "will that work on..." etc. tend to mean a lot of frustration when I try to help the asker.

I am glad you found out and posted your findings. Mind you, the significant improvement in performance and battery life only happens when the dalvik-cache is on the internal data partition.
[Desire Android Development] kluzik1:
Yes I've noticed tested both versions. Performance is as good or even better than the original stock sense for desire. After restoring like 70 apps dalvik located in inernal memory I still have 40 mb which is not good but considering this performance and don't need much more apps and having on board smooth dhd I'll say one more time thank you :)

Beside I always read first and look for informations rather than ask stupid or obvious questions ;)
[Desire Android Development] robocik:
trying to make the process of customizing the MTD as easy as possible...

I want it to be like, one zip which customizes the MTD table and second zip is the rom... still need to test it a bit, but need my phone now.
[Desire Android Development] ClassicalDude:
Robocik, think carefully before you do that! I understand the urge to try and make the process as user-friendly as possible, but no matter how tight you think your implementation is, there always will be users who manage to screw it up and then blame you and expect free support. I have had way too much experience with it with my RTL script.

Only this time it will not be a matter of restoring a nand backup. If the mtd table is messed up, a new user will not be able to dig himself (or herself) out of that hole.

That is why I specifically avoided scripting this solution.
[Desire Android Development] Archont:
I have tried it with an installed Cool Z v8 and 512MB ext4 partition on a class 4 Kingston 8GB microSD and it is working fine.

It took about half an hour (already did S-off and partitioned microSD before) and the ROM seems to respond quicker now.

edit: rebuilding dalvik-cache takes about 1/3 the time it took when using the microSD for it!

Thank you very much!
[Desire Android Development] lvnatic:
Can anyone confirm this is working for leedroid 2.3d? I've only seen one post complaining about it. Also, I don't see how oxygen hboot would work with Sense ROMs, as stated in the tutorial. Oxygen hboot has 90mb while Sense ROMs have at least 180mb.
[Desire Android Development] ClassicalDude:
Errr... Pal, you missed the whole point of the tutorial. It is about how to fit an entire sense rom into an oxygen hboot, and the tremendous gains it will give to the internal free space and the battery life. If this much was not clear to you from reading it, I think it is probably a good idea if you stick, for the time being, to the good ol' a2sd and data2***.
[Desire Android Development] lvnatic:
Ok, sorry, I may be missing the point indeed, but I simply can't see how could you fit a Sense ROM which is minimum of 150mb, into a 90mb hboot. Maybe I don't know how this thing works tho...

Edit: Ok, ok ok ok I got it, sorry for the noob questions. I only have 1 more question please, and sorry for asking it here tho it may not be the best place. If I simply change the hboot, say bravo sense (180MB), can I just flash a normal Sense ROM (i.e. leedroid 2.3d) without changing anything? I would have 70 more MB, and I would be running the dalvik-cache from the internal memory (I will completely delete the A2SD+ script from init.d and I will only use the stock froyo app2sd). Will that work, or the ROM has to be especially optimized for these hboots?
[Desire Android Development] :
lvnatic, this is not possible i guess.

The guide states, that you have to move some parts of the /system partition to /sd-ext to shrink /system. Afterwards, it will fit into the data++ or even the cm7 partition layout.

The idea behind this guide is not to give you "more" free space, but to keep the parts, which the android system has to access often and quickly (like the dalvik cache), on the internal memory, which is significantly faster than your sd card.

However, i can't get it to work with leedroid 2.3d.

After i move and symlink all the important files and switch to data++ hboot, everything runs fine for about 5 minutes, then the phone reboots.

If i move the dalivk cache back to nand, i am getting a bunch of FC's...i had to revert the stock hboot and restore my original nandroid backup...

This is the 3rd time i tried this guide, always looking for errors and mistakes, but it did not work...

I have tried it a 4th time!

My adb logcat is VERY long. You find it here, labeled ADB logcat.zip!

It seems like if there is a problem with the dalvik cache. Leedroid adds an init.d script named 02dalvikcache to init.d, that moves the cache from /data to /cache. it does not matter if i delete this script, move the dalvik to data or leave it on /cache...everytime i get a bunch of FC's...

Please...someone could take a look into my zip file...maybe this will help some other people trying to fit LeeDroid 2.3d into a data++ hboot...
[Desire Android Development] foobar66:
I have used this now for 2 weeks and ... fantastic.

So far, this is the best combination. I have tried so many different combinations of kernels, IO schedulers, Data/app/2SD with different ROMs (Sense and Sense HD). All of them showing various types of lags. Especially data2sd is really *evil* from my experience.

My current setup is modified stock Froyo (with init.d), custom compiled kernel starting from Richard Tripp's sources with some patches, only apps (.apk files) on SD. Everything else running from internal memory. Using NOOP scheduler for IO.

Some optimizations through /etc/init.d/

SCHEDULER=noop
echo $SCHEDULER > /sys/block/mtdblock3/queue/scheduler
echo $SCHEDULER > /sys/block/mtdblock4/queue/scheduler
echo $SCHEDULER > /sys/block/mtdblock5/queue/scheduler
echo $SCHEDULER > /sys/block/mmcblk0/queue/scheduler
echo 1 > /sys/block/mmcblk0/queue/rotational
for i in 1 2 3 4 5
do
echo 0 > /sys/block/mtdblock$i/queue/rotational
done
sync
echo "3" > /proc/sys/vm/drop_caches
echo "1536,3072,4096,51200,57600,64000" > /sys/module/lowmemorykiller/parameters/minfree
mount -o remount,nodev,noatime,nodiratime /dev/block/mtdblock3 /system
mount -o remount,nodev,noatime,nodiratime /dev/block/mtdblock5 /data
setprop dalvik.vm.execution-mode int:fast
echo 128 > /sys/block/mmcblk0/queue/read_ahead_kb

And with dalvik cache set to 64m (in build.prop).

Also I am using some changes through sysctl:

vm.swappiness=0
vm.min_free_kbytes=4096
vm.dirty_expire_centisecs=1200
vm.oom_kill_allocating_task=1
vm.vfs_cache_pressure=50
kernel.panic_on_oops=0
kernel.tainted=0
net.ipv4.ip_forward=0
net.ipv4.conf.default.rp_filter=1
kernel.sysrq=0
kernel.core_uses_pid=1
net.ipv4.tcp_fin_timeout=30
net.ipv4.tcp_keepalive_time=1200
net.ipv4.tcp_window_scaling=0
kernel.randomize_va_space=0
net.ipv4.tcp_wmem=4096 32768 220416
net.ipv4.tcp_rmem=4095 174760 220416
net.core.rmem_max=221184
net.core.wmem_max=221184
net.core.rmem_default = 110592

Very fast, stable ... and ... no lags !!!

Thanks for the guide.
[Desire Android Development] Gramlengo:
LeeDroid 2.4 on my device (before doing ANYTHING) is 101MBs, tried the procedure and ended up with a full /system partition (90MBs on Oxygen Hboot) so I couldn't even push the 3Kbs of 40aps2sd back to the device... :\

Am I doing something wrong? O.o
[Desire Android Development] crendot:
aragornhr has made a little tut for leedroid users, here

works very wellwith lee 2.4 sense version and cm7 table
[Desire Android Development] scar45:
I'm having trouble editing init.rc within boot.img. I can extract it fine using dsixda's kitchen, make the proper edits, recreate the new boot.img file, but when I flash it back (perm or temp) using fastboot, the system refuses to boot (stays on the splash screen before the bootanimation).

I am basically trying to do this on the ROM that I've already flashed (used the LeeDrOiD 2.4 guide by Aragornhr successfully, but just can't get this Market Download workaround to...work).

Thanks in advance for any advice!
[Desire Android Development] danarama:
Has anyone got the market download fix working on aosp?

I think I have too many unknowns in my equasion.

I have AOSP, with a custom MTD layout (which patches boot).

Boot.img flashed fine and rom boots. Reduced size of cache to 5MB to test and all downloads fail. (same with a 30MB cache so its definitely pointing to the ram disk)

I replaced the code in the init.rc as recommended. I know its for advanced only, but I am working towards that one currently :)
[Desire Android Development] danarama:
Never mind. I used the premise of symlinking /system/app to symlink cache instead:

mkdir /sd-ext/cache
mv /cache/* /sd-ext/cache/
ls /sd-ext/cache/ > /tmp/cache
c=0; while read line; do array[c]=`ln -s /sd-ext/cache/"$line" /cache/`; let c=$c+1; done < /tmp/cache
[Desire Android Development] bob1369:
Bypass market problem with small cache

Found this on desire forums useful for those wanting to maximise internal storage

If the need exists i may create boot.img's for noobs for several roms with these modifications​
[Desire Android Development] grooltor:
Some ideas

Hey ClassicalDude!

I'm one of the first ones to try out your very good findings (the 4th post of this thread), and since then I always use CM7 based Sense ROMs (or CM7 itself).

During my various observations, I thought that could be a way to further improve this technique.

Is it possible to keep dalvik-cache on DATA only for system apps?

I mean: dalvik-cache should go on SD-EXT except for system apps, ending with a slow decrease in performance (user apps have their dalvik in SD-EXT), but gaining a lot of space in DATA (this is expecially good for Sense HD ROMs, apps like HTC Contacts generate a LOT of data for contacts pictures, FB feeds and so on).

Since dalvik-cache is created on boot or on installation, someone could implement a script that uses dalvik-cache on SD-EXT by default (so when you install an app its cache goes on SD-EXT), but creates and symlinks dalvik for system apps (done only during first boot) in DATA.

Do you think this is possible and could really deliver some sort of improvement?

Looking forward to hear your opinion.
[Desire Android Development] ClassicalDude:
I guess it should be possible with a script that runs only if the dalvik-cache is empty. But it will make applications run slower, and not really give us that much more space in /data. Besides, the dalvik-cache is updated, and can be deleted from the recovery - this has "unstable system" written all over it.
[Desire Android Development] grooltor:
Ok understood. Thanks :)
[Desire Android Development] erklat:
This happened to me too with AuraxTSense 8.4, so I had to change to CM7 hboot, otherwise couldn't boot. So are we supposed to use CM7 instead of Oxygen ot there is a way we could slim it a bit? Apparently it is not classified as standard Sense rom :D

Just booted and everything seems fine. How to tell if the thing is working except subjective feeling of speed? Here is the script if that helps.

#!/system/bin/sh
#
# Stuff2SD using symlinks and bind mounts

# execute any postinstall script then kill it
/system/bin/strt
if [ -e /dev/block/mmcblk0p2 ];
then

# mount and set perms
busybox mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sd;
busybox chown 1000:1000 /system/sd;
busybox chmod 771 /system/sd;

# clean up any old symlinks, create data directories
for i in data;
do
if [ -h /data/$i ];
then
rm /data/$i;
fi;
if [ ! -d /data/$i ];
then
mkdir /data/$i;
busybox chown 1000:1000 /data/$i;
busybox chmod 771 /data/$i;
fi;
done;

# don't allow /data/data on sd because of upgrade issues - move it if possible
if [ -d /system/sd/data ];
then
busybox cp -a /system/sd/data/* /data/data/;
busybox rm -rf /system/sd/data;
fi;

# move apps from internal memory to sdcard
for i in app ;
do
if [ ! -d /system/sd/$i ];
then
mkdir /system/sd/$i;
fi

busybox chown 1000:1000 /system/sd/$i;
busybox chmod 771 /system/sd/$i

if [ -d /data/$i ] && [ ! -h /data/$i ];
then
busybox cp -a /data/$i/* /system/sd/$i/;
busybox rm -f /data/$i/*;
fi;
done;

# symlink app dirs - they must be on the same filesystem
for i in app ;
do
if [ -d /data/$i ] && [ ! -h /data/$i ];
then
busybox rm -rf /data/$i;
busybox ln -s /system/sd/$i /data/$i;
fi;
done;

# clean up old whiteouts
for i in local misc property system tombstones data;
do
if [ -h /system/sd/$i ]; then rm -f /system/sd/$i; fi
done;

# please don't put odex files in the app directory people!
# it causes dexopt to crash when switching builds!
busybox rm -f /system/sd/app/*.odex

setprop cm.a2sd.active 1;

echo "+++ Apps-to-SD successfully enabled";

else

# replace symlinks with directories so we can boot without sd
for i in app ;
do
if [ -h /data/$i ];
then
rm -f /data/$i;
mkdir /data/$i;
busybox chown 1000:1000 /data/$i;
busybox chmod 771 /data/$i;
fi;
done;

setprop cm.a2sd.active 0;
fi;

sync;

Thanks for this great guide, most appreciated. I hope this has at least some impact on my battery life.