yashsingh1/xdaforums huggingface dataset:
[Hardware Hacking General] E:V:A:
You're taking an interesting approach to this. However, there are a couple of things you need to explain and understand better.

1) What are these "pogo-pins" you're talking about? [There is no such thing well defined, please be specific and use correct terms for whatever it is you're trying to describe.]

2) What make you believe there is a FSA9480 in your Nexus? [There probably isn't! I know the driver is called so, but that chip probably never existed in production.]

3) Obviously (!) you cannot charge your phone and have it play (OTG) host at the same time. Why? Because charging means to short D+ and D-.

4a) You say you can "control the chip" with I2C, can you give some examples of this? But I don't know what you're actually controlling, as it doesn't make sense the way you have explained it.

4b) You also say you have unloaded the Kernel module... How did you do that?

5) It seem that you're confusing the chip signal directions. I.e. whether certain pins are designated as input or output signals...

6) There are more switches/multiplexers built into your phone. It's of essence to understand which ones you're actually controlling.
[Hardware Hacking General] Renate:
You had better explain that slowly to my Nook, because it's sitting beside me here charging and connected to two keyboards and a USB audio adapter.

Shorting D+ and D- is a convention to tell the device that it can draw a lot of current.

Even without the data lines shorted, a device can charge.

Moreover, if you tell your device in software to do a high current charge, it can.

Solution: use host mode and charge at the same time.

One connector does it all.
[Hardware Hacking General] AdamOutler:
One thing I noticed while playing with the FSA chip was some of the registers would not change. They may be overridden by resistor values.

To put the device in host mode, short pin 4-5. To put it in charging mode short 3-4. It may be possible to change the host mode to charge the battery over i2c.

This may or may not be possible.

The main problem I was having was in the SBL most registers would stay static.
[Hardware Hacking General] Renate:
Playing with I2C sounds like fun, but all that stuff already has drivers.

The drivers that I've seen already have user hooks in the file system to get things done.

For example:

echo 1500000 > /sys/devices/platform/bq24073/force_current

Sets the charging current on a Nook touch to maximum.

(Your device probably uses something different.)
[Hardware Hacking General] E:V:A:
@Renate NST: Yes, I should have been more careful with my words. I meant charging as operating as a high current Dedicated Charging Port (DCP). But then again thebeerbaron already understood this.

@thebeerbaron: Here are your "pogo-pins" (right side is towards the top of the phone):

The pins and their function is loosely described in this thread, and very nicely used in this thread, so it seem that the following is true:

[SIZE=2]P1 +5V
P2 Signal: 1-wire interface, using MFM encoding
P3 GND[/SIZE]

(check these!)

I don't have the Samsung parts list of the GT-I9250 so I still don't know what those chips are. But U601 is a Fairchild chip and could be another type of switch. On the other side of this board you find the multiplexers U809 and U810 configured like this:

So how did you unbind/unload that "driver"? [I'm curious to see what driver/Kernel module this is.]

And here is another relevant hack for a wireless charger, But the interesting part is the Kernel hack mentioned:

For those of you wanting to charge at AC speeds instead of USB, Fast Charge Mod is here!

1) Install Franco Kernel (Milestone 1)

2) Run this script to activate it from the terminal (minus quotes):

echo 1 > /sys/kernel/fast_charge/force_fast_charge

and the UI Mode Manager code over here.
[Hardware Hacking General] Renate:
Ok, but I can still pump 1.5 Amps into my Nook while using host mode.

I'm not sure how you are differentiating things here.
[Hardware Hacking General] E:V:A:
Well, Samsung try to conform to the "Battery Charging 1.1" standards, and that's how DCP is defined in there. The limitations are then also present in the chips and/or in the one or more PMIC Kernel drivers. So your NST is either not conforming to any standards or just have a hell-of-a-hacked Kernel, or both.

This project is interesting because it's exploring some hybrid between kernel hacking and hardware tweaking, and not just building a regular charger, which we all know how to do. If you are interested in knowing what kind of crazy hardware is included in a Galaxy class Samsung phone, you can have a look here.
[Hardware Hacking General] Renate:
Generally speaking, as far as standards go, you're not supposed to even try to charge something while it's in host mode.

Still, it's a useful thing to do if you want to use your device docked.

The kernel on my Nook is stock. I'm just giving commands to control the charge current.
[Hardware Hacking General] AdamOutler:
I don't know about the NST, but my Nook Tablet has several additional pins dedicated to charging the device, it's not a true USB port.

What's going on here is trying to convince the USB port to go into host mode, where it natively supplies 5VDC, but instead reverse it, use the 5V line to charge the device and supply 5V from an external source.

While the NT has a dedicated charging circuit, this device repurposes its usb pins based on input conditions. So here's what I see being required

1. Ground USB pin 4 to activate HOST mode.

2. shut off 5V power supply from FSA chip

3. set registers in FSA to charging mode.
[Hardware Hacking General] E:V:A:
It's pointless to discuss standards of what should and should not happen unless we are on the same page. Here are the specs.
[Hardware Hacking General] Renate:
Sorry.

/me wanders off elsewhere.
[Hardware Hacking General] thebeerbaron:
Sorry for the slow reply folks, I appreciate the input, but got sidetracked onto another project today. Wearing many hats means making a lot of context switches!

I haven't tried charging during host mode, as we were trying to keep the external wiring changes to a minimum. Based on what I found last night though, we may go with a completely external solution...

If we go with the external wiring solution, this will be what we do. When I set the FSA to various modes over i2c, it did not charge or connect the USB device as it should. This is very likely because the kernel is listening to the FSA for state changes and telling other devices how to behave based on those states. That's sad.

What is the SBL?

Yes, this is how things should behave. Unfortunately, the Samsung engineers who wrote this device driver were rather short sighted.

If you wade through this mailing list discussion (sorry, I apparently can't link until 8 posts... https://lkml.org/lkml/2011/6/29/124), you'll see the engineers need several attempts to get their code approved. The most interesting part to note (for me), is that they create the device file /sys/bus/i2c/devices/.../switch, which accepts input from userspace and sets the FSA9480 "manual switch 1" register appropriately. Unfortunately for me, they only coded a small portion of the possible states for this register and will not accept arbitrary values. UGH!

I sat down with the GN last night and tried using the /sys/bus/i2c/devices/.../switch device to set the manual mode. What I discovered is that even though this obviously passes values into the driver module (it prints a kernel message when I set a bogus value), the values don't "stick". In the driver code (I'm still not 100% sure I have the right source, but I think I'm close.. again, sorry for lack of clickability: https://bitbucket.org/franciscofranco/android-tuna-omap/src/388ae9aa9b26/drivers/misc/fsa9480.c), it has a _detected function, which gets called whenever the cable changes and overrides any manual settings I put in. For example, I set the "switch" file to "AUDIO", yet the phone remained in USB accessory mode, and plugging/unplugging did nothing. Sigh.

The lesson is, apparently, that I need to write my own driver module, which can replace this fsa9480.c transparently and allow me to ignore cable change detections and provide me with a way of setting the FSA state manually (with more flexibility than the Samsung engineers allowed). We're thinking about a different approach, but this may yet get done...

Some great background info in here, thanks! I'll have to sit down and process this another day.

To unbind the fsa9480 driver, I do:

echo -n "4-0025" > /sys/bus/i2c/drivers/fsa9480/unbind

And to bind it, I do:

echo -n "4-0025" > /sys/bus/i2c/drivers/fsa9480/bind

Yep, that's what's interesting and what's making this difficult. It's kind of a gray area of where the topic experts are and what I need to learn...

Thanks for your input all... maybe something will come along that'll save me from writing a kernel module... fingers crossed!
[Hardware Hacking General] CNLiberal:
I am very interested in the outcome of this project. I purchased the GNex thinking I could charge it while at the same time, connecting an SSD (via SATA->USB converter) to the phone for media playback. Thanks for your hacking skills!
[Hardware Hacking General] Entropy512:
Not true. https://github.com/CyanogenMod/andr...mmit/c7016a2513abfd522b02633b79d2f21bcb99d4e2 - The USB charging standard defines an Accessory Charger Adapter. It's signaled with a particular resistor value (36k if the code comments are correct...) on the ID pin.

Although while I thought the I9100/I777/N7000 used an FSA9480, it looks like the MAX8997 handles the task on these devices... hmm... The FSA might support this mode though, so instead of trying to force-override it, look to see if there's a particular resistor value you can hijack or, in this case, a resistor value that is standardized to provide the function you want.

I hate when I only have access to github's web interface and not the ability to grep my hard drive at home. :)
[Nexus One Q&A, Help & Troubleshooting] mexus88:
I am not sure xda-developers forum is the place to discuss about but now I am almost sure that our N1 will never be getting a real ICS.

I understand now that N1 hardware does not support API mapping and all we get from the developers's effort like dk_zero-cool, texasice and zyr3x is very lag rom.

Unfortunately I don't see any future on ICS here and I believe that we will stay on GB. hope that the developers will go on and develop new and better CM or sense

ron that based on GB.
[Nexus One Q&A, Help & Troubleshooting] Menelkir:
1) This is for general (also, there's already threads about this).

2) This forum is for development, not for opinions.

3) N1 hardware DOES support API mapping, that's not the actual problem with ICS in N1.

4) There's already good ICS roms from developers here. If you're in a hurry to get Google's ICS (its kinda useless to need this imho, since ICS for n1 is quite good enough). Just because google doesn't give ICS to N1, doesn't mean we can't get a stable one. Sense ROMs (all of them) are a good example of this.
[Nexus One Q&A, Help & Troubleshooting] ebautista:
try to thing of this. google provided us open source android. so it mean, it is possible to run on any them. look at hp touchpad. now with CM. look at nokia n9 and samsung bada fone. all of them have ported versions of android. If you are just trying to give your opinion then be sure to post it on the right section.
[Nexus One Q&A, Help & Troubleshooting] tommert38:
If all these ICS ROMs are laggy, then you're cleary doing something wrong. You should try other setups (kernel, a2sd, developer settings). BCM has been running rock solid and smooth for like 2 months now for me (and many others).
[Nexus One Q&A, Help & Troubleshooting] xyrovice:
Real quick fellas, I've been following the BCM ICS thread and, judging from his posts in there (on top of this thread), please realize

Mexus is a pure and unadulterated troll.

He has repeatedly disparaged the efforts of a lot of prominent developers (as well as members) here on XDA in a manner I find to be tremendously disrespectful and ungrateful.

Out of respect for all the hard-working devs here, especially the ICS ones who are giving up so much of their time, I'd like to ask you not to post any more responses in this thread and to not respond to any other rude posts of his you may come across.

Mexus, I hope you'll learn that your attitude does nothing to benefit this community, and that you should work to improve said attitude so that the things you say don't end up being disrespectful, unhelpful, and, ultimately, 100% unnecessary.
[Nexus One Q&A, Help & Troubleshooting] taodan:
@mexus88: You just joined the XDA in April 2012 and already stir the trouble. We would appreciate if you don't post negative comments.
[Nexus One Q&A, Help & Troubleshooting] mdtxoom:
@mexus88: I'm not your opinion.

BCM ist enough fast and almost stable in the newest version.

This is my real ICS, good enough as daily driver.
[Nexus One Q&A, Help & Troubleshooting] joelshawdow:
Guys don't blame mexus88 he is new to this forum..but be + ..ics is almost perfect...one of the ics roms is in alpha..but I see a light in that
[Nexus One Q&A, Help & Troubleshooting] Menelkir:
This thread was moved from development area. As well, if you had understand it the concept of the forum as you said, you'll be speaking in english right now. :P
[Nexus One Q&A, Help & Troubleshooting] boypro25:
i like it! ^^
[Samsung Galaxy Nexus] NCguy:
I've got a GN that due to bluetooth issues requires a couple of daily reboots. I have root and a reboot app which is much faster and more convenient than a stock power off/on.

My question is should I be concerned about unsafe closes on apps like touchdown exchange without doing a shutdown first?
[Samsung Galaxy Nexus] gabryrider94:
don't worry

reboot with an open app isn't unsafe, it's like you shut off the phone...

it's unsafe remove battery, remove only if both touch and phone don't work
[Samsung Galaxy Nexus] NCguy:
That's what I was hoping. I was curious because the shutdown function seems to take a lot longer than the reboot.
[Samsung Galaxy Nexus] nodstuff:
An unprotected reboot can lead to pregnancy.
[Motorola Photon 4G] valentinoh:
First order of business.....

please unlock bootloader with working 4g.

http://googleblog.blogspot.com/2012/05/weve-acquired-motorola-mobility.html?m=1
[Motorola Photon 4G] peetr_:
Hmm, so what will be next? They must have a big plan. I can't wait for some news. :-)
[Motorola Photon 4G] DualSportDad:
Sounds like definitely plan to start making their own phones. Come on Motorola nexus!!!!!!
[Motorola Photon 4G] valentinoh:
I hope something big and new. Why else, buy it.
[Motorola Photon 4G] bitbang3r:
Amen, brothers! Praise Larry & Sergey! :-)

My Photon is now officially pulled from eBay (for at least a few days) just in case Google decides to earn our love & loyalty forever by unlocking our bootloaders ASAP :-)
[Motorola Photon 4G] cornelious2:
access to patents to tell Apple and M$ to suck it.

Sent from my mopho
[Motorola Photon 4G] dsims7_2000:
You would be absoutly correct, Google and Larry Page could care less about Motorola or a cell phone. What they do care about is the 6000 (or is it 16,000?) patents that Motorola owns! Right now, Apple is sueing everyone for infringements, thats getting read to change real fast!!!

I dont know if you guys know this, Motorola was around L-O-N-G before Sammy, HTC, Apple, Noika, all of them. They held all these patents but never really enforced them for whatever reason. If you remember, Apple went after Motorola with its Lawyer Goons with this Paten crap. I guess Motorola did not have the balls to fight, but Larry Page has bigger Goons! F**k, motorola has patent on the old bag phone of the late 80's! So if they every come back........
[Motorola Photon 4G] willysp:
Correct - this is all about now owning patents.

Means little or nothing about current phones.
[Motorola Photon 4G] shabbypenguin:
lol

by field testing a new bootloader or at the very least a new bootloader unlock tool? cuz im sure that wont take a few months to pass carrier testing etc...
[Motorola Photon 4G] moparfreak426:
i couldn't agree with you more. i am really looking forward to having ics... either by update of by unlocked bootloader and flashing cm9

#ICS-lessMotorolaElectrify, ThanksMotorolaForYourIgnorance
[Motorola Photon 4G] redninja007:
yeah

yeah i hope it will be soon :) cant wait to unlock with working 4g...or unlock with boost :)
[Motorola Photon 4G] valentinoh:
Boost?
[Motorola Photon 4G] ourtut:
Lol you can put the photon on pretty much any carrier now. Atm I have my photon on page plus (verizon). I'm pretty sure boost is on the sprint network so 3g or 4g might work (as long as your boot loader is locked). To get on another cdma carrier all you got to do for the most part is flash alother prl.
[Motorola Photon 4G] CCallahan:
Does that include Virgin Mobile? Haven't heard of a successful swap to that yet.
[Motorola Photon 4G] FernBch:
I guess that could be real possible. If I remember right they use Sprint's towers.

My MoPho's in the kitchen sink!!
[Motorola Photon 4G] Android 17:
I hope I'm wrong but I really doubt this will affect prior devices like the Photon, Atrix, etc.

I can imagine future devices having prompt updates, perhaps vanilla android, but seems unlikely they'd suddenly decide to move the ICS Q4 update to sooner out of the bottom of their hearts.
[Motorola Photon 4G] dsims7_2000:
Guys, here is the most informative article I have read on the subject from AndroidPolice. This guy is a Law Student in California and explains the good and the bad of the marriage. Enjoy!

http://www.androidpolice.com/2012/0...-look-back-at-the-deal-and-what-happens-next/
[Motorola Photon 4G] bitbang3r:
Expecting ICS sooner is unrealistic. Expecting unlocked bootloaders for existing phones so we can do it ourselves is another matter entirely.

As far as carrier approval goes, remember that there's a fundamental difference culturally between Motorola and Google. Motorola wouldn't even contemplate releasing an unlocker unless the carriers demanded and paid for it. Google will have its lawyers read the sales & maintenance contract it has with the carriers, and do it anyway as long as there's no clause in that contract explicitly prohibiting them from doing it.

In practical terms, that probably means Sprint and T-Mobile will have official unlockers within weeks, and AT&T & Verizon will never get them. However, I'll bet there will be some VERY interesting tidbits of info in the Sprint unlockers that might prove useful to someone at XDA trying to write one for a Verizon phone... ;-)
[Motorola Photon 4G] moparfreak426:
as long add they unlock my bootloader so i can have a blurless ics rom i think id be pretty dang happy at least until jellybean comes out lol

#ICS-lessMotorolaElectrify, ThanksMotorolaForYourIgnorance
[Motorola Photon 4G] redninja007:
tnx

tnx for the info... im going to look into it :) i still have 6 months before my contract with sprint will end.so i still have a lot of time to figure this out :)
[Motorola Photon 4G] schale01:
Even though on the surface this appears to be the case. This deal has more to it. You don't put Dennis Woodside who has been with Google for 10 years and built most of Google's foreign market to be CEO of a company that they plan to just sit on for patents. No, I suspect that we will see much more coming out of Motorola and not just cell phones. They would be the obvious choice for developing the hardware for the new Google glass project and many other mobile computing devices that replace that desktops that many will never own. So while we may not see an immediate change to existing phone hardware don't doubt for a second that Google has big plans for Motorola.
[Motorola Photon 4G] FernBch:
Now that is the most logical statement yet.

My MoPho's in the kitchen sink!!
[Motorola Photon 4G] thefsfempire:
Interestingly enough Motorola moved us up to Q4 for ICS. Maybe Google had a part of that decision? Maybe they are doing things right (fully unlocked?)... I can dream anyway :)
[Motorola Photon 4G] bitbang3r:
And, let's not forget the fact that they ALSO got Moto's cable-box business as kind of a freebie as part of the deal. Imagine for a moment that 3-5 years from now, every single Comcast DVR in America is ALSO a "Google TV" device with internet connectivity. I shudder to imagine Comcast's 7 year old creaky hardware running like a 200MHz Android tablet from Shenzhen, but I think it's safe to say that the NEW DVRs with better hardware will run it quite well.

I can see Google doing things like preinstalling Amazon.com (market, not videos on demand) in return for .1% of all purchases made from one of their cable boxes (Google wouldn't stop you from installing Amazon on your own, but pre-installing it would mean consumers would be more likely to purchase goods from there than, say, Buy.com or Newegg, let alone Barnes & Noble and Best Buy), just to name one obvious revenue opportunity.

Statistically, almost nobody buys a real TiVO. 99% of Americans with a DVR take whatever the cable or satellite provider gives them, and use it. Motorola owns about half the American cable box market. That's a big deal. If Google ends up driving about a third of the American DVR market (taking satellite into account), that leaves TiVO's sloppy seconds from Hughes, and Scientific Atlanta, for Microsoft and Apple to fight over. And if it comes down to willingness to play hardball and give away the farm for market share, Microsoft has much deeper pockets than Apple. Scientific Atlanta DVR users themselves might prefer an "iBox" DVR, but more likely than not, the UI they'll be seeing is Metro. Apple might score a "boutique" DVR from Dish, but that's pretty much *it*.

It's a pity the DVRs will probably be locked down as badly as the Revue was. I haven't touched my Revue in months. I just kind of lost interest in it after the Honeycomb update permanently unrooted it, and the one time I *did* get in a mood to play with it, their stupid activation server was down & it couldn't get off step 7. :(
[Motorola Photon 4G] Shad0wguy:
We were initially slated for q3. We got pushed back to q4.
[Motorola Photon 4G] dsims7_2000:
Yes and no. Late last year we were "roumored" to get ICS and unlocked bootloader 2nd quarter this year. But you are correct, the "Official" word Q2 this year was Q3 this year, now Q4 this year, then...............
[Android Themes] gkaipale:
Hi all,

Just point here:

-SilverBall 2 (new, added 30 minutes ago)

https://play.google.com/store/apps/...nby5sYXVuY2hlcmV4LnRoZW1lLlNpbHZlckJhbGxJSSJd

-Purple!

https://play.google.com/store/apps/...iY29tLmdhdS5nby5sYXVuY2hlcmV4LnRoZW1lLk5ldyJd

-CyanBox

https://play.google.com/store/apps/...29tLmdhdS5nby5sYXVuY2hlcmV4LnRoZW1lLmZuZXoiXQ..

-HollowSphere

https://play.google.com/store/apps/...nby5sYXVuY2hlcmV4LnRoZW1lLkhhbGxvd1NwaGVyZSJd

Check all the other themes of cource.

If you like them, please rate them. It will help me a lot.
[HTC One S] jaywhy13:
Any idea why this happens? Chrome Beta and the stock browser works fine but none of the following works over 3G/HSPA:

Facebook Chat

Google Talk

Nimbuzz

Whats App
[HTC One S] merdok:
Is this with the stock ROM that you are seeing this?
[HTC One S] jaywhy13:
Yup... just got the device yesterday. Haven't modded a thing yet. I'm also gonna leave a comment in the switching HSPA/3G thread. I'm experiencing that too.
[HTC One S] jaywhy13:
Btw... I'm in Jamaica.
[HTC One S] DownloaderZ:
Maybe your provider is blocking VOIP ports and possibly gchat works on VOIP port?

Someone chime in please..
[HTC One S] jaywhy13:
Seems so, I checked on another forum we got out here... the network I'm on is in the testing phase, they haven't launched the service fully just yet.