I have Poco X2 this Option can be Helpful to many and may work in other MI or Poco Phones
Tap on Kernel version till it says entering CIT Here you can test all your Hardwares take look at screenshot I have posted below.
You can also see additional tools like
Get Logs
Bluetooth test tool
Wifi test tool
Wifi sniffer tool
Modem test tool
And some of Calibration tools like gyro / Camera / Speakers / ACC / Touch Sensor
It's just for testing hardwares. Xiaomi's QC part of production line may use it. There's no "calibration feature".
Related
I bought new tablet Hyundai A7.
Accelerometer does not working. Do someone recognize where accelerometer is on board?
ps: usb connector is already damaged It is a reason why I disassemble it.
The accelerometer is a very tiny IC. about 5x5mm. Hence identifying it from the images you have provided is very difficult as the print on smaller ICs is not readable.
What you can try is find out the name of the sensor h/w from the sources or run some sensor test apps and see if the sensor-HAL reports the name.
Then it will be a "simple" matter of looking up that IC on the motherboard.
BTW, whats your interest in finding the accel-IC?...
If I found it, Ill try change it .
I hope..
This all relates to my experimental Android-x86 (x86_64) builds (http://forum.xda-developers.com/win...-jun-2015-android-x86-lollipop-5-1-1-t3125035). Any and all help is appreciated!
One interesting note is that if I use the debug boot item, I cannot boot as the type cover keeps disconnect and reconnecting in the console, or at least, some of the devices inside of it do.
Sensors output (from Linux, using an iio service for systemd - github.com/hadess/iio-sensor-proxy ):
http://pastebin.com/raw.php?i=Jf2MX3Kt
Could someone please tell me how to get those sensors working under Android? I believe the magnetometer is used to detect if the type cover/keyboard is attached or not, which may relate to the crash when it is removed or reconnected to the device
The NTRIG devices are related to the bluetooth pen, which I believe we should be able to also get working, since I think some examples of pressure sensitive pens are out there
dmesg (android):
http://pastebin.com/raw.php?i=e0gmP91R
note the i2c issues and others - there's an LKML topic about the i2c errors, and it implies they aren't truly fatal
audio devices are detected, but I get no sound output on my builds...older kernels had working audio
DRM is loaded but opengl is null under the tablet information tab
Logcat, with the keyboard disconnect/reconnect crash:
http://pastebin.com/raw.php?i=fzgSabgV
Halp! I have no idea what I'm doing yet, especially with Android and it's codebase, as I'm more of a vanilla Linux person at the moment. I really want to learn and help and get this thing working!
Thanks everyone!
Just so you all know, rbg's 32 bit build of Kitkat is rock solid and only lacks support of sensors and volume rockers: https://groups.google.com/d/msg/android-x86/q-B7lrRzeiM/5IJ-J_J13s0J
I tried rbg build(android_x86-5.1.1_r13-20150831.img) from a live usb(SP3 i5 4gb ram), made the usb with rufus; Rotations wasnt working. Rotations+pen input broke touch input alltogether. And i could not see if the tablet was going to deep sleep or if it scaled cpu frequencies. Any ideas or sugestions for someone that even though loves windows for desktops is really looking for android on a tablet? Would i get better results if i install? How would i install to get completely rif of windows 10?
Edit: Found the 7 September build with bluez integration.
https://groups.google.com/forum/#!p...aZ7E2pFh/android-x86/F4IVDDuul2w/8Tt1Mz67FgAJ
Ill see if it works better.
This is a windows tablet, but I think it would be cool to have this run android as well, so I tried a few emulators running under windows 10, but they are very slow, unstable or didnt run at all. Doid4X, an Nox worked, Andy refused to start).
I kept the Nox App Player, cause that was the one I found most responsive of these.
Perhaps the fact that they barely meets the minimum RAM requirement is a major cause for it being slow.
Then I decided to try the android-x86, which is not an emulator, but an andoid port to x86, and will run natively.
The Lollipop EFI image does work as a live usb media , and I was able to install it to another usb stick, but that got stuck on the aandoid logo when booting. The 4.4r3 EFI image did work better, and was able to install to a second usb stick and boot up into android.
I must say that android-x86 did impress me. It feels quite quick and responsive, and any app I have tried so far does run. Even MineCraft PE works well. The display and touchscreen works well, and volume buttons works.
There are a few driver related issues though, here is a list of some things not working:
- onboard wifi
- onboard Bluetooth
- Sensors (auto rotate will not work)
- Audio out and mic
- Power button
- Battery status
- Camera
I did a few tests, and as a workaround I did use an external usb wifi adapter to get internet working. Also connecting a usb headset with mic did work fine, external keyboard. Also a non branded bluetooth adapter was accepted and the BT icon was enabled, but it didnt find any devices when searching. Even a logitech webcam did work with opencam.
Given the current state of andoid-x86 on this tab, it doesnt make sense to partition the disk to get a dual boot. But if there was working drivers for wifi and audio etc, this could be a decent android system.
Now the android version of the tab 8 looks quite similar to the w1-810, so that makes me wonder how much of the hardware components that are the same. And if it may be possible to get the drivers from the original android to work on android-x86.
I will try to list the hw configuration as I can read from devicemanager/drivers in win10:
wifi: broadcom 4330 / Sound: intel SST audio device / camera: Intel Imaging signal processor 2400 / Bluetooth: BCMBTBUS / Sensors: BMA2x2 ( BMA250E) / Battery control hardware ID is PNP0C0A
Any ideas on how to get these things working would be great.
forum administrators:
I did tag this thread with iconia-tab-8, but for some reason it will not show under "Acer Iconia Tab 8 Discussion" list.
Did I miss something, or doesnt the tag system work properly.
Is there anything I can do to fix this?
I also have this tablet and I am also eager for installing fully functional Android on it. Please guys help us on this. Thanks in advance.
News about Acer Iconia Tab W1-810 with Android
Hi guys, some new about it?
Hello experts.
I am a software engineer and currently working on an evaluation module from TI (Texas Instruments). I have a AM5728 Evaluation Module with me and I have successfully compiled Android SDK 5.03 (8.1 Oreo) on it. After compilation, I found that camera app is not working (black screen for a first run and getting crashed on subsequent runs). It seems to me that board is not able to detect the camera device/module even though it is attached to the board. I probably think it is related to camera HAL issue.
However, the USB camera works completely fine when attached to the EVM and is verified using simple usb cam application. The system camera is not being detected at all.
Therefore, I would like to customize Android at a source level and add code to automatically switch the default camera to the one connected by USB when it is available. Or if switching dynamically is not possible then disable the primary (built-in) camera and make USB (external) camera as the default one.
This way all applications should detect the external (USB) camera as the primary camera. For example, if I open camera application then the device take the picture from the one which is connected via USB.
I have the Android SDK source code available with me, but I am not sure how to proceed.
Really appreciate your help.
Thanks!
hey @devashishtiwari.
I am having a similar problem. Did you find a solution. if yes, please contact me at [email protected], its really urgent.
I found it very usefull on my old phone (galaxy s9). My current smartphone is Samsung Galaxy A10s which is the low end smartphone and ofcourse no nfc on my current phone. Is it possible to install like an NFC tools or something? (Does that tools actually exist?)
NFC is a radio technology that generates its data stream via a magnetic field. Knowing this you easily can see that a device not having related hardware implemented never will be NFC capable.
jwoegerbauer said:
NFC is a radio technology that generates its data stream via a magnetic field. Knowing this you easily can see that a device not having related hardware implemented never will be NFC capable.
Click to expand...
Click to collapse
Which means it is impossible to do?