So I need some clarification on a few things. I am a dummy and didn't check to see what g-sensor I had before I re-imaged my tablet to android 4.1.1. The screen doesn't rotate when I flip the tablet around, so I'm assuming this is a g-sensor problem. Is there any harm in pushing different g-sensor drivers and basically guessing which one I have until it works (kinda of like pushing touchscreen drivers until the touchscreen works)?
If anyone knows the g-sensor drivers used by the A13 tablets, or more specifically the A13 trio stealth pro 7c (so I can do less guess work) that would be awesome.
have you tried looking here
A13 Forum http://www.techknow.me/forum/index.php?topic=5765.0
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,
i brought a Mpman Converter 10 tablet past week, and i am facing some weird issues and seems no one want's or know to help me. Everything started with the offer, it was advertised that this tablet is running windows 10, but when i brought it i saw on the box it was written windows 8. I was thinking that no big issue and i downloaded windows 10 anyupgrade or what is the name, i left it over night to make the update. When i woke up the tablet was frozen i restarted the tablet but the OS was not starting, i tried startup repair with all the combination but nothing helped me. So i decided to download a windows 10 iso from microsoft and install on tablet, with a lot of issues because the manufacturer didn't gave me any cd with drivers nor on the website no driver is provided i contacted the manufacturer via e-mail but he was not handy at all and send me back to my reseller. My issue is that all the drivers are installed on the OS but the touch screen is not working corectly it got an Silead MSSL touch screen with the hardware ID: ACPI\VEN_MSSL&DEV_1680.
The issue is that the touch screen got an offset when i touch the screen and also seems that the x and y axis is reversed i tried all the drivers what were recommended by others for the similar touch screen.
I can't find any help i hope someone could give me some hints what to do next.
sensor is kionix. if you have driver in device manager problem is from intel (Intel(R) Trusted Execution Engine Interface). install version 1.0.0.1064 (date product 09.01.2014) by intel
Mp man converter 8
Hello. I have the same problème with my tablet mpman converter 8. And i tried to install reinstall windows but the problem persists
Hello everyone, I have been reading and respecting you for a long time.
They gave me a Mediacom tablet with Android to repair or throw away as a favor, I'm not asking for money and I'm not a professional, just self-taught. It basically had half the screen where the touch screen didn't work, so in addition to trying with the "pizoelectric" lighter as seen on youtube and various apps, I decided to try replacing the touch screen as well. Once done, the problem remained as it was. I tried to do the factory reset and now I'm stuck in the installation because I can't click on the buttons to finish the installation. I used to at least rotate the screen and run it on the good half. But now I'm stuck in the installation. I also tried to take a usb dongle to attach a mouse to it, but it doesn't see it, also tried on the smartphone, but it doesn't see it anyway. 1. Confirmed that it is not damage to the touch screen. Can I finish installation via adb shell? What do you think is the problem? is it software? Any advice is greatly appreciated.
Thank you
It's hard to advise anything without writing the model name of the device. Adb host will not work when it is not enabled in the device.
ze7zez said:
It's hard to advise anything without writing the model name of the device. Adb host will not work when it is not enabled in the device.
Click to expand...
Click to collapse
The model is smarpad iyo 10, but I doubt it serves as information, since it is probably an Android 9 problem. I thought it was possible at boot to enable a shell and complete the installation or maybe rotate the screen.
Thank you for answering.
The Rockchip A55 RK3566 processor in the Mediacom IYO 10, supports USB OTG, so a mouse connected to an OTG adapter should work.
Which adapter did you use?
The touch screen for the Mediacom IYO 10 is not outstandingly complicated and has no chipset in it. So the touch is controlled by the mother or daughter board electronics, which you probably did not replace when you replaced the screen.
ze7zez said:
The Rockchip A55 RK3566 processor in the Mediacom IYO 10, supports USB OTG, so a mouse connected to an OTG adapter should work.
Which adapter did you use?
The touch screen for the Mediacom IYO 10 is not outstandingly complicated and has no chipset in it. So the touch is controlled by the mother or daughter board electronics, which you probably did not replace when you replaced the screen.
Click to expand...
Click to collapse
The Otg adapter is from Tek-one to-g-15, it may be that it doesn't work, in fact it doesn't work on the mobile either, I try to change it.
As you said, the touch had no chip, just a connector to the motherboard.
An information that I have omitted may be useful, at the beginning the tablet also had another problem, in some circumstances that I have not explored, the screen or the resolution was resized in half, presumably in the working half. Almost immediately the scaling issue was fixed by randomly activating a gui option in hidden developer mode.
Now, excluding the Otg that I'm going to change, do I have any possibility of continuing the installation via shell?
Thanks for the precious information.
You probably don't have TWRP so you won't do anything with the build.prop file.
The lack of a shell is the result of not enabling debugging in the developer options, available only after starting android.
Look for a working OTG adapter.
Maybe this thread will help you.
Is there any emulator for Amazon fire stick?
If i develop an app for amazon fire stick but I don't have a Fire stick so how can I check my app? Is there any emulator for Amazon fire stick ?
stackoverflow.com