[ROM]Unofficial OmniRom 5.1[No RIL]

[xc-racer99]

Code:

/*
 * Your probably long expired 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.
 */

Please Note:I do not have a Verizon Fascinate!!!! The closest thing I have is a Telus Fascinate 4G, which is essentially a Galaxy S 4G. However, this ROM has been built for (and tested on) a Verizon Fascinate.

Installation Instructions - Thanks Ophidian_DarkCore!

Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?pli=1
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.

• 1. Read "Things to take note of" below

• 2. Wipe system, data, and cache paritions (just in case)

• 3. Install zip

• 4. If you want root (SuperSU) or Gapps, install them now (or later, if you so desire)

The first boot can take several minutes. Be patient. If it takes 10+ minutes, pull the battery and reboot to recovery.

Things to Take Note Of

• The RIL (aka data, SMS, calls, etc) is NON-FUNCTIONAL.

• Humberos (the i9000 maintainer) has moved on to different projects which means no first-gen Galaxy S devices are being actively maintained. Builds may break at any time!

• Selinux is currently in permissive mode. I'm not sure whether or not it can be switched to enforcing without breaking things

• The USB connection is MTP and not mass storage as Omni has removed mass storage. Unfortunately, it sometimes is super-duper slow. In recovery there is still an option to mount as mass storage device.

• Live wallpapers are not present as this definitely qualifies as a low-ram device...

• Tv-out support is not present. It was removed upstream and I don't want to bother adding it back in.

• This build is very close to the official omni source code. This means that the recovery is TWRP and there aren't any added "features"
  In order to get it rooted, you need to install SuperSu.

• Gapps slow down the i9000 and Galaxy S 4G significantly so tread carefully.

• Backup Backup Backup! I'm not responsible for you losing any data.

Working

• It boots!

• Wi-Fi

• Seriously, I'm not exactly sure what else works. I suspect that most other functions including Bluetooth and auto-brightness work but I'm not sure

What doesn't

• RIL, cause I removed it...

• Some of the soft keys (possibly fixed in latest build)

• You tell me...

Everything else is not tested!!!


XDA:DevDB Information
Unofficial OmniRom 5.1 for the Samsung Fascinate, ROM for the Samsung Fascinate

Contributors
xc-racer99, Ophidian_DarkCore, humberos
Source Code: https://github.com/omnirom

ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: MTD Rom
Based On: OmniRom

Version Information
Status: Testing

Created 2015-08-01
Last Updated 2015-08-01

 

[xc-racer99]

Thanks Time!
This would not have been possible without the following people:

Thanks to humberos for bringing Lollipop to the first-gen Galaxy S series. This would not have been possible without his work.
Thanks to Ophidian_DarkCore for being the primary tester and prompting me to work on this project.
Thanks to hhp_211 for doing some testing and offering to send me a Fascinate.
Thanks to all others that have helped get this phone to where it is today!
Thanks to vcmerritt. A name you're probably not familiar with, but he was the only one to create something for the T959P (my phone) and without him I'd still be on stock...


Build your own!
Follow the instructions at http://docs.omnirom.org/Setting_Up_A_Compile_Environment using the android-5.1 branch
Before doing a repo sync, put the galaxy_s_series.xml file from the Downloads folder in .repo/local_manifests folder of the source tree.
After syncing the source, open a terminal and in the directory where you downloaded the source code type "source ./build/envsetup.sh" and then "brunch fascinatemtd"

Changelog

Changelog for 2015/08/01 Build

• Untested!!!!!

• TWRP fix (I think)

• Totally removed RIL, prior builds have RIL there but its non-functional

Changelog for 2015/08/13 Build

• Untested!

• Encryption should now work

• Keymapping (ie soft keys Home and Back) may be fixed

Changelog for 2015/08/31

• Updated Android version (5.1.1_r5 to 5.1.1_r12)(upstream Omni Change)

• SoD should be fixed...

• Untested by me

 

[xc-racer99]

Source Code and Downloads

Main Source
http://github.com/omnirom
Device Specific Source Code
http://github.com/xc-racer99/android_device_samsung_fascinatemtd for the device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_device_samsung_aries-common for the common device tree (see android-5.1 branch)
http://github.com/xc-racer99/android_kernel_samsung_aries for the kernel (see android-5.1 branch)
http://github.com/xc-racer99/proprietary_vendor_samsung for the prop blobs (see android-5.1 branch)

Downloads!
All builds are found at https://drive.google.com/folderview...VVSzJxYVU3eHlWZGR1VVNZUWk1V1QzOUk&usp=sharing

Gapps
Gapps can be installed from http://forum.xda-developers.com/showpost.php?p=59731008&postcount=2

SuperSu
SuperSu can be found at https://download.chainfire.eu/696/SuperSU/

 

[Ophidian_DarkCore]

Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.

EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps

 

[xc-racer99]

Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.

Thanks, I wasn't sure how you installed it. Will update OP.

 

[hhp_211]

Thanks, I wasn't sure how you installed it. Will update OP.

Make sure to do the following before flashing this rom: flash this https://mega.nz/#!YBYXGTRI!7NscLqn139vvNCroS94HlQ6uNYpTFqmc1y3ktvtQIsw in odin https://drive.google.com/file/d/0B0J5C6YxKg67bW11WFJrbjYxNW8/view?usp=sharing
Gingerbread bootloader is required, you must have previously been on cm11 before using this rom, otherwise go to one of the cm11 threads and follow the 'from stock' instructions.

EDIT: recommended gapps https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Pico GApps

OK, Only worked from the odin cwm.

I tried flashing and while I got*cwm 6.0.5.1 and/or twrp,,, It looked like it installed cm11 and/or omni,,, but nothing ever booted, always looped back to recovery.


1st impressions are wow!!
looks good and kernel has OC
and a few nice features.

Good work on all involved!


Installed beta SuperSU-2.49

Gonna test with 200/1400, interactive(tweaked), deadline-1024, KSM-off, standard LMK. for now*

Stable so far.

I'll test changing vm heapsize and LMK values

Also trying omni switch, but probably go back to asop recents as its using a lot of mem

oh and I'll check Big Mem settings too.


So far no gapps installed yet but loaded up subway surfer and candy crush,,, both had significant lag before,,, on cm 11, du, slim before,,, but are running fantastic so far on omni !


Later:
Gapps : I went very minimal install package,
Yes performance still takes a hit and I've also noticed some random reboots too.
I'd like to go back and try again without a gapps to make sure/verify, but i don't remember any reboots without gapps.


As a side note,, I wish some one could build a modified base play services that didn't have all the extra services stuff like,,, in car, fit, nfc, weareable, etc.
I always disable that stuff even on my other/main phones.

.

 

[Ophidian_DarkCore]

i juse disableservice and autostarts for that stuff.
my experience has been this rom idles for several days and no crashes. i guess oc's but a last_kmsg would be nice. then have a logcat gathering while you try to recreate the crash. or gtfo?
i was surprised to have 1400. i could never get hummingbirdover 1300 on gb, and i overvolted the piss out of it. even my other hummingbird(sammy aviator).
EDIT: "interactive(tweaked)" hispeed_freq?
edit edit: ksm is optimized in this kernel, and row is best for our flash until fiops is added.

 

[Godlovskiy]

will new releases ?

 

[Ophidian_DarkCore]

will new releases ?

I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet

 

[Godlovskiy]

***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***

in buld 08/01 when I turn on OC phone don't wake

 

[xc-racer99]

***I'm working out lots of bugs and improving performance. Expect a much improved build soon.***

in buld 08/01 when I turn on OC phone don't wake

OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.

will new releases ?

The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.

 

[Godlovskiy]

it is noteworthy that in build from 30/07 this is not observed

 

[xc-racer99]

it is noteworthy that in build from 30/07 this is not observed

Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.

If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.

 

[Ophidian_DarkCore]

it is noteworthy that in build from 30/07 this is not observed

OC didn't actually work in that build I think.

---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------

Ok, that is very noteworthy. I figured it was the same on all of them. Does it only not wake up when OC is enabled? I'll have a look through my code and see exactly what changed.
The most likely way to get around this, so to speak, would be to replace the boot.img in the new build with the one from the older build and then flash the zip. OC is mostly at the kernel level, so the boot.img should be the trick.

If someone does this and they don't see any adverse effects such as wakelocks, I'll do up a new build with the relevant change reverted.

On 200 to 1.4 it stays on a black screen unless you fiddle with the volume buttons before waking the screen.

 

[Cross09]

OC is very phone specific. An OC that works on my phone may not work on your phone. That's one of the reasons the clock speed is normally only 1Ghz - all devices can support it. Some will definitely support higher (there were rumors of people going up to 1.8Ghz a few years back...). For me, 1.2Ghz is stable, 1.4Ghz often crashes.
If the phone isn't waking with an OC, you've pushed it too far. Try a lower OC.


The only way I can do new releases is if somebody sends me bug reports. Since I don't have a fascinate, I can't see what problems will appear. Anything I find out that is wrong on my device (essentially a Galaxy S 4G) that is common with the Fascinate will come to the Fascinate but I haven't found anything like that since I put up the last build.

I can help you with bug reports,you just shoud tell me what I have to do

 

[xc-racer99]

I can help you with bug reports,you just shoud tell me what I have to do

Awesome! Find what doesn't work, reproduce the issue, and then take logs as per http://forum.xda-developers.com/showthread.php?t=2185929 and then let me know. It helps if you explain in detail what exactly you do - more detail is always better than less. While this doesn't really apply here as there's not many builds, its always good to know if the bug is a regression (ie it worked in past builds but no longer works) or if it never worked in the first place.
To transmit this info you can use the bug reports tab at the top of this thread, PM, or just post in the main thread, it doesn't matter to me.

 

[Ophidian_DarkCore]

I can help you with bug reports,you just shoud tell me what I have to do

Here's something for you to do. When headphones are plugged in, no music is playing, and the screen is off, collect logs on why it won't come back on until the headphones are removed. Collect a logcat constantly throughout. Then grab a kmsg and dmesg after you remove the headphones and turn the screen back on.
Collect logs during listview scrolling.
Let me know if the play store can install apps.

 

[quickgiant]

I'm working out lots of bugs and improving performance. Expect a much improved build soon.
Meanwhile, I'm gonna be jamming out on one of my test builds(24 bit audio anyone?) I figured out gcc 4.8. all i'm gonna say for now is it's a user build, debugging all disabled in the kernel, fiops is proposed, telephony all removed, art is set to fully optimize. a bunch of awesome sauce that I'm not gonna tell about just yet

If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.

THANKS!

 

[xda_bg]

If you got 24 bit audio working, you would be my hero. I've been using this thing as a media player for a long time and it's fantastic, but I've been having some issues with Geewiz Media and this would be a nice improvement.

THANKS!

I also would be thankful if you would add 24 bit audio.

Thanks

 

[Ophidian_DarkCore]

I also would be thankful if you would add 24 bit audio.

Thanks

the frame size of 10 million exabytes is larger than my patience^2
http://i.imgur.com/eljXmhJ.png