slitaz -adb

slitaz -adb

slitaz-4.0.iso 34.7M

http://research.cs.wisc.edu/wings/projects/wisense/downloads/adb_tools_linux.tar.gz

check-list:
1.
tux@slitaz:~$ uname -a
Linux slitaz 2.6.37-slitaz #2 SMP Wed Mar 7 10:36:39 CET 2012 i686 GNU/Linux

2.
tux@slitaz:~$ tar -xzf adb_tools_linux.tar.gz

tux@slitaz:~$ ls -l platform-tools/adb
-rwxrwxr-x 1 tux users 1226659 Jun 14 2013

tux@slitaz:~$ platform-tools/adb version
Android Debug Bridge version 1.0.31

3.
tux@slitaz:~$ ldd platform-tools/adb

platform-tools/adb:
linux-gate.so.1 => (0xffffe000)
librt.so.1 => /lib/librt.so.1 (0xb7734000)
libncurses.so.5 => /lib/libncurses.so.5 (0xb7701000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb76e9000)
libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0xb761d000)
libm.so.6 => /lib/libm.so.6 (0xb75f6000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0xb75df000)
libc.so.6 => /lib/libc.so.6 (0xb749b000)
libdl.so.2 => /lib/libdl.so.2 (0xb7497000)
/lib/ld-linux.so.2 => /lib/ld-2.13.so (0xb773d000)

4.
tux@slitaz:~$ sudo tazpkg get-install file

tux@slitaz:~$ file platform-tools/adb

platform-tools/adb: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.8, not stripped 

https://forum.slitaz.org/topic/android-adb-tool-does-not-want-to-work-on-slitaz-40#post-50272

houdini and binfmt_misc

houdini and binfmt_misc


qemu user mode and binfmt_misc
http://alanyih.blogspot.tw/2013/06/slitaz-qemu-user-mode-and-binfmtmisc.html

Kernel Support for miscellaneous (your favourite) Binary Formats v1.1
==============================================================
https://www.kernel.org/doc/Documentation/binfmt_misc.txt

This Kernel feature allows you to invoke almost (for restrictions see below)
every program by simply typing its name in the shell.
This includes for example compiled Java(TM), Python or Emacs programs.
To achieve this you must tell binfmt_misc which interpreter has to be invoked
with which binary. Binfmt_misc recognises the binary-type by matching some bytes
at the beginning of the file with a magic byte sequence (masking out specified
bits) you have supplied. Binfmt_misc can also recognise a filename extension
aka '.com' or '.exe'.

First you must mount binfmt_misc:
mount binfmt_misc -t binfmt_misc /proc/sys/fs/binfmt_misc

Chrooting to: /opt/rootfs-armhf/
http://alanyih.blogspot.tw/2013/06/slitaz-setup-rootfs-armhf.html

3. Mount the binfmt_misc handler
# modprobe binfmt_misc
# mount -t binfmt_misc binfmt_misc /proc/sys/fs/binfmt_misc 

4. register our format with the kernel via the procfs
root@slitaz:~# echo ':arm:M::\x7fELF\x01\x01\x01\x00\x00\x00\x00\x00\x00\x00\x00\x00\x02\x00\x28\x00:\xff\xff\xff\xff\xff\xff\xff\x00\xff\xff\xff\xff\xff\xff\x00\xff\xfe\xff\xff\xff:/usr/bin/qemu-arm-static:' > /proc/sys/fs/binfmt_misc/register

5. check register
root@slitaz:~# cat /proc/sys/fs/binfmt_misc/arm
enabled
interpreter /usr/bin/qemu-arm-static
flags:
offset 0
magic 7f454c4601010100000000000000000002002800
mask ffffffffffffff00ffffffffffff00fffeffffff

1.
tux@slitaz:~ $ adb shell
shell@Z00A:/ $ mount | grep binfmt
binfmt_misc /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0


2.
shell@Z00A:/ $ grep bridge /default.prop
ro.dalvik.vm.native.bridge=libhoudini.so


3.
shell@Z00A:/ $ ls -l /proc/sys/fs/binfmt_misc
-rw-r--r-- root root 0 2015-12-20 21:24 arm_dyn
-rw-r--r-- root root 0 2015-12-20 21:24 arm_exe
--w------- root root 0 2015-12-20 21:24 register
-rw-r--r-- root root 0 2015-12-20 21:24 status


4.
shell@Z00A:/ $ cat /proc/sys/fs/binfmt_misc/status
enabled


5.
shell@Z00A:/ $ cat /proc/sys/fs/binfmt_misc/arm_exe
enabled
interpreter /system/bin/houdini
flags: P
offset 0
magic 7f454c46010101000000000000000000020028


6.
shell@Z00A:/ $ cat /proc/sys/fs/binfmt_misc/arm_dyn
enabled
interpreter /system/bin/houdini
flags: P
offset 0
magic 7f454c46010101000000000000000000030028
shell@Z00A:/ $

Intel Houdini - Binary Translator

Intel Houdini - Binary Translator

ro.product.cpu.abi=x86
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=

ro.dalvik.vm.isa.arm=x86

libhoudini: What It Means for Developers

libhoudini is a proprietary ARM translation layer for x86-powered Android devices. It allows an app that has NDK binaries for ARM, but not x86, to still run on x86 hardware, albeit not as quickly as it would with native x86 binaries.

Given ARM’s near-stranglehold on the Android ecosystem, libhoudini is hugely useful for Intel and hardware vendors interested in using Intel’s mobile CPUs. Without it, only apps that ship x86 NDK binaries would be compatible with x86-powered devices like the Samsung Galaxy Tab 3 10.1” tablet. Some developers probably skip x86 NDK binaries, because they are not aware of popular x86-powered devices, or lack one for testing, or are concerned over APK size. The Play Store for x86 would shrink substantially from the million-plus apps available to ARM devices, to those that do not use the NDK or happen to ship x86 binaries. libhoudini makes ARM-only NDK binaries usable on x86, giving x86-powered Android devices access to more of the Play Store catalog.

Intel Atom Z3580

Intel Atom Z3580

model name : Intel(R) Atom(TM) CPU Z3580 @ 1.33GHz

ro.product.board=moorefield
ro.board.platform=moorefield

Intel® Atom™ Processor Z35xx

Introducing 「Moorefield」; 2014 Quad Core Processor Family for Android Devices

This year Intel will introduce the new Intel® Atom™ processor family Z35xx (code-named "Moorefield"), which offers an ideal combination of fast, smart performance and long battery life for Android devices.
Based on Intel's 22nm Silvermont microarchitecture, the 64-bit-ready SoC features four Intel architecture (IA) cores for up to 2.3GHz of compute performance.

ZE551ML / Z00A - Intel Atom

ZE551ML / Z00A - Intel Atom 

        Device -- Model -- RAM/CPU

• Z00AD -- ZE551ML -- 4GB/2.3GHz or 4GB/1.8GHz or 2GB/1.8GHz (5.5 in 1080p FHD Screen)
• Z008D -- ZE550ML -- 2GB/1.8GHz (5.5 in 720p HD Screen)
• Z00D -- ZE500CL -- 2GB/1.6GHz

1.

tux@slitaz:~ $ uname -a

Linux slitaz 3.2.71-slitaz64 #2 SMP Sat Oct 10 15:35:50 CEST 2015 x86_64 GNU/Linux

2.

tux@slitaz:~ $ adb shell uname -a

Linux localhost 3.10.20-x86_64_moor-265388-ga4369b3 #1 SMP PREEMPT Thu Sep 17 20:35:29 CST 2015 x86_64 GNU/Linux

3.

tux@slitaz:~ $ adb shell cat /proc/version

Linux version 3.10.20-x86_64_moor-265388-ga4369b3 (jenkins@android01-RS704D-E6-PS8) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Thu Sep 17 20:35:29 CST 2015

4.

tux@slitaz:~ $ adb shell cat /proc/cpuinfo | head -26

processor    : 0

vendor_id    : GenuineIntel

cpu family    : 6

model       : 90

model name    : Intel(R) Atom(TM) CPU  Z3580  @ 1.33GHz

stepping    : 0

microcode    : 0x34

cpu MHz       : 500.000

cache size    : 1024 KB

physical id    : 0

siblings    : 4

core id       : 0

cpu cores    : 4

apicid       : 0

initial apicid    : 0

fpu       : yes

fpu_exception    : yes

cpuid level    : 11

wp       : yes

flags       : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt tsc_deadline_timer aes rdrand lahf_lm 3dnowprefetch ida arat epb dtherm tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms

bogomips    : 2662.40

clflush size    : 64

cache_alignment    : 64

address sizes    : 36 bits physical, 48 bits virtual

power management:

5.

tux@slitaz:~ $ adb shell cat /system/build.prop | grep -Ei 'ze551|z00a|abi|x86|moor'

ro.build.display.id=LRX21V.WW-ASUS_Z00A-2.20.40.97_20150917_1572_user

ro.build.version.incremental=WW_Z00A-WW_2.20.40.97_20150917_1572_user_rel-user-20150917

ro.product.model=ASUS_Z00A

ro.product.name=WW_Z00A

ro.product.device=Z00A

ro.product.board=moorefield

# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,

# use ro.product.cpu.abilist instead.

ro.product.cpu.abi=x86

ro.product.cpu.abilist=x86,armeabi-v7a,armeabi

ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi

ro.product.cpu.abilist64=

ro.board.platform=moorefield

ro.build.fingerprint=asus/WW_Z00A/Z00A:5.0/LRX21V/2.20.40.97_20150917_1572_user:user/release-keys

ro.build.csc.version=WW_ZE551ML_2.20.40.97_20150917

ro.dalvik.vm.isa.arm=x86

ro.asus.browser.uap=ASUS-ZE551ML

dalvik.vm.isa.x86.features=sse4_2,aes_in,popcnt,movbe

ro.config.hwrlib=T9_x86

tux@slitaz:~ $

ZenFone 2 Review: Cheap, Fast, Big, Flawed

http://www.xda-developers.com/zenfone-2-review-cheap-fast-big-flawed    

Contents

o Design, Build Quality

o Performance

  1 CPU & System

  2 GPU & Gaming

o On Storage and Memory

o Display

o Audio

o Camera

o Battery Life and Charging

o A Note on System Stability

o Software UI/UX

o Rootability, Future Proofing and Other Thoughts

o Final Thoughts

Android’s ART replaced Dalvik for many reasons, some of them being that AOT trumped JIT compilation and that Dalvik’s garbage collector was inefficient. Ultimately, it aims to improve app performance and the results have been widely discussed ever since ART’s original optional implementation on KitKat. With better performance and less of a need for native and platform-dependent code, the x86 architecture can benefit as apps become more efficient and do not have as many ARM hooks that need to be translated by libhoudini or whatever method of binary translator that gets put in place. Moreover, developers can port their ARM-based NDK applications to x86 and avoid binary translation altogether for more efficient results (some documentation by Intel can be found here). We hope that ASUS does bring further ART optimizations from more recent and upcoming Android builds to strengthen the process.

Unlock bootloader

Unlock bootloader

5. Unlocking Bootloader (UNOFFICIAL METHOD)

BootLoader Unlock (both ZE551ML and ZE550ML)
http://forum.xda-developers.com/showpost.php?p=61426871&postcount=26
http://forum.xda-developers.com/zenfone2/general/congrats-to-bootlocker-unlocked-t3138547

 
Official bootloader unlock for ZenFone 2 is now available

Unlocking your bootloader allows you to put custom software onto your device. Many developers have created custom ROMs and have had to hack their way into the ZenFone 2 to make this available to powerusers in the community.
Now, unlocking the bootloader is as easy as downloading the utility, installing it, and running it.

Proceed with caution and read below notice before attempting

From the ASUS Support site: Unlock Device App: Unlock bootloader

Utilities (1)
 Version V1.0
 Description

Unlock Device App: Unlock boot loader

Notice:

1. Update your software image to V2.20.40.139 or latest version

2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.

You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.

Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.

It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.

Resources (for Asus ZE551ML / ZE550ML)

Resources (for Asus ZE551ML / ZE550ML)

Asus Zenfone 2 | Resources all in one thread

1. Drivers | ADB installer
2. Recovery Related Stuff (Entering Recovery|Stock Recovery | Custom Recovery)
3. Rooting | Flashing | Applying OTA
4. Changing from CN to WW version
5. Unlocking Bootloader (UNOFFICIAL METHOD)
6. Xposed Framework Installer
7. Viper4Android Related Stuff
8. Adjusting DPI without root
9. NTFS support for OTG devices

[INDEX] Asus Zenfone 2

Click on a Link below for More Info

• Manufacturer's Device Home Page
• Basic Device Information
• Official Stock Firmware
• Device Tools, Root/Un-root/Un-brick methods
• Custom ROMs
• Kernels & Radios
• MODS, GUIDES, and Misc

ASUS Zenfone2 Basic Device Information

Basic Device Information
http://forum.xda-developers.com/zenfone2/general/index-asus-zenfone-2-wip-t3149748

There are many variants of the Asus Zenfone 2, and it is important to use the files for the corresponding device or you may damage your device permanently. They are:

Device -- Model -- RAM/CPU

• Z00AD -- ZE551ML -- 4GB/2.3GHz or 4GB/1.8GHz or 2GB/1.8GHz (5.5 in 1080p FHD Screen)
• Z008D -- ZE550ML -- 2GB/1.8GHz (5.5 in 720p HD Screen)
• Z00D -- ZE500CL -- 2GB/1.6GHz
• ZE500KL -- 2GB/1.2 GHz (5.0 in 720p HD Screen)*
• ZE500KG -- 2GB/1.2 GHz (5.0 in 720p HD Screen)*
• ZD551KL -- 2GB/1.7GHz (5.5 in 1080p FHD Screen)

*The Zenfone 2 Laser has it's own forum available here: http://forum.xda-developers.com/zenfone-2-laser

All of these devices share this subforum, but most of the development is targeted towards the Z00A and the Z008.