Related
Is is possible to change the root folder of the sd card used by android? I don't like having it create so many files/folders in the root of my card...
HDR said:
Is is possible to change the root folder of the sd card used by android? I don't like having it create so many files/folders in the root of my card...
Click to expand...
Click to collapse
Of course, you can place Android where ever you wish... just adjust the rel_path statement on your startup.txt.
For example, my installs are in /sdcard/Androids/TP2Ref - from Android's perspective. So in my startup.txt, I have
Code:
relpath=Androids/TP2Ref
- Just make sure that goes in the cmdline section.
Pretty sure this is in the FAQ... Try searching before you post
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
HDR said:
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
Click to expand...
Click to collapse
Only way to do that is to modify the source. I could easily make the changes in init for you, but the next time rootfs is updated (which will probably be soon since stinebd has to prep it for GB), you will lose those settings.
I'm working on some NAND stuff at the moment, so if you feel adventurous, all you have to do is modify init in rootfs and "compile" it. I have a little guide on compiling stuff (see bottom of post #1 for rootfs): http://forum.ppcgeeks.com/tp2-andro...modules-tinboot-nand-boot-more-beginners.html
I'll have a look at that, thanks.
HDR said:
My relpath is set to andboot, but Android is still creating files in / on my sd card, I want to move the media, cache, downloads directories and the FSCK001 files to a subfolder.
Click to expand...
Click to collapse
I can at least give you a easy solution for the FSCK files (no offense Nate ). Put this in the "CustomCommands" section of your froyo.user.conf:
Code:
rm -f /sdcard/*.rec
im totally agree; i dont see the point of having the possibility of choosing android to start in whatever location we want....if anyways android will keep creating files/folders in the root of our sd card.
if i recall correctly the very first releases didn't have this problem it would be great if u devs can change this behaviour by default
elamodelmerol said:
im totally agree; i dont see the point of having the possibility of choosing android to start in whatever location we want....if anyways android will keep creating files/folders in the root of our sd card.
if i recall correctly the very first releases didn't have this problem it would be great if u devs can change this behaviour for default
Click to expand...
Click to collapse
This is what Android needs by default, and where they would normally be created by the system. It's nice to stick as close to AOSP as we can, because then there's this small group of devs that work for this company 'Google' that then become our system image maintainers. Thanks.
i'm tring to make a boot animation and i have the pics as png in a folder,i have a desc, and i have signed and zipped it but when i try to install i get can't find update script. i have looked into other bootanimes and not all have that. so thats where im stuck if anyone could help me learn what i'm doing wrong that would be great. thx
Help Anyone?
dased14 said:
i'm tring to make a boot animation and i have the pics as png in a folder,i have a desc, and i have signed and zipped it but when i try to install i get can't find update script. i have looked into other bootanimes and not all have that. so thats where im stuck if anyone could help me learn what i'm doing wrong that would be great. thx
Click to expand...
Click to collapse
How are you trying to install? Did you make sure you bootanimation.zip is a storage zip?
Trying to make it flashable through recovery, and I think on 7zip I used normal, but i'll check into that after I get home.
dased14 said:
Trying to make it flashable through recovery, and I think on 7zip I used normal, but i'll check into that after I get home.
Click to expand...
Click to collapse
After creating your bootanimation -- You need to make sure that a couple things have been done correctly for the bootanimation to 1) Work and 2) Be able to be flashed via recovery.
1) To make the bootanimation work
a. Make sure that after creating the animation itself that the .zip you create has NO compression -- (e.g You use "store" mode, instead of "normal" -- both 7zip/Winrar have this feature)
b. Make sure the desc.txt file is properly formatted and has the correct folder names inside the file. Also make sure you have a carriage return (press enter) at the VERY last line of your desc.txt file
c) Make sure the .png filenames are somewhat sequential and organized. (e.g. BootUp001, BootUp002, BootUp003, etc)
2a) To make a flashable package
a. First create a folder to house the bootanimation and you'll also need to explicitly define the folder names that you want the animation to be pushed to. (e.g -- Inside lets say the "MyBootanimation" folder -- you should have three folders; they're names respectively are:: system/customize/resource
Inside the resource folder is where your newly created bootanimation.zip will go.
2b) To make the package flashable and work in recovery; you'll need a update-script file which should be in a folder called:: META-INF (ALL CAPS); inside that folder should reside, three more folders:: com/google/android/. The update-script file will go INSIDE the android folder.
I've attached a simple update-script file that will make your package flashable. Unzip the "Extract-ME" file and you'll find the file.
So, to get this to work, you'll open the "MyBootanimation folder and inside it should reside to folders (system (and it's subfolders); which houses the bootanimation and META-INF (and it's subfolders); which houses the update-script). You need to select both files and zip them up in NORMAL mode, not "store" mode. This will create your new package, which you then need to sign via whatever method you use. I use command line and I'd like not to explain that if I don't have to.
here's the file i'm working on if someone wants to take a look at it and tell me what i'm doing wrong that would help me out a lot.if you can i would like to know what is wrong so for future use and the knowledge.
http://dl.dropbox.com/u/9628638/bootanimation1.zip
Lemme know if this helps...
dased14 said:
here's the file i'm working on if someone wants to take a look at it and tell me what i'm doing wrong that would help me out a lot.if you can i would like to know what is wrong so for future use and the knowledge.
Click to expand...
Click to collapse
Two noticeable things:
1. Your images are 850 x 400 (resize all to 800 x 450)
2. Your .zip file is not arranged right.(look at my attached file, should give you an idea)
Your file is way too big to upload here so attaching the base file here for you to work with.
- First, zip the android folder,part2 folder and the desc.txt file as a storage, and name the file bootanimation.zip.
- Second, 7zip my file and navigate to customize>resource and replace the file there with the one you created in the previous step.
- Close and flash the file (This is in amend so you might want to use clockwork 2x (or equivalent RA) to flash it. Feel free to change the update script if you wish)
I tried this on my myn RLS5, works like a charm. Might want to change the desc.txt to match the image dimensions. (800 x 450)
I hope this helps.
PS: I Like the minion animation.
now it came up E:\wrong digest:customize/resource/bootanimation.zip huh?
i put the file here http://dl.dropbox.com/u/9628638/minionsdisco.zip
i know i'm a pain in the [email protected]@, thanks for all the help
edit: i figured out what i was doing wrong it was the way i was zipped files together. now to speed it up and maybe a loop
here's a working one http://dl.dropbox.com/u/9628638/minionsdisco1.zip. how do i speed it up to play more like the movie.
ps thanks to pseudoremora,theidlemonk for helping me figure out what i was doing wrong.
pm me your email...I'll send the file over...i am having trouble uploading it
dased14 said:
now it came up E:\wrong digest:customize/resource/bootanimation.zip huh?
i put the file here http://dl.dropbox.com/u/9628638/minionsdisco.zip
i know i'm a pain in the [email protected]@, thanks for all the help
Click to expand...
Click to collapse
First and foremost -- I don't know whose method recommended that you leave the "system" folder out of the flashing process, but that's a very incorrect way of doing this.
I've stated earlier that you need THREE folders -- SYSTEM, customize, and resource. You only have customize and resource. Your customize folder (and it's subfolders) needs to be placed inside a folder labeled "system".
Secondly, the command you're using in the update-script, while it will work now; will not work if someone decides to change the structure of your package in the future. The update-script I uploaded earlier allows for future flashing because anything placed inside the "system" folder (which Android 100% relies on) will always be flashed, as long as the structure is correct within the system folder.
You should remove the update-script you have now and place this one inside it (if you decide to use the method I've stated above). I've attached the file below (extract first).
Lastly, quite frankly; I've never seen a 60MB bootanimation before and to be honest, that's just unbelievably huge. You need to figure out either how to shorten your animation or to compress it in a manner which will lower its size.
Also, the native resolution for the EVO is 480 x 800 and not 450 x 800 for future reference.
pseudoremora said:
First and foremost -- I don't know whose method recommended that you leave the "system" folder out of the flashing process, but that's a very incorrect way of doing this.
I've stated earlier that you need THREE folders -- SYSTEM, customize, and resource. You only have customize and resource. Your customize folder (and it's subfolders) needs to be placed inside a folder labeled "system".
Secondly, the command you're using in the update-script, while it will work now; will not work if someone decides to change the structure of your package in the future. The update-script I uploaded earlier allows for future flashing because anything placed inside the "system" folder (which Android 100% relies on) will always be flashed, as long as the structure is correct within the system folder.
You should remove the update-script you have now and place this one inside it (if you decide to use the method I've stated above). I've attached the file below (extract first).
Lastly, quite frankly; I've never seen a 60MB bootanimation before and to be honest, that's just unbelievably huge. You need to figure out either how to shorten your animation or to compress it in a manner which will lower its size.
Also, the native resolution for the EVO is 480 x 800 and not 450 x 800 for future reference.
Click to expand...
Click to collapse
ok thanks,how would i compress it to make it smaller? and i want to speed it up to run more like the movie. i have it working it just runs kinda slow?
Not sure if you are on windows, but if you are then pngoptimizer does the trick (should be able to do multiple pngs at a time) and its free online. Also on windows I had an issue with the bootanimation.zip because windows kept adding the thumbs.* file in the two folders other than the desc.txt...that made my animation choppy. Just 7zip into you file and delete if you see it.
pseudoremora said:
First and foremost -- I don't know whose method recommended that you leave the "system" folder out of the flashing process, but that's a very incorrect way of doing this.
I've stated earlier that you need THREE folders -- SYSTEM, customize, and resource. You only have customize and resource. Your customize folder (and it's subfolders) needs to be placed inside a folder labeled "system".
Secondly, the command you're using in the update-script, while it will work now; will not work if someone decides to change the structure of your package in the future. The update-script I uploaded earlier allows for future flashing because anything placed inside the "system" folder (which Android 100% relies on) will always be flashed, as long as the structure is correct within the system folder.
You should remove the update-script you have now and place this one inside it (if you decide to use the method I've stated above). I've attached the file below (extract first).
Lastly, quite frankly; I've never seen a 60MB bootanimation before and to be honest, that's just unbelievably huge. You need to figure out either how to shorten your animation or to compress it in a manner which will lower its size.
Also, the native resolution for the EVO is 480 x 800 and not 450 x 800 for future reference.
Click to expand...
Click to collapse
thanks for your help on this, i'm looking for any ideas on how to compress this to make it smaller in size(without losing any animations) i have been usiing 7zip to compress it
dased14 said:
thanks for your help on this, i'm looking for any ideas on how to compress this to make it smaller in size(without losing any animations) i have been usiing 7zip to compress it
Click to expand...
Click to collapse
pngoptimizer as theidlemonk recommended should be used for each PNG file and hopefully should bring down the size a bit. Otherwise; it really comes down to cutting the animation.
I'm not saying you can't push a 60MB file onto your phone as a bootanimation; but I think it's huge waste of space for such a thing. You have to remember; we're only talking about the bootanimation here and quite frankly, the EVO tends to boot up rather quickly, so trying to show a clip from a movie really shouldn't be your goal -- if anything, you can take bits and pieces from the clip and use that instead.
Personally, I try to make my bootanimations minimal and light. The important part of the animation is actually the looping; so concentrate on that.
pseudoremora said:
pngoptimizer as theidlemonk recommended should be used for each PNG file and hopefully should bring down the size a bit. Otherwise; it really comes down to cutting the animation.
I'm not saying you can't push a 60MB file onto your phone as a bootanimation; but I think it's huge waste of space for such a thing. You have to remember; we're only talking about the bootanimation here and quite frankly, the EVO tends to boot up rather quickly, so trying to show a clip from a movie really shouldn't be your goal -- if anything, you can take bits and pieces from the clip and use that instead.
Personally, I try to make my bootanimations minimal and light. The important part of the animation is actually the looping; so concentrate on that.
Click to expand...
Click to collapse
i'll look into pngoptimizer, now would i set eveything up the same for loop(with fewer animations)like i said this is the first one i have ever tried to make(i hope i get better as i do more) how would i add sound to one. and thx again guys for putting up with me and for all the help
dased14 said:
i'll look into pngoptimizer, now would i set eveything up the same for loop(with fewer animations)like i said this is the first one i have ever tried to make(i hope i get better as i do more) how would i add sound to one. and thx again guys for putting up with me and for all the help
Click to expand...
Click to collapse
I'd advise you take a look at this post and this one also. I wrote that quite some time ago, however it's still very much applicable today.
Edit:: It's actually probably good to read the posts from pages 15, 16, and probably 17 as well in the links I've posted above.
what would you guys say is the best png optimizer to (less loss, better compression)
dased14 said:
what would you guys say is the best png optimizer to (less loss, better compression)
Click to expand...
Click to collapse
Both of us just told you.
Use pngoptimizer. The program itself optimizes each png, taking away any erroneous data and leaves everything else intact; thus giving you a smaller .png file. Doing this for EACH .png file will result in a smaller bootanimation file.
PNGs can be optimized just so much, I would rather think more on the lines of what pseudoremora said: Cutting down animation to keep it minimal and light. Looping will also be a big part as you have over 300 images. Looping would reuse images and allow cutting of parts. (I hope I made sense).
pseudoremora said:
Both of us just told you.
Use pngoptimizer. The program itself optimizes each png, taking away any erroneous data and leaves everything else intact; thus giving you a smaller .png file. Doing this for EACH .png file will result in a smaller bootanimation file.
Click to expand...
Click to collapse
Ok I wasn't sure if that was the name of it or a program type, Googled it and got a bunch of different ones just wanted to make sure. And yes I know its a large file and I will take both of your advice and cut it down. Again thanks for the time and help
This is my first time trying to create a custom boot animation... I think its going to be great if someone would gladly help me out... I can't figure out what has gone wrong with it and why when I restart its just a black screen.. I appreciate everyone who can help me. Thank you... And Thank You XDA... I would upload it directly to xda but the file is too big... so here is the link to whoever wants to help me...
megaupload[dot]com/?d=7NK0BRHR
i noticed and changed alot with it also with the numbering system and still nothing just a black screen...
is it going to the right place some goto (system\customize\resource) some goto (system\media)
whats that ds.store file have never seen that in a evo bootanimation before
both folders are number the same that may make a differance
thing is hugh may want to cut it down maybe split the bigger one in two and remove the smaller and use later as different anime(even after running it through pngoptmizer still over 24.6 mb
hope this helps some
"quoted from pseudoremora"
After creating your bootanimation -- You need to make sure that a couple things have been done correctly for the bootanimation to 1) Work and 2) Be able to be flashed via recovery.
1) To make the bootanimation work
a. Make sure that after creating the animation itself that the .zip you create has NO compression -- (e.g You use "store" mode, instead of "normal" -- both 7zip/Winrar have this feature)
b. Make sure the desc.txt file is properly formatted and has the correct folder names inside the file. Also make sure you have a carriage return (press enter) at the VERY last line of your desc.txt file
c) Make sure the .png filenames are somewhat sequential and organized. (e.g. BootUp001, BootUp002, BootUp003, etc)
2a) To make a flashable package
a. First create a folder to house the bootanimation and you'll also need to explicitly define the folder names that you want the animation to be pushed to. (e.g -- Inside lets say the "MyBootanimation" folder -- you should have three folders; they're names respectively are:: system/customize/resource or system\media
Inside the resource folder is where your newly created bootanimation.zip will go.
2b) To make the package flashable and work in recovery; you'll need a update-script file which should be in a folder called:: META-INF (ALL CAPS); inside that folder should reside, three more folders:: com/google/android/. The update-script file will go INSIDE the android folder.
So, to get this to work, you'll open the "MyBootanimation folder and inside it should reside to folders (system (and it's subfolders); which houses the bootanimation and META-INF (and it's subfolders); which houses the update-script). You need to select both files and zip them up in NORMAL mode, not "store" mode. This will create your new package, which you then need to sign via whatever method you use. I use command line and I'd like not to explain that if I don't have to.
try this(sense base can get asop if thats need)
http://dl.dropbox.com/u/9628638/racecar.zip
dased14 said:
is it going to the right place some goto (system\customize\resource) some goto (system\media)
whats that ds.store file have never seen that in a evo bootanimation before
both folders are number the same that may make a differance
thing is hugh may want to cut it down maybe split the bigger one in two and remove the smaller and use later as different anime(even after running it through pngoptmizer still over 24.6 mb
Click to expand...
Click to collapse
You can also change from png to jpeg. I redid one recently that was 61 mb with pngs, ended up at just over 4 mb with jpegs. Just a thought. And that ds.store, delete it.
Sent from my ADR6300 using XDA App
Hey guys,
For a few days, I was wondering what could happen if we could compile the Standard C library (not trimmed one like Bionic) and compile some linux applications for ARM processor (say, Desire). I successfully compiled the GlibC, and now do have the .a and .so files.
The problem is, I don't know where to put them, so the dynamically linked applications can reach them! I could put them to /system/lib, but I don't want to overwrite the files already there (I don't want to crash the working parts of the system). I was thinking to put them to (say) /data and create symbolic links to /system/lib, but - as I said - what about the libraries which have the same name?
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
Sorry for the wrong section post. I found the solution though..
The thing is to be done is editing the Ramdisk/init.rc; changing LD_LIBRARY_PATH variable, accordingly (say, /data/lib). Once you do that, the system loads libraries from the folders, in specified order.
However, you must be cautious because since at the boot time, Data might not be mounted yet, the libraries that are installed there could not be read. Ergo, don't delete (or move) the system libraries (like I did ) - the phone won't boot without them.
Another issue is libc. Since bash shell is compiled with bionic, it requires bionic version of libc; not glibc. I'm going to try to overcome this by recompling shell; yet still there might be other problems (there might be other native executables need Bionic Libc)
I'll update this thread as I try new things.
theGanymedes said:
Sorry for the wrong section post. I found the solution though..
The thing is to be done is editing the Ramdisk/init.rc; changing LD_LIBRARY_PATH variable, accordingly (say, /data/lib). Once you do that, the system loads libraries from the folders, in specified order.
However, you must be cautious because since at the boot time, Data might not be mounted yet, the libraries that are installed there could not be read. Ergo, don't delete (or move) the system libraries (like I did ) - the phone won't boot without them.
Another issue is libc. Since bash shell is compiled with bionic, it requires bionic version of libc; not glibc. I'm going to try to overcome this by recompling shell; yet still there might be other problems (there might be other native executables need Bionic Libc)
I'll update this thread as I try new things.
Click to expand...
Click to collapse
I just put glibc in /lib, at boot /lib is empty, but then I mount the contents of /lib aftwards. Ideally it would mount from a custom init.rc script. I suppose if you put the libc in /data/lib you could sym link that to /lib during boot. I am pretty sure that /lib needs to be in the root dir and its contents must be executable. I found I had to edit some header file somewhere, I'll get back to ya once I start poking my head round Android again, syncing back up atm.
Hello,
I have an idea to make an App, and I have one problem, I have to upload one folder that its content have a lot of files and folders in order to upload to skydrive. I think that it is more easy if I compress the main folder and then upload this compressed file. How Can I compress this folder?
Thanks you
cansado2930 said:
Hello,
I have an idea to make an App, and I have one problem, I have to upload one folder that its content have a lot of files and folders in order to upload to skydrive. I think that it is more easy if I compress the main folder and then upload this compressed file. How Can I compress this folder?
Thanks you
Click to expand...
Click to collapse
have you tried zip...
dazza9075 said:
have you tried zip...
Click to expand...
Click to collapse
Hi dazza9075,
Thanks by your answer, but I thought the same, but I don't know how to use this, Can you explain about use of zip? Or, Where can I find information about this?
Thank you again
cansado2930 said:
Hi dazza9075,
Thanks by your answer, but I thought the same, but I don't know how to use this, Can you explain about use of zip? Or, Where can I find information about this?
Thank you again
Click to expand...
Click to collapse
+1 for the idea... I also want a program like winrar which also available in symbian phones.plz any dev note this and develop an app for compressing and decompressing files...
WP will unzip zip files, make the sip, copy to sky drive, open via IE, it will then give you the contents of the zip,, it can't compress files to zip though. Technically there would be little point since docs auto sync to sky drive, and WP doesnt support anything else or file system access, but its doable for unlocked devices I suppose
Sent from my SGH-i937 using XDA Windows Phone 7 App
dazza9075 said:
WP will unzip zip files, make the sip, copy to sky drive, open via IE, it will then give you the contents of the zip,, it can't compress files to zip though. Technically there would be little point since docs auto sync to sky drive, and WP doesnt support anything else or file system access, but its doable for unlocked devices I suppose
Sent from my SGH-i937 using XDA Windows Phone 7 App
Click to expand...
Click to collapse
Hi dazza9075,
Thank you by answer, I had thought that it isn't possible, because I want to compress a folder of other app that her content are a lot of files and folders. So, Do some api exist in order to compress this? Or, Have I upload files and folders one by one?
Thank you again
I think it's completely possible
sombody names Ego zheng,wrote an application. It is program manager.
u can repack your apps,and save apps data in a single .zip file.
i think he can do this
contact him for this idea.
Leo_zodiac said:
I think it's completely possible
sombody names Ego zheng,wrote an application. It is program manager.
u can repack your apps,and save apps data in a single .zip file.
i think he can do this
contact him for this idea.
Click to expand...
Click to collapse
its doable so long as you have interop unlock and WP tools installed and setup
if the Windows Phone SDK is missing Zip functionality (it may be called "DEFLATE" which is the name of the compression algorithm; ZIP is the file format) then there are surely libraries for various compression methods which you could download. Alternatively, if you don't mind using native code homebrew, there are compression libraries (zlib, etc.) that can be compiled to a native DLL, and you could then access them via COM.
i add this to new version of my file manager and now you can compress and decompress file and folders
Hi!
Thanks you by your answer, they have been very useful.
Thanks you
Hi again,
I'm using the lib "SharpZipLib" and I have problems with it. Can you explain how use it? or what is the problema? I probe in a program of pc and it working correctly but in app for my mobile say it crashed when it go to create the file, this is code:
FileStream fsOut = File.Create("Copia.zip"); //here is the problema at this moment
ZipOutputStream zipStream = new ZipOutputStream(fsOut);
zipStream.SetLevel(3);
zipStream.Password = null;
........
It can't create the file.
Thank you again
Generally speaking, Silverlight (which WP7 uses for apps) doesn't even allow normal file access, so you might just be getting a MethodAccessException on File.Create. If not, that still won't work without elevated privileges. The default working directory for a program is it's install directory. For a WP7 app, that's going to be either its install location (\Applications\Install\<GUID>\Install) or the Windows directory where the taskhost.exe file lives (\Windows\). Trying to create a file without specifying full path will crete it relative to the working directory, which in this case means creating it in the working directory directly (no path specified). Since the app can't write to the working directory, you'll get an error from that too.
To get around the permissions error, use the IsolatedStore folder (\Applications\Data\<GUID>\Data\IsolatedStore\) or run the app with full permissions ("Trusted" or root unlocked).