ThrottleLock 0.3 is a Pattern Based Lock like on Android. ThrottleLock is a little app to lock your device. It will only be unlocked when a pattern is drawn on a grid of points.
Important: the default code is to click on the first point (the one on the top left corner).

By default the device will be locked automatically when goes into suspended state. Optionally you can also turn it on by executing the link at Startmenu > Programs > ThrottleLock. If you don’t want the device to automatically lock remove the link placed at \Windows\Startup. The app is fully skinable. You can change the skin by replacing the png files and modifying the config.xml to change the fonts and

The app supports multi-language. Spanish and English translations are included. To translate the app to your language just copy the texts.txt file to a file called texts_XXX.txt where XXX is the 3 chars ISO code for your language and then translate the texts included in that file. Careful with the line orders and line breaks, also take care to keep the UTC16 encoding. Check the youtube video for more info

Read the rest of this entry »

ThrottleLock 0.1 is a Pattern Based Lock like on Android. ThrottleLock is a little app to lock your device. It will only be unlocked when a pattern is drawn on a grid of points.
Important: the default code is to click on the first point (the one on the top left corner).

By default the device will be locked automatically when goes into suspended state. Optionally you can also turn it on by executing the link at Startmenu > Programs > ThrottleLock. If you don’t want the device to automatically lock remove the link placed at \Windows\Startup. The app is fully skinable. You can change the skin by replacing the png files and modifying the config.xml to change the fonts and

The app supports multi-language. Spanish and English translations are included. To translate the app to your language just copy the texts.txt file to a file called texts_XXX.txt where XXX is the 3 chars ISO code for your language and then translate the texts included in that file. Careful with the line orders and line breaks, also take care to keep the UTC16 encoding. Check the youtube video for more info

Read the rest of this entry »

You guys might have read the post on android working on HTC devices. Now be_vigilant from xda-dev has putup a cab file for easy installation of Android on the HTC Touch Cruise. Remember that this is just a preRelease buid , so as times goes by and when android gets released we might be able to get a fully working version of android on our devices

Features reported to be working are: ( not tested by me personally )
1) Radio was detected and carrier signal acquired.
2) Adding a contact.
3) Calling the contact. ( The call was working through the loud speaker. )
4) Incoming call works. It displayed on screen “incoming call”. ( no ringtone though )

Bugs Found:
1) Android might disabled the touch screen after a call so you couldnt press on “hang up” on the screen to disconnect the call. You have to scroll through to hang up using the dial pad.
2 ) No ringtone was played on incoming call.
3 ) Calls were routed throughthe loud speaker on polaris ( HTC Touch Cruise )
4) SMS seems to crash the application.
5) hardware keys doesnt respond

Read the rest of this entry »

HTC PocketPC / PDA gets Android OS up and running, we all knew it was just a matter of time before this would happen , its not fully functional ( yet )..

Martin from http://it029000.massey.ac.nz/vogue/ says

A couple of weeks ago I got a new phone, it’s an HTC Vogue (branded as OKTA Touch here in New Zealand).

It is a nice piece of hardware (MSM7500) but I’m not very impressed by the OS (Windows Mobile).

I thought I would make a start at getting Linux up and running on it.

Luckily the hardware is very similar to that used by the Google android project. There are some differences, the VIC is completely different and the phone software (AMSS) is a much older version so that won’t be working soon. It seemed to hang when I turned off the MMU so I rewrote the bootloader (haret) to set up some identity pages and boot with MMU on.

It turns out that it didnt really hang, the peripheral port memory remap register just doesn’t work on this system so you can’t do any i/o with the MMU off. I figured out how the frame buffer works, wrote some debugging code to see what happens during boot and some new VIC code.

Now to get the SD card working, port this stuff to 2.6.24, get android running with the old AMSS and we’re away.

Update: all ported to 2.6.24 and android boots (no input and phone not working so not much use yet).

Update: buttons should work, Volume up/down are the return and menu keys.

Update(9/4/08): Touchscreen works, it’s not perfect and can’t be calibrated but is usable.

Haret

Kernel

initrd for android

default.txt

diffs against android git (branch android-msm)

.config

currently the buttons are not working, but the touchscreen is functional.

also check out the brave souls @ xda-dev trying this on their Vogue, Touch, Kaiser etc

In case you’re not clued into the developer’s loop when it comes to all things Android,
you might not be aware that there’s a brand-spanking-new version of the
SDK out right now, replete with new apps, a new skin, and tightened-up
functionality. In fact, it’s almost like a whole new OS. Keep your eyes
on us, as we’re whipping up an in-depth gallery so you can get a taste
of what’s to come from the Google camp.

Source : engadget.com
Image gallery : images