Guys,
I have a project where I need to record some data in a dark environment and I need something reliable like a physical number pad with obvious buttons to reduce input errors. To store that data I need some sort of reliable device and Pebble seems like a really good potential option.
I have zero experience with one. If I pick up a bluetooth number pad, does anyone know if the Pebble would support it and be able to essentially read it? I have a friend who can code what we need for it but he's not sure about the input device.
Thanks.
Related
Wireless phone jack extenders - by sky
Original product can be seen here
http://www.beststuff.co.uk/store/RTX-Wireless-Telephone-Extension-Base-Unit-and-One-Extension.htm
or really anywhere just by searching for "wireless phone jack".
Known manufacturers are Philips, Phonex, RTX.
Problem: ones SKY gives you when signing on for multiroom *APPARENTLY* don't forward incoming calls.
Meaning phone attached on the pass-through of the main unit gets the calls, slave devices don't.
If anyone happened to hack one of these I'd like to have some info.
They use some strange screws (more star-like than torx, I have to get the screw-drivers at work as I don't have at home) so I can't open them right now.
Greetings,
I'm making a school project and I want to make a control pannel for the samsung galaxy S using the TRRS female jack. (It's the audio insert).
When I bought the phone I got something like this with it, but it only has 1 button, u can use it for play/pause or to aswer incomming calls. I want to make something like this with more buttons, for example next song, previous song, play/pause to control an app.
So basically what I want to know are the following things:
1. How does the TRRS work on the Samsung galaxy S?
Tip = Left Output
Ring = Right Output
Ring = eather Ground or Function?
Sleeve = eather Ground or Function?
Does anyone know which one it is. Than the next, how does the Galaxy S messure the input? I believe it uses a function with different resistors so the ground will have different values in Voltage, and a specifik voltage is a different function?
Does anyone know how this works? Maybe I got it al wrong.
2. So if we have an incomming signal by solving the problem of question 1, what does the phone do with the signal? Does it make an event of the input or something?
In other words, what does the Android system or the phone do with the incomming signal and how can I use it in my application?
I hope theres someone out there with answers, and I'm sorry if I'm not specifik enough, it's my first school year so I don't know alot about it yet and theres not alot information about this on the internet.
Thanks for you help and time!
Mitchell
If you go to Samsung site I think you can get all the device service manuals and you should I imagine be able to work it out from them?
Good luck with the project
Hi!
If you ever make any progress with this, Im happy to try it out!
Hi,
I have a 2015 Audi A3, which unfortunately didn't come with AA as an option (I think it was introduced in 2017). It's a real pain to install the 2017 MMI into an older car, but there are guys out there developing aftermarket Android-based headunits that basically put a whole android "phone" in the dash; which isn't a very eloquent solution and kind of overkill in my opinion. They've got their own SIM cards and you have to change the bluetooth devices the phone is paired to and whatnot. It's really not exactly what I'm looking for. I just want AA and that's it.
Anyway there's one guy who's kind of got what I'm looking for . Unfortunately because the car also didn't come with a touchscreen, I have to toggle through the menus with the knobs and steering wheel buttons, which is meh. I'd love to put a digitizer overlay on the screen and play around with it, maybe have a daughter board made up and inject the screen coordinates into the packets somehow before it's sent down to the phone. I'm more of an EE, don't really have a lot of Android dev experience but I've got a lot of microcontroller and firmware experience. Anyway that's my high level idea of how this might work, not sure if I'm going in the right direction. I did ask the guy at RSNAV (seems to be a one-man show) last night if I might have the source code after signing an NDA and I'm awaiting his response. In the meantime I want to get a plan of action going.
So I'm wondering how AA is integrated on the client-side. Obviously the manufacturer headunits aren't running Android, but they've gotta communicate somehow with the phone. I can't find this info anywhere, I'm guessing this is info Google only shares with Auto manufacturers and the Kentwoods and Pioneers of the world. But maybe I'm wrong. I'm assuming it's a protobuf-based protocol between the headunit and the phone, but I don't know.
Can anybody help me out here? Thanks.
All my android auto head units are running android operating system two Chevy and one Mitsubishi. Main reason why poplar cars get rooted head units and what not. But after market android auto head unit is probably your best choice.
I currently use Screen2Auto and while it is working overall I'm still having issues.
I'm not a developer or anything, just an end user.
I'm curious why no one has come up with an alternative to Android Auto. I.e., an app that will run on an unrooted phone, make the car's headunit think it is interfacing with Android Auto, and allow you to mirror any app that is on your phone.
Are unrooted phones just too locked down to operate an app like this?
Is there a special key or something that the car's headunit requires for communication?
Is it just too onerous of a job to make an app like this?
Just curious. Seems like there would be quite a demand for an app like this.
https://play.google.com/store/apps/details?id=com.bitspice.automate ... this was an awesome attempt to do exactly what you are looking for. It was intended to be an AA replacement, and I was an early adopter/beta tester. The biggest problem was they were never able to find a way to get it to the head unit *legitimately*.The next biggest problem was that everytime they came up with something better than AA, Google would make changes and break it. Several times functionality would have to be changed / removed because of changes to Google's Terms of Service.
Ultimately it becomes a battle between Google's unlimited (seemingly) resources and the developer writing the app.
I'm looking for something a little different than the above. I'm looking for something that mirrors your phone's apps on the car's touchscreen.
I have a useless 4.2 inch screen in my car. Sorry not sure where to post this. It is the remnant of the horribly terrible SYNC system . All it does now is use the back up camera, which I have a new one connected to my Sony AAV-6000. I have had a few ideas on this screen but the top idea is a Raspberry PI. I know I can buy a touchscreen at 4.2" and what I was wondering was how do I either, Make a weather center, or a bouncing EQ that responds to the music playing in the car? Other ideas are very welcome. Do not need two backup cameras and sense the 4.2" is available I want to convert it to a Raspberry PI. The former is the best I can do for ideas, unless someone comes up with a better idea. I just don't want to cut the wires and throw it in there, one because I cannot find the wiring diagram for it and two not sure how to program it. I am a web developer and am fluent in Javascript but that has nothing to do with what I am trying to do but I am sure I can figure out any code. Regardless any ideas or do what I want to do help would be appreciated.