I noticed recently that BT were messing about inside all of their cabinets. Curious, I decided to have a look on their website to see if it was part of the 21CN roll-out. Indeed it was, and as of June I will be able to increase my broadband connection from a pathetic <3 Mbps to a delicious >60 Mbps. Annoyingly, that would be at twice the price, but it will probably be worth it.
I am, however, a long-term O2 customer and the price they are currently giving me for unlimited broadband is unmatched by far. So I went to their website to see if they offered the same product at a reduced price (O2 broadband runs over BT's local loop network). I was informed by a very helpful O2 Guru that they are currently testing on BT's 21CN network and have had positive results. They don't have a date when this will be ready but will announce it on the website when they are ready to roll it out.
So long as I don't have to wait too long, I'm happy to wait and see what O2's prices are.
As this page explains, there's a chance we'll have to fork out to replace those ancient BT sockets, and no, you cannot replace them yourself by law. Seems... fair?
P.S. The nerd in the BT adverts is an absolute tosser. Which idiot thought he was a good replacement for the yummy mummy?
Actually.
Search This Blog
O2 broadband and BT's 21CN
Labels:
21cn
,
BT
,
BT infinity
,
FTTC
,
internet
,
LLU
,
O2
,
O2 broadband
,
VDSL
,
VDSL2
TVCatchup for Android - don't bother
I have this problem when trying to stream the TVCatchup RTSP stream on my Android phone.
I was informed that an Android app is currently under development, so I thought I would give it a go, see if it makes any difference.
I did explain what the problem was, but the "developer" failed to tell me that it would make no difference, but I had to find that out for myself.
The first thing I noticed once installed on my phone was that it consumed a ridiculous amount of internal storage, despite the fact it was installed on my SD card.
For reasons unknown, by neither the development team nor I, the data used was over 2MB and the cache another 2MB. My internal storage reduced by 7MB and I still have no idea why, and neither do they.
The result? Well, I had to uninstall it as the internal memory is very restricted on my phone.
The uninstaller immediately crashed and caused my phone to reboot. On boot it was obvious that the phone believed that the app had been removed but only 4MB of internal storage had been recovered, and this was probably because I had the good sense to clear the stored data and cache.
I reported this on the feedback forum with a clear explanation of what had happened. In fact, the explanation above should be adequate, so it would be impossible for anyone with any knowledge of computing to be puzzled as to how I have come to the conclusion that the fault is with their software.
The first reply was from TVC_Colwal who copy-and-pasted some nonsense from a Wiki site about installing apps onto an SD card, despite the fact I had already explained what I had done. I had to repeat myself.
The second reply was from legoUK who told me that I was wrong, because the app is only around 1MB in size. I could not believe the stupidity of these people. This was the second time my original post had been ignored. I made it very clear in my reply that this person clearly doesn't know anything about .apk files nor the Android system.
The third reply was TVC_Colwal telling me that legoUK was the developer, I was rude, and that they were trying to help me. There are three things wrong with that statement.
I was informed that an Android app is currently under development, so I thought I would give it a go, see if it makes any difference.
I did explain what the problem was, but the "developer" failed to tell me that it would make no difference, but I had to find that out for myself.
The first thing I noticed once installed on my phone was that it consumed a ridiculous amount of internal storage, despite the fact it was installed on my SD card.
For reasons unknown, by neither the development team nor I, the data used was over 2MB and the cache another 2MB. My internal storage reduced by 7MB and I still have no idea why, and neither do they.
The result? Well, I had to uninstall it as the internal memory is very restricted on my phone.
The uninstaller immediately crashed and caused my phone to reboot. On boot it was obvious that the phone believed that the app had been removed but only 4MB of internal storage had been recovered, and this was probably because I had the good sense to clear the stored data and cache.
I reported this on the feedback forum with a clear explanation of what had happened. In fact, the explanation above should be adequate, so it would be impossible for anyone with any knowledge of computing to be puzzled as to how I have come to the conclusion that the fault is with their software.
The first reply was from TVC_Colwal who copy-and-pasted some nonsense from a Wiki site about installing apps onto an SD card, despite the fact I had already explained what I had done. I had to repeat myself.
The second reply was from legoUK who told me that I was wrong, because the app is only around 1MB in size. I could not believe the stupidity of these people. This was the second time my original post had been ignored. I made it very clear in my reply that this person clearly doesn't know anything about .apk files nor the Android system.
The third reply was TVC_Colwal telling me that legoUK was the developer, I was rude, and that they were trying to help me. There are three things wrong with that statement.
- Neither of these clowns bothered reading my original post, or understood what I was saying.
- I was providing THEM with feedback, and at no point did they try to understand or discover what was causing the runaway waste of storage due to THEIR application. I was helping them and they have the cheek to claim the reverse is true!
- I consider it rude to completely ignore what you've been told, or just fob someone off with some Wiki rubbish that they clearly don't understand.
The solution? There wasn't one. I wasn't going to get any help from Dumpty and Numpty so I had to go out hunting myself. I found this very useful page about what can and can't be cleaned up, and from there I figured out how to remove all the shite that came bundled with my latest firmware update, saving a significant amount of space. Unfortunately I never found out what damage had been done by the awful TVCatchup software. I'm guessing fsck didn't find anything either as the space was never freed.
As for the app itself?
Well, on web pages TVCatchup.com first plays an advertisement before showing you the channel. On mobile RTSP though, they did not do this. It is possible, both through RTSP and on the mobile web page, but I doubt they have any idea how to do this.
The first improvement I noticed was that there was a brief TV guide included, to show you what's on Now and Next. Very handy, although I would recommend this app from TVGuide.co.uk.
This was the only improvement, things got worse from this point on.
The video, when it starts playing over RTSP (yes, there is no point in this app at all), is intentionally orientated incorrectly so that a banner can be continually shown. So, not only does the video not fit the screen, they can now show you even more advertisements continually. Ever wished you had more advertising on TV? Well now you can!
And that is it. Literally. The app is clearly a way for TVCatchup so show more adverts, and serves no other purpose. There is this but... well, just look at it.
Advantages:
Disadvantages:
Don't bother.
[Update]
In response to this post, their Twitter twit, who types like a teenage girl, responded:
This shows exactly what kind of people work there, lol.
As for the app itself?
Well, on web pages TVCatchup.com first plays an advertisement before showing you the channel. On mobile RTSP though, they did not do this. It is possible, both through RTSP and on the mobile web page, but I doubt they have any idea how to do this.
The first improvement I noticed was that there was a brief TV guide included, to show you what's on Now and Next. Very handy, although I would recommend this app from TVGuide.co.uk.
This was the only improvement, things got worse from this point on.
The video, when it starts playing over RTSP (yes, there is no point in this app at all), is intentionally orientated incorrectly so that a banner can be continually shown. So, not only does the video not fit the screen, they can now show you even more advertisements continually. Ever wished you had more advertising on TV? Well now you can!
And that is it. Literally. The app is clearly a way for TVCatchup so show more adverts, and serves no other purpose. There is this but... well, just look at it.
Advantages:
- A Now and Next TV guide, although there is much better out there.
Disadvantages:
- The app will bugger your internal storage.
- The developers have no idea what they're doing.
- The screen is not watchable.
- There are more advertisements.
Don't bother.
[Update]
In response to this post, their Twitter twit, who types like a teenage girl, responded:
This shows exactly what kind of people work there, lol.
Labels:
android
,
baby brains
,
beta
,
butthurt
,
crap software
,
fail
,
incompetence
,
IPTV
,
reviews
,
tvcatchup
Running DIMES Agent at start-up
The DIMES Agent does not run until logged in on Windows Vista and later due to UAC as the Windows service, although installed, is blocked automatically by the operating system.
There is still a way to make sure the Agent loads at system start, however: by running it as a scheduled task.
Note: The agent is unable to interact with the desktop so you will not be able to view statistics or change settings once running (but you can through the website). It will run in the background only. Also, on Windows 7 at least, you cannot stop the task once it is running unless you kill it.
Once installed, delete the shortcut from the Startup folder as it is no longer needed, and will probably cause problems later on.
Open the DIMES Agent with the Start Menu shortcut if it hasn't loaded already and input your user details.
Close the DIMES Agent.
Then, open Scheduled Tasks in the Control Panel.
Select Action and Create Task...
Once the window is open you can give the task a name that makes sense (such as DIMES).
Change User or Group... should be changed to SYSTEM and Run with highest privileges must be ticked. UAC blocks DIMES from running because it needs higher privileges to create raw sockets in order to ping.
Next select the Triggers tab and click on New...
From the Begin the task drop-down select At startup.
Enabled should already be ticked but make sure it is and click OK.
Next select the Actions tab and click on New...
Select Start a program from the Action drop-down.
Click Browse... and navigate to the DIMES Agent executable.
Click OK.
That should be it! There are other options you can play with if you need to but once you're done click OK.
Now all you need to do is start it by selecting Run from the Actions menu.
You can check that the DIMES Agent is running by looking at the Task Manager (you'll need to click on Show processes for all users as it will be running under the SYSTEM account).
Or by checking your account statistics, although these take a little while to update.
If you're pedantic, like me, you could always use Wireshark to make sure the pings are going out.
There is still a way to make sure the Agent loads at system start, however: by running it as a scheduled task.
Note: The agent is unable to interact with the desktop so you will not be able to view statistics or change settings once running (but you can through the website). It will run in the background only. Also, on Windows 7 at least, you cannot stop the task once it is running unless you kill it.
Once installed, delete the shortcut from the Startup folder as it is no longer needed, and will probably cause problems later on.
Open the DIMES Agent with the Start Menu shortcut if it hasn't loaded already and input your user details.
Close the DIMES Agent.
Then, open Scheduled Tasks in the Control Panel.
Select Action and Create Task...
Once the window is open you can give the task a name that makes sense (such as DIMES).
Change User or Group... should be changed to SYSTEM and Run with highest privileges must be ticked. UAC blocks DIMES from running because it needs higher privileges to create raw sockets in order to ping.
Next select the Triggers tab and click on New...
From the Begin the task drop-down select At startup.
Enabled should already be ticked but make sure it is and click OK.
Next select the Actions tab and click on New...
Select Start a program from the Action drop-down.
Click Browse... and navigate to the DIMES Agent executable.
Click OK.
That should be it! There are other options you can play with if you need to but once you're done click OK.
Now all you need to do is start it by selecting Run from the Actions menu.
You can check that the DIMES Agent is running by looking at the Task Manager (you'll need to click on Show processes for all users as it will be running under the SYSTEM account).
Or by checking your account statistics, although these take a little while to update.
If you're pedantic, like me, you could always use Wireshark to make sure the pings are going out.
Labels:
DIMES
,
internet
,
network
,
networking
,
ping
,
system start
,
traceroute
,
UAC
Subscribe to:
Posts
(
Atom
)