Related
Just a heads up - I just got a dock care of one of the XDA members here (their donation to me - and thank you, btw). This is the zPad dock. My tests were all done on TnT Lite 3.1.2.
HDMI "just works" - plug it in and the output will show up on your HDMI output (in my case, it was a TV). Sound is also passed through, but seems to have a slight lag.
Ethernet "just works" - plug it in and the device is on the network. I'm not sure if there's a way to disable it, other than pulling the Ethernet port out.
Finally, the USB port also seems to work - I tested it with my USB keyboard. So, it seems like the TnT devs already built the kernel / UI with the dock in mind. I haven't tested the VEGAn build, yet.
EDIT: Just tested VEGAn 1.0.0 beta 4. USB / Ethernet / HDMI all seem to work. In the case of VEGAn, I actually tested HDMI off my PC monitor (which happens to have some cheapo speakers on them) and there's no audio lag. Perhaps it's something device specific, or cable specific.
EDIT2: Ethernet is now failing on VEGAn. I guess I spoke too soon.
Thanks for the tests. As for Ethernet, I wonder if u need to disable the wifi on the gtab when using the Ethernet on the dock?
Sent from my SPH-D700 using XDA App
More Ethernet testing - it seems that it's a DNS issue of some sort. IP ICMP tests definitely work.
Does HDMI out work without the dock being powered?
roebeet said:
More Ethernet testing - it seems that it's a DNS issue of some sort. IP ICMP tests definitely work.
Click to expand...
Click to collapse
Yes, LAN is working. It appears you must boot Tablet with LAN connected and tablet in doc for it to recognize it.... I say recognize it, but when you launch browser you get a notice box that says page can not be displayed due to no connection.. but you just check ok, the box goes away and you are online.
bigwh00p said:
Does HDMI out work without the dock being powered?
Click to expand...
Click to collapse
HDMI and LAN require the doc to be powered.
Can we get a link to the dock you bought?
Thanks for the confirmation! Looks like I'm going to return this and get the elocity just for that HDMI port...
Sent from my Nexus S using XDA App
insight3fl said:
Yes, LAN is working. It appears you must boot Tablet with LAN connected and tablet in doc for it to recognize it.... I say recognize it, but when you launch browser you get a notice box that says page can not be displayed due to no connection.. but you just check ok, the box goes away and you are online.
Click to expand...
Click to collapse
Interesting that I can use the internet, I can retrieve my comcast email, but I could not run my exchange email. When I would refresh it, it just sat idle. when I resumed my wifi connection, it immediately downloaded my messages.
The LAN does need some work here by the Devs for sure. It also stopped for some reason and I had to reboot to reconnect it.
Not sure if there is a problem with my device or if the feature has even been implemented, but when I try to enable the MTP option under Settings>Storage>USB connection - it doesn't work, it just switches right back to USB Mass storage.
Here is a logcat of the event
Code:
E/UsbDeviceManager( 276): waitForState(mtp,adb) FAILED
E/UsbDeviceManager( 276): Failed to switch persistent USB config to mtp,adb
I/dalvikvm( 3933): Total arena pages for JIT: 18
E/UsbDeviceManager( 276): No known USB function in updateUsbNotification
I/StorageNotification( 419): UMS connection changed to false (media state mount
ed)
D/PhoneStatusBar( 419): addNotification score=-10
E/UsbDeviceManager( 276): No known USB function in updateUsbNotification
I/StorageNotification( 419): UMS connection changed to true (media state mounte
d)
I/StorageNotification( 419): UMS connection changed to true (media state mounte
d)
If anyone can offer any info or help I'd much appreciate it.
Edit: just saw that the Nexus S has a Q&A forum, news to me, if a mod comes through please move thread if thought appropriate.
You need a kernel with mtp support. The CM10 kernel doesn't. Try Marmite in the Nexus S 4G dev section
Sent from my Nexus S 4G using Tapatalk 2
I'm using it myself it works perfectly. I'm honestly surprised it took this long for someone to finally build a kernel for ns4g with mtp. i've been waiting for it myself...I find it much easier!!
Thank you much, flashed the kernel you recommended(which seems to be pretty great all the way around) and I have MTP.
hp420 said:
I'm using it myself it works perfectly. I'm honestly surprised it took this long for someone to finally build a kernel for ns4g with mtp. i've been waiting for it myself...I find it much easier!!
Click to expand...
Click to collapse
Yeah, I have a dock and it charges and works great as a desk clock, and with MTP it can always have a data connection to my computer.
Here are some crappy pics
http://minus.com/lbkYoQQTj20cak
http://minus.com/lXr5oZss4pwjp
Glad you found the kernel and mtp working fine for you.. Marmite is a fantastically stable kernel. And the developer bedalus is a really nice and engaging developer..
And yeah.. MTP > Mass Storage.. Soon as I saw marmite had MTP I jumped on it like hot cakes..
Edit: I had that dock and returned it.. If a light breeze hit it the volume buttons would be pressed because the little groove wasn't recessed correctly.
I'm now running 10.1 and MTP seems to have been removed from CM entirely. Anyone know if there's a way to enable it if you have an MTP enabled kernel? Or do we need to wait for CM to put some code in to support it in the ROM?
USB mode switch for SGS1 on CM
koeylondon said:
I'm now running 10.1 and MTP seems to have been removed from CM entirely. Anyone know if there's a way to enable it if you have an MTP enabled kernel? Or do we need to wait for CM to put some code in to support it in the ROM?
Click to expand...
Click to collapse
Search google play and download "USB mode switch for SGS1 on CM" (needs root).
Kang-A-rom
What is it?
a kang of purity rom with a few added functions. It is based on the hard work of others and no credit to me is implied, other than merging and building. All sources are available at:
https://github.com/lostdeveloper
Features:
* Full dac support, on boot, hot plug, volume control
*OC of CPU and GPU
*OTG while charging, fastcharging
*support for most dvbt tuners including the newer r820t tuners.
*automatic mounting of ntfs and exfat storage drives with read and write support
*easycap support, plug n play (requires carcam app)
*firm sleep
*wakelock blocker
*usb/bluetooth tethering (unconfirmed)
*more, and more coming....
Kangarom V2 03/09/2014
Changes:
*plug and play any easycap device (needs carcam app, and one model also needs firmware)
*added support in ramdisk and frameworks/base for USB tethering and bluetooth tethering. I have no way to test this, it needs testing, and I need logcats with any issues. I am completely unsure If I have everything here.
*included dashclock and simple explorer, both open source and useful, while not consuming a lot of space
*Wakelock Blocker, selectively prevent certain wakelocks to save battery
*all purity rom updates from DariosF
Download
http://d-h.st/qOT
________________________________________________________________________________________
Older Changelogs and
Downloads:
Kangarom v1, initial release
http://d-h.st/QXB
_____________________________________________________________________________
other info:
-some models of easycap may also require a firmware to function properly. These firmwares must be obtained by the end user and cannot be included by me for legal reasons. However, they can be downloaded freely from proper sources.
-use of dvbt tuners requires a script to load the needed modules and set up for chrulri's droidtv app.
-firm sleep, and dac on boot require crue's powermanager app to set options for firm sleep, fixed install mode, and fastcharge in hostmode
**The latest version of crue's app may be found here:
http://forum.xda-developers.com/showpost.php?p=50265682&postcount=411
Credit is his, so hit his thanks button.
More INFo about this can be found in my kernel thread, as well as links to the source code used for this:
http://forum.xda-developers.com/showthread.php?t=2558717
Im working on a tilapia build.....not yet.
feel free to ask any questions... Im not too concerned about hardcore dev stuff only. Anything that helps others find answers works for me.
reserved
one more.
would be cool if you could post more information for the dvbt driver
i used mine on usb rom as radio with wavesink and this driver: https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de
do i need the driver app now or only wavesink? or wavesink and a script?
EDIT:
and should i flash your kernel over the rom or is includet?
Awesome. Going to try this out right away. Thanks.
michiil said:
would be cool if you could post more information for the dvbt driver
i used mine on usb rom as radio with wavesink and this driver: https://play.google.com/store/apps/details?id=marto.rtl_tcp_andro&hl=de
do i need the driver app now or only wavesink? or wavesink and a script?
EDIT:
and should i flash your kernel over the rom or is includet?
Click to expand...
Click to collapse
Yea....I wanted to get the build up for you all, but I need to set up the OP properly just really busy. Kernel is included already...... dvbt will work as it use to with sdrtouch and other radio apps that use the userpace driver. To watch tv youll need to use a script to insmod the right modules....again ill link to the exact post when I have time, just search my kernel thread for r820t you will find it.
While these modules are loaded, your radio app wont work....it depends on that userspace driver and it wont have a device to "drive" because it is already loaded at the kernel level. So, the solution is a "load" script for kernel modules, then watch tv, then, an "unload" script...... and now your radio app will work again.
I will seriously fill those first three posts will all the needed info, but Im swamped right now with work. All the info is there in the kernel thread for now just need to search.....sorry.
Flashed this and worked right out of the bag, no need for external OTG apps. Ran PAGAPPS mini modular and is perfect for my needs. This came just in time as I'm getting my DAC in the mail tomorrow and plan on putting this in the dash of my car very soon thereafter. Thanks for all your hard work!
The only thing I think would be awesome is if you could incorporate volume buttons on the nav bar. I've never used Timur's rom but saw some videos and saw he had those. If not it'll be easy enough to get by. Thanks again!
sreister said:
Flashed this and worked right out of the bag, no need for external OTG apps. Ran PAGAPPS mini modular and is perfect for my needs. This came just in time as I'm getting my DAC in the mail tomorrow and plan on putting this in the dash of my car very soon thereafter. Thanks for all your hard work!
The only thing I think would be awesome is if you could incorporate volume buttons on the nav bar. I've never used Timur's rom but saw some videos and saw he had those. If not it'll be easy enough to get by. Thanks again!
Click to expand...
Click to collapse
Yes, its kindve on the list......sort of. The new kitkat framework only supports five total buttons on the navbar. Purity allows you to add two more already, but due to framework limitations I think it will be difficult to do this in a stable way. I was browsing around and i noticed that carbon ROM has a more involved navbar framework where you can set the navbar to launch volume control via "slim shortcuts." I got excited and thought it just needed to be cherry picked but....... I downloaded carbon ROM to try it and when i set it up the systemui crashed and repeatedly crashed until I rebooted. Once rebooted it once again crashed, I had to re flash the ROM and the same thing happened, so no go. This behavior is what I read should be expected if you try anything other than a menu button or a search button, or keyboard cursors on the kitkat navbar. In other words, any other button type would need to be fully implemented into the framework, no shortcuts. Im still researching this.....as time permits
The more likely scenario involves the quick launch shortcuts. With this ROM you can set up the home button for three on screen shortcuts via long-pressing the home button. If you download a volume control app, not a widget, an app, then you could use this quick launch method to access it. Or, you can already set it to open up settings>sound with the activity picker. I use "slider widget" for now.....simple desktop widget for volume control.
Super super suuuppperrrr silly question, but this is 4.4.2 right?
ZenInsight said:
Super super suuuppperrrr silly question, but this is 4.4.2 right?
Click to expand...
Click to collapse
Absolute latest from Google, yes.
This works pretty good on my in dash nexus 7. Couple of issues though... I use Bluetooth tethering from my phone, the tablet will connect but I have no internet connection. Also, I use an external microphone for voice commands, but it doesn't work on this ROM. I normally use AOKP ROM with Timur's kernel, this disables the internal mic and allows me to hook my external mic directly to the inputs of my Behringer UCA202 DAC. Also, the easycap issue that you've already mentioned in your kernel thread. Good work so far!
Sent from my SGH-I747 using xda app-developers app
And it goes in as the daily driver. Thanks for your efforts.
Sent from my SM-N900T using Tapatalk
gregthomas129 said:
This works pretty good on my in dash nexus 7. Couple of issues though... I use Bluetooth tethering from my phone, the tablet will connect but I have no internet connection. Also, I use an external microphone for voice commands, but it doesn't work on this ROM. I normally use AOKP ROM with Timur's kernel, this disables the internal mic and allows me to hook my external mic directly to the inputs of my Behringer UCA202 DAC. Also, the easycap issue that you've already mentioned in your kernel thread. Good work so far!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I did not know about the external mic in usbrom.... Im not sure how easy it will be to figure out, but usb tethering and bluetooth tethering I can kang from cm11....
Ive got a fix for easycap devices as well..... if tilapia build tests well then ill try the tethering thing next.
redeyedjedi said:
I did not know about the external mic in usbrom.... Im not sure how easy it will be to figure out, but usb tethering and bluetooth tethering I can kang from cm11....
Ive got a fix for easycap devices as well..... if tilapia build tests well then ill try the tethering thing next.
Click to expand...
Click to collapse
Its actually a combination of Timur's kernel and AOKP ROM, not USBrom. So I guess the kernel is what makes it work because if I run plain AOKP and the kernel that comes with it, then it operates the same as your ROM does... internal mic works, DAC inputs do not. I install AOKP and then Timur's kernel over top of it. Not really sure if it was intended that way but its the only way I've been able to get the DAC inputs to work. I'm more than happy to do any testing you need... I'd love to see an in car useable 4.4 rom as I'm sure a lot of the other "android in car" crowd would too!
Sent from my SGH-I747 using xda app-developers app
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Kuchar09 said:
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I noticed this too. I installed Stickmount and it seemed to work OK after that.
Sent from my SGH-I747 using xda app-developers app
Kuchar09 said:
So I've tested this a little today and DAC is working on boot every time which is awesome! One thing I did notice is if I boot with DAC and flash drive my flash drive isn't recognized until I unplug the flash drive and replug it in. Anyone else notice this?
I'll have to do more testing after my exams but just thought I'd see if anyone else has experienced this.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hmmmm..…...does it remount for you after deep sleep?? Or do you have to replug after that too?
I guess I'll add this to the list. I'll go test this out. I think we could use the jellybean vold if it mounts on boot.
redeyedjedi said:
Hmmmm..…...does it remount for you after deep sleep?? Or do you have to replug after that too?
I guess I'll add this to the list. I'll go test this out. I think we could use the jellybean vold if it mounts on boot.
Click to expand...
Click to collapse
Haven't tried deep sleep but I just tried booting it up and it didn't show so I unplugged power for my y-charge cable let the screen turn off then reconnect power and the the flash drive showed up in the file system. So this isn't a huge issue just looks like a little something might be missing.
Sent from my Galaxy Nexus using xda app-developers app
does this kernel extend otg+charge functionality to properly sense charging after boot (exactly as plugging in a wall charger)?
I've tried several kernels and they all have the same behavior in that they do not show a charging battery, (only in the pull down notification). this makes Tasker unable to know that power is actually plugged in.
issue is described here in relation to USB Accessory Charger
http://2dindroid.wordpress.com/2013/09/01/more-notes-on-usb-otg-charging-nexus-7-2013/
http://en.wikipedia.org/wiki/USB_OTG#OTG_micro_plugs
EDIT: just realized i was linked here from the Nexus 2013 forum.. ignore the question.
This is not directly rom related but since I assume most people here are doing a fixed install I will ask here.
So during the average commute I am running waze, torque, and Spotify.
I can't seem to catch my tablet up on the charging. During the drive it just slowly goes down while (maybe 1% over a hour). I am using a startech powered USB hub with a powered otg cable going to the tablet. The power side of the otg is plugged into the hub which should provide ample power to charge the nexus.
Is it possible for the nexus to draw more than it is capable of charging? Should I be focusing on my charging selection? Anyone else having a similar issue?
Can anyone tell me an accurate way to measure the draw being used by the tablet and the charging current?
My next option is a hardwired 3amp charger with a toggle switch that will either route the power to a source that is only on when the car is running and the other side of the switch will route it directly to a lead I have coming from the battery (attempt to get ahead while I am grocery shopping or times when I am only out of the car for an hour or so.)
Sent from my SM-N900T using Tapatalk
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 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.