Check to check ноты

Bootloader Check in XIAOMI Redmi Note

How to check bootloader status in XIAOMI Redmi Note

You can read a lot of important information from XIAOMI Redmi Note Fastboot Mode. We can use the XIAOMI fastboot data in order to find the desired firmware, downgrade software, change the region of the firmware or root device, The most important info is bootloader status (locked or unlocked). The unlocked bootloader makes your XIAOMI Redmi Note out of warranty but it gives you also the possibility to change the firmware of your device.

Download Necessary Tools

Installing Necessary Tools

1. Firstly install Xiaomi PC Suite
2. Then you should install Adb mini with fastboot tools setup to get all necessary drivers and applications.

• Windows 10 users should additionally go to c:\Windows\inf and search file «wpdmtp.inf» press right button on it and select INSTALL

Check Bootloader Status Tutorial

1. Turn off XIAOMI Redmi Note phone completely.
2. Then hold down the Volume Down and Power Button.
3. Release both keys as soon as the Fastboot Mode pops up.
4. Connect XIAOMI Redmi Note to computer by using the USB Cable.
5. Turn on Command Prompt as Administrator. You can find it in Start Menu.
6. Make sure that you are using the default directory of ADB and FASTBOOT. If didn’t change the path, you can find files in C:\ADB
7. Use the following commands:
   • type cd\ and press Enter button.
   • type cd adb and press Enter button.

   

Next enter fastboot command:

1. Type in fastboot devices and press enter key
   This command checks communication with phone and sure that all drivers are installed correctly.
2. Enter fastboot oem device-info and press enter key
   This command gives you all necessary information. The most important info is bootloader status, we can check here if we have locked bootloader or unlocked.

The information table should look as follows:

• (bootloader)Device tampered: false
  This means that the phone is working normally without any software problem
• (bootloader)Device unlocked: false
  This means that bootloader is LOCKED
• (bootloader)Device unlocked: true
  This means that bootloader is UNLOCKED

Other Useful Fastboot Command in Xiaomi phones:

1. fastboot reboot
   This command is used to reboot XIAOMI Redmi Note from fastboot mode to normal use.
2. fasboot oem lock
   This command is used to LOCK Bootloader from UNLOCK state if needed.
3. fastboot reboot-edl
   This command is used to reboot XIAOMI Redmi Note from fastboot mode to EDL MODE
   (only older phone supported MIUI 7 and older).

If you found this helpful, click on the Google Star, Like it on Facebook or follow us on Twitter and Instagram

Источник

How to check which character sets (codepages) font supports (has letters for)?

For my app I need to show a list of system fonts, but filter out all the fonts that do not support 20 predefined languages (the set is hardcoded) and show only those which do.

I can have a list of available fonts by calling Vcl.Forms.Screen.Fonts .
Knowing just the font name from that list, how do I check which character sets (codepages) this font supports (has actual letters for) ?

For example, common fonts like Arial or Times New Roman have characters for almost all European languages, including Cyrillic (and also Chinese and such). Yet many less common fonts often have only English letters.

The app is for internal use, so having a function that simply queries the font if it has a certain letter specific to some character set / codepage (e.g. Ф or Ў or ξ ) and that it is not substituted with letter from another generic font (or some placeholder) would suffice.

2 Answers 2

The GetGlyphIndices function can be used to determine whether a glyph exists in a font.

Citing the MSDN docs:

fl [in]: Specifies how glyphs should be handled if they are not supported. This parameter can be the following value.

GGI_MARK_NONEXISTING_GLYPHS — Marks unsupported glyphs with the hexadecimal value 0xffff.

The Remarks sections links again to the Uniscribe functions, e.g. ScriptGetCMap

This function attempts to identify a single-glyph representation for each character in the string pointed to by lpstr. While this is useful for certain low-level purposes (such as manipulating font files), higher-level applications that wish to map a string to glyphs will typically wish to use the Uniscribe functions.

As both APIs are supported from Win2k onwards, it is probably a matter of taste which one to use.

(EDIT: Just noticed that the import is already in Windows.pas)

Sample code

If you want to check entire character set support, you can use EnumFontFamiliesEx from the Windows API — this doesn’t let you query a single font, but rather returns a list of installed fonts which support a given character set (or which have any other set of queryable features).

You’ll need a callback function of the appropriate type :

And then call as :

With the various fields in the TLogFont (MSDN) structure you can query a wide variety of font features. In this case I have restricted only the character set (to Chinese Big-5 in the above example).

The callback will fire once for every resulting font returned from the query. You will need to manage collecting this information as it is returned. To add restrictions for several character sets you would need to call EnumFontFamiliesEx once for each character set of interest. The following constants are defined in the RTL Windows unit :

Cross-referencing would then be up to you — a TDictionary seems like a sensible tool to manage that task.

Источник

Check

Unit Testing Framework for C

Installing Check

The following instructions show how one can either install Check from a package manager or compile from source on one’s platform.

Ubuntu/Debian via Aptitude

Ubuntu and Debian both provide a Check package that can be installed. To install, in a terminal, type:

Fedora via Yum

Fedora provides a Check package that can be installed. To install, in a terminal, type:

Arch Linux via Pacman

Arch Linux provides a Check package that can be installed. To install, in a terminal, type:

GNU/Linux From Source

Check uses autotools as a build system, and the default steps work on GNU/Linux systems. After the latest Check source has been downloaded and unpacked, open a terminal in the unpacked directory, then:

If the «make check» step fails, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

Debian GNU/Hurd From Source

Debian GNU/Hurd does not yet provide a package for Check, so it must be compiled from source. Check uses autotools as a build system, and the default steps work on Debian GNU/Hurd systems. After the latest Check source has been downloaded and unpacked, open a terminal in the unpacked directory, then:

If the «make check» step fails, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

OSX via MacPorts

MacPorts provides a Check package that can be installed. First, install MacPorts if not done already. Then, in a terminal, type:

OSX via Homebrew

Homebrew provides a Check package that can be installed. First, install Homebrew if not done already. Then, in a terminal, type:

OSX From Source

Check uses autotools as a build system, and the default steps work on OSX systems. You must have Xcode installed. After the latest Check source has been downloaded and unpacked, open a terminal in the unpacked directory, then:

If the «make check» step fails, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

OpenBSD via Packages

OpenBSD provides a Check package that can be installed. To install, in a terminal, type:

BSD From Source

Check uses autotools as a build system, and the default steps work when building on the BSD system. Special care is required when cross compiling, which is described below.
After the latest Check source has been downloaded and unpacked, open a terminal in the unpacked directory. To compile on the BSD system directly, type:

If the «make check» step fails, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

Cross compiling for BSD may require an additional configure argument: —enable-timer-replacement . Check attempts to use high resolution timers via the timer_create(), timer_settime(), and timer_delete() functions. For some BSD systems (e.g. OpenBSD), these functions exist but are non-functional stubs. If the functions are available, when compiling on the target system the configure script will verify that the calls are not stubs. If they are valid, Check will use them. When cross compiling, the validity check cannot be performed. To prevent Check from using these when cross compiling for affected BSD systems, add the —enable-timer-replacement configure option.

Cygwin on Windows via Package Manager

Cygwin provides a Check package that can be installed. To install, launch the Cygwin setup program, locate the Check package under the Devel folder, then install.

Cygwin on Windows From Source

Check uses autotools as a build system, and the default steps work on Cygwin. You must have gcc, and make installed. After the latest Check source has been downloaded and unpacked, open a Cygwin terminal in the unpacked directory, then:

If the «make check» step fails, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

MinGW/MinGW-w64 on Windows From Source

MinGW and MinGW-w64 do not provide a package for Check, so it must be compiled from source. Check uses autotools as a build system, and the default steps work on both MinGW and MinGW-w64. Note that because both MinGW and MinGW-w64 do not provide a fork() alternative, Check’s fork mode will be disabled. After the latest Check source has been downloaded and unpacked, open a MSYS terminal in the unpacked directory, then:

If the «make check» step fails, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

Visual Studios on Windows From Source

Check must be compiled from source for Windows. Note that no fork() call is available, and Check’s fork mode will be disabled. The CMake build system is supported for compiling Check with Visual Studios, so download CMake first.

After the latest Check source has been downloaded and unpacked, open the CMake GUI program. Fill in the «Where is the source code» and «Where to build the binaries» fields to point to the unpacked location of the Check source, and press the Configure button. Select the version of Visual Studios to use, and click «OK». Once the configuration completes, CMake will highlight two settings, CMAKE_CONFIGURATION_TYPES and CMAKE_INSTALL_PREFIX. You may leave them as their defaults or modify them. Finally, click «Generate» to create the Visual Studio project files.

Open Visual Studios and load the generated project files. The following is a summary of the important build targets:

• ALL_BUILD: Build Check and all unit tests
• RUN_TESTS: Execute Check’s unit tests
• INSTALL: Install Check to the CMAKE_INSTALL_PREFIX location listed from the CMake GUI

To compile, validate, and install Check, run these three targets from Visual Studios. Note that the RUN_TESTS target only runs Check’s unit tests which do not require a shell interpreter. The remaining tests must be run in a MSYS or comparable environment.

If any of the build targets fail, including the RUN_TESTS target, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

MSVC on Windows From Source

Check must be compiled from source for Windows. Note that no fork() call is available, and Check’s fork mode will be disabled. The CMake build system is supported for compiling Check with Visual Studios, so download CMake first.

After the latest Check source has been downloaded and unpacked, open a terminal (cmd.exe). If MSVC is not in the path, execute the bat file in the MSVC install directory to load it into the path. For example, with Visual Studios 10:

Navigate to the unpacked location of the Check source, then:

Note that the «nmake test» step only runs Check’s unit tests which do not require a shell interpreter. The remaining tests must be run in a MSYS or comparable environment.

If the «make test» step fails, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

Solaris From Source

Check uses autotools as a build system. The PATH must be setup such that POSIX versions of tools are found before legacy once. (see also standards(5) for more details). If the compiler is GCC, setup the PATH as follows:

Otherwise, for Solaris Studio use the following PATH:

Further, ensure that the environment variables LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 are unset. It is recommended to use OpenCSW packages (/opt/csw/bin) to get recent versions of required programs. The configure script will likely find gcc by default; to use Solaris Studio also set the following environment variable:

After the latest Check source has been downloaded and unpacked, open a terminal in the unpacked directory, then:

If the «gmake check» step fails, please send an email to Check’s mailing list and give details as to the failure so it may be investigated and fixed.

Источник