Recent content by E Lizzle

Hard to take advice from someone who replies to a 6 year old thread.

Go into the device manager and remove the Wifi driver. When you reboot, it will reinstall and work. This happened to me once, too, but it was a long time ago. -E

Re: Finally, moving on from windows and bidding a farewell to my 730. I ended up going with a Galaxy S5 also and my experience was similar to abhishek's. As a contrast, I only use my device for professional use. I was able to use Android's native Exchange support to sync my contacts and...

Changes made in OneNote automatically propagate to the other devices in a matter of seconds. -E

For now, I'm switching to Android. My 822 is just plain old and there's nothing really in the pipeline from either a hardware or OS perspective. The "final straw" was when someone gave my wife their old Galaxy 3 last week, so she could run MFP. The Galaxy 3 was like an insane speed demon. I...

Considering that Intel removed their phone SoC from their upcoming lineup, I'd say that ARM will definitely need to be supported by MS, unless they plan to stop targeting phones. The news had to really hurt at MS, you can tell that RT was essentially a nose-thumb in Intel's direction, to show...

Wow, let me take back my last comment! Both of my 822s (release ring) were updated last night to 10586.545 even though they are unsupported devices. This is great, as Verizon has basically zero options right now, so this will keep me going for the time being.

I'd like to express my extreme annoyance that, after having tested and provided feedback for the anniversary edition, MS switched the release preview ring to Redstone a couple of days too early... so none of us on unsupported phones will ever get the final release version without doing reg...

The problem is, on my 822, .494 is the last build I get from any ring. I'm concerned that's the last build for unsupported devices on Win 10 and after all of this I'll have to go back to 8.1 .

Same problem on two 822s, battery won't last a day even with no phone use. Problem started with this build. For some reason "Search" is using 20% even though I never use search.

My issue went away after the band's battery ran dead. When it was plugged into the charger and came back up, it worked fine.

My wife's band is hosed after today's update also. Pressing the button brings it up to a black screen, you have to push it again to get the normal background. And it won't turn off, whether you select "Yes" or "No" it just goes back to the main screen.

This is my biggest complaint about the Metro browser. It's so insanely slow to go back a page. It's always been like that and it seems like they will never fix it. Like squelcher said, as crappy as the "back" cache/re-render works it'd be quicker if they just reloaded the page down the wire. -E

I wouldn't swim with the band in a swimming pool, the chlorine will corrode the heck out of the contacts. -E

For the people having this issue, go to Nokia's website and try to get warranty service. When I entered my serial #, it was out of warranty. But I printed the shipping stuff anyway and sent it in. They sent me back a new phone for no charge. I think there is a hardware defect or something...