I'm looking for some clarification on the meaning of base, instant, and installed modules.
I checked out this link (https://developer.android.com/topic/google-play-instant/faqs) and found that
The size of the instant app (base feature plus any included dependent
feature) should be as small as possible...For an instant app with
multiple features, you must add the size of the base feature APK to a
single feature APK. The total size of both these APKs must be under
4MB.
Having worked through both Google codelabs, I understand the difference between one-feature and multi-feature modules. My question refers to the scenario in which there is only one feature module, the base module.
So, for instance, could the base module be 4 MB in size, and the installed module contain 16 MB more code in addition to that 4 MB to build an APK with total size of 20 MB? Will the Google Play Store accept my app (both as installed and instant version), as long as the instant APK is 4 MB or less, no matter how big the installed APK is?
If there is only one module that is the base module, that module must be under 4 MB in size for an instant app.
The installed app (APK) can be over 4 MB and can be as large as a standard installable APK can be (I've seen them over 100 MB).
Related
I'm trying to run jetracer on the 2GB version of Jetson Nano along with Waveshare's JetRacer Pro AI Kit but all the release files listed in the docs are for the 4GB version. The Waveshare wiki also features files for the 4GB version only. I've seen someone mention there being a pre-built 2GB version for Waveshare cars available on the wiki alongside the 4GB version but it's not there anymore (he meant the AI Kit instead of Pro AI Kit I have but still, it's unavailable for either anymore).
Is there no way to run the AI capabilities for self driving RC cars on a 2GB jetson, then? I thought these were cross platform and worst case scenario, there'd be worse performance - but not impossibility to run it altogether. Would it make sense to flash the card by hand using Jetson's official docs and then trying to follow the Jetracer Setup Guide from step #2 instead? This seems to have a chance of working cause step #1 (the one with ready-baked files) is just an installation of Jetcard anyway so one should be able to bypass it by flashing the card yourself instead of using the provided image. At the same time, I contacted Waveshare's support and they just told me straight away that Jetracer and their kit won't work with a 2GB Jetson and that's that...
Is there a possibility to run Jetracer on a 2GB Jetson then?
I've recently assembled a new AMD Desktop, to replace an older Dell Latitude E7540 laptop.
The AMD Desktop:
Ryzen 3 3100 # 3.8GHz (4C/8T), 32GB DDR4 3600 CL17 RAM, Corsair P600
Gen4 SSD
The DELL Laptop:
Dell Latitude E7540: Intel I7-5600U # 2.6GHz (2C/4T), 16 MB RAM DDR3 1600, Samsung mSATA PM851
On the new AMD Desktop, when executing a docker build command, two situations occur:
The performance is dreadful, even building a simple image, it takes a long time for the command to start. After starting, it takes a long long time to complete (when it completes)
The build window crashes almost 50% of the time.
The benchmarks indicate that the new AMD Desktop is 3.5x faster at single core, and 6x faster at multicore.
As such, I was expecting a much better performance with the new AMD Desktop.
Unfortunately, that's not the case, and for the same Dockerfile (which generates a very big image):
The Dell starts faster
The Dell completes faster (10m vs 30m)
On the Dell, the build window never crashes.
The only difference between both systems is that one is an Intel platform, the new one an Ryzen 3 AMD.
Environment Details are the same on both machines:
Windows Version: Windows 10 Ent. 19049
Docker Desktop Version: Docker 3.0.0
What can explain this abysmal performance on Docker-Desktop on the new AMD system?
After a few troubling days, i can confirm that the problem is not AMD related.
The culprit is the Antivirus, that when ON, its scanning the files used by Docker, which cause all the problems i've described.
Docker documentation states how to disable the antivirus to scan Docker related files:
https://docs.docker.com/engine/security/antivirus/
When antivirus software scans files used by Docker, these files may be locked in a way that causes Docker commands to hang.
One way to reduce these problems is to add the Docker data directory (/var/lib/docker on Linux, %ProgramData%\docker on Windows Server, or $HOME/Library/Containers/com.docker.docker/ on Mac) to the antivirus’s exclusion list. However, this comes with the trade-off that viruses or malware in Docker images, writable layers of containers, or volumes are not detected. If you do choose to exclude Docker’s data directory from background virus scanning, you may want to schedule a recurring task that stops Docker, scans the data directory, and restarts Docker.
An average npm install seems to take around 44 seconds on my machine for a new Angular project, when created using the Angular CLI.
I looked at the usage of the computer resources but I didn't see anything being used at 100% (CPU, RAM, Disk, Ethernet).
Is the install time that 'slow' due to the response times of the requests made during the process, or the speed of the server that feeds me the node modules or is there a specific hardware component that is slowing down the process?
Basically, I want to know if upgrading something on my computer could decrease the install time.
I am using PHPStorm 9 and crashes all the time.
I checked for logs but it does not report anything.
What can I do to debug it?
Edit 1
The app is fresly installed, on freshly formated PC, with fresh installed and updated java.
Also I tried to increase the allocated RAM but each time the app starts returns my values to default.
Edit 2
I am using the 64bit version which demanded an external jdk since there wasn't provided by the app.
I installed the 8.60 X64 java and add to my user and system vars on windows 10.
Edit 3
I am using Eset's nod32.
This is a notice that shows when I load the app.
I've just updated my Galaxy Tab 2 7" to OS v4.1.1 (Jelly Bean). Since that I can't connect to my device (from my Windows 8 PC, via USB) anymore.
Most relevant to me is the fact that I can't even debug my Android apps using the tablet (which is actually the reason why I bought it). Eclipse does show it among the adb devices, but in an offline status.
The Android SDK is updated. I've tried to force the install of the drivers via the android_winusb.inf located in the\android-sdk-windows\extras\google\usb_driver folder, but it doesn't seem to carry the right pieces of information. Tampering the file by manually adding 'em seems to conflict with the along-coming .cat files.
I've also tried by installing Kies, but even that piece of software can't connect to the device.
What do you suggest? Thanks in advance.
Magically, a new OTA update has come "from above" right to my device just a couple of minutes ago. That fixed the whole thing (no action made on the PC side).
Looking at the "about device" data sheet, Android version is still 4.1.1.
I haven't tracked the previous kernel version nor build number, so I can't see if and how they've changed; but I can write 'em down now, just in the case it may matter for someone else to check against:
Kernel version
3.0.31 - 523998
Build number
JRO03C.P3110XXCLK7