yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] Tyfighter:
I got mine with the TF for a nominally higher price than the TF alone. Maybe I'm just a heavy typer, but I've never had any problems with the sensitivity of the keys. In fact, sitting here right now and playing with it, I've tried out several keys and it seems like they have two positions; up and down. I'm having trouble TRYING to get them in the middle where they don't activate.

While it is small, I've got a netbook too, so I'm used to the smaller layout. As many have said already, the battery is awesome and USB ports are pretty sweet, not only for the obvious storage opportunities but I've also used them with xbox controllers and to charge my electric cigarette in a pinch. I haven't yet, but in the near future, I'm planning on putting a bigass SD card into it and getting some real storage space on here. Not to mention that it functions as a stand and protects the all important screen if I'm just tossing the thing in my bag. Had I not seen a friend with this keyboard, I'd probably still be using my nook color.

Now the stuff that I'm not terribly fond of. I don't like that it isn't backlit. I don't like the tiny shift key right next to the up arrow. I'm a right side shifter and I often hit the up arrow with my pinky. That's pretty much it.

My stepmother saw me click my TF into my dock almost right after I'd gotten it and she exclaimed, "Oh, I've got one of those for my iPad!" So then I looked at her keyboard, and it appeared to be just a bluetooth deal with a notch at the top so you could kind of balance the iPad in it. Needless to say, I giggled.

Also, it can't be overstated how awesome it is to have the extra battery in there. It makes battery life a total non issue.
[Eee Pad Transformer Q&A, Help & Troubleshooting] campotino:
Hi guys,

my ASUS Transformer TF101 whit stock ICS and Root doesn't turn on.

It hangs on the first screen with nvidia logo and written eepad.

If I turn on the tablet whit "power on + volume down" and then I press the volume up, I not access on recovery mode but...

"booting recovery kernel image" but does not advance.

If I turn on the tablet whit "power on + volume down" and then I choose "wipe data"...

"booting recovery kernel image" but does not advance, I waited a long time!!!

I tried to restore with stock firmware on miscoSD but the tablet does not find the zip file.

you have any idea?

EDIT:I add the video

[YOUTUBE]3OzAS3GRukg[/YOUTUBE]
[Eee Pad Transformer Q&A, Help & Troubleshooting] SiNJiN76:
What were you trying to do?
[Eee Pad Transformer Q&A, Help & Troubleshooting] campotino:
I want to turn on my tablet!
[Eee Pad Transformer Q&A, Help & Troubleshooting] SiNJiN76:
That's all? It was off and you just trying to turn it on? You weren't trying to flash anything?
[Eee Pad Transformer Q&A, Help & Troubleshooting] campotino:
My transformer is B8O and its bootloader is locked and nvflash don't work.

I was not flash anything.
[Verizon Droid Incredible 2] Claynsen:
I loved the ICS animations for virtuous Affinity 1.46.0 but they won't work on 2.05.0

I've tried to unzip and change some stuff but i can't get it to work. Can someone help?

http://rapidlibrary.com/files/virtuous-affinity-1-46-0-ics-animations-zip_ulz9w8bbbvi99on.html
[Verizon Droid Incredible 2] HypostaticOnion:
UOT Kitchen. I wanna say its in the framework, so you'd only need to upload the framework-res.apk and choose the ics transition animations.

Sent From My Mikrunny'd Superphone Using Magic (TapaTalk)
[Verizon Droid Incredible 2] Claynsen:
Thanks

Nice it worked.

here is the zip if anyone using Affinity 2.05.0 wants to flash it. should give you the ics animations that hide any glitcheyness of the standard "from the side" animations. Also might give you an inverted dropdown, five bars, and blue HC battery icon.

http://www.mediafire.com/?628oha6pqma85kd
[T-Mobile myTouch 4G Slide] CoNsPiRiSiZe:
I recieved my warranty phone, i need to root it.. it comes with .13 HBoot and when i log into the HTCDev.com and hit unlock bootloader nothing happens... what gives? i selected the MT4GS...:mad:
[T-Mobile myTouch 4G Slide] blackknightavalon:
This one specifically mentions the .3 hboot, but it's the best I can come up with.
[T-Mobile myTouch 4G Slide] CoNsPiRiSiZe:
Thanks for replying.. got it figured out... now im running newest AOSPish and everything is great, i think..

Thanks to all who made it possible on the new HBoot!!!
[Samsung Galaxy Nexus] pchoi94:
Hi everyone. I, as many others, have been having an issue with my microphone cutting out during a phone call. I have a roooted Verizon Galaxy Nexus running the 4.0.4 leak, but it appears that for everyone who is having this issue it doesn't matter which ROM you're running or even if you're rooted or not.

[EDIT]: It per one of the posters below, this is not so much a "microphone" issue as it is an "outbound audio" issue. Unfortunately I can't edit the subject name to refer to this, but for me personally when I've been doing google searches on this issue the first word that came to mind anyway was the word "microphone" or "mic" anyway.[/EDIT]

People have been trying different things like flashing different radios, muting and unmuting, turning off voice privacy, etc., but it seems that nothing helps. Not even several hardware replacements or sim card replacements.

However, I did notice a pattern from different forums, etc. It seems that some people either have the problem all the time, or not at all, and it seems that some people reported that traveling to different metro regions affected whether or not they had the issue.

So I was curious to see if the pattern has to do with geographical location as an issue with Verizon's network, vs. hardware/software issues.

This poll has 50 possible answers, 1 for each state. Please answer this poll ONLY if you ARE experiencing this issue, and please only vote for your state if you live in the state's capital. For example, I live in the Denver metro area, so I would vote for Colorado. However, if I lived in Fort Collins or Grand Junction, I would NOT vote at all.

If you have traveled and visited another state's capital and have had this issue there, you can go ahead and vote for it as well.

It will be interesting to see if we have a lot of hits in certain major metro areas and none in others.

[EDIT2] Also, if you don't have the problem at all, go ahead and post a comment with your location. In fact, it would be interesting to see if people don't have the problem but others in the same city do. [/EDIT2]

Thanks!
[Samsung Galaxy Nexus] twiztidninja:
I thought I had this issue just turns out my pinkie was covering the microphone its king of poor positioning watch, the way u hold the phone after changing the way I hold it no one complains they can't hear me
[Samsung Galaxy Nexus] Smokeey:
TLDR: I kept having people telling me that I sounded like a robot.
[Samsung Galaxy Nexus] spencer88:
I had this problem on back to back to back phone calls this morning. Horrible.
[Samsung Galaxy Nexus] evasionoftruth:
My wife and I are both having the issue in Richmond, VA but I could only vote once for myself. She has reverted to an old droid x as she cant rely on the phone anymore.
[Samsung Galaxy Nexus] chaosphoenix:
Might be a little late, but maybe we should collect ZIP codes instead? Then we could use this tool: http://batchgeo.com/
[Samsung Galaxy Nexus] twiztidninja:
Try watching how u hold the phone I'm seriose since I changed the way I hold the phone this is a non issue your prolly plugging the microphone
[Samsung Galaxy Nexus] spencer88:
I voted. I'm in South Carolina. I'm pretty sure it's NOT a regional problem though.
[Samsung Galaxy Nexus] evasionoftruth:
If holding the phone different worked for you, then you don't have the issue this is referring to. This issue can happen with a wired headset, Bluetooth headset, on speaker phone, which none of these would be affected by how you are holding the phone considering you aren't using the mic on the phone. The people on the other end hear a series of clicking sounds, then no audio.
[Samsung Galaxy Nexus] gabe23:
I realize you're trying to help, but you really don't understand the issue. The OP really didn't describe it properly, as it's not a "microphone" problem, but rather an "outbound audio" problem. I use mine at work as a speakerphone with it sitting on my desk, and I lose outbound audio all the time. Others have the problem with a bluetooth headset. I don't doubt that there are some people who have had an issue with covering the microphone hole, but that is not what this thread is about. This is an ongoing issue that people have been troubleshooting for months, and Verizon/Samsung is supposedly working on a software fix to resolve it (I'm not holding my breath).
[Samsung Galaxy Nexus] acherons:
I had the same problem on my 2 rogers GNs(GSM version)

after I upgrade my baseband to i9250xxkk6, the problem gone
[Samsung Galaxy Nexus] adrynalyne:
I like the OP enthusiasm, but I don't think you will be able to glean any info on location. Owners are too spread out. Maybe in a few months.
[Samsung Galaxy Nexus] AnotherHiggins:
I'm in Raleigh, NC.

I got my phone on release day and noticed this problem a few days later. I've since replaced the phone, then the SIM card (a theory that it was SIM-card related was floated over at AF).

After changing the SIM card the problem seemed to go away for a couple of weeks, but it came back with a vengeance.

I hate the idea of getting a "refurb" from Verizon (I put refurb in quotes because, based on the FIVE refurb'ed Incredibles I had, I'm pretty sure they don't do anything except replace the glass if it's scratched), but I guess a functional refurb would be better than an aggravating semi-functional new phone.

I can't help but be reminded of Steve Jobs.... "You're holding it wrong!" :)

I'm glad your phone is working properly but, as others have noted, this is most definitely not the problem we're talking about.
[Samsung Galaxy Nexus] pchoi94:
Thanks for clarifying, I edited my original post, unfortunately I can't edit the subject name, but you're right, it's outbound audio and not mic. Thanks again!
[Samsung Galaxy Nexus] pchoi94:
You're right, I was caught up in it at the moment and thought it would just be interesting to see how the issue maps out, but this little poll in no way is a troubleshooting tool, more of a type of infographic maybe?

The only fix is going to be a software update from el goog. can't wait for it!!!
[Samsung Galaxy Nexus] AnotherHiggins:
I just got off the phone with Tech Support about this.

The Level 2 agent found an internal support document about the problem and read me what it said for the fix.... It says that the upcoming software release is going to cover this. It goes on to say that the tentative (dammit) release date for the software release is late March.

I don't want to trade in the new phone that I've babied since day 1 for a refurb of unknown quality if a fix is coming within the next couple of weeks.

If they don't release the update soon (which wouldn't surprise me at all), I'll probably just flash a new ROM & radio.
[Samsung Galaxy Nexus] chaosphoenix:
Flashing a new rom/radio does not help. I'm running nothing stock (leaked radios, CM9 Kang Nightly, Franco Nightly) and I still have this issue.
[Samsung Galaxy Nexus] Plesk8:
Good to know I'm not alone, Minnesota is currently winning! :-) :-\ :-(
[Samsung Galaxy Nexus] Dan76:
I was told the same thing by VZW support, but mid-march... which is NOW! I'm really getting sick of this. Ready for the fix and some info.
[Samsung Galaxy Nexus] descendency:
I have the same problem on the GSM version. Also Raleigh, NC.
[Samsung Galaxy Nexus] chlehqls:
So is this mainly a Verizon issue? I'm hoping to nab a International GSM phone to work with T-Mobile. So far, I've seen a lot of problems for this phone which is kind of discouraging, but I'm willing to press my luck and buy one...
[Samsung Galaxy Nexus] charlescom:
Although this is a great effort by OP and all of us with this issue, this problem is so widespread that we will only pretty much get a geographic map of VZW Gnex users that is on XDA forum with this poll. :)
[Samsung Galaxy Nexus] trmiv:
This happens to me a lot, probably half of the calls I make. Really annoying issue.
[Samsung Galaxy Nexus] Mendedlogic:
During a phone call perhaps 30 mins in the other party suddenly can't hear me anymore like I muted it on my end I can still hear them tho I would have to hang up and call back for it to only happen again!! Very frustrating for sure specially when my total purchase price from VZW was $300+ I hope they figure this out soon..
[Samsung Galaxy Nexus] pchoi94:
Wanted to report that I was just in Hawaii for a week and did not have this issue at all the whole time I was there.
[Samsung Galaxy Nexus] slickromeo:
hmmm

does everyone who changes their baseband to xxkk6 get this issue resolved? or did this solution only work for you acherons?
[Samsung Galaxy Nexus] rneal_ra:
having issues

I have had this issue since getting the phone on the day it released. I have tried stock, and most roms that come out. Updated to leaked radios. Nothing makes a difference. Really don't want to send it in if it's a software issue. Any new news on if there is a fix for this?
[Samsung Galaxy Nexus] Dan76:
Are you GSM or Verizon LTE? For those of us on Verizon with the problem... rumor has it that the upcoming 4.0.5 update with new radio software will fix the issue. Expected update was mid-march, then late march, now it's scheduled for early april... we'll see.

GSM users are already rolling out to 4.0.5, from what I've read anyway.

Others have better info? I'd sure love to hear it. Thanks.
[Samsung Galaxy Nexus] dmwoods:
Wired Headphone Routing Fix

Wired Headphone Routing Fix

There is an issue with a lot of Android devices where the OS thinks the headphone is being plugged in and unplugged on its own.

I have rooted 4.0.4 AOKP and it still occured. The app should include older versions of Android shortly as soon as Google Play

shows my latest changes.

Try this free application to resolve it. Search Google play for Wired Headphone Routing Fix
[Samsung Galaxy Nexus] JayferX:
Wired Headphone Routing Fix

I installed and tried this last night, so far so good

Anyone else tried it?
[Samsung Galaxy Nexus] Dan76:
Are you on VZW with the problem? Is it still resolved?
[Samsung Galaxy Nexus] bangdrum:
I'm on vzw and just installed this. I'll report back and see if it works.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] bangdrum:
Well, first call with the app and it happened 30 seconds into it. ****. :(

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] Liftoperator:
Wired headphone routing fix

I made a couple long calls with this app yesterday, and so far, no problems. It was happening to me on every call so I'm hoping this has fixed it. Will post back here if I lose outbound audio again.
[Samsung Galaxy Nexus] cguella:
Make Sense

I guess it makes sense that this app won't work. The mic only cuts out. We can still hear the other party so if it was a headphone cutoff issue addressed by this widget - I would expect to not hear them as well (but we do). It couldn't be this simple I was hopeful for this fix as well... Love my GN except I can't make calls. Kind of defeats the purpose of calling it a phone at all.
[Samsung Galaxy Nexus] Juggernaut79:
It's happened to me twice in NC. Once in Raleigh. I don't make that many calls though and when i do they are normally short.
[Samsung Galaxy Nexus] spencer88:
I had this horrible problem, and now for a month and a half... I haven't had the problem. I don't think for a second it's fixed, I'm just waiting for it to happen again. I can't be that lucky.
[Samsung Galaxy Nexus] ScottiePP7:
New phone, same problem

I am re-posting this from the thread at google (I posted this yesterday there so that's why the time difference). This is my current status.

Ok here we go....

I got my original Nexus in December of last year. It had the outbound audio issue and I dealt with it as best I could. However last week, my speaker blew out.

I went to VZW and they over nighted me a replacement phone. Manufactured at the end of February this year. The phone was shipped with 4.02 on it. I unlocked and rooted the phone and installed the full leaked 4.04 on top of it. I installed no other apps than twitter, chrome and draw something. Things seemed to be working fine through a handful of phone calls.

About 20 min ago the outbound audio issue reared its ugly head.

Now being that today is Monday this is my first day with this phone in the office (I worked from home on Friday when I got the device). I work in area right on the edge of a 4G network and have Wi-Fi in my building. This means I am handing off between wifi, 3G and 4G all day long. Someone above mentioned this as a possible cause to the issue so I wanted to say that if this is the case, I am on board with having to handoff all the time.​

Is this the case for anyone else with the issue? Are you doing a lot of lte/3g/wifi handoffs?

I have set my phone for 3G only and rebooted to see if I get this issue sometime this week. I will post any updates.
[Samsung Galaxy Nexus] bangdrum:
No. I always have full signal of 4g. But after I updated to the 4.0.4 radio from verizon I've not had the issue once.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] spencer88:
My last post I had posted yesterday. Well later in the same day I had the problem 3 times in a row. I think I jynxed myself by even talking about it.
[Samsung Galaxy Nexus] cguella:
Prefer to Jinx Myself

Since these updates no muted mic issue (Update happened again a few times no fix here):

Verizon Galaxy Nexus (Since available)

AOKP 4.0.4 Milestone 5 (Over a week now)

Flashed new radios FC05 (Two days)

Charlotte, NC
[Samsung Galaxy Nexus] cguella:
What could It Be ????

to summarize:

- Not 4G - since it happens on 3g

- Not headphone routing issue - happened with the switcher widget in place

- Not Wifi/3g/4g switching - happened with 3g only

- Not provisioning - VZW reprovisioned my device 2x

- Not hardware from China or Korea - Both have had the issue

- Not root/stock issue - Both seem to get it

- Not radio version issue - so far all radio flashes have not fixed it

- Not 4.0.2 4.0.4 issue - it has happened to both custom ROM or stock

What else is there? Fundamental hardware defect? Software defect?
[Samsung Galaxy Nexus] ohumad:
I too have had this problem, located in St. Paul, MN. Its happened less than 5 times I would guess, still really annoying. All calls took place around St. Paul. Running stock Galaxy Nexus from VZW with LTE switched off.
[Samsung Galaxy Nexus] loraque:
I just got called from the wife, who reported this problem. St Paul also. It would certainly seem that the region DOES have something to do with it... the spread on the votes is not much of a spread- Focus of issues in MN and NC does not make sense on pop distribution. I did try disabling her Voice Privacy setting in the dialer as another thread said this mitigated it. It also does seem that it is either a software issue, or some problem perhaps with the local networks in some areas?

How can there be so many votes for MN and not for CA or NY for example? Having a hard time with that being coincidence.

We are using the new radios and CM9.
[Samsung Galaxy Nexus] matt30:
It's probably a problem with the way the poll is set up. A bunch of people live in St. Paul but not many people live in Sacramento or Albany - the capital of CA and NY.
[Samsung Galaxy Nexus] bangdrum:
I'm in Sacramento, and I have this happen every day.
[Samsung Galaxy Nexus] adjuster11:
Not giving me the warm fuzzies.

I recently dumped stock 4.0.2 and went with AOKP build 37, with imm76 radios. I'm still getting this one way audio issue. Just disabled NFC, and 4G, to see if that might work.

I hope someone finds an answer, but cguella appears to be way ahead of me in his search.
[Samsung Galaxy Nexus] pchoi94:
Hi folks,

Just wanted to report back that I traveled to Houston for a week on a business trip and did not have the issue happen once. I also had full bars on 3G most of the time (there wasn't any 4G where I was staying, which was way north of Houston actually).

Got back home to Denver (Boulder area) where I have around 2 bars and the issue has happened a couple of times so far. Would be interesting to see how much reception affects this as well.

People might assume that 2 bars is "good enough" but maybe with the radios on the Gnex (compared to Motorola, for example), it just doesn't cut the mustard?

On a side note, I also noticed that my battery lasted twice as long, which is expected. My radio signal was around -75dmn in Houston, whereas it is around -105dmn in Denver area.

hmm, I may set up another poll to track the issue per signal strength...
[Samsung Galaxy Nexus] adjuster11:
I'm wondering if it's region related, since I'm in Lakewood, just on the West side of Denver. The only place I travel is in state, so I don't get to find out if it "works" somewhere else.

Good point though!
[Samsung Galaxy Nexus] jkc120:
I really think this is regional.

I think I'm going to contact the California State Attorney General and FTC about this. Verizon continues to deflect and wants to replace devices, when it's been clearly shown people's replacements have the same problem.

Maybe if enough of us complain to the FTC and our local state AG we'll get some response from them... :(

---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------

I've had it happen at my work's parking lot with full 4G bars @ like -75 dBm and perfect 3G service as well. I don't think it's (entirely) signal related.
[Samsung Galaxy Nexus] Dan76:
Even after 4.0.4? My experience after the update has been incredibly better... although it's only been six days.
[Samsung Galaxy Nexus] Manos Lijeros:
regional

It may be regional... I do see the poll shows 22% in NC affected, low 10s in Colorado and California, and in between in Minn.

Bob Egan suggested there may be some issue with the reverse channel communication. I am working on this via twitter (I've tweeted to 30 Internet luminaries (Bob Egan, Google Execs, Verizon CIO & PR staff, writers, etc...).

Verizon Support is all over me know... The last thing they asked me to do (since I have the 4.0.4 update) was to run it in safe mode to see if the issue happens in Safe Mode. Bottom line... The issue is still here in safe mode.

I am updating my issue and my quest to solve this issue at 2-sidedcoin.blogspot.com. I tweet under ManosLijeros, and I'm active over the last three days (that is where this issue is located).
[Samsung Galaxy Nexus] Dan76:
It's most certainly regional. If you've seen these other threads:

Poor Quality Control

4.0.4 Update

Mic cutting out problem

You'll see that many of us have a theory is that the Galaxy Nexus will lose outgoing audio (or crackle, pop, whatever) on many VZW LTE towers in certain areas of the US, likely due to poor or old tower technology. Or possibly due to the companies that did contract work on certain towers.

Obviously those towers work, it's just an incompatibility of those towers with the specific radio in the Galaxy Nexus (which is unique among all verizon phones).
[Samsung Galaxy Nexus] Jep0:
Samsung Charge has same issue

I just replaced my Samsung Charge (after 3 Charge replacements) with the Galaxy Nexus through Verizon. The Charge has the exact same issue as the Nexus with mic-drop. I have experienced this for quite a while now. It starts once in a while on long calls then becomes more frequent with shortest call time around 2 minutes.

I have had this Nexus for almost a week now and it's doing the same thing. I went to the Verizon store, and of course they were very suprised to here about this issue. Lol. they did say it might be bad towers in the area. I live in Reno, NV. This never happened with my Samsung Omnia or Omnia II. The only true fix that I have seen out of this is someone switching over to a Razr Maxx. I would rather not do that if I don't have to.

Does anyone know if the Charge and the Nexus share the same radio?