February 2, 2009 at 15:11Setting up GPRS and installing Opera Mini on an Eee PC
Not so long ago on Habré a link flashed to the English-language instructions for installing Opera Mini on a computer. But, following her, I was faced with moments that required "additional digging." Having achieved the result, I, as usual, wrote down a short instruction for myself for the future - so that next time I wouldn’t remember what I was doing, and not google info, but simply re-read my own note. So, I decided to install Opera Mini on my Asus EEE PC 901 with Eeebuntu.
However, this method is suitable for any operating system - Windows, OSX - if only a Java machine would run under them.
1. A bit of lyrics
The last 2 years Fedora has been on my laptops. First it was familiar to me on Masterhost hosting Fedora Core 4, then 7, 9 and finally Fedora 10. What made me change my beloved a few days ago with a stranger wearing the sultry African name Eeebuntu so spicy for Russian ears?
Since mid-2008, I discovered for myself the perfect size for my handbag and tasks (programming in C, J2ME, PHP, etc. - including on the go) class of devices - netbooks. But, using Eee, you are faced with the need to take a file and finish the axis every time after installing the system, installing drivers for a network card, WiFi module, etc., etc. ... Finding out a week ago that Fedora was recently installed and “doped” 10 I suddenly forgot how to work with a network card (a “colleague in Fedor” told me - “It happens. It is treated simply - by reinstallation”), I realized that my patience was over. So on my Eee PC appeared Eeebuntu. There were no problems - he immediately recognized both the network card and the Wi-Fi, he did not offer to get a new user by entering the username / password in an unchangeable Cyrillic layout, as Fedor did ... In general, everything, what I need, earned "sparks", for the first time I did not have to take a file. Well, after my software for working on the road compiled perfectly and worked under a new axis, I realized that Eeebuntu is a long time.
2. Configuring GPRS
For the GPRS connection, I used the wvdial utility.
First, make sure that the bluetooth service is running (/etc/init.d/bluetooth status). If necessary, change the bluetooth mode of the laptop from invisible to visible to other devices. Unfortunately, I couldn’t figure out how to do this from the console using the hciconfig utility - and I just used the “blue-tooth” icon in the Gnome’s system tray, choosing “Preferences” -> “Visible and accessible to other devices” ("Always visible").
On the phone (I have the steps for the Nokia E61 phone), we will command: Menu -> Communication -> Bluetooth. We’ll go to the “Paired devices” tab. Options -> New device sett. -> New search. We indicate our laptop in the list of detected devices and press “Select” on the phone. We will affirmatively answer the question “Allow automatic connection of the device?” The phone will offer to enter a secret digital code for communication. Just do not enter something common like “0000” or “1234”! It’s better to indicate the phone number of some of your friends as a code. A window appears on the computer asking you to enter the code. We introduce this code. Click on the Bluetooth icon again and switch the mode to “Other devices can connect” (“Hidden”). Close the “Bluetooth Settings” window.
Having acquainted the phone with a laptop, let's proceed to configure the GPRS connection.
Write the connection parameters in /etc/wvdial.conf. In my case (MTS, Moscow) they turned out like this:
The team
Switch the bluetoooth mode of the phone to visible: Menu -> Communication -> Bluetooth -> Access to phone -> Accessible to everyone
Find the bluetooth address of the phone, having ordered on the laptop:
Return the phone to stealth mode.
Add the entry for / dev / rfcomm2 to the /etc/bluetooth/rfcomm.conf file, adding the following lines to it (naturally, replacing the phone’s bluetooth address with your own):
Reboot.
Now, to establish a GPRS connection, just command
3. Installing Java
The English-language manual suggested using one of the “third-party” Java implementations. I’m developing mobile, it’s easier for me to use the usual Sun's . I installed the JDK (Java Development Kit) . If you are not involved in Java development, you can install a less "voluminous" JRE (Java Runtime Environment). Since my netbook does not foresee other users, when I install the OS, I assign the disks as follows: a 4-gigabyte SSD "drive" is mounted as "/", and a 16-gigabyte SSD-cabinet is mounted as "/ home". So I installed the JDK in /home/yana/jdk1.6.0_11. From the admin point of view, this is a categorical lamer, however, you can do it right on your computer (I will be grateful for the tips on correctly partitioning the netbook disks), but I have done so far as it suits me.
4. Emulator "mobile Java"
The official website of the "microemulator" - microemu.org . We get from it (Download -> Releases) on SourceForge.net, from where we download the latest microemulator. Unzip the downloaded archive. Now create a menu item to launch the microemulator: System -> Control Center (Preferences) -> Main Menu -> New Item. In the opened window for setting a new menu item, write:
Type: Application
Name: MicroEmulator
Command: <path to the Java directory> / bin / java -jar <path to the directory into which the microemulator was unpacked> /microemulator.jar
In my case, the Command field looks like this :
5. Put the Opera
Download Opera Mini files. Using the just created menu item, we launch the microemulator. An image of the mobile phone will appear on the computer screen. But surfing the web on the tiny screen of a virtual phone is somehow not comme il faut. In the microemulator menu, select: Options -> Select device ... -> Add ... Choose the directory where we unpacked the microemulator, and in it - the devices directory. In the list of files, specify microemu-device-resizable.jar. In the list of devices, select “Resizable device - russian keyboard”, click on “Set as default” and close the window for the list of devices: “Ok”. Now click on the “Resize” button in the lower right corner of the window. For the screen of my Asus Eee PC 901, I chose a width of 1010 and a height of 493 pixels. Now run the Opera Mini in the microemulator: File -> Open JAD File ..., we’ll indicate the recently downloaded Opera Mini jad file (then Opera Mini can be selected much faster: File:> Recent MIDlets ...). The line “Opera Mini” appears in the emulator window - double-click on it. Opera is running! For convenience, the largest font can be set in the Opera menu: Menu -> Tools -> Options; Font Size: Extra Large.
6. Problems with the microemulator
The first problem I encountered was the inability to enter text. Trying to enter a username, password or any other text on a web page, I fell into a trap: clicking on the left and right “Ok” and “Cancel” buttons, on the corners of the program window, or on Enter with Esc'ape - nothing it didn’t help, I didn’t succeed in returning from the text input window to the web page. Nothing could be found in the docks to the microemulator. I tried to outsmart the emulator by switching the emulated device from the Resizable device to the Default device. On the netbook screen, instead of a large browser window, the image of the mobile phone again appears with a tiny screen and buttons - and the right / left software is perfectly clicked by the mouse. But after switching the device, the emulator resets the current application. Using the poke method, I was able to find out
The second problem: in the text input windows you can print in Latin alphabet without any problems. But the letters of the Cyrillic alphabet sometimes (often!) Simply stop being entered. The solution I found is not the most convenient, but quite working: having previously printed the text in a text editor, I transfer it to the emulator using regular copy / paste. Inconveniently - but better than never.
But I was not able to download files and copy text or URLs from a browser.
However, this method is suitable for any operating system - Windows, OSX - if only a Java machine would run under them.
1. A bit of lyrics
The last 2 years Fedora has been on my laptops. First it was familiar to me on Masterhost hosting Fedora Core 4, then 7, 9 and finally Fedora 10. What made me change my beloved a few days ago with a stranger wearing the sultry African name Eeebuntu so spicy for Russian ears?
Since mid-2008, I discovered for myself the perfect size for my handbag and tasks (programming in C, J2ME, PHP, etc. - including on the go) class of devices - netbooks. But, using Eee, you are faced with the need to take a file and finish the axis every time after installing the system, installing drivers for a network card, WiFi module, etc., etc. ... Finding out a week ago that Fedora was recently installed and “doped” 10 I suddenly forgot how to work with a network card (a “colleague in Fedor” told me - “It happens. It is treated simply - by reinstallation”), I realized that my patience was over. So on my Eee PC appeared Eeebuntu. There were no problems - he immediately recognized both the network card and the Wi-Fi, he did not offer to get a new user by entering the username / password in an unchangeable Cyrillic layout, as Fedor did ... In general, everything, what I need, earned "sparks", for the first time I did not have to take a file. Well, after my software for working on the road compiled perfectly and worked under a new axis, I realized that Eeebuntu is a long time.
2. Configuring GPRS
For the GPRS connection, I used the wvdial utility.
First, make sure that the bluetooth service is running (/etc/init.d/bluetooth status). If necessary, change the bluetooth mode of the laptop from invisible to visible to other devices. Unfortunately, I couldn’t figure out how to do this from the console using the hciconfig utility - and I just used the “blue-tooth” icon in the Gnome’s system tray, choosing “Preferences” -> “Visible and accessible to other devices” ("Always visible").
On the phone (I have the steps for the Nokia E61 phone), we will command: Menu -> Communication -> Bluetooth. We’ll go to the “Paired devices” tab. Options -> New device sett. -> New search. We indicate our laptop in the list of detected devices and press “Select” on the phone. We will affirmatively answer the question “Allow automatic connection of the device?” The phone will offer to enter a secret digital code for communication. Just do not enter something common like “0000” or “1234”! It’s better to indicate the phone number of some of your friends as a code. A window appears on the computer asking you to enter the code. We introduce this code. Click on the Bluetooth icon again and switch the mode to “Other devices can connect” (“Hidden”). Close the “Bluetooth Settings” window.
Having acquainted the phone with a laptop, let's proceed to configure the GPRS connection.
Write the connection parameters in /etc/wvdial.conf. In my case (MTS, Moscow) they turned out like this:
[Dialer mts] Modem = / dev / rfcomm2 Phone = * 99 # Username = mts Password = mts Init2 = AT + CGDCONT = 1, "IP", "internet.mts.ru" ISDN = 0 Auto Reconnect = on Stupid mode = off Idle Seconds = 0 Auto DNS = on
The team
# sdptool browsefind out which channel is used for modem connection:
# sdptool browse
...
Service Name: Dial-Up Networking
Service RecHandle: 0x10052
Service Class ID List:
"Dialup Networking" (0x1103)
Protocol Descriptor List:
"L2CAP" (0x0100)
"RFCOMM" (0x0003)
Channel: 2
...Switch the bluetoooth mode of the phone to visible: Menu -> Communication -> Bluetooth -> Access to phone -> Accessible to everyone
Find the bluetooth address of the phone, having ordered on the laptop:
$ hcitool scan Scanning ... 00: 12: D2: 14: A0: 2F Yana
Return the phone to stealth mode.
Add the entry for / dev / rfcomm2 to the /etc/bluetooth/rfcomm.conf file, adding the following lines to it (naturally, replacing the phone’s bluetooth address with your own):
rfcomm2 {
# # Automatically bind the device at startup
bind yes;
#
# # Bluetooth address of the device
device 00: 12: D2: 14: A0: 2F;
#
# # RFCOMM channel for the connection
channel 2;
#
# # Description of the connection
comment "Modem (Nokia E61)";
}Reboot.
Now, to establish a GPRS connection, just command
$ sudo wvdial mts
3. Installing Java
The English-language manual suggested using one of the “third-party” Java implementations. I’m developing mobile, it’s easier for me to use the usual Sun's . I installed the JDK (Java Development Kit) . If you are not involved in Java development, you can install a less "voluminous" JRE (Java Runtime Environment). Since my netbook does not foresee other users, when I install the OS, I assign the disks as follows: a 4-gigabyte SSD "drive" is mounted as "/", and a 16-gigabyte SSD-cabinet is mounted as "/ home". So I installed the JDK in /home/yana/jdk1.6.0_11. From the admin point of view, this is a categorical lamer, however, you can do it right on your computer (I will be grateful for the tips on correctly partitioning the netbook disks), but I have done so far as it suits me.
4. Emulator "mobile Java"
The official website of the "microemulator" - microemu.org . We get from it (Download -> Releases) on SourceForge.net, from where we download the latest microemulator. Unzip the downloaded archive. Now create a menu item to launch the microemulator: System -> Control Center (Preferences) -> Main Menu -> New Item. In the opened window for setting a new menu item, write:
Type: Application
Name: MicroEmulator
Command: <path to the Java directory> / bin / java -jar <path to the directory into which the microemulator was unpacked> /microemulator.jar
In my case, the Command field looks like this :
/home/yana/jdk1.6.0_11/bin/java -jar /home/yana/Distr/microemulator/microemulator-2.0.3/microemulator.jar
5. Put the Opera
Download Opera Mini files. Using the just created menu item, we launch the microemulator. An image of the mobile phone will appear on the computer screen. But surfing the web on the tiny screen of a virtual phone is somehow not comme il faut. In the microemulator menu, select: Options -> Select device ... -> Add ... Choose the directory where we unpacked the microemulator, and in it - the devices directory. In the list of files, specify microemu-device-resizable.jar. In the list of devices, select “Resizable device - russian keyboard”, click on “Set as default” and close the window for the list of devices: “Ok”. Now click on the “Resize” button in the lower right corner of the window. For the screen of my Asus Eee PC 901, I chose a width of 1010 and a height of 493 pixels. Now run the Opera Mini in the microemulator: File -> Open JAD File ..., we’ll indicate the recently downloaded Opera Mini jad file (then Opera Mini can be selected much faster: File:> Recent MIDlets ...). The line “Opera Mini” appears in the emulator window - double-click on it. Opera is running! For convenience, the largest font can be set in the Opera menu: Menu -> Tools -> Options; Font Size: Extra Large.
6. Problems with the microemulator
The first problem I encountered was the inability to enter text. Trying to enter a username, password or any other text on a web page, I fell into a trap: clicking on the left and right “Ok” and “Cancel” buttons, on the corners of the program window, or on Enter with Esc'ape - nothing it didn’t help, I didn’t succeed in returning from the text input window to the web page. Nothing could be found in the docks to the microemulator. I tried to outsmart the emulator by switching the emulated device from the Resizable device to the Default device. On the netbook screen, instead of a large browser window, the image of the mobile phone again appears with a tiny screen and buttons - and the right / left software is perfectly clicked by the mouse. But after switching the device, the emulator resets the current application. Using the poke method, I was able to find out
The second problem: in the text input windows you can print in Latin alphabet without any problems. But the letters of the Cyrillic alphabet sometimes (often!) Simply stop being entered. The solution I found is not the most convenient, but quite working: having previously printed the text in a text editor, I transfer it to the emulator using regular copy / paste. Inconveniently - but better than never.
But I was not able to download files and copy text or URLs from a browser.