yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] Megatr0n.:
Ok guys, I have it working.

Steps to get it to show your phone:

1. Install QPST

2. Make sure you have your phone drivers installed.

2.5 Make sure your Epic is not USB debugging mode, to disable, go to settings>applications>development>uncheck USB debugging

3. On your Epic, with the touchscreen dialer, dial ##8778#

4. Change the setting from AP to CP, then hit Home.

5. Connect your phone to your computer with the usb cable.

6. Your computer will automatically install the modem drivers for your Epic wait until you see the “device is ready for use”

After this you can follow the steps provided by the OP and it'll work fine.

Once you're finished be sure to set your settings back to normal (go to ##8778# and change it back to AP and re-enable debugging mode)

Information pulled from the PRL flashing thread--all credit goes to whomever came up with how to do this (which, obviously, isn't me): http://xdaforums.com/showthread.php?t=1267893
[Samsung Epic 4G Touch] jazzneel:
ah thanks so much! Do you mind if I put this on the OP? I will give you credit of course!
[Samsung Epic 4G Touch] Megatr0n.:
No problem, go ahead. :)
[Samsung Epic 4G Touch] cnstarz:
usb tethering doesn't work in CP mode, and QPST still doesn't detect when you switch back to AP.
[Samsung Epic 4G Touch] Megatr0n.:
You're using incorrect settings. USB tethering isn't supposed to work and everyone has already confirmed that QPST doesn't work in AP mode.

The instructions specifically tells you to disable USB debugging mode (which gives you the USB option) and change the setting from AP to CP. After that, connect it to your computer and wait until it installs your modem drivers. Then, open up QPST and it will work.
[Samsung Epic 4G Touch] cnstarz:
but you have to enable usb tethering in order to do this... you can't enable it if it's in CP, at least mine isn't enabling even with usb debugging turned off.... in fact, tethering can only be enabled while usb debugging is turned on.
[Samsung Epic 4G Touch] Megatr0n.:
Did you actually try the instructions or are you just arm-chairing it? Because, I already did it and I used the same method to flash a custom PRL.
[Samsung Epic 4G Touch] cnstarz:
yeah im doing it word for word. tried on 3 different usb ports on my computer. doesn't make any sense. im on caulk's rom if that makes any difference. :x
[Samsung Epic 4G Touch] Megatr0n.:
I'm using Calk 2.6 with EL26 modem and kernel, so that's not the problem.

Let's start from scratch.

First, restart your phone and computer.

1. Disable USB debugging on your phone.

2. Change settings from AP to CP.

3. Connect your phone to your computer.

4. Wait until it tells you that your phone is ready or the modem is ready.

5. Open up QPST configuration (not services) and go to the ports section.

What COM ports are available to you at this time? Are there any ports that listed as 'phone'?
[Samsung Epic 4G Touch] cnstarz:
yeah dude, no ports listed as 'phone'. bleh. i'll try on my comp downstairs. this doesn't make any sense.

---------- Post added at 04:00 PM ---------- Previous post was at 03:47 PM ----------

i figured it out. you need to add these instructions after step 6...

7. Open QPST Configurations. Start>All Programs> QPST> QPST Configuration.

8. Click on the “Ports” tab and “Add a new port”

9. Select the “COMXX – USB\QC Diagnostic” and click ok, in my case the port number was 10, your port number will be different, if you see more than one, disconnect all your external devices such as external HDDs, phones, Bluetooth dongles, ect. If you don’t see a port. Disconnect your phone, restart your computer, connect your phone and try again, you might want to remember your Epic’s port number for future use. If you still don't see a port uncheck the box for "Show Serial and USB/QC Diagnostic ports only" and add all of the USB/Unknown ports. One of them should show an active phone.
[Samsung Epic 4G Touch] Megatr0n.:
Cool, glad you got it working. Hopefully the OP updates his post to show the additional steps.
[Samsung Epic 4G Touch] jazzneel:
Done! Thanks both for all your help!!
[Samsung Epic 4G Touch] HarryJames:
Magatron thanks for helping me. I glad to see you in the forum i realy thank you to solving our problem :)
[Samsung Galaxy Nexus] peterv6:
Is there no enter button on the keyboard?

When I write an sms I would like to be able to hit the enter button to

start a new sentence on a new line but I don't seem to be able to do so?

cheers!
[Samsung Galaxy Nexus] _TB_TB_:
See here: http://xdaforums.com/showthread.php?p=23362533
[Samsung Galaxy Nexus] cwoggon:
Try typing "\n"? (Joke)

Anyways, I hadn't run into this issue yet, but I can definitely see this annoying me...

Anyone know if line breaks are removed in SMS messages? If they are, this is really a non-issue I guess.
[Samsung Galaxy Nexus] gokpog:
No, you can use line breaks but the official Android keyboard + messaging app combo never had an "enter/return" option in the messaging app. It was always replaced by the smiley button. ICS is no exception, you'll have to either use a different keyboard or SMS app if you want line breaks.
[Samsung Galaxy Nexus] mobilehavoc:
I don't want to flash a custom rom but all this talk about the vast improvements in 4.0.3 are making me wonder what the hold up is in rolling it out to Galaxy Nexus owners. At least GSM owners like myself, there aren't any carrier approvals required for that.
[Samsung Galaxy Nexus] kangxi:
Not really sure what the hold up is. I too want the pure stock version of 4.0.3, don't like a lot of customizations are whatnot. Hopefully it will come soon.

I have used Bugless Beast, which is pretty much AOSP with very minor changes and fixes.
[Samsung Galaxy Nexus] sishgupta:
I held out for about two weeks lol.

Finally caved, I flashed AOKP and Franco's Kernel. Been loving it ever since I'll never go back to stock.
[Samsung Galaxy Nexus] dwang:
My guess is 4.0.3 won't be released and google will push out 4.0.4 w the multi touch bug fixed. :)

There's also a browser crash bug w 4.0.3 that I hope google fixes as well.
[Samsung Galaxy Nexus] GR36:
There is always something coming that's the best rom in the world it seems
[Samsung Galaxy Nexus] faizalmzain:
I never experience browser crash on ics, be it on nexus s or gnex.
[Samsung Galaxy Nexus] daleski75:
When they have sorted out the bugs with the battery life then I think 4.0.3 will be released.
[Samsung Galaxy Nexus] dwang:
I guess you aren't visiting the same websites as me. Easy to reproduce.

Go to androidandme mobile site or nytimes mobile site and move around and view a couple of articles. The browser will crash soon afterwards.

It has to do with the ads. If you use an ad blocker the crashes disappear.
[Samsung Galaxy Nexus] Deleted member 2842059:
Lucky. My stock GN browser is buggy as all get out. A crash once a day? Switched to Dolphin solved the problem.

I agree though. It's 2012. Let's go with 4.03. I won't root or change. Stock only.
[Samsung Galaxy Nexus] appel_:
Just visit the desktop g+ site :-) Works every time on mine with 4.0.1
[Samsung Galaxy Nexus] Raptor1956:
If they can improve battery life by at least 25% then I'll be happy.

What other improvement are we to expect with 4.0.3 / 4.0.4?

Brian
[Samsung Galaxy Nexus] joshnichols189:
That's not even realistic. The LTE version is going to have crappy battery life almost by default. My GSM Nexus gets great battery life.
[Samsung Galaxy Nexus] Stadsport:
Nothing wrong with the battery life on the LTE version, you just have to turn off LTE ;)
[Samsung Galaxy Nexus] @rbiter:
But then you get not so fast speeds. Verizon 3g maxes out around 3mbps. But most don't see even that. Though I do have to say Verizon 3g handles congestion better.
[Samsung Galaxy Nexus] tigajr:
No problem here. Can not reproduce it. I visit both sites every single day. Running stock ICS. Browser could not be more stable.
[Samsung Galaxy Nexus] sishgupta:
I had my 4.0.3 browser crash on me Today. First time I can remember on any version and I just flashed 4.0.3 on Friday.
[Samsung Galaxy Nexus] dwang:
Are u on 4.0.3? Only happens w that version.
[Samsung Galaxy Nexus] deidein:
I've been hesitant to root, because the rooting process gives me a panic attack and I don't want to have to re-do it after a push to 4.0.3 happens. I take it there's no assumption yet as to when a push upgrade is due to happen?
[Samsung Galaxy Nexus] mobilehavoc:
I'm hesitant mainly because I'd have to wipe and because Google Wallet is working perfectly right now and I don't want to mess with it.
[Samsung Galaxy Nexus] psycho2097:
I had perfectly working google wallet also on 4.0.2 stock and thought I will just wait out till Google releases official 4.0.3. But then I got tired n flashed aokp.n believe me, it's like my phone is freaking fast .if you thought that 4.0.2 is smooth seriously you gotta try 4.0.3.its mind numbing. Plus Franco's kernel.

PS-i like all the customizations of aokp...except the bootanination.n wallet works.:-)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] psycho2097:
Just 5mins.just 1 if you can adb. 0.2 if you are already OEM unlocked.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] psycho2097:
Yea..my browser crashed like ten times already after I flashed aokp yesterday. It just freezes up,like I lost my connection.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Stadsport:
True, and I agree that there are clear disadvantages to disabling LTE, but Evdo Rev A is totally adequate for ordinary web browsing most of the time. Coming from AT&T (which has really spotty service in my area) I'll gladly take slightly-slower 3G in favor of little or no data transfer at all ;)
[Samsung Galaxy Nexus] qreffie:
I'm kind of surprised that with all the LTE phones that are out on Verizon now that they haven't figured out a way to have it switch between 3G and 4G like the GSM version does where it only uses the HSPA+ connection when the user accessing the internet and remains on regular speed for background data. That would most certainly help with the battery problem.
[Samsung Galaxy Nexus] JFMFT:
I bought a Nexus so I could stop jumping from ROM to ROM. It takes so much time that I don't have. Stock 4.0.3 or whatever the update ends up being will be great. I can wait for it, however.
[Samsung Galaxy Nexus] Stadsport:
I don't know enough about it from a technical side of things, but my understanding is it's not that simple, because LTE is GSM and EVDO is CDMA. HSPA+ is just UMTS/HSPA (3G) cranked up to eleven. Switching from HSPA to HSPA+ is like opening another door. Switching from EVDO Rev.A to LTE is packing up, checking out, and checking in at another hotel. It has to disconnect the EVDO connection and start up a new LTE connection. The transition is a lot longer and, since it has to locate a signal, a lot more power-consuming. For someone just wanting to check their facebook, it's a lot quicker to just load the page over 3G than to switch to LTE.

Again, this is just my understanding. It's probably not the clearest reflection of reality.

But for that reason, I just leave LTE off. If I'm somewhere without wifi, plugged in, then of course I'll use it. But for most everyday applications, 3G is enough for me. To each his own, of course.
[Samsung Galaxy Nexus] PaulG1488:
completely off topic here but dwang are u gonna cook a rom up for the gnex I was a big fan of your rom in the good old g1 days it be awesome if you did something for this

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ianwood:
Actually, it is because CDMA/LTE requires you to be on both networks at the same time to use LTE and receive voice calls/text. There is no handover signaling between CDMA and LTE. GSM/LTE has a built-in signaling mechanism that allows voice calls/texts to initiate a handover to 3G. This means you can shut down the 3G radio while the LTE radio is being used.
[Samsung Galaxy Nexus] martonikaj:
Yep I agree. Think a lot of people are like this. They like to root and ROM, but don't want it to be a

must have

to get the experience they want.
[Samsung Galaxy Nexus] lukassky:
Dude, i've tried to reproduce the same issue and i got NO crashes at all!! My browser works nice :/
[Samsung Galaxy Nexus] Super Chimp:
Hoping that now Christmas & the New Year are out the way that they might get on with rolling this out, assuming that they are now going to jump over 4.0.2 which I never received.
[Samsung Galaxy Nexus] s.m.knipe:
I'm not too big of a fan of this site anymore, but something interesting did pop up on it:

http://thedroidguy.com/2012/01/veri...nexus-issues-that-dont-warrant-a-replacement/

Pay attention to the dates in the "resolution" sections of this "leak." It looks like Verizon is expecting one update in mid-late January, and another one in early March...
[Samsung Galaxy Nexus] mingtaoh:
i hope they make a better gallery app...i dont really like the default one...
[Samsung Galaxy Nexus] funkyblue04:
Bloody Google. Always something! It should have been released same time as the Nexus S version. Its just not good enough!
[Samsung Galaxy Nexus] xlillo:
I did flash my sgn immediately after buy it... :D

I suppose that in short time, google will make a really fine work in android 4, fixing the bugs and extend the battery life.
[Samsung Galaxy Nexus] tigajr:
I have been trying to reproduce the crashes you have been experiencing with no success. I went to NY Times and Android and Me, moved around and read lots of articles. No problem. The ICS browser is rock solid. I am still running 4.0.1, stock ICS, no custom ROM.

I am perplexed that everyone is experiencing crashes. Maybe my GM is not working well. :p

Obs. English is not my native language
[Samsung Galaxy Nexus] mark manning:
He is mostly right except for the fact Verizon doesn't use voice over lte, only data. That is the sole reason as to why both radios are on, verizon has said it will do voice over lte as the technology evolves

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dwang:
Did you not read the part where I say it only happens on 4.0.3? If you are on 4.0.1 you won't see it.
[Samsung Galaxy Nexus] tigajr:
You are right, I didn't pay attention to the second part.
[Samsung Galaxy Nexus] rjstang:
Just got my gsm nexus today and it only updated to 4.0.1. Wonder when I will get 4.0.2 let alone 4.0.3!
[Samsung Galaxy Nexus] rockingwing:
Have my GNex now for 3 Weeks and I already flashed it several times... Now sticking with AOKP milestone 1 and franco.Kernel #8
[Samsung Galaxy Nexus] gabster21:
This is getting ridiculous, 4.0.3 has been out for almost a month now and Google still hasn't come out with a build for the Galaxy Nexus! The reason I got a Nexus was to get updates as soon as they are released.

I'm truly baffled as to what holdup is.. if an xda developer can compile and release a stable 4.0.3 ROM in his basement, how is it possible for thousands of full-time employees with access to virtually infinite amount of resources and knowledge to not be able to churn out a stable release for their flagship phone?
[Samsung Galaxy Nexus] mark manning:
+10000

I think big red has something to do with it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] crackers8199:
do they also have something to do with the gsm version not having it either?
[Samsung Galaxy Nexus] mark manning:
Maybe its part of the deal they made with google

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Game4set:
Thank you! I've seriously felt like something is up. So this is a Nexus device and all updates are supposed to be handled by Google right? Then was is up with this leaked list of bugs from Verizon?: http://thedroidguy.com/2012/01/veri...nexus-issues-that-dont-warrant-a-replacement/

It seems as if they're in charge of the phone and ironing out its issues. According to that list there's an update coming mid-January and one in March.

And I still don't understand why most Android news outlets haven't talked about that list. I'm pretty sure it seems legit. I don't see why anybody would make it up.
[Samsung Galaxy Nexus] crackers8199:
You're kidding right? You think Google would allow Verizon to dictate when they can push software updates to a nexus phone on a different network?
[Samsung Galaxy Nexus] funkyblue04:
I gave up and installed a ROM. Bloody Google!
[Samsung Galaxy Nexus] mark manning:
Kinda I do. Let's see what phones get it first as a friendly bet.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] RogerPodacter:
guys this same thing happened a lot with nexus one and nexus s. Google would release an update partially and find bugs and halt till fixed. I remember waiting for a sokid month a few times like we are now. Its just normal software traits. Verizon has nothing to do with it. And the entire planet earth would not be ignored by google due to one tiny country, and a sub carrier within that even.
[Samsung Galaxy Nexus] kirdroid:
+1 ... May be Google is waiting for verizon to complete their testing, what ever that is on a pure Google phone god knows. Due to this Google may be holding back releasing on the gsm version, so that it doesn't look bad and people start complaining about fragmentation on nexus phones.

This is just speculation but anything is possible when US carriers are involved.
[Samsung Galaxy Nexus] reuthermonkey:
Nexus S is a great example. The Nexus S 4g got some updates sooner than the Nexus S. In other cases, the Nexus S got the updates first.

Either way, it's a nexus. If you want 4.0.3, then just compile from source and build it yourself, or download a ROM.
[Samsung Galaxy Nexus] gabster21:
The part in bold contradicts the rest of the sentence, you shouldn't have to resort to compiling/flashing custom ROMs to get the latest version of Android on a Nexus device. Even more so a month after the release of the source code.
[Samsung Galaxy Nexus] jackie_jagger:
Plus I believe the code still isn't perfected for the Galaxy Nexus just yet, I mean if it was - there would've been an official image of 4.0.3 !
[Samsung Galaxy Nexus] reuthermonkey:
Huh?

They're probably not hosting the image because it's not ready for general use. While I haven't noticed any bugs, it's quite possible that Google identified some. Either way, if you compile it yourself you're essentially making a factory image from source - precisely as Google would. There's no magic to it. They provided the source. They provided the drivers.

Why is it suddenly such a foreign concept to compile a rom to get the latest version? Have you never used linux before?
[Samsung Galaxy Nexus] luffyp:
Does the fact that 4.0.3 is still not out mean that the 4.0.3 source code is still not finalized and is being modified/added/patched?
[Samsung Galaxy Nexus] EddyOS:
4.0.3 isn't out on Google's 'flagship' phone because the Nexus S is buggered since getting the rollout - hence Google pulling the update.

It'll be ready once it's ready
[Samsung Galaxy Nexus] gabster21:
Now I'm even more confused. On one hand you have people raving about how happy they are with their 4.0.3 ROMs are and how it fixes a lot of issues from 4.0.2, while on the other hand people in here are now saying that it's "not ready". When is a release ever "ready"? Just release the image and fix the bugs in the next version (4.0.4).
[Samsung Galaxy Nexus] Haelous:
Which 4.0.3 ROM are you running that is "stable" (read: zero major bugs), including no Browser crash?

They'll likely fix glaring issues like that first, or skip 4.0.3.

There are GSM phones still on 4.0.1 while all LTE phones are on 4.0.2.
[Samsung Galaxy Nexus] Simmo3D:
The only ROM I would install is ARHD 2.1.3 which is based on factory images so either way its still 4.0.2 for me. Come on Google!!
[Samsung Galaxy Nexus] ATnTdude:
I remember my Nexus One being on a leaked 2.2 build for about 6 weeks before Google OTA'd the final Froyo build. It was a pretty stable build, but it still wasn't at their QA level. Dems the breaks with a Nexus. Welcome to the party.
[Samsung Galaxy Nexus] 1Speed:
I am with ya. Most if not all vzw phones have 4.0.2, where most GSM phones (including mine) are still running 4.0.1.

Wouldn't you think they would update the GSM version first because there are no possible contract issues like their may be with Verizon. I have a feeling the majority of gnex users are on Verizon so maybe that is why they got the update first.

I really like google but they need to get their crap together.
[Samsung Galaxy Nexus] mobilehavoc:
Say what you will...I've run custom ROMs on my HTC Incredible, LG G2X and HTC Sensation 4G so I know what I'm doing but I will tell you one thing while custom ROMs are awesome and bring amazing stuff to the table they are NEVER - from experience - as stable as the factory/OEM supplied ROMs. There are always a few minor little nitpicky things that don't work or have issues that drive you crazy. I specifically got a Nexus because I want Google to release updates and not have to resort to custom ROMs. Don't think that's unreasonable.
[Samsung Galaxy Nexus] inorde:
Seconded, I have a HTC Hero which has seen many, many Roms. I want a phone with a clean Android I don't have to flash. It was cool, but I'm done with it now. There were always small issues. Even if they were based on the factory roms.

I assume there's a good reason that it takes this long. They might try to pick up a few bugfixes and improvement for the Galaxy Nexus on the way.

If everything goes as planned, I'll be picking up my Nexus on Friday.
[Samsung Galaxy Nexus] s.m.knipe:
I am fairly certain that that list is just a guide to help Verizon CSR's absorb and deflect issues people may call in with. It doesn't mean that Verizon has a hand in it, they probably asked Google for some sort of loose roadmap so they can tell people with issues "later this month" or "in late Q1" your issue will be resolved with an update. Then they can look like the hero just because they have a little information to prevent returns...
[Samsung Galaxy Nexus] mark manning:
I third all of that, that is the whole reason I got a nexus. Sick of flashing, and I wanted something stock with timely updates that just works right.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] diomark:
There needs to be a +1 button:) I fourth that..

-mark
[Samsung Galaxy Nexus] gabster21:
Exactly, people keeps saying "but you can compile your own ROM, or flash an existing one!" You can do that with any phone, you don't need a Nexus!
[Samsung Galaxy Nexus] reuthermonkey:
If you don't have the drivers you cannot. This was a very real problem with my previous phone, the samsung vibrant, for example. I can't do it for my Kindle Fire, either. In fact, that's the problem with all non-nexus devices.

Good luck compiling Android 4.0.3 from source (or 4.0.2... or 4.0.1) for the Samsung Galaxy S. Or the Nook Tablet. Tell me how that goes without the drivers.

Compiling the latest version of Android for a Nexus is trivial. I'm doing it right this moment, in fact. Currently for my GN. Next up is my Nexus S 4G.

:~/android$ time make -j8
============================================
PLATFORM_VERSION_CODENAME=AOSP
PLATFORM_VERSION=4.0.3.0.2.0.1.0
TARGET_PRODUCT=full_maguro
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=OPENMASTER
OUT_DIR=out
============================================
Checking build tools versions...

So again.

Just because the binaries aren't physically uploaded to Google's servers for deployment does *NOT* mean that you can't install it. Everything you need to get AOSP 4.0.3 on your phone is right there. If you don't have linux, just spin up a cloud server for a couple hours to compile it.
[Samsung Galaxy Nexus] gabster21:
But you can always download and flash a pre-compiled 4.0.3 ROM for any phone and that means wiping your phone and all your configs which I hate. Nexus phones are supposed to be supported by Google, support meaning releasing the actual image and

pushing

it to phones.

Many people have not even received 4.0.2 yet (I had to manually flash it myself).
[Samsung Galaxy Nexus] EddyOS:
4.0.2 is being pushed out again now so people will be getting it. The next OTA will be pushed once Google fixes whatever broke the Nexus S