Related
So I was a Messagpad 2100 user, and I have been looking for a device to really replace it since I stopped using it in 2007 (yeah, I know it was canceled 10 years before that -- it was a pretty amazing device though). I think the N7 might finally be the device. Anyway one of the key's to using the Newton was it's case/keyboard setup:
http://www.flickr.com/photos/atow/4314242537/
It was super handy to be able to pop the Newton out for a meeting etc
So, questions:
1. If I were to plug a keyboard into the N7 (possibly using an adapter to go from USB to micro USB), will it work?
2. Does anyone know of a keyboard with a micro USB out? I looked in the most obvious places and couldn't find one.
Yes, I know about BT keyboards (I've been using one and it works), but I want to avoid the charging/battery issue if at all possible.
..
Get the logitech bluetooth keyboard for android 3.0+. Given your question you may not realize how much better (and how much lower power consumption) bluetooth is now. You'll get dedicated android keys and won't have to worry about wonky keyboard mapping issues; not to mention the hassle of using a wired setup (can require using an app to set it up each time). Also, you can connect more than one device with bluetooth, so you can have a keyboard and mouse (with the USB you'll be limited to one).
BTW- the wired keyboard will drain the battery on your nexus (not sure how it compares to battery drain from bluetooth though).
slack04 said:
Get the logitech bluetooth keyboard for android 3.0+. Given your question you may not realize how much better (and how much lower power consumption) bluetooth is now. You'll get dedicated android keys and won't have to worry about wonky keyboard mapping issues; not to mention the hassle of using a wired setup (can require using an app to set it up each time). Also, you can connect more than one device with bluetooth, so you can have a keyboard and mouse (with the USB you'll be limited to one).
BTW- the wired keyboard will drain the battery on your nexus (not sure how it compares to battery drain from bluetooth though).
Click to expand...
Click to collapse
I've used a couple different wired keyboards with no need for a OTG adapter. Didn't check for battery usage, but I did notice that both wires were very thin and susceptible to break. For that reason only, my next keyboard will be a bluetooth.
Wireless vs. wired keyboard and battery life
slack04 said:
Get the logitech bluetooth keyboard for android 3.0+. Given your question you may not realize how much better (and how much lower power consumption) bluetooth is now. You'll get dedicated android keys and won't have to worry about wonky keyboard mapping issues; not to mention the hassle of using a wired setup (can require using an app to set it up each time). Also, you can connect more than one device with bluetooth, so you can have a keyboard and mouse (with the USB you'll be limited to one).
BTW- the wired keyboard will drain the battery on your nexus (not sure how it compares to battery drain from bluetooth though).
Click to expand...
Click to collapse
I prefer my wired, USB, mobile keyboard over my Bluetooth wireless keyboard because of the wired keyboard's size and layout. However, I want to maximize the battery life on my Nexus 7.
The posts in this forum seem to be inconclusive. So, does anyone have a solid answer as to whether a wired, or a wireless Bluetooth, keyboard is best for the Nexus 7's battery life?
Thanks!
Chaps, thinking out the box but can you get a USB keyboard WITH a battery built in to help power the device..
ccinco said:
I prefer my wired, USB, mobile keyboard over my Bluetooth wireless keyboard because of the wired keyboard's size and layout. However, I want to maximize the battery life on my Nexus 7.
The posts in this forum seem to be inconclusive. So, does anyone have a solid answer as to whether a wired, or a wireless Bluetooth, keyboard is best for the Nexus 7's battery life?
Thanks!
Click to expand...
Click to collapse
I would expect the Bluetooth keyboard would use no more power than the USB keyboard, as the keyboard would draw power from the USB to drive it's electronics, whereas the Bluetooth keyboard would have a battery. I would prefer not use a USB keyboard as I wouldn't like to damage the USB port if I bumped the OTG adapter - there have been reports of port damage from simple knocks and drops.
I just bought the Motorola keyboard with trackpad for $29 (woot), and expect it to turn up any day now. I previously used the older Motorola bluetooth keyboard with the N7, but sold it with my old Acer A500 before I realized I'd prefer a keyboard with my N7...
http://www.amazon.com/Motorola-Wireless-Keyboard-Trackpad-Packaging/dp/B006291K7A
I am back to trying to find a solution for this. I'm not opposed to a BT keyboard, if I could find that's small enough without being too small. Most these days seem designed to work with an iPad, and tend to be 13" long or so -- too big. I'm hunting for something not much larger (so 9" or less than the N7 but also not utter crap. I suspect that when the 7" ipad finally is released, we'll see a bunch of design smarts applied to this.
I've been using a Stowaway BT keyboard I bought years ago for my Windows Mobile 5 phone. I still think it's the best portable keyboard.
http://www.amazon.com/Stowaway-Ultra-Slim-Bluetooth-Blackberry-Handhelds/dp/B0002OKCXE
It's an aluminum clamshell design that locks opens into a 4-row keyboard with full-size keys. They feel like my laptop's keys, and have just enough resistance to let you know they've been pressed. Two function keys give you access to the full 101-key character set. There are other functions like "save" and "new", but they don't appear to work because under Android. There's also a built-in stand that seems flimsy at first, but has no problem holding the N7 in either orientation. However, this keyboard does NOT like your lap. It must be used on a stable, flat surface. Even though it does lock open, there's enough "spring" due to the thinness of the keyboard that typing is difficult.
The Stowaway is pricey - around $70, although you can find them discounted to $50 if you shop around. Maybe some of the cheaper clamshell designs may work as well. YMMV. My co-worker bought 3 different keyboards that were just unusable. #1 had "clicky" keys - impossible to touch type on. #2 had those rubbery "chiclet" keys - again, impossible to accurately touch type on. #3 was OK to type on - if you had little pixie fingers. The key spacing was only 3/4 of the norm.
That is *exactly* what I'm looking for -- the thinkoutside keyboards were awesome. That someone isn't making something like this now boggles the mind, but I guess there isn't really a market for these when the device most likely used with it these days (ipad) is much larger. I'll bet we see more of these when the smaller ipad is on the market.
Can anyone here can comment in new feed of Facebook with extended keyboard. I had used logitech keyboard, can comment in wall, chat, but can't comment in new feed
Sent from my GT-I9100 using Tapatalk 2
I want to modify my brodit car dock (Note 1) for my Note 2.
The first problem is, that the 619k resistor for tiggering car dock mode with fast charging (AC-Mode) isn´t recognized by the Note 2. Here ist the thread: http://forum.xda-developers.com/showthread.php?t=820275&page=18
Okay, the fast charging-mode only (shown as "AC") can be triggered with pins D+ D- connected. But this isn't working too.
It seems, Samsung want Note 2-owners to buy original accessories only?
Frank2 said:
I want to modify my brodit car dock (Note 1) for my Note 2.
The first problem is, that the 619k resistor for tiggering car dock mode with fast charging (AC-Mode) isn´t recognized by the Note 2. Here ist the thread: http://forum.xda-developers.com/showthread.php?t=820275&page=18
Okay, the fast charging-mode only (shown as "AC") can be triggered with pins D+ D- connected. But this isn't working too.
It seems, Samsung want Note 2-owners to buy original accessories only?
Click to expand...
Click to collapse
What's the amperage of the adapter in mAh?
Frank2 said:
I want to modify my brodit car dock (Note 1) for my Note 2.
The first problem is, that the 619k resistor for tiggering car dock mode with fast charging (AC-Mode) isn´t recognized by the Note 2. Here ist the thread: http://forum.xda-developers.com/showthread.php?t=820275&page=18
Okay, the fast charging-mode only (shown as "AC") can be triggered with pins D+ D- connected. But this isn't working too.
It seems, Samsung want Note 2-owners to buy original accessories only?
Click to expand...
Click to collapse
FYI, on the S3 in the official jelly bean releases, car dock mode is totally broken, this may be the same for the note. car dock mode not triggered, charging not triggered and audio is not routed out of the car dock.
I have the Samsung Note 1 car dock.
It will charge the Note 2 but it will not put it into car mode. The usb connection is very slight between connected and not connected. It's not a perfect fit.
Frank2 said:
I want to modify my brodit car dock (Note 1) for my Note 2.
The first problem is, that the 619k resistor for tiggering car dock mode with fast charging (AC-Mode) isn´t recognized by the Note 2. Here ist the thread: http://forum.xda-developers.com/showthread.php?t=820275&page=18
Okay, the fast charging-mode only (shown as "AC") can be triggered with pins D+ D- connected. But this isn't working too.
It seems, Samsung want Note 2-owners to buy original accessories only?
Click to expand...
Click to collapse
Not exactly what you're asking, but I use Tasker in a similar situation to engage car dock mode. In my case, I'm using BT connection as a trigger (battery life is so good now I dont see the need to cut BT on and off as I did with Note1), instead of charging as a trigger. With Note1 I used charging as a trigger to cut BT on, the BT connection as a trigger for car dock mode (or absence of connection for 60 secs to turn BT back off). Bottom line, Tasker gives a lot more flexibility in creating scenarios than a hardwired solution, and with a lot less effort.
The Perseus kernel was updated recently, with this in its changelog, maybe you should give it a try?
Enabled OTG car dock, smart dock and music dock charging. Alternatively this can be triggered if you short pins 4 and 5 of the USB connector with a 40.2kΩ, 64.9kΩ or 619kΩ resistor.
Click to expand...
Click to collapse
Hi hchxoom
That's an excellent idea. Just wondered if you were already doing this or is it just theoretical. Like others, when I use the original note car dock, it will charge but not route the speakers through the dock. I can plug the audio cable in to the headphone socket but that's fiddly and crappy sound. What you are saying is that I can force the audio to be redirected by using tasker to select dock mode?
Thanks
Sent from my GT-N7100 using xda app-developers app
nijinski said:
Hi hchxoom
That's an excellent idea. Just wondered if you were already doing this or is it just theoretical. Like others, when I use the original note car dock, it will charge but not route the speakers through the dock. I can plug the audio cable in to the headphone socket but that's fiddly and crappy sound. What you are saying is that I can force the audio to be redirected by using tasker to select dock mode?
Thanks
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Doing it now. Set it up a few weeks ago, or rather tweaked my Note1 setup. Still tweak it periodically as I find ways to improve it. I started down the nfc path briefly, and will experiment further, but havent yet found added asvantage.
The biggest difference btw current setup and Note1 setup is due to the phenomenal battery performance on Note2. On Note1 BT and GPS on all the time were killers, so my setup included scripts to turn them on and off, which complicated matters sifnificantly and, in the case of GPS, required root.
Now, I just leave BT and GPS on all the time (well, I also have tasker setup to begin cutting them off if not in use when batt hits 25%, but that is rarely triggered).
So, when I get in the car and turn it on, BT connects automatically. Tasker recognizes that change in connectivity and launches my CarMode actions. In my setting, it looks specifically for the connection with MY vehicle, not just any BT. The actions currently launched include: 1 turn on car mode, 2 turn off wifi (so I dont get offers to connect evry time I drive by McD's), 3 disable my lock screen (after first successful unlock), 4 load Ulysses Speedometer app (my preferred card dock base app), 5 /6/7 turn up BT volume, media volume , and incall volume to max (just in case I ever turned them down). IF charging (meaning I've also put it in my dock) it also disables screen sleep. Then end result of this is that I get my car setup every time I drive, even when I don't dock it... so it can stay in my pocket for a quick trip to the store and still have full features avail.
When the BT connection terminates (car off and exit), Tasker launches my exit actions, including: 1 car mode off, 2 turn on wifi, 3 go to home page of launcher, 4 reset my lockscreen password. I don't have to ask it to terminate the speedo app, bc that functionality is built into the app.
To make the above work (specifically lockscreen disable and reset) I also needed the SecureSettings plugin app.
Hope this helps.
Thanks for the info. I tried it out. Unfortunately just switching on car dock mode doesnt seem to output audio via the dock. All the other stuff seems to work well though. I just hope there is an official note 2 powered car dock in the not too distant future.
Sent from my GT-N7100 using xda app-developers app
nijinski said:
Thanks for the info. I tried it out. Unfortunately just switching on car dock mode doesnt seem to output audio via the dock. All the other stuff seems to work well though. I just hope there is an official note 2 powered car dock in the not too distant future.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Worka fine for me via BT, but sounds like you're trying via usb... perhaps they changed the wiring a bit.
nijinski said:
Thanks for the info. I tried it out. Unfortunately just switching on car dock mode doesnt seem to output audio via the dock. All the other stuff seems to work well though. I just hope there is an official note 2 powered car dock in the not too distant future.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
All, we at iBOLT are working on finishing up the car-dock for the Note 2 with a release date around the 4 weeks from now. It will work with all cases too, including Otterbox Defender type. The big challenge is that there is no car-mode and no aux-out through the micro-usb in the latest Jellybean firmware version from Samsung for the Galaxy Note 2. Although anyone can still download and automatically start (using an NFC tag) any of the "vehicle interface" apps from the Google Play store, type applications like CarHome Ultra, it will not work as intended.
Without integrated car-mode support in the Jellybean firmware the "Car Home App" will not default as the new home screen. As a result pressing the "home" button will take the user back to the standard Samsung "home" screen instead of the "Car Home screen" from the app. A core value of car-mode, in our opinion, is that a user should be able to "toogle" between GPS Navigation apps, music players apps, camera, speed camera warning apps etc and any time press the "home" button on the phone and it should take the user back to the "car-home" interface. This is also how it has worked for the past few years and for reasons beyond anybody's understanding (including people working for Samsung) the latest Jellybean firmware does not have the great aux-out and car-mode functionality turned on.
If you want these features, help us out by contacting Samsung telling them to re-active these features in future upgrades.
Without integrated car-mode support in the Jellybean firmware the "Car Home App" will not default as the new home screen. As a result pressing the "home" button will take the user back to the standard Samsung "home" screen instead of the "Car Home screen" from the app. A core value of car-mode, in our opinion, is that a user should be able to "toogle" between GPS Navigation apps, music players apps, camera, speed camera warning apps etc and any time press the "home" button on the phone and it should take the user back to the "car-home" interface. This is also how it has worked for the past few years and for reasons beyond anybody's understanding (including people working for Samsung) the latest Jellybean firmware does not have the great aux-out and car-mode functionality turned on.
If you want these features, help us out by contacting Samsung telling them to re-active these features in future upgrades.
Click to expand...
Click to collapse
Is it my understanding that the iBolt Hardware will support aux-out through the micro-usb once the firmware is updated? Also is it known if all firmware versions/ carrier models have this feature disabled?
MikaelPe said:
All, we at iBOLT are working on finishing up the car-dock for the Note 2 with a release date around the 4 weeks from now. It will work with all cases too, including Otterbox Defender type. The big challenge is that there is no car-mode and no aux-out through the micro-usb in the latest Jellybean firmware version from Samsung for the Galaxy Note 2. Although anyone can still download and automatically start (using an NFC tag) any of the "vehicle interface" apps from the Google Play store, type applications like CarHome Ultra, it will not work as intended.
Without integrated car-mode support in the Jellybean firmware the "Car Home App" will not default as the new home screen. As a result pressing the "home" button will take the user back to the standard Samsung "home" screen instead of the "Car Home screen" from the app. A core value of car-mode, in our opinion, is that a user should be able to "toogle" between GPS Navigation apps, music players apps, camera, speed camera warning apps etc and any time press the "home" button on the phone and it should take the user back to the "car-home" interface. This is also how it has worked for the past few years and for reasons beyond anybody's understanding (including people working for Samsung) the latest Jellybean firmware does not have the great aux-out and car-mode functionality turned on.
If you want these features, help us out by contacting Samsung telling them to re-active these features in future upgrades.
Click to expand...
Click to collapse
but some people are reporting that USB Audio does work for the note 2?
http://forum.xda-developers.com/showthread.php?t=1891086
or is this via OTG?
Hi. I've followed the Pogo Charger thread looking for pin-out info on the Nexus 10 pogo connector. No posts on the actual pin-out. I did learn about the 'polimeter', but I digress.
I've done some probing around and have some preliminary info on the connector to share. I used a Fluke 189 dvm and a Tektronix 2252 scope.
First order is to identify pin 1. I'm assuming that when viewing the connector with the screen up, pin 1 is on the left.
Pins 1 and 6 are ground. Zero resistance between the two.
Pin 2 is a control pin. Open circuit voltage is 1.12 V. If you pull it down with a 1.5K ohm (minimum) resistor momentarily and let it go up, the Nexus 10 powers on. (Discovering that was good for excitement ...) Once powered on, if you pull it down again, Nexus goes into clock mode. Obviously meant for a dock. Don't know if this pin does other tricks. Note that the picture of the pogo charger connector shows pin 2 missing.
No clues about pins 3-5. One is obviously +5 for charging. But I'm not ready to apply power to unknown pins yet. Seems to me that since there's a charger floating around, it would be better to wait for someone to check out its pins.
Pins 3-5 are near ground level. No pull-ups, clocks, etc.
I had no luck finding audio on any of the pins. There might be a control function that mutes the Nexus speakers and enables audio. Or it might happen when you supply charging power.
I hope that there are some brave souls out there that could help identify more pins. The charger is the most important because it might enable other pins.
Murray
Usually, with these SOCs, varying resistances between the control pin and ground can cause you to enter various modes, such as download mode on other Samsung devices, along with countless other modes, dock, speaker dock, etc.
If we could get some ultra high resolution teardown photos, I could work out the charging pins.
My pins should be here in a couple of weeks too, so I can start making my pogo charger.
Sent from my GT-I9300 using Tapatalk 2
The hi-res photo is a good idea, but I don't think it's going work here. Take a look at the logic board in the teardown at
www dot powerbookmedic dot com/wordpress/2012/11/16/google-nexus-10-take-apart-first-look.
(Sorry, but the site isn't letting me insert a proper URL because I'm a new guy ...)
The dock cable connector is the one on the lower right diagonal from the SoC. Judging from the size of the passive components, it looks like the power management circuit is above the connector just to the right of the processor. Here's the problem: the top of the board has a power/ground plane that hides all of the traces from the connector.
alias_neo said:
Usually, with these SOCs, varying resistances between the control pin and ground can cause you to enter various modes, such as download mode on other Samsung devices, along with countless other modes, dock, speaker dock, etc.
If we could get some ultra high resolution teardown photos, I could work out the charging pins.
My pins should be here in a couple of weeks too, so I can start making my pogo charger.
Click to expand...
Click to collapse
alias_neo - Any progress on the pin out or your pogo charger?
8008Hacker said:
alias_neo - Any progress on the pin out or your pogo charger?
Click to expand...
Click to collapse
Friday not, haven't been home much, working late to finish up before Christmas, so by the time I been getting home I'm collapsed.
Will probably get started and finished with it over Christmas holiday.
Sent from my GT-I9300 using Tapatalk 2
alias_neo said:
Friday not, haven't been home much, working late to finish up before Christmas, so by the time I been getting home I'm collapsed.
Will probably get started and finished with it over Christmas holiday.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I'll have mine by then and I plan on ripping it apart the day I get it and figuring out the proper pins for charging...
tpayne1 said:
I'll have mine by then and I plan on ripping it apart the day I get it and figuring out the proper pins for charging...
Click to expand...
Click to collapse
Just as importantly, see what the ID pin is connected to (if anything?) and which two pins are connected for data (which, since it has 5 pins, I assume it does data too).
according to this site 2 pins are for data transfer and 2 pins are for audio (left and right).
BuGGr said:
according to this site 2 pins are for data transfer and 2 pins are for audio (left and right).
Click to expand...
Click to collapse
Apparently you haven't read anything in this thread, which completely nullifies that speculation page completely.
3 pins are already known...that leaves 3....we have 1 for power...that leaves 2....can't have data AND audio...
I did, but I forgot about the dock pin. maybe some pins have a multi purpose of some sort.
a spec sheet from samsung would be ideal but I guess that will never happen.
After not seeing any interesting signals on the pogo pins a few weeks ago, I decided to look at the software. The kernel file ".../arch/arm/mach-exynos/board-manta-pogo.c" gives a lot of clues about the pogo connector. This post has some of my initial findings. I have to preface this rather long post by saying that although I've done embedded h/w and s/w for decades, I've never done an embedded Linux system and my knowledge of the Exynos gpio came from a few hours with the 911 page Exynos 4412 User's Manual. Please feel free to critique/correct anything said here.
The good news is that the code defines much of what the dock can do. It is more complex than I would have thought. Obviously the code doesn't define how the gpio connects to the pogo pins. Looks like some may connect directly, but others go through external logic, like the audio MUX mentioned below.
Here is an overview of the dock interface:
- The dock circuitry triggers an interrupt during docking/undocking. The interrupt triggers software debouncing of a gpio input to determine the dock state: UNDOCKED, UNSTABLE, DOCKED.
- I couldn't find an ADC input. This means that its unlikely that an external resistor can set various doc states based its value as others have postulated.
- The N10 uses one pin for a bi-directional data interface. It uses a non-standard protocol that bit-bangs MFM-encoded short command-response messages. When the dock is "acquired" (i.e., connected with stable signals), it sends an ID address and DOCK_VERSION constants. This probably tells the dock which features are supported by the device. Looks like the N10 can tell if its a Samsung dock based on the response message. Haven't followed the trail to find out other command functions.
- The audio interface is SPDIF, not analog or USB as others have predicted. Makes good sense as SPDIF requires only one pin. The reason that I didn't see SPDIF when I scoped the pogo pins is that the audio gets turned on and off. One other wrinkle: the audio pin is being multiplexed with another function. The mux logic looks like it's external to the cpu.
- The code sets the power status to one of four states: NONE, 500MA, 1A, and 2A.
- The code has several interfaces to the USB interface. For example, it controls power to the vbus line.
Suggests that it might support OTG on the dock.
Based on this, here is a SWAG on what the pin-out might be. We know we've got 2 ground and 1 charging pin. Let's assume that pin 2 is the interrupt pin. The two remaining pins might be multiplexed: in one state, the pins are the proprietary command interface and the SPDIF out; in the other state they are the USB d pins.
I'll continue reading the code to refine what I've seen. It would be great if some of the kernel devs could jump in and confirm some of this. I'm not comfortable in this environment yet. If I were, I'd be running the code under the debugger to see what happens when pin 2 is stimulated.
To me the data interface is the most exciting. The protocol should be hackable to extend the command set for use with custom docks. Want the docked N10 to turn on the table lamp when the alarm goes off? No problem. I'm sure that there are lots of ways that this could be used. Open source docks maybe?
8008Hacker said:
After not seeing any interesting signals on the pogo pins a few weeks ago, I decided to look at the software. The kernel file ".../arch/arm/mach-exynos/board-manta-pogo.c" gives a lot of clues about the pogo connector. This post has some of my initial findings. I have to preface this rather long post by saying that although I've done embedded h/w and s/w for decades, I've never done an embedded Linux system and my knowledge of the Exynos gpio came from a few hours with the 911 page Exynos 4412 User's Manual. Please feel free to critique/correct anything said here.
The good news is that the code defines much of what the dock can do. It is more complex than I would have thought. Obviously the code doesn't define how the gpio connects to the pogo pins. Looks like some may connect directly, but others go through external logic, like the audio MUX mentioned below.
Here is an overview of the dock interface:
- The dock circuitry triggers an interrupt during docking/undocking. The interrupt triggers software debouncing of a gpio input to determine the dock state: UNDOCKED, UNSTABLE, DOCKED.
- I couldn't find an ADC input. This means that its unlikely that an external resistor can set various doc states based its value as others have postulated.
- The N10 uses one pin for a bi-directional data interface. It uses a non-standard protocol that bit-bangs MFM-encoded short command-response messages. When the dock is "acquired" (i.e., connected with stable signals), it sends an ID address and DOCK_VERSION constants. This probably tells the dock which features are supported by the device. Looks like the N10 can tell if its a Samsung dock based on the response message. Haven't followed the trail to find out other command functions.
- The audio interface is SPDIF, not analog or USB as others have predicted. Makes good sense as SPDIF requires only one pin. The reason that I didn't see SPDIF when I scoped the pogo pins is that the audio gets turned on and off. One other wrinkle: the audio pin is being multiplexed with another function. The mux logic looks like it's external to the cpu.
- The code sets the power status to one of four states: NONE, 500MA, 1A, and 2A.
- The code has several interfaces to the USB interface. For example, it controls power to the vbus line.
Suggests that it might support OTG on the dock.
Based on this, here is a SWAG on what the pin-out might be. We know we've got 2 ground and 1 charging pin. Let's assume that pin 2 is the interrupt pin. The two remaining pins might be multiplexed: in one state, the pins are the proprietary command interface and the SPDIF out; in the other state they are the USB d pins.
I'll continue reading the code to refine what I've seen. It would be great if some of the kernel devs could jump in and confirm some of this. I'm not comfortable in this environment yet. If I were, I'd be running the code under the debugger to see what happens when pin 2 is stimulated.
To me the data interface is the most exciting. The protocol should be hackable to extend the command set for use with custom docks. Want the docked N10 to turn on the table lamp when the alarm goes off? No problem. I'm sure that there are lots of ways that this could be used. Open source docks maybe?
Click to expand...
Click to collapse
I've also been looking through the kernel today and my findings were the same.
Looks to me like the pogo can do USB data, SPDIF, and/or power for charging.
dalingrin said:
I've also been looking through the kernel today and my findings were the same.
Looks to me like the pogo can do USB data, SPDIF, and/or power for charging.
Click to expand...
Click to collapse
Thanks for the confirmation.
I love this thread. This sort of intelligent, collaborative discussion is what these forums used to contain back in the good old days (when all of this were fields etc.). I'm fascinated to learn how you guys are able to probe and deconstruct the software and hardware to discover the inner workings of these amazing machines.
8008Hacker said:
I couldn't find an ADC input. This means that its unlikely that an external resistor can set various doc states based its value as others have postulated.
Click to expand...
Click to collapse
It's possible dock state is triggered using binary pulses. I seem to remember the Nexus One dock used this method. The N1 docks also had audio out jacks which actually connected to the phone using a private bluetooth pairing.
8008Hacker said:
We know we've got 2 ground and 1 charging pin. Let's assume that pin 2 is the interrupt pin
Click to expand...
Click to collapse
I was looking through the documentation on the Atmel ATtiny series microprocessors Here, specifically, the amount of functions available on each pin. Is it possible that one of the ground pins is actually the interrupt pin and is currently pulled low until a voltage is present on the vcc pin?
Keep up the good work
skally said:
It's possible dock state is triggered using binary pulses. I seem to remember the Nexus One dock used this method.
Click to expand...
Click to collapse
It does. The dock code maintains several states. Docked, power state, audio state, usb state, etc. Some of them are affected by the command/response channel I mentioned. This channel uses binary pulses on the pogo connector.
skally said:
The N1 docks also had audio out jacks which actually connected to the phone using a private bluetooth pairing..
Click to expand...
Click to collapse
The N10 uses SPDIF, a well-known protocol for transmitting CD-quality audio in stereo or 5.1 surround sound. Good choice by Sammy, imho
skally said:
I was looking through the documentation on the Atmel ATtiny series microprocessors Here, specifically, the amount of functions available on each pin...
Click to expand...
Click to collapse
I'm a real fan of the Atmel AT devices and have done a lot of projects with them. The Exynos has even more options on its I/O pins. Take a look at the manual.
skally said:
Is it possible that one of the ground pins is actually the interrupt pin and is currently pulled low until a voltage is present on the vcc pin?..
Click to expand...
Click to collapse
Don't think so. There's zero resistance between them. Having two grounds is actually a safety feature. Note that the grounds are on both ends of the connectors. This ensures that one of the grounds connects first before other signals no matter how the device is mechanically skewed as it docks. Prevents ESD (electro-static damage) to the interface.
could it be used for a keyboard or so?
I'm all for open source and reverse engineering but doesn't it seem like this is something that Nexus could just make a diagram available for? I don't get why this is something the community if left to figure out.
jerryp7 said:
I'm all for open source and reverse engineering but doesn't it seem like this is something that Nexus could just make a diagram available for? I don't get why this is something the community if left to figure out.
Click to expand...
Click to collapse
Well,
The pogo technology as with the rest of the hardware in the nexus devices isn't open hardware, it's proprietary for someone, they probably don't want to share it except with licensed partners making hardware.
Sent from my GT-I9300 using Tapatalk 2
alias_neo said:
Well,
The pogo technology as with the rest of the hardware in the nexus devices isn't open hardware, it's proprietary for someone, they probably don't want to share it except with licensed partners making hardware.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
That makes sense. Thanks.
I have looked high and low for a way to turn on my Nexus7 without using the power button while it is in sleep mode.
The reason is because i am putting my tablet in my 2002 Mustang GT to replace the stock radio. Once installed , the power, and volume buttons are no longer accessible. I have bought an AMP and use the remote volume knob to adjust the volume. Next my issue was getting the tablet to wake from sleep.
After some serious thinking, i have found a way.
This does not require flashing,hacking, taking the tablet apart to rewire ANYTHING.
What i am going to do is connect the charging cord to a secondary cigarette lighter, then plug in a USB adapter.
On the power side of the secondary cigarette lighter connect a toggle switch. (The secondary cigarette lighter will be hidden behind the tablet)
Mount the cool looking toggle switch somewhere in the car where it is easily accessible.
When you want to wake the table, and or charge it, turn on the toggle switch. (This SHOULD work with any tablet)
You may want to download an app to put the tablet to sleep for when getting out of your car.
If anyone else tries this please let me know how it worked out for you.
LOL
A great solution to a unique problem.
Let's see pics when you are done dash mounting your N7.
I still have to cut out a small piece of the dash to allow room for the charging cable. That will be done tomorrow, along with a better video. I just wanted to show my progress.
Copy and paste link.
youtu.be/1psLH24ZsiE
Here is another video i made during the day, and after it was all mounted.
Copy & Paste.
youtu.be/P89paX9fcYw
Here's a thought, couldn't you just wave a little magnet over the bottom right part of the nexus screen? This should wake it up just as if you were opening a cover.
fangthorn said:
Here's a thought, couldn't you just wave a little magnet over the bottom right part of the nexus screen? This should wake it up just as if you were opening a cover.
Click to expand...
Click to collapse
While that is a good idea, that doesn't help with charging.
I personally would want the battery in the tablet to cycle threw its charges instead of always staying connected. (in case i ever wanted to take the tablet out)
Thanks for the videos. Looks like quite the fun project. You did some great work there.
RumoredNow said:
Thanks for the videos. Looks like quite the fun project. You did some great work there.
Click to expand...
Click to collapse
Thanks RoumoredNow. Its still a work in progress.
1. Better mounting of the tablet.
2. Add DC 4 port USB hub.
3. Add front and rear cameras.
4. Add 2 Standard USB connections built into the dash. (for passengers to charge there phone or play threw the audio system)
5. Another AMP
6. Replace the stock 8 speakers.
7. Add Sub-woofer.
8. Anything else i may think of, or suggestions i may like.
This is just an update to anyone wanting to mount there tablet in a mustang.
I have found that a simple piece of plywood does the job well. the area to mount a tablet in a mustang (without cutting up the dash) is about the same thickness as the tablet.
So using a piece of plywood, you can screw it to the BACKSIDE of the stereo mounting bracket. A couple of pieces of Velcro added to the plywood and tablet will keep it centered and in place while putting the radio bezel back on.
The Velcro also added cushion and a space filler to snug the tablet up to the radio bezel.
See images.
Just remember that baking a tablet in a car all of the time _will_ destroy the battery, and rather fast. Maybe that's fine. Just warning you.
As for turning the device off. If you have bluetooth in the car or something, you could use Tasker to watch for the BT device. When it goes away, start a timer, maybe 30 minutes or something, then shut down. That way quick runs into the store or it's not powered off/rebooting etc. There are many posts on this exact same subject in this exact sub-forum... Nexus 7 seems to be popular for cooking in vehicles for some reason.
But yes, the "unplug it from the power" solution is always the solution. Using a "pretty" switch is one way to do it. Some cars have lighter ports which are only powered when the car is powered, but I know mine are hot all of the time and a lot of cars these days are.
Use mKernel and a ROM that supports it and you can use the double tap to wake function, works great on my tablet, just tap the screen twice to wake it up.
U can use timur's kernel, And a otg-y cable, so when power unplug nexus go on stand by, And when plug power nexus start.
That rom is created Just for car installation.
Inviato dal mio Nexus 7 utilizzando Tapatalk
**EDIT: The ebay item i bought below does not fit well in the nexus7.
While it does fit, and does charge, it is loose and sometimes gives a bad connection then disables charging. I suggest to NOT buy it for a nexus7.
I just wanted to update that i have got my OTG cable for my nexus7 (2012) and it works great with timur's rom. Here is a link to the 1 i bought from a USA seller.
I have used a 16gig USB stick with it for testing till i get a larger 1.
http://cgi.ebay.com/ws/eBayISAPI.dll?ViewItem&item=111423491796
A couple of things i wanted to point out about having a toggle switch connected to wake my tablet.
PROS:
1st. This will allow you to charge the tablet when your not in your car.
2nd. Your car does NOT have to be running or in accessory mode to charge your tablet.
3rd. Depending on how you wire your amp, you can still listen to music on your tablet when the accessory is off.
4th. You can still use ftp, AirDroid, ES File Explorer, ect.. (As im typing this, i'm transferring over 600 songs to my tablet in the car.)
CONS:
1st. Tablet does not wake when switch is moved to accessory mode. (toggle switch must be pressed)
There may be more cons, but i haven't found any related to my setup yet.
I'll add to this as i run across PROS and CONS.
my sETP N HELP PLEASE
02sonicblue said:
A couple of things i wanted to point out about having a toggle switch connected to wake my tablet.
PROS:
1st. This will allow you to charge the tablet when your not in your car.
2nd. Your car does NOT have to be running or in accessory mode to charge your tablet.
3rd. Depending on how you wire your amp, you can still listen to music on your tablet when the accessory is off.
4th. You can still use ftp, AirDroid, ES File Explorer, ect.. (As im typing this, i'm transferring over 600 songs to my tablet in the car.)
CONS:
1st. Tablet does not wake when switch is moved to accessory mode. (toggle switch must be pressed)
There may be more cons, but i haven't found any related to my setup yet.
I'll add to this as i run across PROS and CONS.
Click to expand...
Click to collapse
i have it set up with my acc line just connected to my ligheter cable and when ever i turn off ignition my tablet turns off and goes on airplane mode.. what i did was i bough a usb addapet that conects to positive n negative line. outputs 2 amps.. its located in the glove box ran the wire through the back and its pluges to the tablet.. so when i turn on the switch the table goes out of airplane mode, turns on my wifi (Wifi Teher) and Bluetoot (For bluetooth gps reciever) and lastly plays my music. . very pleased with the process.. now im hving one issue wich im trying to fix.. since i have booth bluetooth and wifi my tablet seems to drain more battery than it charges... im running c-rom 4.4.4 and i was looking into tfinding a fast charge. if anyone can help me setup fast charge please let me know and good luck. im pretty good with electrical in case you need any help..
****VERY IMPORTANT OPINION*****
I RECOMEND YOU SET A FUSE BEHIND EVERY WIRE TAP YOU MAKE, I HAD TO REPLACE MY ENTIRE WIRING HARNEST DUE TO A SHORTAGE.. SO A FUSE WOULD JUST BLOW AND NOT CAUSE SHORTAGE> :good::cyclops:
This post is old but I still have problems. Anyone had luck or did you just threw away your old and got a new model instead?
yattamove said:
This post is old but I still have problems. Anyone had luck or did you just threw away your old and got a new model instead?
Click to expand...
Click to collapse
Got everything set up perfectly let me know if you need any help
Sent from my Nexus 7 using XDA Free mobile app
Good project! Have you tried timur's kernel yet? Maybe it will solve your problem.
yattamove said:
Good project! Have you tried timur's kernel yet? Maybe it will solve your problem.
Click to expand...
Click to collapse
The thing im using 4.4.4 rom and I believe timurs kernal is only for 2013 version of nexus 7. (Might be wrong) what I ended up doing is making a switch wich in case my battery dieson the tablet I can turn on the switch and charge the tablet over night even when the car is off..
Sent from my GT-I9505 using XDA Free mobile app
egren58 said:
The thing im using 4.4.4 rom and I believe timurs kernal is only for 2013 version of nexus 7. (Might be wrong) what I ended up doing is making a switch wich in case my battery dieson the tablet I can turn on the switch and charge the tablet over night even when the car is off..
Sent from my GT-I9505 using XDA Free mobile app
Click to expand...
Click to collapse
I have 2 nexus7 (2012) models. My first one, i had timurs USB ROM for Nexus 7
I never could get it to fast charge even when fast charging was turned on. i was backing up my music and the rom went into a boot loop while it was backing up. So i tried to clear the cache and that didn't help. i then tried to revert back to factory (4.4.4) and i bricked it. It was hung at writing the bootloader. So i left it all nite while i went to bed and the battery died.
My 2nd tablet i left stock (i haven't even tried rooting it yet).
Hey guys.
I cycle each day to/from work for about 14 miles and use my watch all the time, but sometimes it's difficult to do something on the watch while cycling.
I was thinking of mounting the watch on the handlebar and wanted to ask you guys for a nice solution.
Also, I am using Strava to track my cycling, but what else are you guys using?
EDIT: I have a metal strap attached to my watch, that does not fully open (like the original strap) so I don't really think I can add and remove the watch from the handlebar unless I attach it to the bar end, or something like that.