• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Splash Screen

GingaB said:
Cool. Whats the difference between your version and ones on the alpharev site?? Apart from the more obvious what else yu gain out of this? Im unfamiliar with this stufff at the moment.
Click to expand...

No this is nothing to do whith Alpharev Hboot Pre-defined Partition layouts.

This is a custom layout where YOU define the partion layouts. Nothing to do with Hboot. Everything on the alpharev site is completely different to this.
 
Can be. I use the clockwork version (as I use clockwork). /298MB data ;)

I dont even need a2sd, but I keep it anyway.
 
I got Cordy installed w/o changing my cache size by changing app install location to be automatic instead of internal, then moving the app back to 'phone' afterwards and resetting the location as internal. No problems so far, and I've done this a couple times for updating Angry Birds as well. Do either of you (Rasta or Dan) foresee a problem arising from doing it like that?

EDIT: Scratch that, just realized I had installed Cordy when it first came out while it was still smaller than 25 MB. Haven't tried updating it till now and it doesn't work. The above question still holds for A.B. though.
 
ive never tested that method although i never had a problem with AB with a 25 cache

im not sure how the install location would make a difference at this stage as cache is a "temp" directory use by market to store the apk while it installs it and to cache data while running the game itself

it would still need to use this location even if you changed the install location
 
Oh the /cache space is literally just for install, not running it?

I've been wondering if its worth a symlink from cache to ext recently, so this would be an excuse to try it.
 
SUroot said:
Oh the /cache space is literally just for install, not running it?

I've been wondering if its worth a symlink from cache to ext recently, so this would be an excuse to try it.
Click to expand...

i actually typed that and deleted it in the post above but then the thought of it is pointless as you would still need a partition to symlink which would make the purpose of it pointless

I do believe its for running it too but its maily used by market as a temp location

EDIT: unless you did it as a loop back so you have a tiny physical cache partition but a 50mb ext loop back ala data2sd
 
Rastaman-FB said:
i actually typed that and deleted it in the post above but then the thought of it is pointless as you would still need a partition to symlink which would make the purpose of it pointless

I do believe its for running it too but its maily used by market as a temp location

EDIT: unless you did it as a loop back so you have a tiny physical cache partition but a 50mb ext loop back ala data2sd
Click to expand...


Yes, not thinking of doing away with the partition all together. Also I havent thought about the logistics of it yet, but I assume all that would be needed is a directory within sd-ext and symlink /cache contents there. CM does this to get around stupid cache size on hboot.
 
Rastaman-FB said:
ive never tested that method although i never had a problem with AB with a 25 cache

im not sure how the install location would make a difference at this stage as cache is a "temp" directory use by market to store the apk while it installs it and to cache data while running the game itself

it would still need to use this location even if you changed the install location
Click to expand...

I realised afterwards that I was mixing up two separate issues I've experienced:
1) With my 25MB cache, certain apps (like A.B.) have errored out and not finished downloading unless I switched install location to auto. I thought that maybe they were coded to install to sd (fat) by default and the system setting of an internal location was conflicting, but if you've not had similar problems I'm not so sure.

2) As my setup currently stands, an app that's got an apk bigger than the cache partition can't install. This can possibly be overcome by symlinking /cache to a bigger location somewhere else, as you two have just been talking about. I'd be interested to find out if/how that works, though I'll have to do some more reading to understand it as I'm a bit lost at this point.
 
Staggers said:
I realised afterwards that I was mixing up two separate issues I've experienced:
1) With my 25MB cache, certain apps (like A.B.) have errored out and not finished downloading unless I switched install location to auto. I thought that maybe they were coded to install to sd (fat) by default and the system setting of an internal location was conflicting, but if you've not had similar problems I'm not so sure.

2) As my setup currently stands, an app that's got an apk bigger than the cache partition can't install. This can possibly be overcome by symlinking /cache to a bigger location somewhere else, as you two have just been talking about. I'd be interested to find out if/how that works, though I'll have to do some more reading to understand it as I'm a bit lost at this point.
Click to expand...

I will look for or frankenstein a solution and test it to let you know.
 
still though simlinking is a bit wierd if you just symlink like a2sd then it will probably go by the physical cache size and not the hidden sd-ext size (im only guessing)
so in order to get around it you would have to make a cache2sd/cache2whatever solution using loopback. this wouldnt be a problem as its temp anyway so a dirty shutdown wouldnt cause any problems
 
Found some commands online so I sent them to droidzone. He sent me loads of helpful commands in order.

I applied them and it worked sort of. QSI reported cache as 1.01 GB and Cordy downloaded fine.

Still needs some work as because I have a2sd, the mounting seemed to conflict (one at a time only maybe?) so on install, installer got force close.

I hadnt added it to init.d (only Terminal) so reboot cleared, went to sd-ext/cache and managed to install the downloaded apk manually.
 
SUroot said:
Found some commands online so I sent them to droidzone. He sent me loads of helpful commands in order.

I applied them and it worked sort of. QSI reported cache as 1.01 GB and Cordy downloaded fine.

Still needs some work as because I have a2sd, the mounting seemed to conflict (one at a time only maybe?) so on install, installer got force close.

I hadnt added it to init.d (only Terminal) so reboot cleared, went to sd-ext/cache and managed to install the downloaded apk manually.
Click to expand...

lol you just created an auto app backup lol
im guessing it doesnt auto clear the data from sd-ext/cache
 
Rastaman-FB said:
lol you just created an auto app backup lol
im guessing it doesnt auto clear the data from sd-ext/cache
Click to expand...


Hahah yeah. No sd-ext/cache is just a folder which remains in tact after reboot.



If you manually create sd-ext/cache using Root explorer,

All you need to do in terminal emulator is:

Code: 
busybox mount -o noatime,nodiratime -t auto /dev/block/mmcblk0p2 /system/sd
Then

Code: 
/system/xbin/busybox mount -o rw,nodev,noatime,nodiratime /system/sd/cache /cache
Code courtesy of Droidzone. Although his method involved some recovery work to delete the cache and create the folder. But if its just temp for download....

Above code, download app, reboot to go back to true /cache. Install app via r.e
 
I'm also investigating the possibility of 100MB loop file in EXT (didnt get very far) and second EXT partition (although teh above would be better to share the same partition) but cannot work out how to get it to see mmcblk0p3 as a mount point yet :(

Ownhere uses multiple ext partitions in his data2ext so enlisting his help too.
 
You must log in or register to reply here.
Back
Top Bottom