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.
Related
ADB will not connect via USB.
No ports open on the device, so no connecting ADB over IP (I have seen this work on the Maylong M-150 (Walgreens) tablet.)
Browser sends HTTP User-Agent:
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_5_7;en-us) AppleWebKit/530.17 (KHTML, like Gecko) Version/4.0 Safari/530.17
I have tested the factory reset button combination, it is valid. Hold Volume+ and Nook and Power, while the device is turned off.
WiFi options are rudimentary. There is no support for proxy in network settings, additionally, after receiving an IP address from DHCP, the device appears to connect to a website to verify connectivity. If you have a captive portal network setup (where HTTP outgoing requests are redirected to a login page), then the verification process will just hang. You will be unable to go anywhere using the included browser. After several minutes, the verification process will fail, and then you may be able to connect to the captive portal using the web browser. This is discussed on page 56 of the Nook Color user guide.
Would it be helpful to anyone to include the open source libraries that the device includes (under Legal Notices). I don't know if it is helpful to know what libraries are included (or omitted) compared to a conventional Android device?
Additionally, some notes on the MicroUSB connector. It is proprietary.
* It will sync, but not charge, when connected to my PC desktop's USB (wattage unknown.)
* An ordinary MicroUSB will sync, but not charge, when connected to PC.
* I left the included 120VAC-to-USB transformer at the office, so I do not know the listed wattage.
* The nook cable will charge the device when connected to my Moto Droid1 120VAC-to-USB.
* An ordinary MicroUSB will not charge the device when connect to the Moto Droid1 120VAC-to-USB transformer.
* Finally, the Nook cable will not fit in my Moto Droid1. Therefore it will not charge or sync. Careful examination of the Nook cable shows that the metal trapezoid connector is slightly longer, and appears to have additional pins. 12, in addition to the 5 conventional pins. I cannot tell by observation whether the receptacle within the nook makes contact with these pins.
phiz said:
Additionally, some notes on the MicroUSB connector. It is proprietary.
* It will sync, but not charge, when connected to my PC desktop's USB (wattage unknown.)
* An ordinary MicroUSB will sync, but not charge, when connected to PC.
* I left the included 120VAC-to-USB transformer at the office, so I do not know the listed wattage.
* The nook cable will charge the device when connected to my Moto Droid1 120VAC-to-USB.
* An ordinary MicroUSB will not charge the device when connect to the Moto Droid1 120VAC-to-USB transformer.
* Finally, the Nook cable will not fit in my Moto Droid1. Therefore it will not charge or sync. Careful examination of the Nook cable shows that the metal trapezoid connector is slightly longer, and appears to have additional pins. 12, in addition to the 5 conventional pins. I cannot tell by observation whether the receptacle within the nook makes contact with these pins.
Click to expand...
Click to collapse
* Mine is charging off my Dell monitor using the Nook USB cable.
* Charger is 5V - 1.9A.
I've read everywhere that the USB cable can't charge over the PC. It even says it in the manual, but it charges just fine connected to my computer. It takes forever though and the light never turns solid green. But the battery percentage still increases to 100%.
Motherboard is a Gigabyte EP45-UD3P if anyone's curious.
The micro usb has two extra pins so that it will quickcharge using the ac adapter. If connected to a computer and the screen is on it does not pull enough to charge the device but with screen off it will. One of the techs said that on the b&n forums.
So as far as rooting this thing, it seems apparent that there are three attack vectors.
* If device checks MicroSD on bootup for updates.
* Userland exploit, loading a file, going to a URL, Wifi Protocol stuff etc. Perhaps in the PDF libraries? (Note, because of sand-boxing this may not lead directly to full root, but it may allowing running of other software that would be useful for reconnaissance on the device.)
* Wait for Nook SDK to come out, and use the increased access to the device to compromise it.
The device is frustrating to use as is. Not because of any major design flaws, but because of the untapped potential. Like, I would love to have DropBox to ease file management. And the browser is left wanting (it reports as Mac OSX, and does not render some pages well (Google reader is wholly unusable.)
I'm considering returning it. It has so much potential, but I'm expecting the quality of the Chinese knockoff android tablets to continue to improve.
charges perfectly fine off my 10 watt panasonic wall adapter with an oem micro usb. says it's not charging but it went from 93 to 100 in ~10 minutes while i was using it.
there was a good bit of stutter when registering my device. i had to tap multiple times to switch b/t numbers and letter input. sometimes i had to tap the character multiple times for it to register.
i agree though, this is the sweetest tablet next to the galaxy tab and iphone hardware wise. too bad it's locked down right now.
just like all the cheap-o android tabs, this one does have soft back and menu buttons. if you click the book icon at the bottom the back and menu buttons are there. the home, volumes, and power buttons are the only physical buttons. no search button, but i rarely use in on any of my other android devices.
video playback is horrid! all my mp4 will play but choppy. even streaming was crappy. i tried youtube mobile with no videos being able to be played. madthumbs (nsfw!) worked but so stuttery it made it unfappable.
NM reboot fixed everything. my ripped videos and stuff downloaded with videodownload helper play fine now. able to watch some kung fu treachery on the beautiful screen.
the little book icon (read it now) at the bottom doesn't seem to bring up the menu and back buttons anymore. now it just takes me to the last read book on the homepage. i'd rather have the back and menu buttons back.
The charging connector has too many pins for just charge control. I counted 12 extra pins over the 5 standard USB, but it's tiny enough that I could've skipped one. I'm sure that two are used for controlling the LED in the connector shell, one is probably used as a cable identifier, leaving 9 unknowns.
My guesses:
-OMAP boot mode (MMC boot, select pins (1-2)
-serial (2)
-JTAG (4 or 5)
-audio (2-3)
I thought that extra current capacity could account for all the rest, but why spend on what I'm guessing is not a cheap connector just to bus all those tiny pins together?
Anyway, I tried to buy a second charge/sync cable to dissect today but my local store only had cases and screen protectors in stock. The connector has all pins populated so I'm hoping I can break them out and start probing for a bootloader on serial. Hopefully iFixit will get a teardown done soon and we can get a good look at the parts.
seem like there's bug in that read it now button.
to get the menu and back buttons back you need to open a pdf on you sd card. then for some reason you get you back and menu buttons when you hit the read it now.
this is helpful in that with the menu button you can now have a forward button for web browsing, refresh and you can go back without scrolling all the way to the top.
pokey9000 said:
The charging connector has too many pins for just charge control. I counted 12 extra pins over the 5 standard USB, but it's tiny enough that I could've skipped one. I'm sure that two are used for controlling the LED in the connector shell, one is probably used as a cable identifier, leaving 9 unknowns.
Anyway, I tried to buy a second charge/sync cable to dissect today but my local store only had cases and screen protectors in stock. The connector has all pins populated so I'm hoping I can break them out and start probing for a bootloader on serial. Hopefully iFixit will get a teardown done soon and we can get a good look at the parts.
Click to expand...
Click to collapse
I want them to look into the additional pin issues. See this: meta ifixit com/View/1108/Nook+Color+Teardown+Request
You know, while they're in there.
madsquabbles said:
video playback is horrid! all my mp4 will play but choppy.
Click to expand...
Click to collapse
No problems with MP4/M4V playback here. I used the newest handbrake and selected the iPod touch preset to start with.
What I changed:
Picture Tab:
- Width -> 848
- Anamorphic -> Loose
Video Tab
- Framerate -> 23.976
- Constant Quality -> 59.31%
Audio Tab
- Mixdown -> Stereo (Maybe Pro Logic II will work?)
Chapters Tab
- Unchecked "Create Chapter Markers"
My source video was a 1080p MKV with AC3 audio. It looks gorgeous even though it's actually sized smaller than the full res of the screen (NookColor won't play MP4/M4V wider than 854).
I'm playing this off a Class 2 SD card and I didn't notice any choppiness.
I'm not sure if this is the right place to ask but do you guys think that it might be better to go with an archos 70 instead of the nook color since it seems like its roughly the same price and perhaps easier for people to work on? looks like they're similarly priced.
milkham said:
I'm not sure if this is the right place to ask but do you guys think that it might be better to go with an archos 70 instead of the nook color since it seems like its roughly the same price and perhaps easier for people to work on? looks like they're similarly priced.
Click to expand...
Click to collapse
I believe the archos 70 has a lower resolution screen and the viewing angle is not as good.
rubyw59 said:
I believe the archos 70 has a lower resolution screen and the viewing angle is not as good.
Click to expand...
Click to collapse
That's what I've read as well and I think it applies to the g-tablet. I've read on the forums here folks that have had or looked at both the NC and the archos and gtablet and they say the NC has a much better display. The who IPS thing, same as iPad and the newest iPhone 4.
Infinitely better screen...not even comparable. Text on the Gtablet looks blocky and absolute crap. I haven't seen a screen that bad in years. Maybe it's because I have professional IPS monitors at home. The nook color screen is simply stunning and easy on the eyes at any angle on the lowest brightness setting. It will burn out your retinas at the highest.
Great Product!
I've been on a quest for an Android Tablet before Christmas. I bought and returned the Viewsonic G-Tablet. Horrendous viewing angles, heavy to hold (weighs 1.55 lbs) and cost $379-$399. I returned my Archos 70, which cost me $301.99 with shipping. I think I finally found my tablet, the Nook Color. Once it got rooted, it was a no brainer. GORGEOUS SCREEN, 512 MB RAM, easy to carry, great customer support from Barnes and Noble (I purchased the 2 year additional warranty $54) and pretty good Out of the Box (OTM) software. I know more better Android tablets will be coming out next year, but for $250, you can't go wrong with a quality product like the Nook Color and the customer support service of B&N. Great product =)
bruce, thank you for this update. i have really been looking at all the tablets, I know the holy grail is honeycomb, but i don't think that is reality until next summer and I don't want to wait. I have been looking at all these inexpensive tablets from china, there is one I saw on androidforums with gps that sounded good, but the nook so far seems good.
After you root, does this still work as an e reader? Also, how hard is this to root for someone technical, but has never rooted a device (i used to work on unix computers 20 years ago)? Is there easy step by step instructions? Thanks again.
I haven't exhaustively compared the other options on the market right now, but my intuition is that the NC is the best on the market as far as price-point and build-quality, but there is no market access and limited app support.
By the time development really gets going on a NC rom, i predict that we will have competitive alternatives, either from brand name manufacturers (Asus), or no-name Chinese manufacturers (right now the Chinese tablets are held back by their resistive touchscreens.) And these alternatives will presumably have dedicated android buttons, which the NC does not.
If you need a tablet right now, and are a tinkerer, then the NC is the way to go. If you want a more full-featured and robust solution, we are going to see compelling alternatives in the 6-10 month time frame, I predict.
I don't think it will take 6-10 months for custom ROMs and Market access.
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?
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).
Seeing videos of people integrating Raspberry Pis into their cars with OpenAuto got me interested in Android Auto. There is one thing I don't like about it, however: you're just adding another device to pass on audio/video/touch to an external display, from the phone. Why not cut out the middle man?
Back in the good old days of my Xperia S, phones had a dedicated micro-HDMI output. Delicous 60fps 720p (and even 1080p, with the UI drawn at 720p, but for instance video playback in full 1080p), and a free charging/OTG port. However, nowadays, we're stuck with MHL, and unless you have a Samsung phone, which has a proprietary connector, you can't use MHL and OTG at the same time, nor does MHL properly support touch functionality (only in theory), so we need the OTG.
DisplayLink to the rescue. We're going to sacrifice a lot of display smoothness/responsiveness here unless you have a modern phone with a USB 3.0 Type-C port (so you can use a newer high performance DisplayLink adapter), but we can use an OTG hub to get both HID touch functionality and HDMI through the DisplayLink adapter at the same time. More on this later. Also, I originally bought a $6 USB to HDMI adapter off eBay thinking it would be DisplayLink (or a compatible off-brand clone), but it turns out to be the really dodgy Fresco Logic FL2000, which is so cheap because it does none of the clever things that DisplayLink adapters do, and instead just spits out full resolution frames as fast as it can, which is completely incompatible with USB 2.0 or low power devices like phones. I found an affordable HP DisplayLink DVI adapter second hand from a Chinese seller that works.
On to the next hurdle: charging while using OTG. This is an interesting one, as it's not something I really gave a lot of thought initially. I mean surely just using a powered hub and giving the phone 5V over its micro-USB port would work, right? Well, it's a bit more complex than that, but Sony used to have an OTG dock that could charge, so I'm confident once I get the right OTG hub, it will work fine on my Z5. The one I got off eBay wouldn't do anything but charge, and when I opened it up, I saw it doesn't even use the 5th OTG pin, which would explain why it didn't work. I soldered a regular Type-A plug onto it and used my Sony OTG adapter to test, and I can get either charging or OTG, so something a bit less hacky is required. I ordered the Acasis H027, so when it arrives, we'll see if that works.
Touch: I haven't tested it yet. I have an HDMI touch screen in storage at my brother's house, so next time I visit I'll see if I can get touches to register on the phone. Based on my Googling most people on the internet seem to have gotten this to work fine, although there is no touch calibration on Android as far as I'm aware, like there is on Windows.
Portrait mode: this is my personal pet project and what I've been struggling with the most so far. It would be by far the easiest to just use a touch screen in landscape mode, but hear me out. Because HDMI (touch) monitors are cheap anyway, and in the 7 inch to 24 inch size range, bigger usually means cheaper, I want Tesla-style portrait mode. In portrait mode we can fit more screen estate in the centre console of the car than in landscape mode, and a bigger screen = bigger text = quicker glancing = safer driving. And it also happens to look extremely cool. If you have a big car you can probably fit a 20 or 24 inch screen, but I think I'm going for 13 inch. However. Using the DisplayLink Presenter app or the DisplayLink Desktop demo app which as far as I can tell does exactly the same things, I cannot for the life of me get native portrait mode to work. Android insists on pillarboxing portrait mode, and no amount of forcing rotation, setting build.props like ro.sf.hwrotation or persist.demo.hdmirotation works to change its mind. More worryingly, it seems that for the HDMI rotation prop to work, you need to also set persist.demo.singledisplay, which prevents apps from accessing secondary displays, which means DisplayLink Presenter, which itself is an app, cannot mirror the screen output any more and you get a sad single stripe of garbage pixels on an otherwise completely black screen. I probably need help here from an XDA developer, to hack the DisplayLink app, or to develop an Xposed module that causes all apps to draw themselves in portrait mode while the system is actually in landscape mode, or something along those lines. I've tried most things in my power that I could think of, and since my phone is unlocked, rooted, magisk'd and xposed, that is actually quite a lot, but nothing helped. So, uh, help?
Lastly there is DPI, which is one of the easier hurdles that I did solve. Android Auto (in phone mode, so not connected to any head unit) has a ridiculously huge UI on my phone's native dpi, and while I understand the reasons for it, with a larger external touch screen attached it just becomes unreasonably huge. With Tasker set to run "wm density 240" the entire Android UI becomes a lot more suited to a large screen, and even though Android Auto is still pretty huge compared to other apps, it's what I would consider reasonable.
More to come!
So, quick update:
While the screen portrait mode issues were "simple" to fix (although root was definitely required), the touch orientation issues as well as charging-during-OTG require kernel modifications to be fixed. I managed to compile a modified kernel with charging-during-OTG support thanks to @nlra 's work on that front, but I couldn't get the new image to boot.
A few things happened in the mean time:
- I discovered scrcpy
- I got an Xperia XZ3 (which I haven't rooted yet)
Scrcpy seems to be basically what Android Auto does, but for the whole Android desktop instead of only one app. I kind of don't like it because it involves adding a computer in between the display and the phone again (probably a Raspberry Pi), but the advantages are so huge it's basically the only realistic option right now.
Scrcpy:
- Basically always runs at 60fps, even on USB 2.0
- Handles portrait/landscape gracefully
- Integrates display, touch, (audio in a future version), and charging in a single connection
- Doesn't require root (although automatically setting the Android resolution to 1920x1080 and keeping the display on at 0% brightness are things that can probably only be accomplished with Tasker, which requires root)
So basically this simplifies and moves the project further immensely, however there are still some blocking issues right now. Touch screens only work on Windows because in addition to generating touch events, Windows also generates fallback mouse click events for touches, something that Linux doesn't do, and because there is no formal touch screen support in scrcpy, multi-touch doesn't work at all. Audio support also seems to be in an experimental state currently, and is not enabled for regular builds.
I hope ROM1V will eventually implement touch screen support (it's been in his GitHub issue tracker since March) as I have enough work to do as it is. I will focus on the hardware part (Raspi, cabling, VESA mount etc.) first and if by that time touch support is still missing I'll take a crack at it myself. Thankfully scrcpy is built on SDL which I'm fairly familiar with, although I've never worked with the touch input API before.
For the charging you need hub with usb-c PowerDelivery passthrough and HDMI. I am testing ones with less power consumption right now. I am not sure why you weren't able to use it.
I think people would be better of using following app for changing resolution, etc. using SecondScreen (I think root is required to run HDMI in portait mode, because it is grayed out for me).
I am doing the same project, but I keep the screen 1600x1200 horizontally and use apps in split view mode. I don't want root. I was thinking of using SamsungDEX for it, but the menus are too small.
The good thing is though, that on Samsung it is possible to create two-apps split screen pair (e.g. google map + music) as a launcher shortcut (using Good Lock (MultiStar plugin) from Galaxy Store). Unfortunately, I don't think it is possible to automate launching two apps in split screen automatically, nor create a split-pair shortcut on other launchers.
It would be good to have some multiwindow manager since I also wanted my BMW-tuning/logging gauges app to run in a floating window on top or minimized to a floating icon. It is possible naturally but it is a lot of manual clicking :/
One more thing that I don't think will be possible, is to completely turn off the phone screen. With the screen on, Note8 doesn't do fast charging. Can the screen be off with scrcpy somehow, I don't think?
So this dead?
Hey guys,
Looking to up my game with automations on my phone and set ringer profiles. I have WiFi on all of the time anyway, so I'm setting ring profiles based on being at work, being at home, night, day, etc.
But I'm thinking of kind of next-leveling it, and wanted to see just where I would start, if I need add-ons for Tasker, stuff like that.
So I have only gotten around to making a 'night' routine for Tasker. IF I'm home and IF the time is in a certain range, it goes silent. That way, if I'm lucky enough to actually be out, the phone still makes sound, but not when I'm trying to sleep. The next level I would like to try is different profiles based on what I'm doing at home or at work, using NFC. More specifically, I have a wireless charging dock at my desk, and one at home. I work IT, so I spend about half of my day at the desk, and half working the office floor. The floor is a little louder than my office (OK, a LOT louder), so I would prefer a different ring volume for each.
So when docked (At the dock at work), I'd like my volume to be minimal. As soon as I take it off the dock (But still at work), I'd like it to be mid-range. Re-dock it, goes to the low volume again. Leave work, full volume.
Similar thing I'd like to try at home. Any time of night, if it's not docked (In the home dock), it's a relatively normal volume. Dock it, and the hours fit into the specified range, and it goes silent.
I'd also like to change the behavior of the screen based on these. At work, the clock is on, at home(When I'm trying to sleep), the clock is off and the screen is dark.
So I know to do this, I need NFC tags on each charger, I've looked up interference from the chargers, and it seems to be a mixed bag. I could play with where to place the tag exactly, that's not an issue, but if I'm going to automate, I'd love to do this as automated as possible, if you know what I mean. Rather than tap it on a tag, I'd love to just set it in the dock or pick it up to activate it. So that's it. Anyone have any suggestion on a brand of tag, a specific criteria I may need to look for (I don't know if these things have ratings or anything like that), and any extensions or companions I need for Tasker to do something like this? Any help, as always, will be greatly appreciated, and feel free to ask followup questions if I was unclear on anything.
I don't really see why you NFC. Assuming you know whether you're at work or home based on the WiFi, then you can know whether you are on a wireless charger based on a profile state of power -> power -> wireless.
As a completely unrelated idea, if your P4 is rooted, and the device spends a bit of time on a charger, you might look at Advanced Charging Controller (ACC) (XDA thread
ktmom said:
I don't really see why you NFC. Assuming you know whether you're at work or home based on the WiFi, then you can know whether you are on a wireless charger based on a profile state of power -> power -> wireless.
As a completely unrelated idea, if your P4 is rooted, and the device spends a bit of time on a charger, you might look at Advanced Charging Controller (ACC) (XDA thread
Click to expand...
Click to collapse
Part of it is on the dock in the office vs. off the dock, walking around the office. Part of it is on the dock at home, vs. plugged into power, sitting next to the TV in the living room. Same with work. If I'm working in a conference room, I might just bring a charger and cable in there, but might still want the ringer loud. SO I'm kind of compartmentalizing both work and home, based on which area I'm in.
Part of it is also playing with Tasker, NFC tags, and all of those possibilities.
And unfortunately, a Verizon phone, so they've hosed me(As usual), and I don't think, even with it being a Pixel, that I can root it. :-
Since I think your question is, do I need any plugins to read NFC, the answer is no.
ktmom said:
I don't really see why you NFC. Assuming you know whether you're at work or home based on the WiFi, then you can know whether you are on a wireless charger based on a profile state of power -> power -> wireless.
As a completely unrelated idea, if your P4 is rooted, and the device spends a bit of time on a charger, you might look at Advanced Charging Controller (ACC) (XDA thread
Click to expand...
Click to collapse
Oh wait, I see the part now about wired vs. unwired power. Got it!
I'll try that, see how it works for me.
Thanks, your basic tips have helped me. I now have a work day profile, a weeknight profile, and a weekend profile(Morning noisy time is later on the weekend), all based on whether it is charging wirelessly or not and where I am.