A step-by-step guide to set up proxy in Android mobiles



Are you a proud owner of one of the Android mobiles- Nexusone, HTC desire, Droid, Galaxy, etc? Or are you still on the search to see if Android mobiles are really worth all the hype? Then, our say would be “Android is one of the amazing cutting edge technologies of today which has features that no mobile ever can imagine”. Be it the flexibility in customization or the speed and power, Android phones rock.

One such speciality is that you can run any and every website that can be run on a computer owing to the HTML5 compatibility. Which means that you can surf, mail, chat upload and do wonders with your pocket-sized Android mobile! But the million dollar question is HOW TO ENABLE PROXY SETTING FOR THE ANDROID PHONE EASILY

Today most colleges and workplaces are wifi enabled with a local proxy configuration. It is quite obvious that the wireless network can be used for net access only with the proxy enabled. To enable proxy settings you’ll have to install custom ROM and for that ROOTING is essential. Tracking how to do that can be a cumbersome task. And that's where we come to help you do it quickly and easily. Read on !!!



ALL YOU NEED TO DO

  • Root your android mobile

  • Install custom ROM (Open Desire)

  • Set the proxy for the wireless network followed by Orbot installation
ROOTING ANDROID MOBILE (For Windows users)

REQUIREMENTS

Unrevoked3 for Windows – download here
PREPARING YOUR MOBILE


  1. Incase you have already installed HTC Sync, uninstall it.

  2. Install the hboot driver following these steps. Note: Though the steps given in the link.

  3. Reinstall HTC Sync.

  4. You would have downloaded a file called reflash-bundle.exe. Double click it.

  5. It will ask you to specify the download destination. Give a rememberable location.

ROOTING
  1. Go to the place where you installed Unrevoked.
  2. Ensure that “USB DEBUGGING” option is turned on.
  3. Select SETTINGS-"APPLICATION-DEVELOPMENT "on your Android mobile.
  4. Conect your android phone to computer through USB.
  5. Run reflash.
  6. It may take some time. Meanwhile your phone is rooted automatically.
  7. The operation has successfully if you don’t get stuck up anywhere in the middle.
  8. And at the end of all this, your phone is rooted !!!
POST-ROOTING TASKS

Once the rooting process is completed successfully, HTC Sync can be installed again.So, Finally, your android mobile is rooted and you will be in the “Recovery mode”.
Just restart your mobile in the “Normal mode” and boom !!! you have the root permissions !!!

ROOTING ANDROID MOBILE (For LINUX Users)

REQUIREMENTS

  1. A blank cd
  2. A CD/DVD writer installed with a good software to burn with. (Don’t have a burner? Try this software )
  3. A Linux Live CD (Don’t have? Try Slax)
  4. If on a wireless network, Download “Unrevoked” for Linux and copy it onto a USB stick or your phone’s SD card.
STEPS
  1. Burn your Linux Live CD to your blank CD using the burner.
  2. Put the burnt CD in the CD drive and restart the system.
  3. Your CD should start booting. If not, change the boot sequence and make your CD to boot before your hard drive.
  4. You will see Slax start screen. Select “Slax Graphics Mode (KDE)“.Wait for it to load.
  5. The Slax desktop opens. Start Firefox using the icon in the taskbar at the bottom, and go to: http://unrevoked.com/.
  6. Select the name of your Android mobile, click “Unrevoked3″ and select “Download for Linux”. Click Save when prompted.
  7. If you are on a wireless network just copy the “Unrevoked” software that you previously put in your USB drive or SD card to the Desktop.
  8. Extract the downloaded file. (Detailed steps given below)
  9. On your android phone, select Settings->Applications->Development and check if “USB Debugging” Option is turned on.
  10. Connect your mobile to the USB cable.
  11. Run “Unrevoked”(reflash) and rest while it automatically roots your mobile.
  12. If you finally see a “success” message you know that you have a rooted phone now!!!
HOW TO EXTRACT THE FILE DOWNLOADED FROM FIREFOX
  1. Close any opened windows. Go to Slax Desktop.
  2. Double-click the HOME icon on the Desktop- click Downloads.
  3. Right-click reflash.tar.gz and select Preview in Archiver
  4. In the window that opens right click the file, and select “Extract”
  5. When it asks you to select a location, click the Folder icon next the text box (named root) and select Downloads
  6. Click OK.
POST ROOTING TASKS
Once the rooting process is completed successfully, HTC Sync can be installed again.So, Finally, your android mobile is rooted and you will be in the “Recovery mode”.
Just restart your mobile in the “Normal mode” and boom !!! you have the root permissions !!!

WHAT ALL CAN I DO WITH A ROOTED PHONE???

You can
    • run any application that requires ROOT permission like


          • Shootme (allows you to take screen shots)

          • Titanium Backup(back up all apps and apps data)




    • install custom ROMS like the leaked versions of Froyo which aids you to enable proxy , our ultimate aim!!!

    • install custom themes and Bootscreen .

    • install all your applications in the memory card rather than in the phone.
ALL U NEED TO DO

  • Root your android mobile

  • Install custom ROM (Open Desire)

  • Set the proxy for the wireless network followed by Orbot installation
The next step is installing Custom Rom that supports proxy connection. One such Rom is Open Desire I will be talking exclusively on how to install the Rom following that will describe on how to use the proxy settings. You need to install Rom Manager to install Rom without any problem

STEPS TO INSTALL A ROM
  1. Take a backup of all data and application. This is very important.
  2. There is an option to do it with ease in ROM Manager called “Backup current ROM”.
  3. Download the ROM file from the post on XDA. Some custom ROMs like the HTC Sense Froyo need a radio file. If so, then download that file too.
  4. Connect the Android mobile to your system in the Disk Drive mode.
  5. Copy the downloaded ROM file( compulsorily zipped) and a radio file (if needed) into the SD card.
  6. Unmount the phone.
  7. Eject the SD card and change the phone mode to “Charge Only”.
  8. Reboot the mobile into in Recovery mode.
    • STEPS TO REBOOT
    1. If you have installed ROM Manager, choose “reboot into Recovery” option.
    2. Else if you have installed adb, just open Command Prompt/Terminal and enter the command: adb shell reboot recovery.
    3. Else Turn off your phone->Hold Volume Down key->select Recovery by pressing Power button.
  1. Now you will be in the Recovery mode.
  2. Select the zip file (ROM file)from the SD card and install it.
  3. Specify which ROM you wish to install from the given list.
  4. Once the ROM is installed, keep pressing the back button until you reach the start screen of Clockwork Recovery.
  5. Reboot the system now.

NOTE: If the ROM installation need a new radio installation to complete, check if there is any specific steps in the ROM topic, if not , repeat steps 9-12, but select the zipped radio file instead of the zipped ROM file in step 11.

15. The phone will automatically restart and attempt to boot in the custom ROM.

ABOUT OpenDesire

OpenDesire was made with made purely for the HTC Desire and is compiled from a variety of public repositories, OpenDesire is NOT a port of any HTC ROM, it is compiled from source purely with the exception of the Google Apps for which the source code is not publicised.

OpenDesire was built with stability and reliability in mind and therefore does not contain any additional applications. Since version 3.x some community maintained repositories from CyanogenMod have been included in the release.

FEATURES

  • Built 100% from source (with the exception of Google Apps)

  • 2.6.34.x kernel

  • Google Apps

  • Superuser by ChainsDD

  • Legacy A2SD with Cache2SD

  • Busybox

  • 720p camcorder support

  • FLAC / WMA / WMV media support

  • Deodexed & Zipaligned

  • many more mods/tweaks & hacks

ALL U NEED TO DO

Root your android mobile
Install custom ROM (Open Desire)
Set the proxy for the wireless network from settings followed by Orbot installation.

Here are some of the pictures showing the proxy settings in my phone..












Once all these settings are done you can browse internet via proxy through the browser.To enable using the applications via proxy Orbot installation is necessary.


Orbot:-
Install Orbot to enable using all applications via proxy settings!!
Orbot is an application that allows mobile phone users to access the web, instant messaging and email without being monitored or blocked by their mobile internet service provider. Orbot brings the features and functionality of Tor to the Android mobile operating system.
Orbot contains Tor, libevent and privoxy. Orbot provides a local HTTP proxy and the standard SOCKS4A/SOCKS5 proxy interfaces into the Tor network. Orbot has the ability to transparently torify all of the TCP traffic on your Android device when it has the correct permissions.
Orbot can be installed from android market.
I will be adding more details to the guide in future...Please post your queries,doubts in the comments section...I will try to answer them!!

Eyes-Free Review: Droid2 From MOT

Here is a quick eyes-free access overview of the MOT Droid2.

Hardware

  1. The device has a pull-out keyboard, and the buttons are much more tactile than the original Droid.
  2. The device also has dropped the hard-to-use D-Pad from the original Droid in favor of PC-style arrow keys.
  3. There is once again no dedicated number row at the top.
  4. The capacitive buttons on the front of the device appear in adifferent order from the original Droid --- with the device inportrait mode, reading left to right you have: Menu, home, back, and search.
  5. In addition, MOT ships a voice search application on the devicethat is triggered by pressing a special microphone button --it's worth learning the position of this key, since voice-searchcan be useful --- and more importantly, if you're relying onspoken feedback, hitting this button leads to the phone fallinginexplicably silent.

Software

If you look under accessibility, you'll find an applicationcalled Voice Readouts from MOT. This appears to be a screenreaderanalogous to TalkBack, though in my experience, it did notproduce spoken feedback in many instances. That said, thisapplication collaborates well with TalkBack --- and afterinstalling TalkBack from the Android Market (note: the Droid2does not come with TalkBack bundled) -- you can activate bothTalkBack and VoiceReadout for an optimal experience.

VoiceReadout appears to have a preliminary version oftouch-exploration. With VoiceReadout active, a single tap speaksthe item under the finger; a double-tap activates thatitem. Note that moving the finger around on the display does notappear to trigger touch exploration; also, touch explorationappears to be available in only some contexts.

Instances where touch exploration appears to be active

  1. Settings application.
  2. Portions of Android Market.

In general, touch exploration appears to be available inListView.

In addition, the Droid2 also includes a low-vision accessibilitytool called Zoom Mode ( look for it under Settings ->Accessibility ) this tool provides a magnification lens.

Summary

All in all, the Droid2 appears to be one of the better choicesfor eyes-free use from among the presently available crop ofAndroid phones. Touch exploration, though preliminary, is nice tosee on the platform, and the bundled low-vision magnification aidis a nice touch. Voice Readouts is also a great example of anAndroid accessibility service done right in that it co-existspeacefully with other screenreaders like TalkBack to provide anoptimal end-user experience. To users not familiar with adaptivetechnologies in general, this might not sound like a big deal ---but users of PC screenreders have long been familiar with theneed to have only one screenreader turned on. As we transition tomodern platforms like Android, it's useful to remind ourselvesthat screenreaders can in fact co-exist, with each tool providingsomething useful to create an overall experience that is greaterthan the sum of the parts.

Welcoming Loquendo Susan To Android (FroYo)

Android 2.2 (AKA FroYo) introduces many platform enhancements,and one that I find particularly relevant is the ability toplug-in additional Text-To-Speech engines. What this means froman end-user point of view:

  • Android comes with a set of built-in voices since Android 1.6--- these are the Pico voices for English, French, Italian,German and Spanish.
  • With the Text-ToSpeech plug-in mechanism in place, we can nowadd new engines to the platform.
  • The first such add-on was ESpeak, which brings support formany of the world's languages.
  • And now, vendors are able to sell high-quality add-on voicesvia the Android Market.
  • Loquendo Susan is the first commercially available voice forAndroid. Users running FroYo can buy this voice on the AndroidMarket. Thanks to the plug-in mechanism, once you buy a newvoice, you can switch all your talking applications to use thenewly installed voice --- see instructions below.

Activating And Using Newly Installed Voices

Goto Settings → Voice Input And Output →Text To Speech Settings. First, activate the newlyinstalled voice by clicking the corresponding checkbox item forthat voice. Next, go to Default Engine in theText To Speech Settings menu, and make the newlyinstalled voice your default engine. Finaly, if you want allapplications to use the new voice, check option Always usemy settings

With this in place, my Nexus and Droid both speak usingLoquendo Susan --- thus turning my Android into into a trulypleasant eyes-free device.

Stitcher And TalkBack: The World In My Ears

Shortwave Radio --- and DXing was one my hobbies growingup--- I spent many hours listening to far-off radio stations---and in the process developed a love for languages. Fastforward to the late 90's, and one could now listen to radiostations from all around the world on the Internet --- but thistime without the hiss and static of shortwave propogation. But there was acatch --- you needed to be at your computer to listen to thesestations. At home, I solved this problem by setting up a set ofliving room speakers connected to the computer in myoffice-bedroom; with a wireless keyboard, this brought Internet radio to my living room.

Fast-forward to the next decade, and I now have the Internetin my pocket in the form of a smart phone. I recently discoveredStitcher on the Android Market --- and it got me the final mile tohaving ubiquitous access to Internet Radio!

Using Stitcher With TalkBack

There is little more to say other than try it out!.Stitcher on Android is a simple Android application thatworksout of the box with TalkBack. Once you install stitcherfromMarket, use the arrow keys or trackball on your phone tobrowse through the various categories. Clicking on stations launchesplayback immediately. Note that for now, the stop buttonin the player is not navigable by the trackball --- Ihave gotten used to hitting it by dead-reckoning since it alwaysappears in afixed position. In the last few weeks, stitcher hasreplaced StreamFuriously, my previous Internet Radio solution on Android.

So here's to happy listening!A brief note on the title of thispost --- The World In My Ears was also the title of abook on DXing by Arthur Cushen fromNew Zealand --- I remember hearing his voice in the 80's on the BBC's World Service.

An Eyes-Free View Of Android At The Google IO Sandbox

Google IO 2010 is playing home to over 5,000 attendees in SanFrancisco this week. A number of Google Access engineers are atthe conference consuming and producing information --- here is abrief view of some of the exciting bits seen on the Android showfloor from an eyes-free perspective.

Hardware And New Devices From An Eyes Free Perspective

Many of the phone manufacturers were showing off their latestdevices on the show floor --- visit the Android Sandboxat Google IO to see these first hand. Charles and I walkedthrough the various displays Wednesday (May 19) afternoon to testdrive these devices first-hand --- given the large number ofAndroid devices coming out every week, this was a uniqueopportunity to see many of these devices for the firsttime. Here are some highlights:

  • All devices were running Android 1.6 or later, andconsequently, Settings/Accessibility was available onevery device. Having worked on this for the last2 years, it's extremely gratifying to see phone manufacturersincluding accessibility in their devices.
  • We found one device from Motorola where we couldn't find theaccessibility setting --- the booth representative promised tocheck after we pointed this out --- waiting to hear back.
  • My favorite device was the LG Ally --- check this device outif you get a chance.
    • Device to be sold by Verizon.
    • Device has an elegant tactual feel.
    • Front of the device sports hardware answer/hangupbuttons.
    • The pull-out qwerty keyboard is a pleasure to use --- I wouldrate this one of the best designed cell phone keyboards I'veseen.
  • Android devices continue to show up in many shapes and sizes--- re-emphasizing that there is a device for everyone. Thismakes it even more important to choose a device that meets yourparticular needs.

Software --- Android Applications Galore

We also visited the various vendors showing off their latestAndroid applications. What was gratifying was that even thoughmost of these developers had paid little thought to eyes-freeuse --- and were blissfully unaware of the existence of anAndroid Accessibility API, their applications worked for the mostpart with Accessibility enabled. Where there were gaps, we wereable to show developers what they needed to do --- everyone wasextremely receptive. Below is a brief summary of what we saw ---and a shout-out to all the friendly developers wemet:

Where

This is a very accessible application I have been usingfor a while --- the developers were thrilled to hear that it wasaccessible since they had made no special effort.

Aloqua

A competing application to Where with a veryslick visual UI. This application doesn't raise the appropriateAccess Events at present because it's a custom UI. When we firsttalked to their lead developer he was extremely hesitant sayingI dont want to change my custom UI. However, I could hear his face light up when we said You dont need tochange your look and feel --- you just need to set a couple ofcustom Java properties (specifically, property ContentDescription

Pandora

Another favorite of mine that works well with access ---except --- the player controls are unlabeled. I showed them theapplication in action on my Droid --- looking forward to seeingthis application become even more usable.

NPR News

There are many NPR tools on the Android Market --- NPRNews is the official application.The application was originally written by a Googler and OpenSourced --- I have been using it for about 4 months and it'scompletely accessible. It could do with some power-user shortcutkeys to make it even more efficient.

MLB At Bat

I had originally played with this application during lastyear's World Series; at the time, the application was quiteusable with TalkBack. I'm happy to report that nothing hasregressed --- the application still continues to to work well,except for a couple of glitches with unlabled playercontrols.The booth representatives had actually heard of accessibility ---and were receptive to fixing the remaining issues.

Summary: The light-weight design of the Android Access layerhas proven valuable in making sure that it makes it on toevery device. The minimal set ofresponsibilities the API places on developers has meant that alarge number of Android applications are accessible out of the box.

Audio Books On Android --- Thanks Librivox!

In my previousarticle, I alluded to an Audio Books application forAndroid. I did not go into much detail on the application itselfbecause I felt it deserved an article of its own.So heregoes!

In Praise Of Librivox

If you aren't familiar with the Librivox project, please visitLibrivox.orgto see the wonderful work that that project is doing. Androidapplication AudioBooks brings the wonders of Librivoxto Android --- now, you can carry all 30,000 audio books andcounting in your pocket and access themanywhere.Here are some highlights:

  • Browse, and quickly play available audio books. You canbrowse by several criteria.
  • Books you listen to get downloaded to your device and areavailable for offline listening.
  • All books provide a table of contents, allowing you to jumpto a specific portion of a book.
  • 90% of the application user interface is completelyaccessible with TalkBack --- see below for missing accessfeatures.

The only glitche with using application AudioBookswith the Android Access API is that the player controls withinthe audio-book player are presently missing contentdescriptions --- this is Android-API speak to say that thecontrols are images with missing labels. So the first time youuse this app, you'll need someone to tell you the buttons ---alternatively just experiment to discover theirfunctions. There are pause, play, rewind and forward buttons ---if the friendly folk who developed this application stumble uponthis post, please get in touch, and I can show you what you needto add to your code to make the eyes-free experience evensmoother.

Happy Listening --- And Share And Enjoy!

Microlog, Microlog4Android, SLF4J and Other Stuff

Right now a lot of interesting stuff are happening with both Microlog and Microlog4Android. I have been working with Microlog, while Jarle has been working on Microlog4Android (M4A). Let me start with Microlog.

I have started the work on Microlog V3.0. To start with I have been able to make the structure a little bit easier. For example I have removed some abstract classes, like the AbstractFileAppender. This was created for one purpose only, to be able to re-use parts of the file logging functionality between Microlog and M4A. A nice side effect of this construction is that we save some memory, both in terms of the memory footprint and run-time memory. Some bugs are fixed and there are some minor improvements.

Even though Microlog is my long time sweetheart, the most exciting things are happening within the M4A project. When moving the code from the Microlog to M4A, we skipped a lot of code. It was the core and only a few appenders that was moved. Working with the Android platform is quite different and the needs are a little bit different. For example, there is not really a need to log to the console. Instead we have replaced the ConsoleAppender with the LogCatAppender. This works as the built in log classes.  The reason for moving Microlog to the Android platform was to give Android developers more opportunities than the built in logging facilities. It is possible to use the logcat tool to log to file, but in that case you do not get the normal logcat logging in Eclipse. I have never heard of any way of logging to a file on the SD card or on the device, using the Android logging classes. With M4A it is possible to log to a file on the SD card. Just use the modified FileAppender to use M4A to log to file.

Another unique feature in Microlog is the ability to log to a remote server. This far we have the HTTPAppender which logs to a HTTP server. This is definitely something that is not possible with the standard Android logging facility. The HTTP logging is ideal for field test or similar, where the developers need to collect logs in a central place. No need to transfer log file manually. Note that during the development it might be more natural for individual developers to log to a file.

But that is not all! The most prominent addition is the SLF4J implementation. This gives you as a developer freedom to change the logging implementation whenever you feel like it. For example you want to use M4A during development for file logging, but want to remove the logging at deployment time. Just replace the M4A jar with the NOP implementation. If you want to revert back to good old Android LogCat logging (only), use the SLF4J implementation.

Last but not least, we have changed the PropertyConfigurator to read configuration files from an Android resource directory. The microlog.properties file could either be stored in the /res/raw or the /assets directory.

For those of you that want to try it out, it is available for download at: http://code.google.com/p/microlog4android/downloads/list
 
Please note that the latest release (V0.5) is rather experimental, but please try it out and give us feedback.

Powered by Blogger