HTC's Desire and other new HTC mobiles with the Sense UI, have built-in widgets for controlling power usage, like turning on and off Wireless or Bluetooth.

One of these widgets are called Powercontrol. When this is added you may with a single touch turn on and off various powerhungry hardware elements.

These are WiFi, Bluetooth, GPS, Auto synchronisation and Screen light.

But, I was wondering how to turn on and off Mobile network. And I realized that is was also possible fairly easy, but still not with a single touch.

Hold down the power button, until the powermenu appear. In this menu you have the option of turning on and off mobile networking.

I have successfully installed Froyo on Desire and did not experience any problems.

During the first try I was stopped in process by a 25 Mb free RAM requirement. I needed to uninstall a few programs and Google Earth alone takes a lot but is easy to re-install.

All settings and data is kept and all downloaded programs still work after the update.

I find my phone somewhat faster but it may be a wish, that it has to be so.

I expect a lot more battery lifetime now, since processing is much faster, then the CPU should work much less, which in the end must improve battery life.

Update¶

Battery time has not improved im sorry to say. Battery time seems to be the same. I find it rather strange. A four times faster program must be using 1/4 active CPU time, which in turn should be positive on power usage.

Update 2¶

I have not really experienced any improvements in speed. Response times are mostly the same when using the phone in daily use. I have not really experienced much change even though there should be drastic changes in the kernel.

I have been writing a ScrewTurn plugin and have had my problem debugging it.

I read the ScrewTurn form articles on debugging plugins, and find it annoying to include my code in the ST core just to debug.

I found an alternative method I would like to share. It involves three steps

• Include the plugin project in the Screwturn solution.
• Create a post build event in the plugin project.
• fix one line of code in the screwturn source, that will not affect the use of screwturn at all.
  

What I have done is¶

1) I have a folder with the screwturn code, where the ST solution file also exists. At some other folder I have a plugin project that references the ST pluginframework code. I have also added my plugin project to the screwturn solutiuon. There is no need to move the plugin project to the screwturn solution path.

2) In my plugin project properties page, I have create a post build event, that copies the result (binaries) of my plugin project into the correct locations of the screwturn website. This post build event code is generic, since it references the plugins path with $(Target*) and the ST solution with $(SolutionDir) so it doesn't matter how these are placed, for you to use this exact code without changes.

copy /Y "$(TargetPath)" "$(SolutionDir)WebApplication\public\Plugins"
copy /Y "$(TargetDir)$(TargetName).pdb" "$(SolutionDir)WebApplication\public\Plugins"

3) I then changed one ST core code line to load the PDB file also, as shown below:

from:

asm = Assembly.Load(LoadAssemblyFromProvider(Path.GetFileName(assembly)));

to:

asm = Assembly.Load(LoadAssemblyFromProvider(Path.GetFileName(assembly)), LoadAssemblyFromProvider(Path.GetFileNameWithoutExtension(assembly)+".pdb"));

The line is located in the core project in the file ProviderLoader a few lines down in method LoadFrom, that is exactly in line number 242 for ST version 3.0.3.555.


This method of debugging make a nice separation between the plugin code and the screwturn code. I hope this may be a help to others to easier debug plugins.

Enhver der har at gøre med administrative opgaver i Windows vil snart skulle bruge PowerShell i stedet for bedstefar DOS.

Jeg er allerede startet med Powershell og det er både sjovt og interessant. Det er interessant fordi PowerShell er meget anderledes i struktur i forhold til alle andre programmeringssprog jeg nogensinde er stødt på.

Kort fortalt er det sådan at alle slags data omdannes til objekter som kan samles i lister. En sådan liste kan sendes igennem et antal kommandoer som hver gør noget (filtrerer, beregner, konverterer) ved hvert objekt i listen. Det der kommer ud i den anden ende, kan til sidst sendes til et output (fil, skærm, netværk osv.) eller gemmes som en ny liste (variabel) til senere brug.

Se mit network monitor script, som logger i en fil, hvem der forbinder sig til hvilken port på din server.

About JQuery on these pages¶

I have added JQuery to my installation of ScrewTurn.

If you look at the menu area, you see that a marker continuously runs up and down. If you hover the mouse over a link in the menu, the marker seeks the mouse position. When the mouse is removed from the menu, the marker returns to its up down cycle.

Another effect you can see is to hover the mouse over the title "Seneste ændringer" in the navigation area to the left. The list of changes now appear. If you remove the mouse, the list disappers by itself.

These effects was made by a few lines of JQuery calls, only made possible if you add JQuery support to your site.

Adding Jquery support¶

First of all the site needs to load the JQuery code on every page.

In ScrewTurn this is done by editing the MasterPage head area by using the Adminstration menu, and then click the Content editing tab.

In the Content editing window, you can select a Namespace, but this have no effect, since the root HTML Head is always used, no matter what namespace is selected when viewing pages. So select <root> namespace and then click the HTML Head area.

Insert this line in the editing area somewhere.

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js"></script>

This line tells you site to load Jquery from google, which is the fastest and most reliable way to load JQuery.

From now on your ScrewTurn site supports JQuery.

Making your first effect¶

After adding JQuery support to your ScrewTurn site, you can now create one or more effects.

One thing I have found extremely annoying on ScrewTurn is the tooltip on links, that unessacerely pop up to say exactly what is already printed on screen.

Another thing is the lack of access keys on often used buttons, for instance the save button. I have therefore added ALT+S to the save button in the page editor. the other buttons can be altered by JQuery the same way, but I'll leave this to you to figure out.

<script type="text/javascript"><nowiki>
google.setOnLoadCallback(
function() {
  // turn off titles on all a elements in PageHeaderDiv
  $("#PageHeaderDiv a").attr("title", "");
  // Add keypress ALT+S to the SAVE button if one exists
  $("input[type=submit][value=Save]").attr({accesskey: "s"});
</nowiki></script>

Ensure a good practice¶

You can through the administration menu, put this and future code in the Header file for a specific namespace or in the global HTML Head to address all namespaces.

One nice extra feature that comes out of this, is that you now can change aspects of your site, simply by editing the content files.

From this on you dont need to edit files directly on the server, like in the Theme folder - to make small fixes. Its very quick to change the text color on all p elements, and then see the effect of it. You can change the actual texts on specific elements, change colors, make quick fixes or ad-hoc changes.

Example for changing text color on all p elements in the right pane id="rigthpane" of your pages:

  $("#rightpane p").css({color: "#555"});

I will therefore urge you to follow good practice and do refactoring. You should always stop and think about, whether the changes you make to your site using JQuery in the header files, should really be placed in theme files instead.

Refactoring is a good practise which is sometimes forgotten. Consider refactoring as cleaning up. You should clean up, because if your toolbox is a mess, it takes longer to do a simple job later on.

Review of the Jabra Halo bluetooth headset¶

You are welcome to leave your comments.

I was lucky to be receiving the Jabra Halo headset for christmas gift and have now used it with different pieces of equipment.

First impressions are "wow". The design, the fit on the head and not to forget the sound, are all perfect.

Immediately after unpaking I was able to pair it with my mobile to have the pleasent and very nice and full sound flow to my ears, all within a few minutes. The batteries in my set was charged enough to make it work out of the box.

The packaging contains the headset, a short (20cm) USB cable for PC charging, a mini jack sound cord for normal headphone connections, a charging adapter, a soft pouch for storage, and a little quick start manual.

The cubs are mostly flat with rounded edges and is made by some soft microfiber, which rests softly on the ears. There is nothing to hold the cubs on the correct spot on the ears, so they have a tendency to move away from the hot spot on the ear, but only if you move quickly or if you bump into something with your head.

The headset can be folded on hinges to take up less space in the pocket. The hinges can be locked in open position, so the hinge is almost hidden. The hinges are actually a great invention. To unlock the hinges you just fold with a little extra force. The whole construction is made is plastic and the feeling to it is that it's quite fragile, but I have not experienced any fractures. Its just a feeling that makes me take more care than I normally would when folding and storing them. This is actually positive, because it makes you take care.

Plugs¶

There is only one connection to the headset, which is used for both charging and headphone connection, and it is located at the bottom of one of the cubs. the headset works both as a bluetooth headset as well as a normal headset with the proprietary 3.5 mm headphones cable.

Unfortunately the plug position makes it difficult, if not impossible, to use the headset with a firmly closed winter coat. The plug is in the way when you wear a big coat with high column. I would have preferred the plug to be inserted somewhere higher, but location of plugs is always a compromise.

Mostly you don't need the headphone plug because you just use bluetooth. But at times you want to listen to radio, which demands for a wire (antenna) connected to the phone.

Operating the headset¶

There is only one real button on the headset. This is used to start or stop playback, initate dialup and end conversations. This button works like any normal headset dialup button.

Besides the physical button there is a touch button on the edge of one of the earcubs. The touch area is visible only by the white print of a volume scale with + and - at the ends. The touch button only works with bare fingers. A hand in gloves cannot operate it.

The touch area is actually the volume button. Touch and slide the finger up to turn volume up or slide down to turn volume down. The response is a beep in the ears, and the slow speed of the touch button or the awquard sensitivity makes is a confusing experience to use it. The volume range is also not complete. The lowest volume is not silence, which makes is strange to turn down, since it seems to not respond except for the low pitch beep, even if it is already at lowest volume.

Finally the volume is not a volume command sent to the mobile, it a internally controlled volume system, which means that you have to operate the mobiles volume separately when using the headset. The volumecontrol is working internally both when using bluetooth as well as through wired operation. When the headset is connected by wire it is not possible to control volume at all, which is very annoying when using the headset for radio with the mobile.

If you double tab on volume-up of the touch area, you shift to next song, and if you double tab on volume-down twice, you simply jump to the previos song. A single tab on the volume-down just restart the current song. This is the normal function for the media player in most phones.

In my opnion the touch button is an exciting technology, but it's not really working, due to the slow speed, strange sensitivity, and the beep that is not synchonised with the fingered operation of the scale and the 'internal only' volume system.

Connections¶

I have connected the headset with my N95-8G, my Play Station 3 and my PC. All three worked with no problems.

Over the first few days the stability of the connection was not at all good. I used the headset outdoors while walking the dog, and had frequent fallouts of sound which makes the sound stutter sometimes and at other times you simply misses whole sentences of your radio podcast. My mobile was optimally placed in a highly placed jacket pocket just 30 cm from the headset.

When connected to the Play Station 3 placed 4 meters away, there was no problems. The Play Station must have a powerfull bluetooth transmitter because this is also used for the 6axis controllers.

I have also have stable sound from my PC where the transmitter is also more powerfull. Even when walking away from it, I received almost stable sound, also when there was about 5 meters and a soft wall between me and the PC.

I have used many other handfree single ear headsets with my N95-8G and only the Jabra Halo headset have these fallouts.

In my opinion it seems that the Jabra Halo bluetooth receiver is simply not sensitive enough, causing the reception to fail when a less than strong transmission hits it.

I think I need to test more and get back here with an update. I will try to adjust the Bluetooth settings on the Nokia, so it will not be interrupted by passing public profiles etc.

At times when the sound just flows without interruptions its all a very nice experience to wear the Halo :-)

Handsfree¶

The headset also contains a microphone for conversations. This works fine, but the microphone captures more noise than voice when you are in noisy environments, for instance when driving a car. The opponent can simply not hear you when this happen.

When the surroundings are resoanbly quite, then the handsfree is working like a charm. But as soon you sit in a car with the engine running and the fan is blowing and there is some driving noise, any conversation is impossible.

Noise cancellation¶

The headset contains a dedicated microphone to cancel outside noise to reduce interference from for instance other people speaking while you hear music. It seems to work somewhat, but of course noise cancellation is a strange thing that cannot be accurately determined without a well known noise. I can only say that is seems to be working.

Positive impressions¶

• Sound quality is excellent.
• Can pair with two sound units.
• Features outside noise elimination system.
• Good battery lifetime.
• Nice design.
• Sits very well on head.
• Pleasent on the ears.
• Full range of advanced features.
  

Negative impressions¶

• Sometimes fallouts in sound when using bluetooth connection.
• Difficult to control active connections when two paired units are in range.
• Touch button for volume are not well working
• Volume management is only internal and is not possible when using as wired headset.
• Handfree in car almost impossible.
• Sound quality in car is poor also when using as wired headset.
• Takes up too much space, even when folded.
• Has a fragile plastic feeling to it.
• Slides off the hotspot on the ears, just by the weight.
  

Conclusion¶

The question: Would I buy it

I have now had a change to test it without paying for it my self. And thats nice because I would probably not buy it.

The fallouts even with short distance to the mobile are too dominant to ignore in daily use. Other mobiles maybe are better, but then again, Nokia N95-8G should be one of the better to test with.

If the fallouts could be solved, then yes i would buy it.

Create a folder named GodMode.{ED7BA470-8E54-465E-825C-99712043E01C}.

Now look in the folder, which is filled with tools to manage Windows 7.