Jump to content


[Android] for the Omnia 2 info

  • Please log in to reply
7 replies to this topic




  • Members
  • PipPip
  • 109 posts
  • Devices:Samsung Omnia II; HTC Trophy
Posted Image

| General
|| Project
|| Specifications
||| Features
||| Upcoming features
||| Possible features
|| Carrier Settings
|| Keymapping
|| Videos
| Development
| Modifications
| Guides

This topic is about Android for the Samsung Omnia II.
The official development site and other links related to the developers are under the section "Links"
IMPORTANT: Always use these official sites for downloading Android and do not post mirrors! Reason for this is quite simple. This way they can track how much interest there is for their work (so they know their work is not for nothing).

Current status (February 11 2011): Beta 2 - Android 2.1 Eclair

The project
Project Homepage
Here you can log issues, browse through developer comment updates, a wiki and FAQ. Use this as your primary resource!
Current beta homepage
This is the place to find the good stuff! Here you can download Android beta and it's official updates.

Almar's Twitter
Here Almar tweets about latest developments
Thread at XDA
To see what our friends at XDA are talking about

- Android 2.1 (Eclair)
- Display and touchscreen
- Hardware keys
- Internal and External storage
- Sound
- 2D acceleration and brightness control/backlight
- Vibrator
- Battery driver/charging
- Phone
- Wifi & Android market
- 3G/data

Known issues:
- No GSM data/3G
- Random freezes
- Processor always 100% (no sleep)
- Incorrect clock timings
- Incorrect clock timings after sleep
- Incorrect WiFi status bar
- Call drops sound after 30 seconds, use call light application from Market as workaround
- Video not working
- Iptables/netfilter not supported by kernel

Upcoming features
- Android 2.2 (Froyo) / samdroid 8.5 (with hardware accelerated video and all its optimizations!)
- Android 2.3 (Gingerbread) {slooooow and some Eclair features broken}
- Bluetooth implementation in Android (working at kernel level)
- Camera's (Output ok, fixing last issues)
- Sensor implementation in Android (working at kernel level)

Possible features
- Open Source (github.com build)
- TV-Out

Carrier settings
Android WIKI APN list for a lot of carriers

Brazil - Tim, Claro, Oi, Vivo
Canada - Rogers, Fido, Bell
Croatia - T-Mobile, Vip, Tele2
France - Bouygues Télécom, Virgin, NRJ, M6Mobile, LeclercMobile, Zéro Forfait, Orange France, SFR, Orange Ile de la Réunion (D.O.M)
Spain - Vodafone, Movistar, Orange, Yoigo, Simyo
The Netherlands - KPN&Hi, Vodafone, Tele 2, Telfort, T-Mobile

Posted Image
Cube key - Menu (pressed for search)
Camera key - Back
Volume up key - Volume up
Volume down key - Volume down
Stand-by key - Stand-by (pressed for phone options like power off)
Back key - Search
Call key - Phone app / call (pressed for voice dialer)
Hang-up key - Stand-by? / hang-up

January 19 - Beta 1

Development News

Edited by XeOS, 14 February 2011 - 08:18 AM.

  • 0




  • Members
  • PipPip
  • 109 posts
  • Devices:Samsung Omnia II; HTC Trophy
Development news

2011-02-11: We have prepared Beta2 SD card installer (1024mb only). It includes latest update (2011-02-10) Download at official site (it will wipe Your current installation). NO 2D/3D libs.
2011-02-09: Sleep problem solved, Alarm function working, battery drain and percentage correction, upgrading from C4 to D1 the 6500 framework, more powerfull dalvik machine (Linpack 5.x) and all the usable corrections published
2011-01-31: GSM data network working + latest kernel,modules, patches and applications from Rapid and Voyteckst su correction.
2011-01-27: The timer after sleep and battery charge corrected. Interface for the radio signal level,powerstate,etc. implemented by Beamrider. New su for rooting
2011-01-19: Sleep problem solved
2011-01-18: Small update for correcting installtion problems
2011-01-17: Beta 1 Test version

Edited by XeOS, 14 February 2011 - 08:16 AM.

  • 0




  • Members
  • PipPip
  • 109 posts
  • Devices:Samsung Omnia II; HTC Trophy

2D/3D Drivers:
on Rapidshare
on Filesonic

Button fixes:
Update file to wake up the phone with Hang up and Lock buttons only - by Rapid81
Menu button unlock policy fix - by ult_nrg

Calibrator tool for beta2:
Tool for calibrating the touchscreen on O2 in Froyo by hayashi1986

(Live) wallpapers/bootscreens/themes:
Here you can find the thread for Omnia II Android bootscreens/ (live) wallpapers/themes - by paranoiadk
Thread to discuss and share liva wallpapers - by aafi-rocks

Edited by Speedfrog, 28 May 2011 - 08:44 PM.

  • 0




  • Members
  • PipPip
  • 109 posts
  • Devices:Samsung Omnia II; HTC Trophy
User updates:
Radie's update package - February 4 2011
- All official updates
- 2D/3D driver package (initial one posted on official thread by Rapid81)

Edited by XeOS, 05 February 2011 - 10:50 AM.

  • 0




  • Members
  • PipPip
  • 109 posts
  • Devices:Samsung Omnia II; HTC Trophy


Manual install guide on My Storage - by quato7906
Manual install guide on My Storage YouTube video - by neio
Manual install guide from ubuntu - by emptyara
Beta 2 clean install on Windows - by Kapica
1. Clean SD card of beta1
a) Clean format with SD Formatter, or
Use EASEUS Partition Master and format the EXT2 partition on SD card

2. Rename o2b2filesys.tar.gz to ext2.tar.gz

3. Copy ext2.tar.gz and new zImage to My Storage and overwrite

4. Go to O2Beta directory and run haret.exe
And thats it, u get beta2 installed, rest as usual...
To add 2D/3D rename tar.gz to o2b2update as devs said...
If you experience reboots I think its to lack od 2d/3d, open the 2d/3d o2update.tar.gz and copy system directory into ext2.tar with Total Commander, save archive, copy to My Storage, and try to install now

then I've tried to add the 3D drivers to the archive and 7Zip told me that there are 2 files with the same name in \modules.

There were 2 duplicated files (2 files with the same name + another 2 files with the same name)

the names are : xt_mark.ko and xt_tcpmss.ko

I renamed the smaller ones and Android started.

Beta 2 install - by FactionOne, addition by barryhamsy

For folks who can't or don't want to do an Ubuntu install...

To do an 'easy' install to SD using the NEW BETA2 files...

1) Open a BETA1 package.
2) Put the o2beta folder, haret.exe and default.txt in the root of your 'My Storage'
3) Open the BETA2 package.
4) Put the zImage and o2b2filesys.tar.gz in the root of your 'My Storage'
5) Rename o2b2filesys.tar.gz to ext2.tar.gz (this is so the 'old' installer will be able to extract the file for you)

[EDIT: Thanks to ult_nrg for testing/feedback, here are confirmed steps for 2D/3D Library install]

6) Download a 2D/3D Library package (these are linked in the thread, I'm using a package by nOObody, recommended by Rapid81) [I will add a link when I go back through the thread]- Link http://pfc.treck.hu/...2bupdate.tar.gz
7) Rename the o2update.tar.gz file to o2b2update.tar.gz (for new auto-update routine) and put it in the root of your 'My Storage'
8) (Where necessary) Clear (on PC), and Format your SD card in the WinMo Samsung Settings
9) Run \My Storage\o2beta\haret.exe
9a) -= haret.exe will boot a linux shell on your device and set-up the partitions on the SD card, wait for device to reboot=-
10) Run \MyStorage\haret.exe
10a) -= haret.exe will boot Android from your SD card and set-up routine will run, wait for Android to start=-

My advice once you've booted for the first time is let the device 'settle down' for maybe a minute (try to keep the screen awake (tap occassionally) just in case), then shut it down and boot again before changing settings/installing apps etc. In theory it shouldn't make a difference, but I (and some others) have found it seems to help.

Good luck!


Follow everything up here and here is my next step.

1. Download from Official Beta website -http://o2droid.phj.hu/o2b2update.tar.gz
2. Rename to o2bupdate.tar.gz and then put in My Storage root.
3. Run Haret.exe from My Storage
4. Shutdown and restart back to WM.
5. Download Radie Package - http://www.4shared.c...dR/Updates.html
6. Put everything in Updates folder to My Storage root.
7. Run Haret.exe from My Storage
8. Shutdown and restart back to WM.
9. Download button fixes by Rapid81. Refer post 3
10. Put in My Storage root and run Haret.exe
11. Shut Down and back to WM.
12. Download button policy fix by ult_nrg. Refer post 3
13. Put in My Storage root and run Haret.exe

How to get additional language fonts such as Hebrew, Arabic - by felalex
All you need to do is to find the correct .ttf files and put them in /system/fonts. Once you find them create an update in .tar.gz format
This is based on the following guide

How to change the keymapping - by Rapid81
If you want to change the buttons mappings under the Android, first you need to know the necessary keycodes.

key 158 - Camera button
key 139- Middle button
key 217 - WinMo Back button, near the Camera button
key 231 - Call button
key 115 - Volume Up button
key 114 - Volume Down button
key 116 - Lock and Hangup button

The Functions you can use to map to the keys:
BACK - Back function
MENU - Menu function
SEARCH - Search
HOME - Home function
CALL - Start a call function
VOLUME_UP - Volume up
VOLUME_DOWN - Volume down
POWER - Lock/Screen off function
CAMERA - Start the Camera

All the keymappings can be found in the system\usr\keylayout\qwerty.kl file.

You can found WAKE and WAKE_DROPPED texts after some mappings. The WAKE means, if you put it after a function, that function will turns off/on the screen. The WAKE_DROPPED probably means, the function not do this things, but I noticed, either with this, the screen will turn on when you press the button. If you not put these after a function, the screen will not turn off or on.

After you edited the qwerty.kl, you need to overwrite the old one on the ext2/3 partition of the Android. You can do it with ADB Console or with an update file (o2bupdate.tar.gz).

Here is an update file to wake up the phone with Hang up and Lock buttons only
Menu button unlock policy fix - by ult_nrg

ADB Installation and usage tutorial - by Rapid81
Click here
- Windows driver help for ADB - by E.C.
It could be because the driver inf didn't have your phone hardware IDs, you may need to manually add your hardware IDs to the inf file.

To find out your phone hardware IDs
- Open "Device Manager"
- Select the "device with exclamation mark" and open "Properties"
- Go to "Details" tab and change the "Property" to "Hardware Ids"

- Open my inf file
- Add or Modify your hardware IDs

%USB\VID_04E8&PID_681C.DeviceDescRelease%=androidusb.Dev, <<YOUR HARDWARE IDS>>
%USB\VID_04E8&PID_681C&MI_02.DeviceDescRelease%=androidusb.Dev, <<YOUR HARDWARE IDS>>
%USB\VID_04E8&PID_681C.DeviceDescRelease%=androidusb.Dev, <<YOUR HARDWARE IDS>>

And try again!

Wireless ADB - by paranoiadk

No one seems to have explored the possibilities with wireless adb...
Well, there's a program in market, namely "adbWireless" that lets you connect your phone with an adb console wirelessly.
But I went further.

You can download QtADB here: http://qtadb.wordpress.com/
It works with adbWireless and it works flawlessly.


Android manager WiFi: http://global.mobile...oad/android.jsp
(also requires their own market app)

There are tutorials and description on the sites. If you need more info, google it. It's easy to find.

GPS quick fix - by Voyteckst
For those with gps problems (and maybe others):

Uncomment following entries in /etc/gps.conf (thanks for Sandor):

... or download following file: o2bupdate_gps.tar.gz, rename to o2bupdate.tar.gz, put to My Storage, boot android ;-)
Rapidshare mirror

It allows from now to download xtra.bin file for faster fix.

- Install Android on My Storage fo better performance
- Have a class 6 or 10 SDHC card for better performance when installing on SD
- Format your storage for installation of Android from within WinMo for best results
- Skype works on Android 2.2 (Froyo)
- If you have rooted your phone, use Root Explorer to see it

Edited by XeOS, 14 February 2011 - 06:19 PM.

  • 0




  • Members
  • PipPipPipPipPipPip
  • 1,243 posts
  • Gender:Male
  • Location:Hungary
  • Devices:Motorola Defy+
ADB Installation and usage tutorial

Step 1
First af all, you need to set the ports under Android.
To do that, write this to the phone: *#7284#
Then you need to select the followings:
UART -> Modem

Attached File  N__vtelen1.jpg   56.75KB   1486 downloads

After this, go to the Settings\Applications\Development and check the USB Debugging if it not checked already.

Attached File  N__vtelen2.jpg   85.84KB   132 downloads

Step 2:
Download the Android SDK from here. Install (if you downloaded the installer) or unzip to a location where you'll easly found it. For example C:\android-sdk-windows.

Step 3:
Download Samsung KIES. Install it. It contains 2 of the 3 necessary drivers.

Step 4:
Download the SamsungADB.zip and unzip it somewhere, where you'll easly found it.

Step 5:
If the Android did not went to sleep after it started, then unplug from USB (if it plugged) and put to sleep with the Hangup button. After that, plug onto the USB. The Windows will install 2 of the 3 drivers automatically. The 3rd one will not be found. This will be the ADB driver. Go to the Device Manager and browse the driver (not just add the path to the search root, you need to select the driver yourself!!!) what you extracted from the SamsungADB.zip. Choose one of the followings:
Samsung Android Composite ADB Interface or ADB testing interface and install it.
If the Windows ask for a confirmation to install a not trusted driver, then say yes.

Step 6:
Press Windows+R and type into "cmd".
In the upcoming windows, navigate to the unzipped or installed Android SDK directory with the following command:
For example: "cd c:\android-sdk-windows"
In there, navigate to the "platform-tools" directory with this command:
"cd platform-tools"

Step 7:
This is where the party started. ;)

Commands you can use:
  • adb devices -> If you see your device here, you did a good job. ;)
  • adb shell -> console
  • In the console:
  • logcat -> List all android events/errors
  • cat /proc/kmsg -> kernel log
[*]adb push filename folder -> Send file from Windows to android, to the specified folder
[*]adb pull filename -> Receive file from Android to Windows
[*]Backup all installed applications (rooting is necessary):
  • tar czvf /storage/App_backup.tzg /data/app* -> Backup
  • tar xzvf /storage/App_backup.tzg -> Restore

Alternative way from voyteckst. THX!
  • root Your phone
  • install adb wireless from Market
  • install android sdk on Windows
  • run wifi on android
  • enable adb wireless (it will show ip addres and ip - remember it)
  • from Windows commandline: adb connect android_ip_address:port
Use adb like normal ;-)

Edited by Rapid81, 09 February 2011 - 09:14 AM.

  • 1



    The Viking

  • Moderator Team
  • PipPipPipPipPipPip
  • 2,014 posts
  • Gender:Male
  • Location:Norway
  • Interests:football
  • Devices:Omnia II 16 GB
XeOS hasnt been online since 9.march, so send me the info and i can add it.

  • 0




  • Members
  • Pip
  • 23 posts
  • Devices:Samsung I8000 Omnia II
I was wondering, what is the button at the top right for (when you drag down the top bar) the one with the two opposing arrows? i dont mean the on next to wifi, the data connection one, but the one that only becomes visible when you drag down the top. thanks for the answer

  • 0

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users