• If you are experiencing issues logging in, we moved to a new and more secure software and older account passwords were not able to be migrated. We recommend trying to reset your password, then contacting us if there are issues.
  • Nearly done! Migration cleanup is mostly done. There are a small number of issues left that we continue to work on, but all the heavy lifting is done. We still would love to hear feedback over at this thread and also check out the new XDA app! Thanks and we hope you enjoy the new forums, and thanks for your support of XDA <3

[ROM][5.1][Unofficial OmniROM for Galaxy S I9000 | I9000B]

Sidebar
Status
Not open for further replies.
humberos

humberos

Inactive Recognized Developer
Oct 8, 2010
1,616
5,321
0
Brasília
www.humberos.com.br
Mar 13, 2015 at 11:39 PM

Please read this post before
http://forum.xda-developers.com/showpost.php?p=61424227&postcount=1241

This is an unofficial build of Omni for the Samsung Galaxy S
(aka I9000|I9000B aka galaxysmtd|galaxysbmtd)​
Code: 
/*
 * Your [I]old[/I] warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */
Installation Instructions

Coming from JB
  1. You must be rooted!
  2. You must have a custom recovery installed.
  3. Wipe your device.
  4. Flash the ROM zip, it will appear an error, warning that all data will be wiped due different partition table.
  5. Reflash the ROM zip, it will continue now.
  6. Flash the GAPPS.
  7. Reboot. (It can take up to 5 min.)
  8. Enjoy
Coming from Omni Kit Kat
  1. Flash the ROM zip
  2. Reboot
  3. Wait the upgrading android dialog
  4. Enjoy!
Google Apps

Root

Unofficial OmniROM Download


XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy S I9000

Contributors
humberos
Source Code: https://github.com/omnirom

ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP

Version Information
Status: Beta

Created 2015-03-14
Last Updated 2015-04-17
 
Last edited:
  • Like
Reactions: smamow, ddudek77, orange_moon35 and 132 others
humberos

humberos

Inactive Recognized Developer
Oct 8, 2010
1,616
5,321
0
Brasília
www.humberos.com.br
Mar 13, 2015 at 11:40 PM
Know Issues | Workaround

20150313

Issues
  1. Dialer -> *#06# -> FC
  2. Gesture Typing (AOSP Keyboard)
Workaround
  1. Recents Apps: Settings-> Buttons -> custom actions (on) -> home key -> longpress -> action -> Recents app switcher
  2. Home [wake]: Settings->Buttons->Custom actions (on)->Home key->Button wake (on)

20150325

Fixed
  1. Dialer -> *#06# -> FC
  2. Home button actions
Features
  1. SELinux (enforcing)
Issues

  1. Gesture Typing (AOSP Keyboard) it's not broken since it requires gesture libs from GApps.
  2. Microphone mute
  3. Can't move app to sd
  4. Soft reboots -> workaround (click here)

20150401

Fixed
  1. SELinux
  2. Soft reboots
Features
  1. LZ4 as default ZRAM memory compressor
Issues
  1. Microphone mute during calls
  2. Can't move app to sd
  3. Camera video recording - fixed(requires kernel update) - also -> click here

20150416

Fixed
  1. SELinux
  2. Sdcard permission
Features
  1. Bigmem
Issues
  1. Microphone mute during calls
  2. Can't move app to sd
20150430
Fixed
Features
  1. Android-5.1.1
Issues
  1. App to SD
  2. Microphone mute option doesn't works during calls

20150704
Features

  1. New TWRP theme
Issues

  1. Microphone mute option doesn't works during calls
  2. ... you tell me!
 
Last edited:
  • Like
Reactions: nice_2000, alispeedsport, saladin_hs and 33 others
humberos

humberos

Inactive Recognized Developer
Oct 8, 2010
1,616
5,321
0
Brasília
www.humberos.com.br
Mar 13, 2015 at 11:41 PM
Removed Features

Removed Features:
  1. TV Output: it requires an ugly hack and I will not implements it for now.
  2. Live wallpapers (due to low ram memory status)

Building your own OmniROM HomeMade
http://docs.omnirom.org/Setting_Up_A_Compile_Environment

.repo/local_manifests/roomservice.xml
Code: 
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project name="DonkeyCoyote/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="android-5.1" />
  <project name="android_device_samsung_aries-common" path="device/samsung/aries-common" remote="omnirom" revision="android-5.1" />
  <project name="android_device_samsung_galaxysmtd" path="device/samsung/galaxysmtd" remote="omnirom" revision="android-5.1" />
  <project name="android_device_samsung_galaxysbmtd" path="device/samsung/galaxysbmtd" remote="omnirom" revision="android-5.1" />
  <project name="android_device_samsung_vibrantmtd" path="device/samsung/vibrantmtd" remote="omnirom" revision="android-5.1" />
  <project name="android_device_samsung_captivatemtd" path="device/samsung/captivatemtd" remote="omnirom" revision="android-5.1" />
  <project name="android_kernel_samsung_aries" path="kernel/samsung/aries" remote="omnirom" revision="android-5.1" />
  <project name="android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="omnirom" revision="android-5.1" />
  <project name="android_prebuilts_gcc_linux-x86_arm_arm-eabi-4.7" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.7" remote="omnirom" revision="android-5.1" />
  <project name="android_prebuilts_gcc_darwin-x86_arm_arm-eabi-4.7" path="prebuilts/gcc/darwin-x86/arm/arm-eabi-4.7" remote="omnirom" revision="android-5.1" />
  <project name="android_hardware_samsung" path="hardware/samsung" remote="omnirom" revision="android-5.1" />
</manifest>
 
Last edited:
  • Like
Reactions: nice_2000, myciter, alispeedsport and 21 others
H

He_Knows_It_All

Senior Member
Oct 30, 2012
72
10
0
Luton
Mar 14, 2015 at 12:21 AM
humberos said:
This is an unofficial build of Omni for the Samsung Galaxy S
(aka I9000|I9000B aka galaxysmtd|galaxysbmtd)​
Code: 
/*
 * Your [I]old[/I] warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */
Installation Instructions

Coming from JB
  1. You must be rooted!
  2. You must have a custom recovery installed.
  3. Wipe your device.
  4. Flash the ROM zip, it will appear an error, warning that all data will be wiped due different partition table.
  5. Reflash the ROM zip, it will continue now.
  6. Flash the GAPPS.
  7. Reboot. (It can take up to 5 min.)
  8. Enjoy
Coming from Omni Kit Kat
  1. Flash the ROM zip
  2. Reboot
  3. Wait the upgrading android dialog
  4. Enjoy!

Download: HERE

XDA:DevDB Information
OmniROM, ROM for the Samsung Galaxy S I9000

Contributors
humberos
Source Code: https://github.com/omnirom

ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Based On: AOSP

Version Information
Status: Alpha

Created 2015-03-14
Last Updated 2015-03-13
Click to expand...
is the wifi working in this build? because since i started using 5.0.2, i wasn't able to use wifi. it said "Turning wifi on" but it never did.. Plus when i clicked on the wifi toggle in the notification, it did nothing.
 
  • Like
Reactions: lampjesman, Coece and Koushik(SGS)
humberos

humberos

Inactive Recognized Developer
Oct 8, 2010
1,616
5,321
0
Brasília
www.humberos.com.br
Mar 14, 2015 at 3:39 AM
He_Knows_It_All said:
is the wifi working in this build? because since i started using 5.0.2, i wasn't able to use wifi. it said "Turning wifi on" but it never did.. Plus when i clicked on the wifi toggle in the notification, it did nothing.
Click to expand...
I have no Wi-Fi issues here.
It is working fine for me.

Any logs?
 
  • Like
Reactions: ethereal_mist, Monfro, VENESOLANITO and 2 others
faorekh

faorekh

Senior Member
May 24, 2014
174
93
28
60
Boryspil
Mar 14, 2015 at 9:46 AM
harshad_kp said:
what gapps can we use with this rom...
Click to expand...
I am using gapps from @devloz. He already prepared gapps for 5.1! Here

---------- Post added at 09:46 AM ---------- Previous post was at 09:40 AM ----------
He_Knows_It_All said:
is the wifi working in this build? because since i started using 5.0.2, i wasn't able to use wifi. it said "Turning wifi on" but it never did..
Click to expand...
I've had the same problem with omni-5.0.2-20150211-galaxysmtd-HOMEMADE. But with the first variant on 5.1 everything is OK!
 
Last edited:
A

Audiracecar90

Senior Member
Oct 18, 2014
344
148
0
Tuticorin
Mar 14, 2015 at 10:05 AM
Thankyou for your built humberos I'm flashing your built lollipop 5.0.2 device vibrrant T959 after i'll flash rom flashing tooks 10 m ins in cwm but after flashing when i reboot system im struck in vibrant logo below are the logs.Any idea??? Still now i'm not getting Lollipop. thanks in advance

1.bml_over_mtd
+ export PATH=/:/sbin:/system/xbin:/system/bin:/:/sbin:/system/xbin:/system/bin:/tmp:/sbin:/system/bin
+ busybox cat
+ busybox date
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
########################################################################################
#
# Flashing boot image with bml_over_mtd on Sat Mar 14 07:47:31 GMT 2015
#
########################################################################################
+ /tmp/bml_over_mtd scan boot
/tmp/bml_over_mtd.sh: line 1: /tmp/bml_over_mtd: not found
+ status=127
+ test 127 -eq 15
+ echo Running flash_image...
Running flash_image...
+ /sbin/flash_image boot /tmp/boot.img
mtd: successfully wrote block at 0
mtd: not writing bad block at 0x00040000 (ret 1 errno 22)
mtd: successfully wrote block at 80000
mtd: successfully wrote block at c0000
mtd: successfully wrote block at 100000
mtd: successfully wrote block at 140000
mtd: successfully wrote block at 180000
mtd: successfully wrote block at 1c0000
mtd: successfully wrote block at 200000
mtd: successfully wrote block at 240000
mtd: successfully wrote block at 280000
mtd: successfully wrote block at 2c0000
mtd: successfully wrote block at 300000
mtd: successfully wrote block at 340000
mtd: successfully wrote block at 380000
mtd: successfully wrote block at 3c0000
mtd: successfully wrote block at 400000
mtd: successfully wrote block at 440000
mtd: successfully wrote block at 480000
mtd: successfully wrote block at 4c0000
mtd: successfully wrote block at 500000
mtd: successfully wrote block at 540000
mtd: successfully wrote block at 580000
mtd: successfully wrote block at 5c0000
mtd: successfully wrote block at 600000
mtd: successfully wrote block at 640000
mtd: successfully wrote block at 680000
mtd: successfully wrote block at 6c0000
wrote boot partition
+ exit
2.mtd

+ restore_modem
+ /tmp/busybox true
+ /tmp/busybox mkdir -p /radio
+ /tmp/busybox grep -q /radio /proc/mounts
+ /tmp/busybox umount -l /dev/block/mtdblock5
umount: can't forcibly umount /dev/block/mtdblock5: Invalid argument
+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock5 /radio
+ /tmp/busybox test -e /radio/modem.bin
+ /tmp/busybox umount -l /radio
+ /tmp/busybox test -e /dev/lvpool/system
+ /tmp/busybox blockdev --getsize64 /dev/mapper/lvpool-system
+ [ 629145600 != 629145600 ]
+ /tmp/busybox test -e /dev/lvpool/swap
+ check_mount /mnt/sdcard /dev/block/mmcblk0p1 vfat
+ /tmp/busybox readlink /mnt/sdcard
+ local MOUNT_POINT=
+ /tmp/busybox test -n
+ echo Using non-readlink mount point /mnt/sdcard
Using non-readlink mount point /mnt/sdcard
+ MOUNT_POINT=/mnt/sdcard
+ /tmp/busybox grep -q /mnt/sdcard /proc/mounts
+ /tmp/busybox mkdir -p /mnt/sdcard
+ /tmp/busybox umount -l /dev/block/mmcblk0p1
umount: can't forcibly umount /dev/block/mmcblk0p1: Invalid argument
+ /tmp/busybox mount -t vfat /dev/block/mmcblk0p1 /mnt/sdcard
+ /tmp/busybox test -e /sdcard/omni.cfg
+ /tmp/busybox umount -l /system
umount: can't forcibly umount /system: Invalid argument
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument
+ /tmp/bml_over_mtd.sh boot 72 reservoir 2004 /tmp/boot.img
+ /tmp/busybox true
+ restore_log bml_over_mtd.log /sdcard
+ local omni_log_path=/sdcard/omni/log
+ /tmp/busybox test -e /tmp/omni/bml_over_mtd.log
+ mkdir -p /sdcard/omni/log
+ /tmp/busybox cp /tmp/omni/bml_over_mtd.log /sdcard/omni/log/bml_over_mtd.log
+ restore_log mtd.log /sdcard
+ local omni_log_path=/sdcard/omni/log
+ /tmp/busybox test -e /tmp/omni/mtd.log
+ mkdir -p /sdcard/omni/log
+ /tmp/busybox cp /tmp/omni/mtd.log /sdcard/omni/log/mtd.log
 
D

devloz

Senior Member
May 3, 2013
585
465
0
Mar 14, 2015 at 10:26 AM
I don't know what it is, but i think memory leak is more serious than on 5.0.2 (maybe one of memory leak fixes was reverted in trust that Google fixed it in 5.1?) and now instead of ~200MB of free RAM i have ~100MB ("System" eats twice RAM than it ate in 5.0.2) - is it memory leak or "new~lol" memory management system(!) ?

After todays night i had bug with lock screen (statusbar space was present but it wasn't filled - attachment).

About "Quick Wi-Fi" and "Quick Bluetooth" - I don't know if i like automatic turning on when going to "Quick list" of any of them :/ -- Great idea, but Google (or OmniROM) could rethink it's behavior in specific situations.

PS: I uploaded another image of 5.1 with really serious memory leak and remember: IT'S NOT I9000 - just wanted to show how serious it got.

@Audiracecar90 you could put text between
Code: 
 tags. Second block (of boot image!) failed to flash, isn't it critical?
 

Attachments

Last edited:
  • Like
Reactions: VENESOLANITO, MatteoB92 and faorekh
blueberry60

blueberry60

Elite Member
Nov 13, 2010
1,182
890
0
Mar 14, 2015 at 10:37 AM
devloz said:
I don't know what it is, but i think memory leak is more serious than on 5.0.2 (maybe one of memory leak fixes was reverted in trust that Google fixed it in 5.1?) and now instead of ~200MB of free RAM i have ~100MB ("System" eats twice RAM than it ate in 5.0.2) - is it memory leak or "new~lol" memory management system(!) ?

After todays night i had bug with lock screen (statusbar space was present but it wasn't filled - attachment).

About "Quick Wi-Fi" and "Quick Bluetooth" - I don't know if i like automatic turning on when going to "Quick list" of any of them :/ -- Great idea, but Google (or OmniROM) could rethink it's behavior in specific situations.

PS: I uploaded another image of 5.1 with really serious memory leak and remember: IT'S NOT I9000 - just wanted to show how serious it got.

@Audiracecar90 you could put text between
Code: 
 tags. Second block (of boot image!) failed to flash, isn't it critical?[/QUOTE]

Yes,you are right.

[img]http://i.imgur.com/rjHHls9.png[/img]
Click to expand...
 
Status
Not open for further replies.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone