Re: sounds very convenient
Sounds like you're stuck in the 1990s. Maybe you didn't get the memo that Microsoft is a very different company now than it was under Bill Gates.
You're not a Tory are you, because they're stuck in the past too...
33 posts • joined 24 Aug 2010
"After setup it prompts to hide the Cortana/Search box which takes up substantial taskbar space; fine if you like what it does, but a nuisance if not."
What a load of crap. You don't need this to hide the Cortana/Search box, you simply Right click on the taskbar, go to 'Cortana' and select 'Hidden'. No 3rd party junk needed to do that.
As always, research before publishing crap. :)
Unfortunately, CyanogenMod doesn't write test cases for anything they change, which is why they introduce so many bugs.
The general process:
'Lets add this, this looks good, although I don't understand what it actually does ha ha.'
'Yeah, it looks great that, it looks funky.'
*Copy, Paste, git commit (no attribution to the author)*
'Oh yeah, it seems to work alright, lets merge it.'
That's about the gist of it from what I've seen and experienced...
The issue isn't really the cap itself, although 2mbit down isn't great.
The issue is that they have implemented it in such a horribly broken way that you get a burst of high speed data for a second or two, then nothing, then another burst a few seconds later.
This causes problems with audio and video streams, and makes sites load slowly in the browser.
If they had implemented the cap properly, most people would not have made a fuss. The cap which they have implemented gives you bursts, not a continual stream of data, which causes problems.
Tmobile used to cap their PAYG offerings to 384kbit/sec down. Although this was annoying and they lied about it, their cap was implemented properly and you would get a continual 384kbit/sec down.
Virgin, on the other hand, have made an utter mess over the implementation which has allowed a lot more people to notice it than otherwise would have.
Also, it took them far too long to be honest about it, and they are still lying by stating that their data is unlimited. It isn't, it is limited, by a speed cap.
"What, like Android and Apple? Everybody ships buggy software and fixes it later, welcome to reality!"
I think both iOS and Android have more than enough marketshare and a compelling enough ecosystem to get away with a number of bugs / omissions.
MS does not, because it is make or break for WP, so you are *completely* missing the point I was making.
If someone technically minded and knowledgeable like me washes their hands of the platform because of stupid fucking bugs which shouldn't have got through QA then what is the average customer going to do?
Even though you are being a dick about it, you have a slight point.
The fail is caused by the lack of interest and complacency by MS. They have shipped a half baked, buggy OS and expect it to take off somehow, without getting their finger out to fix the bugs and finish the baking.
I like WP, and I really wanted it to succeed, but MS are being entirely short sighted and blinkered and they need to get in the real world.
They need to fix the outstanding software issues and omissions pronto, because I do wonder how many people who buy a WP8 device return it or sell it on.
Fix the shortcomings with the companion apps (syncing / Xbox music et al). They are useless and horribly buggy.
Push software updates to all devices at once instead of the very obscure way they pushed the portico update to Lumia devices which succeeded in pissing off all the early adopters of unlocked phones.
The whole thing seems very haphazard and unplanned. I wonder if MS even has a roadmap for WP8, or are they blindly bumbling along randomly?
Stick a 32GB class 10 SD into it and sync some music to it and watch it all go to fuck, probably requiring a factory reset to get into some state of normality. I suffered that on several occasions with both a Samsung and Sandisk micro SD, and that occurred with both with the shipped and the 'portico' update.
The whole Xbox music thing is an utter mess and completely unfit for purpose. The syncing applications are a load of shit. The micro SDcard support doesn't work with commodity class 10 cards and every now and again the mobile baseband will hang causing texts and calls not to get through. All documented issues on the Nokia support forums too, so definitely not an isolated case of bad hardware.
Those are the main reasons why I sold my 820, that and of course the complete lack of app traction.
The OS simply isn't ready. It needs a lot more work to bring it up to standard. It's been rushed, it feels rushed and it acts rushed. Which is a pity, because I was waiting for it a long time to replace my WP7 device.
Do what? 'Nobody exploits the boot-process.' - what a load of garbage.
The boot process is exploited by bootkits and some rootkits (TDL4 amongst others) to ensure their malicious code is ran before the Windows loader, making removal difficult because often even a format and reinstall will *not* get rid of the malware.
The initial infection happens in userspace, but after that, the malware is triggered on each boot.
Secure boot stops that.
Yeah, they have a habit of using those HDNL morons and the packaging is always dinged when they deliver something.
They also use City Sprint, who, to be fair, are pretty good, better than DPD who just bugger off without attempting to deliver half the time.
I do wish Amazon would provide options though, as you say.
It's more about dithering than the number of bits, and it's 24 bit colour (16 million colours), not 32.
Firefox seems to render using RGB565 on Android (16 bit) but they don't dither which is why it looks crap.
It looks much better with dithered RGB565, so I'm not quite sure why they don't do it.
Perhaps it is a technical limitation with some of the devices they support or their choice of minimum Android API version 8.
Yeah, it's not an issue with Chrome, it's an issue with Google.
It has only just started happening today and affects stable, beta and dev channels, of which none have been updated today, so the problem must lie server side.
Also, using terminology 'latest' version is confusing, because there are 3 latest versions, stable, beta and dev channels.
Best to put the version number, unlike most of the muppets in that linked Google thread.
Hmmm, if Win 8 is crapware, what the hell can Android be described as? A pile of buggy junk slapped together haphazardly is probably a fairly accurate description.
Seriously, actually try using Windows 8 and Android 4.0 side by side, then tell me that Windows 8 is the crapware.
I have the same issue, my cab hasn't been upgraded, but the 'area' has apparently been enabled for FTTC.
I received a letter from BT (addressed to my address, not an unaddressed leaflet) the other day inviting me to sign up to BT infinity, so I tried and it's still not fucking available.
You would think they would have the brains to send letters to those who can get the service, not those who can't.
Yeah, it's getting very old that one now. And I don't particularly like Apple either.
As well as fondleslab, and various other stupid terms that El Reg has hammered to death and beyond...think up some new ones guys, or just stop trying to be funny, because you really aren't. It's *boring* now. ;)
This post has been deleted by a moderator
Had a Vertex 2e on Win 7 x64 for about a month now, no issues at all.
It seems that these issues apply to the Vertex 3 only.
The only way that you can benefit from the Vertex 3 over the Vertex 2e is if you have a SATA3 capable mainboard.
If you have a SATA2, get the Vertex 2e, as you won't get the benefit of the Vertex 3's speed boost without SATA3.
Roger Heathcote 1, you are a funny guy, *not*. Your post reeks of condescending FUD.
I have a HTC Desire and a Samsung Omnia 7. I'll give you a clue about the one I prefer and use all the time, and it isn't the Desire.
WP7 is missing some features at the moment, that I won't dispute, but even so, it's much nicer to use than Android or iOS.
It deserves to do well.
It depends on the device. The Nexus S is a Google sponsored phone, running stock Android which is aimed at developers mainly, so the updates come straight from Google and it should always have the latest version of Android. The Nexus One is the same.
With devices like the HTC Desire, Desire HD, Samsung Galaxy S, <insert random Android device here>, the updates come from the manufacturer, not Google. The manufacturers are not forced to update the devices, so many devices end up being either abandoned, or don't receive updates in a timely manner and end up being stuck on an old, insecure version.
I expect most of it is down to commercial reasons, why should manufacturers update their existing devices when you can force people to upgrade by abandoning them.
Take the HTC Desire for example, it's been 6 months now since the Android 2.3 (Gingerbread) source was made public, and HTC still have not released a 2.3 update for the Desire, and HTC get the source *long* before it is made public.
There are 2 ways you can ensure you will always have the latest, most secure version of Android. Buy a device sponsored by Google, such as the Nexus S.
Or...do what I do, root your device and build your own ROM from the latest Android source, it's not *that* hard to do.
In my opinion, the highest performing free AV is Ariva. Any of the other free offerings, including MSE, will bog your system down. Avira also consistently has one of the best detection rates.
The highest performing paid AV I think is either Avira Premium and Norton AntiVirus (not Norton Internet Security). Symantec have really reduced the footprint and increased the performance of their client with the 2010/2011 offerings.
However, Avira Premium is cheaper and tends to consistently score higher than Norton on AV Comparatives tests.
The Android platform source code isn't being patched for current releases. That is the main issue.
Also, then you get an additional delay due to manufacturers and networks hacking about with the updates.
I would argue that you are more secure on Android if you are rooted and have a well maintained custom ROM installed, like CyanogenMod.
Rovio tweeted at the weekend that the reasons they didn't offer a paid version straight away and went for the ad supported model was that they wanted the game released worldwide, but paid apps aren't available in some countries and paid apps have never done particularly well on Android.
Apparently a paid version with no ads will be forthcoming. :)
They haven't been accepting new customers to UKOnline for about a year now.
I tried to sign up with them when I moved, but was told that they couldn't process new signups.
This was just a matter of time I guess.
Word of warning though, the SKY 'broadband' service is poor compared to the UKOnline service, so I wouldn't advise staying if you do get switched over.
Biting the hand that feeds IT © 1998–2020