[dmmarck]

Weird, both of mine are showing 41.7 on my Mac.

This one - 41,727,304 bytes
Old one - 41,727,304 bytes



Edit: Also downloaded from one the mirrors; same size again. I'll open up her guts after my movie .

If any third party can do a similar comparison be my guest, I would greatly appreciate it. Perhaps the ghost of Jobs is toying with me?

I keed I keed

[dmmarck]

Also, the md5's for each:

md5 for the new one - d8cddf4a824cb8beda1b03b8b5586da4

md5 for the old one - d8cddf4a824cb8beda1b03b8b5586da4

Edit: forgot a b in the "old one"; my apologies! They match 100%.

[Cyber Warrior]

Nope think you're right... I remember the last one being around 30kb as well.

Definitely 41.7 from the last update and this new one... both packages are the same exact size just to clear things up.. not sure why I had 30kb stuck in my head.

[2defmouze]

Also, the md5's for each:

md5 for the new one - d8cddf4a824cb8beda1b03b8b5586da4

md5 for the old one - d8cddf4a824cb8beda1b03b85586da4

This ends discussion btw.. MD5s match mean same file

Sent from my Galaxy Nexus using Tapatalk 2

[dmmarck]

I blame Verizon lol

Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2

[ruh-roh-raggy]

Thanks, guys! Maybe the older DL borked on me. I don't know much about md5's except to be sure they match. When Google pulled then reposted the file, would that in any way change the md5? Those dmmarck posted above are so close to being the same. Does that mean that Google made a change?

[dmmarck]

Thanks, guys! Maybe the older DL borked on me. I don't know much about md5's except to be sure they match. When Google pulled then reposted the file, would that in any way change the md5? Those dmmarck posted above are so close to being the same. Does that mean that Google made a change?

They are the same, I forgot a b, my apologies lol

I updated the md5 post. I typed them out digit by digit, so yeah, clearly my vision is terrible when reading in Root Explorer

[Cyber Warrior]

Thanks, guys! Maybe the older DL borked on me. I don't know much about md5's except to be sure they match. When Google pulled then reposted the file, would that in any way change the md5? Those dmmarck posted above are so close to being the same. Does that mean that Google made a change?

Good eye man... took me three times to catch that

They are the same, I forgot a b, my apologies lol

I updated the md5 post. I typed them out digit by digit, so yeah, clearly my vision is terrible when reading in Root Explorer

Figured it was a typo... had we worried there for a second

[ruh-roh-raggy]

They are the same, I forgot a b, my apologies lol

I updated the md5 post. I typed them out digit by digit, so yeah, clearly my vision is terrible when reading in Root Explorer

No prob! Thanks for doing all that checking.

[dmmarck]

Good eye man... took me three times to catch that

Figured it was a typo... had we worried there for a second

I blame 19 years of higher education for destroying whatever was left of my vision.

Good eye indeed, thanks for catching it lol

[masterxchief]

I was hoping for a new build. This one seems laggy on the lockscreen and in the browser. Also the mutitasking button takes forever to load the app list.

[danielcee3]

The keyboard is laggy on this build I revert back to 4.0.2 2 weeks ago because of that

Sent from my Galaxy Nexus using Android Central Forums

[trigun123478]

The 4g is solid on this build and battery life is better, but I do also notice more lag with this build. I also still have a few calls where the audio starts breaking up and I have to call the person back, its kinda like the mic mute problem but different. I had hoped for a little more polished build.

[stbxxl]

It's really intriguing that Google/Verizon are posting the exact same update they did for a few hours on May 1st. I wonder what caused the delay. Anyway, I'm glad I flashed the update then and don't have do it now. The new FC04/05 radios made quite a difference for me.

[dmmarck]

It's really intriguing that Google/Verizon are posting the exact same update they did for a few hours on May 1st. I wonder what caused the delay. Anyway, I'm glad I flashed the update then and don't have do it now. The new FC04/05 radios made quite a difference for me.

I've been wondering that myself. Maybe the soak test was successful?

[below_radar_00]

I finally took the plunge and installed .4 today. I installed the official leak from Google so this isn't a custom rom or anything. I'm having some major issues though.

1. I'm not receiving any phone calls. If someone calls me it rings once or twice on their end and then goes to VM. I don't get any sort of notification during the call. It's only after the call has ended that I just get notification via my incoming call log. I don't even think I get a missed call notification. I have LOTS of people calling this phone since I run a business so I'm getting plenty of reports of this and I really need to get that fixed asap. I can make calls fine and I can make and receive texts fine.

2. I don't have a lock screen anymore. When I hit the power button my phone goes straight into it's last screen. I checked the settings to make sure I'm set to slide to unlock and I am.

3. My home button doesn't work...at all. I'm running Nova Launcher so maybe it's a Nova thing but I usually have my home key set to jump back to the home screen. It's not doing that. I tried setting it up again in Nova and it didn't work. I also tried assigning the home key different functions like open app drawer to see if that worked and it didn't.

4. My LightFlow notifications won't cut off. If I get a text I have LightFlow set to give me an orange LED notification. Normally I check my text and it goes away. It's not going away now. I just get persistent notifications.

Any ideas on these? ESPECIALLY number 1!

[dmmarck]

I finally took the plunge and installed .4 today. I installed the official leak from Google so this isn't a custom rom or anything. I'm having some major issues though.

1. I'm not receiving any phone calls. If someone calls me it rings once or twice on their end and then goes to VM. I don't get any sort of notification during the call. It's only after the call has ended that I just get notification via my incoming call log. I don't even think I get a missed call notification. I have LOTS of people calling this phone since I run a business so I'm getting plenty of reports of this and I really need to get that fixed asap. I can make calls fine and I can make and receive texts fine.

2. I don't have a lock screen anymore. When I hit the power button my phone goes straight into it's last screen. I checked the settings to make sure I'm set to slide to unlock and I am.

3. My home button doesn't work...at all. I'm running Nova Launcher so maybe it's a Nova thing but I usually have my home key set to jump back to the home screen. It's not doing that. I tried setting it up again in Nova and it didn't work. I also tried assigning the home key different functions like open app drawer to see if that worked and it didn't.

4. My LightFlow notifications won't cut off. If I get a text I have LightFlow set to give me an orange LED notification. Normally I check my text and it goes away. It's not going away now. I just get persistent notifications.

Any ideas on these? ESPECIALLY number 1!

The only thing I can recommend is wiping and starting again. I haven't heard of any of those issues with this release.

[below_radar_00]

What about trying to install the update again over my current .4? Would that work?

[dmmarck]

What about trying to install the update again over my current .4? Would that work?

No. Think of the update as a "patch"--it needs to come from 4.0.2 to work correctly. If you're rooted/unlocked, you can try flashing the deodexed version featured a few pages back and in the development/rom subforum.

[below_radar_00]

It's a deodexed .4 file? Would I be able to install that without a wipe? I'm trying to avoid the wipe at all costs.

[dmmarck]

It's a deodexed .4 file? Would I be able to install that without a wipe? I'm trying to avoid the wipe at all costs.

A wipe how? If you're locked, unlocking will wipe everything, including the internal sdcard. Wiping generally is advised, if only because you want to prevent issues. If you want to try it, sure, but if you have any issues the first place to start is a wipe.

Also, if you're rooted, you can use Titanium Backup to save your stuff and restore after flashing.

[below_radar_00]

Oh sorry, yes I'm rooted and unlocked. So installing the .4 deodexed while rooted and unlocked won't initially require a full wipe? I'm looking for that ROM and I haven't found it in the subforum yet. Is it named something other than 4.0.4 deodexed?

[dmmarck]

Here ya go ==> [ROM][LINK] Stock Rooted 4.04 Official IMM76K Update

With regards to wiping, you can try not wiping, but I'd still wipe cache/dalvik. If you run into issues, then you know the first place to look is wiping data and flashing again. So in sum, I suggest you wipe, and trying without is at your own risk. You may get lucky, you may get a ton of FC's .

[Ken7]

So will there ever be an OTA update for this thing? I may just decide to join the ranks of the many that just gave up and get a phone that's more reliable.

[2defmouze]

So will there ever be an OTA update for this thing? I may just decide to join the ranks of the many that just gave up and get a phone that's more reliable.

Nope never, see ya.


What do you think? It's being tested. It will be pushed soon. If you don't want to wait, go trade in for another phone, no one will stop you. And no hard feelings. Get a phone you'll be happy with.

Sent from my Galaxy Nexus using Tapatalk 2