Thread: Is the CA-146C adapter trash?
View Single Post
shadowjk is offline shadowjk
2010-04-18 , 09:59
Posts: 1,258 | Thanked: 672 times | Joined on Mar 2009
#14
Originally Posted by extechop View Post
That would be the DC-10, a rather chunky thing. BTW, why does Nokia no longer have any technical info on products like this on their website?
Yeah it's very annoying. You'd think they no longer want to sell stuff.

By the way, I tried to get a word to a friend-of-a-friend at the Nokia development department, asking that logging about this kind of events (for example, the dialogue between devices over the MicroUSB port) be made available to the user, so that cases where it doesn't work won't stay "this just doesn't work" type mysteries. For example, it turns out quite a lot of the "no name" brand USB charger devices return more or less random device types to the N900, which often will refuse to talk to them because of this.
For the powerusers/developers out there:

/sys/class/i2c-adapter/i2c-1/1-0048/twl4030_usb/
contains some nodes. 'vbus' is probably 1 when there is voltage on the microusb port. linkstat seems to change whenever something is connected. I am guessing microamps_requested* either shows how much power n900 was given permission to draw, or how much it asked for..

/sys/devices/platform/musb_hdrc/

has the node 'charger', which is 1 whenever a charger that identifies itself with shorted d+/d- is connected. vbus is probably same as before. Other intersting nodes like 'mA' and 'connect'.

What's missing is sysnodes for the actual charger. I get the impression bme is very lazy about checking the charger status, not noticing if the charger aborted because of too crap power available on the musb port. It will also, of course, happily claim charging when charging from an otherwise healthy powersource that's unable to charge faster than n900 uses power.