Setting up GPRS and installing Opera Mini on an Eee PC
Not so long ago, a link to Habré flashed a link to the English instructions for installing Opera Mini on a computer. But, following her, I was faced with moments that required an “extra digging.” Having achieved the result, I usually wrote down a small instruction for myself for the future - so that next time I wouldn’t remember what I was doing, and not google info, but just read my own note. So, I decided to put 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 runs under them.
')
1. Some lyrics
The last 2 years on my laptops was Fedora. At first it was familiar to me from Masterhosto 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 piquant for the Russian ear?
Since mid-2008, I discovered the ideal for the size of my handbag and tasks (programming in C, J2ME, PHP, etc. - including on the road) class of devices - netbooks. But, using Eee, you come across the need to take a file and bring up the axis every time you install the system, installing the drivers for the network card, WiFi module, etc., etc. ... Having discovered a week ago that the recently installed and “doped” Fedora 10 suddenly forgot how to work with a network card (“a colleague from 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 Wi-Fi, he did not offer to start a new user by entering a username / password in the irremovable Cyrillic layout, as Fyodor did ... In general, everything that I needed earned a distort. I did not have to take the file. Well, after my software for work on the road was perfectly compiled and earned under the new axis, I realized that Eeebuntu is for a long time.
2. Configure GPRS
For 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 was not able to figure out how to do this from the console using the hciconfig utility - and I simply used the “blue-tooth” icon in the Gnome system tray, selecting “Preferences” -> “Visible and accessible to other devices” ("Always visible").
On the phone (I have listed the actions for the Nokia E61 phone), we will command: Menu -> Communications -> Bluetooth. Go to the tab "paired devices." Options -> New Security System -> New Search. We will indicate our laptop in the list of detected devices and click on the "Select" on the phone. An affirmative answer to the question "Allow automatic connection of the device?" The phone will offer to enter the secret digital code for communication. Just do not enter something commonly used like "0000" or "1234"! It is better to specify as a code the number of some phone of your friends. A window appears on your computer asking you to enter a code. Let's enter this code. Again, click on the Bluetooth icon and switch the mode to “Other devices can connect” (“Hidden”). Close the Bluetooth Settings window.
After introducing the phone to the laptop, let's proceed to setting up a GPRS connection.
Let's write the connection parameters in /etc/wvdial.conf. In my case (MTS, Moscow) they turned out like this:
By team
Switch the phone's bluetoooth mode to visible: Menu -> Communication -> Bluetooth -> Access to phone -> Accessible to all
Find the bluetooth address of the phone, having commanded on the laptop:
Return the phone to the hidden mode.
Add an entry for / dev / rfcomm2 to the /etc/bluetooth/rfcomm.conf file, adding the following lines to it (of course, replacing the phone’s bluetooth address with your own):
Reboot.
Now, to establish a GPRS connection, it’s enough to command
3. Install Java
The English manual suggested using one of the “third-party” Java implementations. I’m working on mobile development, it’s easier for me to use my familiar 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 installing the OS, I assign disks as follows: 4-gigabyte SSD- “disk” is mounted as “/”, and 16-gigabyte SSD-scale - as “/ home”. So I installed the JDK in /home/yana/jdk1.6.0_11. From the admin's point of view, this is a categorical lamination, however, you can do it right on your computer (I will be grateful for the advice on competently partitioning a netbook disk), but I have done as I prefer.
4. Emulator "mobile Java"
The official website of the micro - emulator is microemu.org . We fall from it (Download -> Releases) on SourceForge.net , from where we download the latest version of the microemulator. Unzip the downloaded archive. Now create a menu item to start the micro-emulator: System -> Control Center (Preferences) -> Main Menu -> New Item. In the opened window for setting a new menu item, we will write:
Type: Application
Name: MicroEmulator
Command: < java directory path > / bin / java -jar <path to the directory where the micro-emulator was unpacked> /microemulator.jar
In my case, the Command field looks like this:
5. We put the Opera
Download the Opera Mini files. With the help of the newly created menu item, we launch the micro-emulator. An image of a mobile phone appears on the computer screen. But surfing the web on a miniature virtual phone screen is somehow not comme il faut. In the menu of the micro-emulator, select: Options -> Select device ... -> Add ... Select the directory where we unpacked the microemulator, and in it the devices directory. In the list of files we will indicate microemu-device-resizable.jar. In the list of devices, select “Resizable device - russian keyboard”, click on “Set as default” and close the window of 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 we’ll launch the Opera Mini: File -> Open JAD File ... in the micro-emulator, specify the Opera Mini jad-file that we recently downloaded (later it will be possible to choose Opera Mini much faster: File:> Recent MIDlets ...). The line “Opera Mini” will appear in the emulator window - click on it. Opera is running! For convenience, in the Opera menu you can set the largest font: Menu -> Tools -> Options; Font size: Very large.
6. Problems with the micro-emulator
The first problem I encountered is the inability to enter text. Trying to enter a username, password or any other text on a web page, I got into a trap: click the mouse on either the left and right screen buttons “Ok” and “Cancel”, not at the corners of the program window, or Enter with Esc'eype nothing It did not help, I could not get back from the text entry window to the web page. At the docks to the micro-emulator, nothing was found. I tried to outwit the emulator by switching the emulated device from the Resizable device to the Default device. On the screen of a netbook, instead of a large browser window, the image of a mobile phone with a tiny small screen and buttons reappears - and the right / left software is perfectly pressed by the mouse. But after switching the device, the emulator resets the current application. By typing, I managed to find out that the F1 and F2 keys correspond to the left and right softbattons.
The second problem: in the text input boxes, you can print in Latin without any problems. But the Cyrillic letters sometimes (often!) Simply cease to be entered. The solution I found is not the most convenient, but quite working: after having printed the text in a text editor, I transfer it to the emulator using the usual copy / paste. Inconvenient - but better than that.
But I did not manage to upload files and copy text or URLs from the browser.
However, this method is suitable for any operating system — Windows, OSX — if only a Java machine runs under them.
')
1. Some lyrics
The last 2 years on my laptops was Fedora. At first it was familiar to me from Masterhosto 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 piquant for the Russian ear?
Since mid-2008, I discovered the ideal for the size of my handbag and tasks (programming in C, J2ME, PHP, etc. - including on the road) class of devices - netbooks. But, using Eee, you come across the need to take a file and bring up the axis every time you install the system, installing the drivers for the network card, WiFi module, etc., etc. ... Having discovered a week ago that the recently installed and “doped” Fedora 10 suddenly forgot how to work with a network card (“a colleague from 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 Wi-Fi, he did not offer to start a new user by entering a username / password in the irremovable Cyrillic layout, as Fyodor did ... In general, everything that I needed earned a distort. I did not have to take the file. Well, after my software for work on the road was perfectly compiled and earned under the new axis, I realized that Eeebuntu is for a long time.
2. Configure GPRS
For 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 was not able to figure out how to do this from the console using the hciconfig utility - and I simply used the “blue-tooth” icon in the Gnome system tray, selecting “Preferences” -> “Visible and accessible to other devices” ("Always visible").
On the phone (I have listed the actions for the Nokia E61 phone), we will command: Menu -> Communications -> Bluetooth. Go to the tab "paired devices." Options -> New Security System -> New Search. We will indicate our laptop in the list of detected devices and click on the "Select" on the phone. An affirmative answer to the question "Allow automatic connection of the device?" The phone will offer to enter the secret digital code for communication. Just do not enter something commonly used like "0000" or "1234"! It is better to specify as a code the number of some phone of your friends. A window appears on your computer asking you to enter a code. Let's enter this code. Again, click on the Bluetooth icon and switch the mode to “Other devices can connect” (“Hidden”). Close the Bluetooth Settings window.
After introducing the phone to the laptop, let's proceed to setting up a GPRS connection.
Let's 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
By 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 phone's bluetoooth mode to visible: Menu -> Communication -> Bluetooth -> Access to phone -> Accessible to all
Find the bluetooth address of the phone, having commanded on the laptop:
$ hcitool scan Scanning ... 00: 12: D2: 14: A0: 2F Yana
Return the phone to the hidden mode.
Add an entry for / dev / rfcomm2 to the /etc/bluetooth/rfcomm.conf file, adding the following lines to it (of course, 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, it’s enough to command
$ sudo wvdial mts
3. Install Java
The English manual suggested using one of the “third-party” Java implementations. I’m working on mobile development, it’s easier for me to use my familiar 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 installing the OS, I assign disks as follows: 4-gigabyte SSD- “disk” is mounted as “/”, and 16-gigabyte SSD-scale - as “/ home”. So I installed the JDK in /home/yana/jdk1.6.0_11. From the admin's point of view, this is a categorical lamination, however, you can do it right on your computer (I will be grateful for the advice on competently partitioning a netbook disk), but I have done as I prefer.
4. Emulator "mobile Java"
The official website of the micro - emulator is microemu.org . We fall from it (Download -> Releases) on SourceForge.net , from where we download the latest version of the microemulator. Unzip the downloaded archive. Now create a menu item to start the micro-emulator: System -> Control Center (Preferences) -> Main Menu -> New Item. In the opened window for setting a new menu item, we will write:
Type: Application
Name: MicroEmulator
Command: < java directory path > / bin / java -jar <path to the directory where the micro-emulator 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. We put the Opera
Download the Opera Mini files. With the help of the newly created menu item, we launch the micro-emulator. An image of a mobile phone appears on the computer screen. But surfing the web on a miniature virtual phone screen is somehow not comme il faut. In the menu of the micro-emulator, select: Options -> Select device ... -> Add ... Select the directory where we unpacked the microemulator, and in it the devices directory. In the list of files we will indicate microemu-device-resizable.jar. In the list of devices, select “Resizable device - russian keyboard”, click on “Set as default” and close the window of 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 we’ll launch the Opera Mini: File -> Open JAD File ... in the micro-emulator, specify the Opera Mini jad-file that we recently downloaded (later it will be possible to choose Opera Mini much faster: File:> Recent MIDlets ...). The line “Opera Mini” will appear in the emulator window - click on it. Opera is running! For convenience, in the Opera menu you can set the largest font: Menu -> Tools -> Options; Font size: Very large.
6. Problems with the micro-emulator
The first problem I encountered is the inability to enter text. Trying to enter a username, password or any other text on a web page, I got into a trap: click the mouse on either the left and right screen buttons “Ok” and “Cancel”, not at the corners of the program window, or Enter with Esc'eype nothing It did not help, I could not get back from the text entry window to the web page. At the docks to the micro-emulator, nothing was found. I tried to outwit the emulator by switching the emulated device from the Resizable device to the Default device. On the screen of a netbook, instead of a large browser window, the image of a mobile phone with a tiny small screen and buttons reappears - and the right / left software is perfectly pressed by the mouse. But after switching the device, the emulator resets the current application. By typing, I managed to find out that the F1 and F2 keys correspond to the left and right softbattons.
The second problem: in the text input boxes, you can print in Latin without any problems. But the Cyrillic letters sometimes (often!) Simply cease to be entered. The solution I found is not the most convenient, but quite working: after having printed the text in a text editor, I transfer it to the emulator using the usual copy / paste. Inconvenient - but better than that.
But I did not manage to upload files and copy text or URLs from the browser.
Source: https://habr.com/ru/post/50875/
All Articles