Any of you out there have any information on using the toolchain to make a custom firmware for the SW1? It's essentially a paperweight now since I no longer have a cell phone, but I'd love to be able to pair it with my windows tablet and do some custom programming, ie starting off with a simple firmware that pairs with my tablet and then displays bitmaps sent to it, then relaying touch and accelerometer data back to the tablet. I have the programming experience to do this, but unfortunately, I have no idea how to pair the watch to my tablet with the stock firmware (it doesn't show up during a bluetooth device search on the tablet) and there is not enough documentation with the alpha toolchain to write a simple firmware replacement that enables pairing.
Related
In short: Is it possible to cluster, network or push device output from one device to another, share storage devices and network/gps interfaces?
The long version: I have been wanting to build an in-car device that would store media and act as a gps and what not, but haven't found a way that I want to implement it yet. I was thinking if I found a x86 port of android, got most of the voice stuff working, I could have a headless device that I could store music on and use as navigation. I know the phones are capable of that, but if I want to keep say 500 gb of music on me, how does one do that?
My thoughts were if it were possible to either cluster or network an installed android powered unit to an android powered phone, I could always have network access from the unit in the car and share the gps from the phone, or have the phone access the storage from the device (not through dlna, but the music app seeing it as physical storage) and allow me to push the output from the in car device to the phone and let me interact with the system how ever I need to I could accomplish a form of in-car entertainment.
I figured that there could be apps written that would let the in-car device act as a headless unit, with its only interface being audio, it could store navigation directions/maps and what not, so if I didn't have the phone that day, I could still navigate to where I needed to. The phone and the device could constantly be in communication with each other if the car was parked by a wifi hotspot or something, so if I chose to navigate somewhere when I was at home, the car would already have the directions. I could also have it pull any media changes through wifi, and always have an updated media library.
I know the phones are fully capable of doing this, but for most of it, you have to have a window holster for the car to use the gps, and wires running for audio and charging and what not, but if there were a way that the in-car device could be hardwired to the audio system and left alone, the phone could stay in my pocked, be linked via bluetooth and I could have a small button-pad or something that would allow me to initiate google voice search, control the media player and interact with navigation. The whole thing with linking the phone and device together would be so the mobile network could be shared between android devices and the incar device could pull the information it needed. The thought of the display sharing was in case I needed to interact with the incar device.
I know what I am going on about is specific to me, but my thoughts behind it were if it were possible to do at least the network sharing (with out tethering or mobile hot spot blah blah blah) that android phone and tablet owners could do the same thing. They could share their mobile network through their tablet and have a tablet that would be always connected, would share mailboxes with the phone and basically act the way the Blackberry playbook is proposed or how the Palm Foleo was supposed to work. If the devices had a network ability of some level, the tablet could pull text messages, email messages, contacts or any other sync-able item.. That way, this wouldn't just be done for my benefit, but it would take tablet and phone owners to another league. Two devices that share the same information from one source and don't have to sync with the same servers twice. It would take a lot of redundancy out.
I hope you guys can see usefulness in my idea, and can shed some light for me.
Sorry from bringing this back from the dead, but since I never got any responses I'll add a bit more..
Does android have anything that would work like blackberry bridge between two android devices?
Droid Vnc server and androidvnc works fine for screen sharing. What I really like is the hpc aspects to CPU cycle sharing over wifi/nfc. Really interesting possibilities.
What I am looking for is to have the ability to use two separate android devices, but have them communicate via wifi/bluetooth or what ever and act as the same device in the sense that when the device with the data plan gets a text message or phone call, the notification goes through the other device that would be physically docked to audio equipment or what ever...
I have a Droid X, Droid Incredible, Droid Pro and a first gen Droid laying around.. Currently the Droid Pro is my in use phone.. The rest are just laying here. I want to be able to dock one of the others in my car, turn the GPS on, link it to my droid pro and have the other phone use the droid pro's active data connection for guidance/searches etc, and it would be docked to car audio, so it would need to access the pro's sd card, and have access to the pro's phone audio, or the ability to route calls from the pro to the other device via bluetooth or whatever, not by call forwarding.. This way it would be a sort of infotainment/telematics system..
Think of the possibilities this would open up for android tablets etc. If You could reply to text messages from your tablet because the tablet is linked/bridged to the phone in your pocket... That would make these tablet/laptop combos more appealing because it would the perfect convergence between tablet and phone.
Oh, and I guess, the other thing is that I have multiple cars, so one device would go in each car, and then when I got in the car, the one in that car would link with my phone, and everything would be the same, car to car, or device to device...
I guess another way to bump this:
Would it be possible for an app to do ADB to ADB via bluetooth or something, because then an app could be written like pdanet that would allow the network to be shared at least?
I dont remember the name of the app I think the name of it is Dashboard? and it will store/push all texts/emails etc. to every device u have dashboard installed on...Best buy has an app kinda like that too...Like the Idea of the screen sharing is that kinda like remote desktop/control?
I just search how to neywork cluster android came across your post ..... if you use the Google apps like Google play music/maps as well Google hangouts since with Google voice you can easily do what you want with out the need for both devices being together you can upload 50000 songs 9n play music for free and any device with ur hangouts and voice will receive ur calls and email notifications .....just need to make sure have Internet
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?
Hi there
I'm embarking on an ambitious project and i was wondering if anyone could help me by giving suggestions.
I am making my own home automation system, and I already have the necessary hardware to get it up and running, but I want to take it a step farther.
I have this (Use google translate lol) http://cba.sakura.ne.jp/kit01/kit_399.htm kit, which is basically a set of 8 relay switches that can be used to turn on and off mains devices (such as lights, powerpoints, ect) that are controlled by a computer through a DB25 printer port. I also have an old Dell D600 laptop that has said printer port, and the software needed to drive the circuit board. This is all well and good, as everything is working so far, but before I bother to install this thing in my roof and hook it up to control my lights, power points, ect, I was wondering if there is a way to use my android phone (HTC Legend, unrooted ) or tablet (Motorola xoom wifi rooted with Tiamat, o/c to 1.7ghz) to control this board through a computer.
I already have a client that remote controls the computer (splashtop remote), and I can achieve this with some difficulty by remote controlling the computer and using the PC software through my phone/tablet, but I was wondering if there is an android home automation program and its PC client service that supports DB25 printer port pinout settings, so I could directly control the circuit board through the app, like the leading home automation apps already available (minus the extremely expensive proprietary hardware that you need with them). If not, has anyone else considered developing one? If anyone could give me any help on this it would be greatly appreciated.
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.
I've recently started flying quadcopters (DJI Phantom 4 Pro & 3DR Solo). I've been using a Gen 3 iPad to display inflight video and telemetry which also augments the handheld controller. Thing is, iPad brightness is unimpressive in sunlight and there are android apps for the 3DR that are not available to iOS.
So I went to Best Buy and purchased a Samsung Galaxy Tab S2 8.0 with a fairly bright OLED display. I was operating under the deluded impression that the device would USB tether to the Phantom and 3DR controllers as seamlessly as the iPad. It didn't. Specs on the android tablet are as follows:
Device: gts28vewifi
Model: SM-T713 (T713XXU2APK6)
Build: MMB29M
OS: Samsung implementation of Marshmallow 6.0.1
On board memory: 32 GB
External SD memory: 256 GB of U3.
The first issue that I immediately noticed while attempting to connect the Samsung tablet to the Phantom Controller was the small window containing three app icons that repeatedly cycled open & closed as soon as I connected the USB cable from the Phantom controller to the T713 tablet. I started fooling around with setting USB modes (Charging, MTP, PTP, Midi, etc.) thinking that there was a mode incompatibility with the Phantom controller. Nothing seemed to work.
So I put the tablet into Developer Mode, enabled USB Debugging, and flipped the OEM lock off. I fooled a bit with trying to set a compatible mode through the Developer interface without much success. Oddly, when I plugged the iPad into the controller and verified connectivity, then unplugged it and plugged in the android tablet, the android tablet worked fine. (until I unplugged the USB cable. Reattaching the cable after detaching did not reinstate connectivity.)
After fooling around for over 4 hours without any reliable success, I decided that maybe Samsung's USB implementation on this WiFi-Only tablet was less than stellar and I should look at rooting the T713 with a build that implemented USB more effectively and reliably than Samsung's implementation (maybe Nougat?).
I'm an android virgin for all intents and purposes. I've done a fair amount of work on different flavors of Linux, OS X, iOS, and Windows over the years so I assumed that for a first timer, rooting the T713 would not be trivial. I spent several hours reading up on the protocols and tools for rooting, and specifically as it related to the T713. The signal to noise ratio of online information, especially with respect to the 713, appears to be fairly low. But I did find and use Odin (3.07) to install the TWRP 3.0.2-1 tar file according to one online article. I haven't made any further progress beyond that.
After booting into TWRP I noticed that (1) I could tether between the tablet and a Windows 10 machine and eventually get "adb devices" to return a serial number as well as reboot the T713. But I've not been able to get fastboot to connect nor have I been able to upload SuperSU to the tablet. Checking tablet's log, entries complained that the T713 couldn't mount /data and was unable to find the crypto folder. Then I read that /data needed to be formatted (after I had already tried unsuccessfully to wipe it. Okay, my bad. Can't wipe an unmounted device. I get it.) I did, however, manage to get TWRP to format /data.
Thing is, I "assumed" that /data was formatted since the terminal output didn't give any indication of anything in progress. So I think I must have rebooted the T713. The problem now is that the I've had a slowly flashing "Samsung" splash logo throbbing on screen for the past 4 hours; and I think it's looking at me funny.
I've tried to boot it into Recovery Mode and Download Mode without success. TWRP no longer loads. I'm somewhat lost at this point and would appreciate it if someone could point me in the right direction, or link me to some current material on how to either get back into Recovery Mode, or alternatively help me figure out why I am unable to re-flash the tablet.
Thanks