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.
Related
I've got a question I have not been able to find a definitive answer to.
Everyday other day on a blog I read I am seeing someone has created a robot controlled via an application running on a iPhone/Android, using either Bluetooth or Wifi.
But my question is, can an android device function as a wired remote via the usb port?
Is there any IO class for the USB port that can be used to turn on various things and read back various sensor information given the propper platform?
Am I seeking USB Host mode or is that something else?
My goal is to have an android device running an application monitoring various sensors and controlling various other hardware devices with a nice touch screen interface if possible. Since the phone would be located with the control hardware using Bluetooth for this seems silly if I am able to use USB and a cable from the Android Device to the Control Hardware, essentially making the android device the brains.
thanks in advance guys!
Nobody has any feedback on this?
Instructions:
1. Download ZIP file and flash it (Cyanogenmod 12 is what i tested it on).
2. Install in recovery and reboot
3. Voila
Downloads:
nvsystemservices.zip Download here.
Bugreport: Report in this thread. This is still in testing.
Known Problems:
Issues connecting the controller (reboot works sometimes)
No console mode
Audio only routed to controller (and it is bugged aswell)
My thanks goes to:
Steel01
Version Information
Status: Testing
Created: 2015-04-01
Last Updated: 2015-04-01
XDA:DevDB Information
SHIELD Apps for Cyanogenmod 12, Device Specific App for the Nvidia Shield Tablet
Contributors
silasje1, Steel01
Version Information
Status: Testing
Created 2015-04-01
Last Updated 2015-05-26
Reserved
Awesome!!
Current info is going here since I can't truly edit the OP or reserved posts.
Several apps work out of the box on any ROM with correct vendor blobs. The only blobs I've seen have issues are the OMX libs. The ones from Nvidias AOSP work correctly. The easy apps are:
Shield Hub (this includes gamestream and Grid)
Dabbler (full stylus support with palm detection and all that fancy stuff)
No support (yet):
Controller Mapper (I don't personally care to work on this)
Game cast (or whatever the stream to Twitch and such thing is called)
Partial Support:
Wireless Controller Pairing (see explanation below)
Console Mode (see explanation below)
Wireless Controller Pairing:
As of this last edit, all ROMs based on my CM-Shield repo have this functionality. That's virtually all custom ROMs now. Though support may be too strong a term. It kind of works, but with a few caveats.
1. Pairing can now be started from the SHIELD Controller app icon. After pairing, the app will not close, so just hit home or back to get out of it. If the light stops blinking on the controller, it's connected.
2. In Development Settings, the disable usb audio routing option needs to be enabled otherwise the tablets internal speakers will be disabled due to a lib misreading something. I have yet to find a workaround for this. Headphones plugged into the tablet work fine and headphones on the controller work, but is crackly. I expect HDMI audio will work as well, but that is not tested.
3. If the wireless band changes (connecting to a 5 GHZ band from a 2.4 GHZ one or vice versa), the controller will drop and you'll have to reboot to get it back. Not certain what can be done about that yet.
4. Occasionally, I have seen the controller fail to reconnect after both the shield device and the controller have gone to sleep. It didn't happen every time, though, and rebooting will cause an auto reconnect.
Console Mode:
The official app works as expected with one small caveat. If the hdmi cable is disconnected while in console mode, the display will rotate to landscape, but the touch orientation will still be portrait. This should be able to be fixed with another small patch once I know what the app is expecting.
Previously, I made a script that toggles console mode that might still be useful. Touch goes to portrait mode while in console mode and I haven't figured out how to rotate that yet. Other than that, it seems to work pretty well. It just isn't terribly useful until wireless controller pairing works unless you have a bluetooth controller or a keyboard/mouse combo plugged in. I'm also restarting all services and that probably isn't necessary, but I don't know how to track down which ones really need restarted. For general use, this should be put into the control app with a section watching hdmi. And when hdmi is disconnected (and isn't reconnected within 5 seconds or so), switch back to the internal display.
Code:
#!/system/bin/sh
# Toggle console mode
DEVICE=$(getprop ro.product.device);
CONSOLE_RES="1920x1080";
WM_RES="1200x1920";
if [ "${DEVICE}" == "roth" ]; then
WM_RES="1280x720";
fi;
if [ "$(getprop persist.tegra.stb.mode)" == "1" ]; then
# Switching console mode off. Window Manager uses default resolution.
setprop persist.sys.display.resolution "";
setprop persist.tegra.hdmi.primary 0;
setprop persist.tegra.hdmi.resolution Max_60;
setprop persist.tegra.stb.mode 0;
if [ "${DEVICE}" == "roth" ]; then
setprop persist.tegra.panel.rotation 90;
fi;
else
# Switching console mode on. Window Manager uses console resolution.
WM_RES=${CONSOLE_RES}
setprop persist.sys.display.resolution ${CONSOLE_RES}
setprop persist.tegra.hdmi.primary 1
setprop persist.tegra.hdmi.resolution Max;
setprop persist.tegra.stb.mode 1;
if [ "${DEVICE}" == "roth" ]; then
setprop persist.tegra.panel.rotation "";
fi;
fi;
wm size ${WM_RES};
restart;
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------OLD POST:
Alright, info dump.
@OP: you should link or copy over the patches I made to cm to allow controller pairing. And more may be needed to make it stable.
Grid should work out of the box on any ROM that has the vendor blobs set up properly. More or less, just needs the OMX libs from nvidias aosp. Just download from the play store and go, don't bother with anything here. Same for Dabbler.
Controller mapping is pretty much entirely framework and internal ROM changes. To me, this seems pointless to replicate since Tincore does the same thing and is free. But if someone else want to implement it, go right ahead.
Console mode. I have posts for the tablet and the portable in my cm threads about this. I can set some props and reboot a couple times to make it work. It just isn't clean yet. I'm wanting to make this part of an open source control app. I'll add the info here when I have a fewxminutes at my desktop (which might be a few days...)
Controller, the one most people (and me) really care about. Yeah, I kinda made it work, but it's flaky. What really needs to happen is for someone to decompile the official pairing app and figure out the pairing sequence. Then it can be implemented in an open source app and for Linux. I haven't had time to get to that yet. Side note: I've had issues with the controller on stock when booting through multirom. If you have problems, try with a bare metal install, no kexec, nothing extra.
Thanks for the continued efforts to get this working.
The zip was installed with a clean flash, but I have no controller app for me to pair it.
ah ... if they worked. Then im keep stock rom and flashing cm 12.1
On cm 12 the flashable zip works on cm12.1 i dont get the app icon (but the APK are there)
silasje1 said:
On cm 12 the flashable zip works on cm12.1 i dont get the app icon (but the APK are there)
Click to expand...
Click to collapse
Noticed that too. When I did get mine working on CM12 there is no audio on GRID games.
Yeah the audio is routed to the Controller (and the audio that comes from the controller is bad )
I don''t know why the apps don't work. I will wait for the next OTA from nvidia and see if i can make it work then. I anybody wants to try feel free to
The only reason I still like stock is the gamepad mapper. This zip does't seem to fix it on CM12 or 12.1
FoxyDrew said:
The only reason I still like stock is the gamepad mapper. This zip does't seem to fix it on CM12 or 12.1
Click to expand...
Click to collapse
It is advertised as having issues with all the stock features besides GRID, we're all working on this right now though.
CM12.1 will soon reign!
berryman13 said:
It is advertised as having issues with all the stock features besides GRID, we're all working on this right now though.
CM12.1 will soon reign!
Click to expand...
Click to collapse
Legendary
I've been just waiting on someone saying this very thing. Thank you.
Cool, I'm waiting your result (hope dabler and controller paring will be work)
Pardon me for my stupidity. I made an error in the flashable zip. BUT, i fixed it and i uploaded a new version in the Downloads Tab
Please try and report.
on cm 12.1 and 12 does not work, even in the list of applications installed no
Would it be possible to do a TiBu or Parcel backup then just restore them back on the ROM you're using? Is it a vendor issue not allowing everything to work?
Not that easy, unfortunately. The apps that would work like that are already on the Play Store. The controller app requires framework changes like I mentioned in post #3. The controller mapper is integrated into Nvidias Android release, there isn't even an icon to run it. I'm planning on trying to reverse engineer the controller and console apps, but that's after I solidify my CM and Multirom releases. Might be a while yet...
It probably doesn't work in cm12.1 for one of two reasons. 1, the signing keys changed between cm releases. 2, those builds don't have my wifi changes to hackishly support the controller. If it doesn't even show in the list, it's likely the first.
Steel01
romixer said:
on cm 12.1 and 12 does not work, even in the list of applications installed no
Click to expand...
Click to collapse
Don't know what is going wrong but i delete the download untill i have more time to look into it.
Edit:
i will come back when Nvidia has the new ota 3.0 (based on 5.1) ready and add the files then
Sounds good
silasje1 said:
Downloads:
See Downloads Tab (empty for now)
Click to expand...
Click to collapse
Derp, can't find no Download Tab. Yes, I'm that dumb .
Btw, so this on 12.1 is a go?
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?
Hey there! i was at my local store looking for a controller and came across the Steelseries Stratus Duo, i got it and brought it home hoping that it would work nicely with my phone, the exact opposite was true, i was using Bluetooth
and it had horrible lag and often times disconnected i tried to fix the lag and connection drops, nothing worked.
And sense this has no way to update firmware (at-least at the moment) on the Bluetooth side, i am not able to use it in that mode.
I have tested this on multiple devices, some carrying the bt 5.0 chip some with bt 4.2 and some with bt 4.1
the controller says it is using a Bt 4.1 chip (that's what it says on the box)
all exhibit the same issue's as noted above. most if not all are supposed to be compatible, but all of them are glitchy. with this controller.
So i was understandably disappointed, not wanting to return the controller,i tried out something, if you have ever used steam link app for android and plugged in a USB controller? if so the application will ask you if you want to use it with your device? you can choose yes or no, i tried it and was really surprised that it worked as well as it did, absolutely no issues with lag nor random connection drops.
just REALLY SOLID PERFORMANCE.
So, that gave me an idea, what if i made a stand alone application that allows us to use the included USB receiver with android?
and add extra functionality on top of it. such as emulating other controllers for better app compatibility.
I was looking for a driver or something that can pull access from that receiver. something i can integrate into my project.
As far as i know the controller is just seen as a Xbox 360 controller so i was wondering if there is a Pre-made driver for integration with apps, that would save me a lot of time and would simplify the process quite a bit.
The app will be free and will be given to people on my discord and on host sites.
Here's a link to the discord server i created.
nevermind its not letting me post links (thats fine)
I created the discord server because other people are having this issue as well.
and that's where all the progress will be recorded. also if you have this controller and are experiencing issues you can join too!
Any help would be greatly appreciated.
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