I am not finding Bootanimation.zip file on Android emulator 2.3.3. I have checked all below paths.
system/media or system/customize/resource or data/local.
I need to put Bootanimation.zip in right location of emulator and test
Thanks
system/media and /data/local/ are the right places.
The latter is preferable as it makes it easier to modify, and does not require the tedious
modification of the system.img (system partition) size.
Note that bootanimation.zip should be lowercase, and -0 compressed.
Related
In Android Studio, in
~/StudioProjects/$APPLICATION/build/android-profile/,
there are many files profile-*.rawproto, e.g., profile-2017-04-25-18-19-51-815.rawproto.
I have never seen the file suffix .rawproto, does this suggest a certain kind of file, and if so, what is this file generally used for?
With some digging online, it seems to be related to Gradle in IntelliJ/Studio, which is a sensible conclusion since it is in the build directory. But this is all the information I am able to find on what this is or what it should do.
That filename pattern is mentioned in ProcessProfileWriterFactory.java, part of the Android Gradle plugin. Once a real filename is created, it is passed to ProcessProfileWriter.java which seems to write some analytics data about the build process to a file. The rawproto file format is probably Google's Protocol Buffers.
Using Gradle 2.10 within Android Studio, I'm having some problems with the amount of space on my root partition combined with the fact that gradle produces quite a lot of tmp files.
I'd like to change my gradle tmp file to ~/tmp, but so far haven't managed to do so.
Things I've tried:
$ export TEMP=TMP=TMPDIR=<home folder>/tmp
$ studio &
No success, gradle still uses /tmp.
Modify java.io.tmpdir via Gradle's jvmargs in gradle.properties:
org.gradle.jvmargs=-Xmx2048M -Djava.io.tmpdir=<home folder>/tmp
Still no success.
Of course, my root issue is the lack of space on /, and I have managed to get it usable for some time more, but unless I completely reconfigured lots of stuff on my machine I will run short from time to time. Since my home directory is mounted on a 1 TB partition it would be nice to use it for tmp files instead.
Actually, if there's a solution system-wide that also affects gradle, that would be just as good or even better. Any ideas?
UPDATE: This does not seem to actually be about / being full, even though "No space left on device" is what's reported. After making sure my / partition has lots of space this still happened.
After searching some more I found http://www.out4mind.com/en/android-studio-updates-error-linux/ which suggests setting the tmpdir from studio64.vmoptions:
$ echo "-Djava.io.tmpdir=<<<home folder>>>/tmp" >> ~/.AndroidStudio<<<version>>>/studio64.vmoptions
I tried that, but after restarting AS, the same error persists. I also verified using
jps -lvm
that my java.io.tmpdir is in fact set. Still no success though.
I'm starting to think that this might be NDK related because my project has native code and I do use the gradle-experimental plugin with NDK support. Question is which device is full, is there a RAM disk involved when invoking the native compiler?
I notice that the later versions of gradle have a means to exclude resources, however I have not seen any examples supporting this where we specify .jni.srcDirs, which unselectively includes everything under each .srcDir path.
Does anyone know of a way to specify certain subdirectories to exclude, for NDK?
What about excluding individual files by extension?
My only alternative seems to be to explicitly list files that are used.
P.S. I don't want to use Android.mk; if possible I would prefer to stick with Gradle's automation.
At least for the present, this doesn't seem to be possible through gradle.
What I've done for now is to delete unwanted files (example sources) from the source folders (then had git ignore those deletions so it doesn't try to check in changes to the project's submodule dependencies). This way I can keep the repos the same but still have Android Studio / gradle not process those unwanted files.
Of course, if you cut gradle out of the picture altogether, you can do whatever you like with your makefile, including solving this problem.
In the 2009.1 version of Perforce Visual Client for 32-bin Windows, the "Reconcile Offline Work" option does weird things. In the middle box where the "Local files not in depot" should be displayed, I never get anything. What I do see is that the first time I reconcile a folder, it looks like perforce is filling the box with the "local files not in depot" because a list flashes quickly before my eyes. Then all of a sudden, the list quickly disappears into thin air and I'm left with an empty list. Does anyone know how I can get this feature to show me the files that I have not yet added? It seems like the "Modified files" and "Depot files missing from workspace" features work fine.
Also, as a side note, "Reconcile Offline Work" seemed to work fine in the 2009 beta version.
I had exactly the same problem.
The solution for me was obscure but trivial.
I simply changed the root directory of my client workspace from "C:\depot" to "c:\depot".
Yes, that's right, all I did was to change the drive letter from uppercase to lowercase. And, yes, I verified that changing the drive letter back to uppercase breaks it again and that changing the drive letter back to lowercase again fixes it again. So, this is not just a coincidence.
This is almost certainly a bug in the Perforce reconcile feature.
If you look closely at the reconcile paths, they all appear with a lowercase drive letter, even if you specify an uppercase drive letter, so my guess is that the matching algorithm is simply doing a case-sensitive comparison on the file paths. This is appropriate for everything but the drive letter. Their file lister probably always sets the drive letter to lowercase, so an uppercase drive letter on your client workspace root will never match.
This certainly sometimes happens. I seems the problem is likely to occur if I change the workspace view somehow and/or upgrade P4V to new version. So the solution which worked for me in the past was to trash the problematic workspace and create a new one (sometimes have to choose a different name too).
Perhaps deleting the .p4qt and .p4scc in your user home directory can help too.
Incidently, I did have a conversation with Perforce support on the related subject some time ago, and as the problems like this are very difficult to reproduce, therefore there wasn't much that they could do.
I have found issues with long filenames in p4 reconcile
from the base direectory
p4 reconcile ./...
never returned.
but if I cd further up the tree
cd components
p4 reconcile ./...
worked.
I was able to reconcile the whole tree eventually by stepping up directories, depending on how much longer your paths are this might work for you.
I had an instance where p4v showed the visual indicator that files had changes, and doing a diff showed the changes appropriately, but resolve on any parent directory didn't show them.
Those files had been changed by downgrading a library using a unity package install, and their "last modified" date was older than the previously submitted files. On OSX running the touch command on all the files in relevant directories updated all their modified times and reconcile worked after that.
Are there any good tools for comparing two folder structures (files included) between two environments?
i.e. comparing a dev computer with production
Edit:
A note on some lessons learned: dir /s /o:N >> output.txt works well in conjunction with a text comparison tool (I used WinMerge), but the filesystem does appear to matter. NTFS against FAT32 doesn't work well, as one scans the folders in reverse alphabetical order, and the other doesn't. To solve this issue, I copied the files from the FAT32 to an NTFS drive.
Also, DiffMerge is nice, but slow. It actually hung when run on the server (that's where I had access to both sets of files) to a point that I had to force a quit.
I'm sure others have thoughts on doing this with *NIX. Probably a similar technique like ls -alR > output
It's still pretty manual, but it works well.
Just keep in mind that the times on the folders will more than likely be different, so you may want to use a regex to replace them and make them more consistent, since that's fairly benign (I used [\d]{2}/[\d]{2}/[\d]{4}[\s]*[\d]{2}\:[\d]{2}\sAM[\s]*\<DIR\> and [\d]{2}/[\d]{2}/[\d]{4}[\s]*[\d]{2}\:[\d]{2}\sPM[\s]*\<DIR\>).
I use Diff merge (http://www.sourcegear.com/diffmerge/ - it has a free version) for comparing folder structures on Windows
For a tool that runs on Windows (but can work against Linux samba shares), try BeyondCompare.
One windows.
Use your favorite diff tool on the files generated from this cmd.
Run this from the folders you wish to compare.
c:\somefolder>dir /s > searchResult.txt
WinMerge also does folder and file comparison and its FREEE
Option 1)
Mount one of the machines on the other, then use some standard directory compare utility.
Option 2)
Use rsync --dry-run and use the output in some way.
Option 3)
Generate hashes (e.g. sha256) of the files on each side, then compare the lists.
WinDiff and KDiff both seem good at doing this without the need for command line dir listing. My personal preference is KDiff.
WinDiff shows an expanded list of all files/folders. (I was only interested in differences so turned off "Show Identical Files" in the Options menu).
KDiff presents an expandable tree view with nice colour coding.