Official I got the OTA DL09 update discussion. See Post #2 for problems/solutions!

[Kevin Gossett]

OK everyone, I'm at a loss. I'm trying to update my wife's Fascinate, which is mostly stock. It is rooted, and I did rename the bloat, but have renamed everything back. I am still getting the IP error though. Will CWM cause this?

 

[jack22182]

I got the update this morning. GPS is better but still NO comparison to the startup and ready speed I used to get on the Storm2 when using Google Maps.

I think they botched the button backlight behavior (or my phone isn't doing it right). Note that I did do the little mod to disable the unlock screen and let me bring the screen up from sleep to unlocked and ready just by pressing the side button. I also use the side button to put the screen back to sleep before I holster it to save battery.

When I wake up the screen with the side button, the screen comes on but the bottom row button backlight does not - I have to actually press a bottom row button to get those to light up, and in a completely darkened room there's no way to see which bottom row button I'm pressing. (BAD).

If the bottom row is lit (because I pressed one of the bottom row buttons to light them up) and the screen stays on until it dims just before it sleeps, the bottom row goes out when the screen dims, and if I press the screen to make it go bright again before it sleeps, the bottom row comes back on. In other words, the bottom row stays on until just before the screen goes to sleep instead of arbitrarily turning off on its own. (GOOD).

If the bottom row is NOT lit (because I never pressed any of the bottom row buttons) and the screen stays on until it dims just before it sleeps, and I press the screen to make it go bright again before it sleeps, the bottom row backlight comes on. In other words, the bottom row backlight will come on if I press the screen right before it sleeps even if it has not been on before in the current "screen on" session. (INTERESTING).

This seems like it should have been a simple fix. If Screen Is Lit, Light The Bottom Row Too. How hard could that be?

Is anyone else seeing this, or could it be a result of the unlock screen modification?

Jack

 

[flanny02]

One more question. Is it good or bad to have google locations checked all the time? I am pretty sure I have always had it checked, but I very rarely use GPS stuff.

Any suggestions on this?

 

[flanny02]

Which location settings should be checked?

 

[Chris Kerrigan]

Which location settings should be checked?

Depends on what your needs are. If you don't use any Verizon apps, (such as VZNav) then you don't really need Verizon Location Services enabled. I have that disabled, but Google Location Services enabled.

 

[jbr05ki]

first try the following,

unplug your phone, if on your computer you see any media sync processes running close them down, if not proceed

Settings>usb settings>set to mass storage

settings>applications>development>check debbugging mode and stay awake

plug in the device and wait 3 to 4 minutestry and mount the card with and without debugging mode on

I gotta do this every time just to get a chance to connect my phone to both my Mac and PC.

Good grief.

 

[bababooey]

Just got my update here in Stockton, CA. Tried it last night, but no dice. Worked great today. It only took about 10 minutes from start to finish. Capacitive buttons don't stay lit for entire time that the screen does. But they do stay lit a lot longer. about 2 seconds shorter than the screen. No complaints there. GPS locked me on indoors within 3 seconds and it's lined up to the exact room and side of my house. I did notice that when I wake my screen up with google maps open, the capacitive buttons don't light. Which I actually like. Apps so far seem to be working fine. Overall, I am happy with this update.

 

[johnner1999]

Anyone seeing (or hearing) much lower volume levels in Google Navigation mode

 

[Billvert]

MY phone did not automatically OTA update yet so about 15 minutes ago I went into Settings> About Phone> System Updates> Check New>.
The update was there it appears to first download a compressed file to the phone (about 45 seconds) then prompt you to install or opt out. The second portion of the update took about 4 1/2 minutes including reboot.
GPS test inside of the house:
My GPS used to take about 1 minute to show me 7 blocks from my house and another 6 to 10 minutes to get about a block away, it never found my exact location. After the update it was 1 block away (Bing Maps) in 15 seconds and right on top of my house in less than 30.
GPS Test (Inside the house) showed 7-9 satellites and 28 ft. to 13.9 ft. respectively. I have Standalone GPS checked only.
NOTE: phone was rooted with ClockworkMod and Titanium recovery. After update ConnectBot shows root prompt but phone is no longer rooted.
My phone probably did not OTA because I had my WIFI on for the last 30 hours.

Spokane, WA

 

[jdcoykendall]

Just updated my wife's fascinate which is rooted with the bloat. GPS seems to be fixed on her device. Poconos PA

 

[jackchaos]

Is anyone else seeing this, or could it be a result of the unlock screen modification?

Jack

I am seeing the exact same behavior as you.

Edit: I too have done the screen unlock modification. Perhaps that's the cause.

 

[idahoakl]

OK everyone, I'm at a loss. I'm trying to update my wife's Fascinate, which is mostly stock. It is rooted, and I did rename the bloat, but have renamed everything back. I am still getting the IP error though. Will CWM cause this?

I had to flash back the stock recovery and kernel to get the update to apply. I was receiving the same error. Not sure if you have to do both but I did and there didn't seem be any issues.

I followed the instructions here for the recovery and kernel flashes.
Odin Restore files to get you to stock - xda-developers

 

[Kevin Gossett]

I relfashed the recovery too, and no dice. I guess I will try the kernel too

Edit: Flashed the stock kernel too and now everything seems to be working. Thanks!

 

[French]

"Originally Posted by Zkippy
Oh no...Here we go again. I returned my first Fascinate due to the IP_PREVIOUS_UPDATE_FAILED error. I was never able to update it to DI01, and it was exchanged with the understanding there was a batch of Fascinates that were unable to update. When I got my current phone, DI01 installed flawlessly. I am now rooted, but have all bloatware re-enabled, and guess what? IP_PREVIOUS_UPDATE_FAILED has reared it's ugly head again, and I'm back where I was with my first phone pre-DI01.
I am having the same issue. does anyone know what to do?"


Hello,

Go to XDA Forums and under Fascinate there is an Odin file to get you back to DI01. Run ODIN with that file and then try updating. This removes root and puts you back to factory reset.

[ODIN] Full DI01 ODIN Package - xda-developers

I was rooted and debinged. I never messed with installing any new ROMs or kernels or anything. I then had to remove root due to work issues.

So now I'm also getting the IP_Previous_Failed error. I rerooted, and added back the bing search (I had just renamed it with old appended to it). I am still getting the error.

Before I ever left the Verizon store I had installed the first update (which I can't recall the numbers). So I have that fully installed and yet I am unable to update to this current.

If I go the route of Odin for restore does that mean I lose all my data? Because honestly, that is the hugest PITA I can imagine right now.

I'm so fed up with this phone.

 

[xFenixKnightx]

Got my update by manually checking here in Houston TX at about 4:30pm. Took 10 mins. GPS is working great. Soft keys stay lit on until screen times out. Love it. Thing I do not love is the icon I can't get off. The diamond with the waves. Help? Or is that there for good now?

 

[DroidXcon]

Yeah i think the GPS thing is always there now

 

[DroidXcon]

I was rooted and debinged. I never messed with installing any new ROMs or kernels or anything. I then had to remove root due to work issues.

So now I'm also getting the IP_Previous_Failed error. I rerooted, and added back the bing search (I had just renamed it with old appended to it). I am still getting the error.

Before I ever left the Verizon store I had installed the first update (which I can't recall the numbers). So I have that fully installed and yet I am unable to update to this current.

If I go the route of Odin for restore does that mean I lose all my data? Because honestly, that is the hugest PITA I can imagine right now.

I'm so fed up with this phone.

If you do a titanium backup you can get all the data back....

but yes if you use odin and do not use TB you will have a fresh copy of DI01 out of the box style

 

[makav3ll1]

Got my update by manually checking here in Houston TX at about 4:30pm. Took 10 mins. GPS is working great. Soft keys stay lit on until screen times out. Love it. Thing I do not love is the icon I can't get off. The diamond with the waves. Help? Or is that there for good now?

That icon is there for good now, but damn thats a sexy clock widget, name?

 

[belial151]

I am having the same issue. does anyone know what to do?

I called verizon wireless. They had me do a factory reset and try again, but the update still didn't work. So they are sending me a new phone.

 

[French]

If you do a titanium backup you can get all the data back....

but yes if you use odin and do not use TB you will have a fresh copy of DI01 out of the box style

Would MyBackup Pro accomplish the same thing as Titanium? I know it backs up apps and media without root...and supposedly data with root.

Sounds like now that I'm rerooted I need to do the backup, flash Odin (which I'm not even sure I know how to do), install the update, then root AGAIN, restore MYBackupPro and then maybe...just MAYBE I'm in business?