Android Studio virtual device cannot correctly set the internal storage on the M1 Pro - android-virtual-device

When I try to modify the internal storage of the virtual machine, it changes the internal storage to twice the size I set, and generates a system.img with the same size as I set.
system environment:
M1 Pro
MacOS 13.2
Android Studio Electric Eel | 2022.1.1 Patch 1
Pixel 6 Pro emulator profie
Android 13.0 Google APIs | arm64 API 33
I try to modify the internal storage of a virtual device
Edit disk.dataPartition.size=64G in config.ini file
Change the configuration on Android Virtual Device Manager
But it changes the internal storage to twice the size I set, and my hard disk space usage will also increase to the set sizeenter image description hereenter image description here

Related

Android Studio and Emulator not responding

I have an Acer Aspire E5-573 laptop with 4Gb RAM, Windows-10 64 bit operating system. Whenever I start my Android Studio, my laptop stops responding, and I am my program does not run on the emulator. What do you think would be the problem?
You have to increase your RAM atleast 8gb,
alternative way:
Use lower version of android studio because version 4.0 and up has many features like animations etc. don't use AVD Android Virtual Device instead try to use Physical phone as emulator
Its mainly happen when your computers memory (RAM) run out, when there is no sufficient memory(RAM) space left to run your program than your laptop is not responding.
Possible solution
Increase your RAM (memory) to minimum 8 GB and
Include a SSD storage in your laptop

Blue screen due Windows IoT Core 10 B+ loading

I try to run Windows IoT Core 10 B+ over Raspberry Pi 3 B+.
The plate is new. The OS I downloaded from here: Windows IoT 10 B+, I used:
RaspberryPi 3B+ Technical Preview Build 17661
I user this manual to install the OS to teh flash.
I have 4 INCH HDMI LCD with Touch Pad connected to the plate.
For connect the LCD I was need to modify original config (g:\config.txt) file - see code below.
But the problem not in config, when I use original config, I have no device detected in Dashboard. If I use modified config, I have monitor working, but have blue screen.
I have follow drives after FFU uploading:
USB Drive F:
EFIESP G:
MainOS H:
Data J:
I searched for logs and important files, and didn't found much:
j:\FirstBoot.Complete
Some DUMP like files, however, it is unable to open it in Visual Studio as DUMP files:
j:\DUMP0c15.tmp
j:\DUMP0c35.tmp
j:\DedicatedDumpFile.sys
Follow directories, however it are empty:
j:\Logfiles\WMI\RtBackup\
j:\CrashDump\
h:\Windows\tracing\
h:\Windows\LiveKernelReports\
h:\Windows\system32\winevt\Logs\
The modified content of: g:\config.txt:
init_uart_clock=16000000 # Set UART clock to 16Mhz
kernel_old=1 # Load kernel.img at physical memory address 0x0
safe_mode_gpio=8 # A temp firmware limitation workaround
max_usb_current=1 # Enable maximum usb current
gpu_mem=32 # Set VC to 32MB, ARM DRAM to (1008-32)MB
hdmi_force_hotplug=1 # Enable HDMI display even if it is not connected (640x480)
core_freq=250 # Frequency of GPU processor core in MHz
framebuffer_ignore_alpha=1 # Ignore the alpha channel for Windows.
framebuffer_swap=1 # Set the frame buffer to be Windows BGR compatible.
disable_overscan=1 # Disable overscan
hdmi_group=2 # Use VESA Display Mode Timing over CEA
hdmi_mode=87 # 5 inch screen
hdmi_cvt 480 800 60 6 0 0 0 # 5 inch screen
dtoverlay=ads7846,cs=1,penirq=25,penirq_pull=2,speed=50000,keep_vref_on=0,swapxy=0,pmax=255,xohms=150,xmin=200,xmax=3900,ymin=200,ymax=3900
display_rotate=3
This is screenshot of blue screen:
As I see, there is notification about: BAD_SYSTEM_CONFIG_INFO
I read troubleshooting page and some other information.
I have follow questions:
What are the drives responsible for: G:, F:, J:, H: ?
Where can I find boot logs in the Windows IoT file system?
Where can I find more documentation about Windows IoT OS architecture and its system's directory tree?
What can be the problem?
PS: I have successful expirianse to run Windows IoT Core 10 on Raspberry Pi 3.
Please note there is no official release version of Windows IoT Core for Raspberry Pi 3B+. There is only one insider preview version 17761 suppose to working on 3B+. So use the image you download without any modification to see if it works.
But th eproblem not in config, when I use original config, I have to
device detected in Dashboard. If I use modified config, I have monitor
working, but have blue screen.
If you mean you can't detected the device in Dashboard please connect a display via HDMI to see the system boot up or not. For me "BAD_SYSTEM_CONFIG_INFO" seems due to you change the default settings so cause the system boot fails.
What are the drives responsible for: G:, F:, J:, H: ?
MainOS: OS and OEM-preloaded apps.
EFI: Fixed-size partition with the boot manager, boot configuration database.
Data: User data partition, user registry hives, apps, apps data.
More detailed information please refer to "IoT Device Layout".
Where can I find boot logs in the Windows IoT file system?
You may need use WinDbg to get boot information when the system can boot up successfully.
Where can I find more documentation about Windows IoT OS architecture
and its system's directory tree?
It seem no such dedicated document. But you can reference the following documents:
"Windows kernel", "Architecture of Windows 10", "An overview of Windows 10 IoT", "Windows file sharing"
Windows IoT Core is a Windows 10 edition for IoT. It has many commonalities with Windows 10 other editions and has some limitations due to its device limited resource. So you can compare Windows 10 IoT Core and a full version Windows 10 like Windows 10 IoT Enterprise to understand it.

Android emulator slow after restarting computer

After restarting my computer the Android emulator is very slow on visual studio 2015, but after a few hours of running it's back at normal speed.
While the emulator is slow I constantly get messages like process system isn't responding, settings isn't responding, launcher3 isn't responding.
Emulator specs:
Android 6.0 - API Level 23
CPU : Intel Atom(x86)
RAM: 1835 VM Heap: 128
Internal Storage: 800
SD Card: 100
Use Host GPU enabled
Anyone know the cause of this happening?
Finally fixed it.
In my case, I have a laptop with an extra graphic's card.
After changing settings in the nvidia panel: Control 3D settings -> Prefer nvidia processor.
then
right click AVD Manager.exe -> execute with graphic processor.
That fixed it for me

Windows 7 image to Oracle VirtualBox

I just bought a Macbook Air and installed Oracle VirtualBox on it. I have a Lenovo laptop with Windows 7 on it that I took a system image of it (Control Panel -> Backup and Restore -> Create a system image) on an external hard drive. I would like to have this system image on the VirtualBox, but I'm having trouble. On the external harddrive there seems to be two different VHD files (one is 4.4 mb and one is 50.3 gb in size). I do not see an ISO file on the external harddrive. When I created the new virtual machine and selected the 50.3gb vhd file as the virtual hard disk, I received the "Fatal boot: Int 18" error. Does anyone have any suggestions or ideas how I can get this to work? Thanks in advance!
The Windows 7 backup image is not intended to be bootable by all accounts. You will need to restore the image. Acronis appears to be able to restore the image to a partition, if you dont want to write 50 Gb to DVDs.
the backup VHDs are not bootable in the form they are created with
Windows backup.
Reference

Windows Mobile 6 Emulator change storage?

How do i change the size of the Windows Mobile 6 Emulator. Its fixed at 32mb. I read this post: Increasing Windows Mobile 5 Emulator Storage
But it only helps for the 5.0 version. Isnt there any way to increase the storage size in version 6.0?
I've just answered in the WinMo 5.0 question, but it works for 6.0 too, so I'll repost it:
Under http://forum.xda-developers.com/showthread.php?t=549675 you will find a driver for the emulator that sets up a RAM Disk, that for the emulator is seen as an external storage card but doesn't suffer from the issues with mapping a folder. I've checked with SQL Compact sdf file stored in the RAMDisk and it works like a charm. I've used it as a 64MB drive but supposedly it can handle up to 256 MB.

Resources