yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] xc-racer99:
No, it should be Humberos is the man! I basically re-hashed his code for the i9000 and used bits and pieces from people like Bhundven, noiphonehere, maxfierke, Dao, and FB to get things to work properly.

For a status update, I figured out the lockscreen notification problem. I have a new build being made that I hopefully will be able to upload in the next couple of days (internet dependent). TV-Out looks totally broken as the proprietary blobs no longer function. I don't have the know-how to make ugly hacks to get them to work. The new build will have SElinux in enforcing mode and have the different GPS initialization (like the last build) until someone tells me that it doesn't work :p

Uh-oh, looks like I jumped the gun.... Having problems once again
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Any updates on getting the play store to work? I have searched, downloaded, and tried every gapp made for 5.1. I found that I can load any app on the rom, if I get the APK version of it.
[Samsung Galaxy S (4G Model)] xc-racer99:
Darn, so its still not working. Not surprising. I've been struggling on the notification issue and am at my wit's end as to what the problem is. I don't think its only our phone as several i9000 users have been reporting it as well. Whether it is only the first-gen Galaxy S series that is having the problem or not is anyone's guess. My programming skills are insufficient to fix the issue!

I'll have another look at gapps over the next couple of days and see if I can figure out a combination that works 100% of the time.

I'm assuming the error message is still 963 or does it silently fail now? Its probably related to the fact that we have only an external sd card and no internal sd card like most devices...

All the problems with the notifications that I've found are:

Only one notification will show up at a time

Large notifications such as the music player do not render properly. They are cut off at the normal notification size and occasionally it seems as if there are two layers there (one for the small version, one for the bigger version) (see attached picture, taken with VLC as the media player, but also appears with Apollo)

Notifications don't always show up. A little icon appears in the top left corner of the status bar but no notification is present. Seems hit or miss

The words No notifications appears in the lockscreen just above the clock when there are no notifications. Otherwise, a notification (and only one) which can't be clicked covers part of the clock
[Samsung Galaxy S (4G Model)] racav1904:
Help me please

I get this error when i tried to install this

E: error executing updater binary in zip

Please help me
[Samsung Galaxy S (4G Model)] robonxt:
which build are you installing? I think somewhere in this thread was a post by someone that said in one of the builds there was a typo
[Samsung Galaxy S (4G Model)] champ1919:
Dusted off old phone and can't believe this is running on it. Great job and thanks!
[Samsung Galaxy S (4G Model)] ArcFlash3:
I have been struggling to install this rom. I've spent literally hours trying to figure this out to no avail. I have a T959V with rooted GB and AntonX's kernel (running CWM 5.0.2.8) and every time I attempt to install the rom I get an assert error and a status 7. Here's the error word for word:

assert failed: run_program("/tmp/updater.sh") ==
0
E:Error in /sdcard/omni-5.1.1-20151201-galaxys4g
mtd-HOMEMADE.zip
(Status 7)
Installation aborted.

I tried editing the updater script and removing the assert but that just caused the phone to reboot during the install. What am I doing wrong here? I'm sorely confused and frustrated and I can't find answers anywhere. Someone please help.
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, commenting out the assert would mean you're entirely skipping the updater.sh script which is required. Can you post the contents of omni_mtd.log, omni_bml.log, and bml_over_mtd.log from your sdcard (whichever of them exist, if any).

My best guess is that you don't have a second partition on your SD card - this is required for this ROM.
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
I have tried with and without SD card, reformatting SD card, using ext4 only, FAT only, and either get error 963 or 903 but either way it fails.
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, thanks for the update. I'll see if there's anything I can do to get them to work. In the meantime, you could try using https://f-droid.org/wiki/page/com.jackpf.apkdownloader to download the APKs. I haven't tried it lately myself, but when I did last year it worked just fine. It appears that this no longer exists. If you can find a version of it somewhere...
[Samsung Galaxy S (4G Model)] DickyG:
Hmm...although many of the apps force closed on me (including Maps so I couldn't test GPS), Playstore worked fine. I used the Gapps package 20150513.5.1.x.
[Samsung Galaxy S (4G Model)] xc-racer99:
Well that's bizarre. I just tried those same gapps and it didn't work.... Go figure. I'm trying a different set now. Some more info on the error code 963 is at http://xdaforums.com/htc-one-m8/help/getting-error-code-963-907-play-store-t3119007 The part about the *.obb files is interesting. If there are any Android/obb/* files on your sdcard, try removing them and see if you can then install any apps.

Update: Alright, the next set that I tried didn't work either. It's probably an issue with the build. I'll try some more things and see if I can find out the reason.

Update 2: Even more bizarre, I just triggered the notification error on my first build, which never had it before.... What is going on???:confused:
[Samsung Galaxy S (4G Model)] DickyG:
Strange indeed. I won't get a chance to test anymore until next week. When I do, I'll flash the same Gapps package and see what happens. At the very least, I'll remember to copy down the Playstore version #. I was successful in downloading one or two apps (just to make sure they installed). But for the most part, I merely restored apps from Titanium Backup. I have a feeling that GPS will work. It works on all the 4.4.2 and 4.4.4. ROM's. If you go to etc/init.d and find a file labeled "GPS", I think it will work. This was solved by one of the developers while working on Beanstalk and SlimSaber. Forget about TV out...that and WiFi calling are lost causes.
[Samsung Galaxy S (4G Model)] xc-racer99:
Well, believe it or not I actually had TV-Out working on my personal builds of Android 4.2. The only problem was that there was a green bar across the screen when it was horizontal (a la CM9). However, that won't happen on Lollipop. Edit: I mean TV-Out in general, not the green bar

Could your restoring from Titanium Backup have caused any of the force closes? (ie did you restore any system/google apps)
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, I haven't solved the notification issue but I have found a workaround (at least, it seems to be working for me). In Settings, go to Performance, then Advanced. Select Force high-end graphics and reboot your phone.

Added benefit - tinted status bar Disadvantage - slightly worse performance (although I personally didn't notice much difference at all)

Edit: I haven't had any luck with gapps yet. Still trying things when I get the chance but I think our best bet is to wait for DickyG (no pressure;))
[Samsung Galaxy S (4G Model)] DickyG:
Good question...when I restore from Titanium, I use the "restore missing apps + all system data" option...there's another option called "restore all apps with data" which I don't use. I just noticed, however, that the first option includes Google Playstore so now I'm wondering if my working Playstore was because I restored it with Titanium even though the Gapps flash might not have worked (?)

At any rate, I've got to go out of town for business for a few days...will work on it some more when I return.
[Samsung Galaxy S (4G Model)] xc-racer99:
Haha, yes, that would be the reason for your force-closes. System app data is typically not compatible between different ROMs. Some things such as the wallpaper typically will work. Whether or not that was the reason your gapps were mostly working is another matter.

Update: I've done some more digging, and the problem is a little bit bizarre. It appears that the Google Play Store doesn't like the file system (yaffs2) that is in use by /data or the fact that I had to manually mount the partition in Lollipop otherwise the boot would hang indefinitely. I'm theorizing that DickyG got the Play Store to work as he used Link2SD in which data files are moved to the second partition on the SD Card, which is (typically) an ext4 filesystem and is mounted in a different method.

Therefore, the next build will have the data partition on the second partition of the SD Card, hence it will be mandatory that there be (at least) two partitions on the SD card. Installation will not proceed if there is not. I currently don't have very good Internet access so I won't be able to upload a build until Monday at the earliest. Patches have not been pushed to my Github yet as I am still testing a few things out. I have now pushed my changes to github.

All other devices that are in a similar situation have, as far as I can tell, been doing this as well. It sucks, but at least this way you can decide how big of a data partition you want.
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Changelog for 20150720 Build

The data partition is now the second partition of the SD Card as opposed to internal storage

Gapps now work. If you get error 461 when installing from Play Store, a full data wipe should fix it. You can try experimenting with clearing data for the Play Store and/or Play Services or removing and re-adding your Google account if you don't want to do a full data wipe.

HSPA vs UMTS settings in DeviceSettings has been fixed

High-End graphics are forced by default to fix notification issue

ART parameters have been tweaked

Miscellaneous other tweaks, see my Github for details

If coming from a previous build your data will not come with you. In addition, you will not be able to restore a nandroid backup of your data. You best bet is to use TitaniumBackup or equivalent.

Please Note: Two (or more) partitions are required on the SD card! /data is placed on the second partition and will wipe all data on that partition (but the first partition will remain untouched). As data is now on the SD card, the ability to hot-swap SD cards has been removed. This was done so that Gapps would work. As an added benefit, you can decide how big of a data partition you want. I would recommend a 2GB partition on a class 10 SD card, but less is fine (don't go below a 512MB partition). Many recoveries will have an option to partition the SD card, but be warned that this will probably wipe all data on all partition of the SD card. On linux, gparted will work; on Windows minitool partition wizard should work.

Credits to @http://xdaforums.com/member.php?u=3770444 for the original idea with his Hefe Hook Kernel.

If you're finding the device very laggy, try changing the LMK parameters in Performance Settings to kill less often. This is more a problem with Gapps installed, otherwise it seems fine.

If for some reason you really, really do not want /data on the sd card, you can try using the boot.img, the updater.sh and the updater-script from a previous build but this method is totally untested!!!!
[Samsung Galaxy S (4G Model)] mataflakitas:
Thanks for you hard work ...
[Samsung Galaxy S (4G Model)] Rebel_X:
Great work done here, thanks a lot. This phone is really old, I don't use it as a daily driver, but managed to test this rom on it. And here are my findings:

Gapps working fine, installed PA Gapps "pico". System partition has ~43MB left after flashing the rom, gapps and supersu.

GPS doesn't work. I left the phone on the balcony for an hour running GPS Status after downloading A-GPS data and no "fix" let alone not a single satellite found. Also tried Z-Device test for GPS Accuracy to see the log of NMEA, bunch of zeros.

For the first time since Gingerbread roms, the Compass is F&#$ing working!!! WOAH O_O (Calibration was needed by moving the phone in 8 figure multiple times).

Yeah, the phone is very laggy, maybe because of gapps as you mentioned, but it feels great running LP on this phone T_T

I encountered a problem once using the stuck browser, the screen started to "literally" fade to white with horizontal rainbow lines at the bottom of screen. Phone became unresponsive, I had to reboot it.
[Samsung Galaxy S (4G Model)] xc-racer99:
Thanks for the update!

Yeah, I was working on the GPS for my variant yesterday and I figured out that I made a typo in the gps initialization on the T959V as well... I'll need to do some more selinux testing on the fix but will hopefully be able to upload another build later today/tomorrow. I also found the cause of the bluetooth issues and have fixed that. Still have no idea why the 720p recording is so laggy (IMO, its worse than on previous ROMs, which were less than stellar). Dock Audio, well I can't test that as I don't have a dock (I suspect not working, but if someone has a dock and can test, it would be appreciated).

Totally bizarre that the compass is working as I didn't do anything special with it..... My guess would be that the non-working TV-Out was causing some sort of weird conflict with it. They were both set to start in the same "class" in init.aries.rc but the tvouthack kept dying which might have also killed off the geomagneticd...

Also, the lag is definitely due to gapps. I'm currently running it without any gapps and it is quite responsive. I think we just have too little RAM for the newer gapps.
[Samsung Galaxy S (4G Model)] DickyG:
Just downloaded the new build...will do some testing tomorrow. I did get a chance to do some more testing on the older build. Two things which are now working: (1) Google search (2) Bluetooth...at least it connected...haven't tried to make a call yet.

GPS...Personally, I don't care...we have units in both cars so we never use our phones. However, I noticed on my phone running CM11, there is a file called "GPS" in etc/init.d....and it's not present in OmniRom.

Will report more tomorrow.

Thanks for your hard work!
[Samsung Galaxy S (4G Model)] xc-racer99:
On the latest build posted, bluetooth sort of works. However, parts of the bluetooth stack are enabled that our phone doesn't support leading to crashes. I found the issue and have fixed it.

I removed the gps file in /etc/init.d but simply moved it to /system/bin (rename as gps.sh) and started it manually (it was much easier for the selinux side of things). However, the word "service" is not spelled "serivce" (you can see the typo in init.aries.gps.rc, don't bother trying to fix it there though is its part of the boot.img and will just get overwritten on boot again).... This will also be fixed in a build that I'll hopefully be able to post later today.
[Samsung Galaxy S (4G Model)] DickyG:
Now I'm getting frustrated! Since my early success, can't get Gapps to work...keep getting the "491" error message. I've tried a few packages including the Pico version.

After installing, I've tried:

1. Going into Accounts and deleting my Google account.

2. Clearing cache & data in Playstore and Google Services Apps.

3. Rebooting

4. Re-adding my Google account.

...and I'm still getting the "491" error message.

Which package is working for you guys?

Thanks....
[Samsung Galaxy S (4G Model)] xc-racer99:
Wait, 491 or 461? I had difficulty with error 461 as did some guys on the i9000. I figured it was just due to the fact that I didn't install the gapps and the ROM at the same time. After I did a complete data wipe I had no issues. I was using the "HDPI_miniGAPPS-5.1.1-20150709-signed.zip" which I believe I got from http://xdaforums.com/showpost.php?p=59731008&postcount=2
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Get it at the same place as always :)

Changelog for 2015/07/24 Build

Stabilized bluetooth connection

Fixed typo in GPS initialization. Does it work?

Added ability to use f2fs file system on /data. Supposed to give better performance

Added force fast charge and touch wake to kernel. Touchwake is accessible through its sysfs path, fast charge through Performance Settings, BatterySelinux currently denies these requests...

If the gps doesn't work, could someone please send me their dmesg output? To do so, in a terminal emulator type in su, then "dmesg > /sdcard/dmesg.txt" or from a computer with working adb, "adb shell su -c dmesg.txt > dmesg.txt"
[Samsung Galaxy S (4G Model)] DickyG:
It was definitely 491...about a zillion times.

But...it's now working! Installed the Gapps package you recommended. Still got the 491 error message but I did the following:

1. Went to settings and deleted Google account

2. Wiped data of Playstore, Play Services, Google Framework, and Download Manager

3. Re-installed Google account

(I got the solution by Googling the problem)

I then restored a few apps through Titanium and used Link2Sd to link everything (except the Google stuff) to the SD card...no problems.

One interesting note:

On my regular phone, (which is running CM11), I have a total Internal storage of 553 MB, with about 250MB free.

On my spare phone ,also an S4g, I'm showing total internal storage of 1GB with about 550MB free, although I have not re-installed all my apps. This is the phone that is currently running OmniROM.

I'll test GPS tomorrow but so far, everything is working.
[Samsung Galaxy S (4G Model)] xc-racer99:
Yep, the storage size is right. Let me guess, the second partition on your SD card is 1GB?

They show different values because I set the /data partition to be the second parition on the SD card as opposed to the one on the internal storage (oneNand). oneNand is much faster than an SD card, but we don't have very much of it. So, there's this thing called "datadata" where all the data files for the apps are stored on the oneNand so you don't get much of a performance drop while you still get the extra space on the /data partition (and, in our case, the ext4 filesystem to satisfy gapps). The i9000 also uses datadata, but they use all of their internal storage space (which is half the size of ours) for it. Their system and data partitions are on their internal SD card (they have both an internal (non-removable) and an external (removable) one).

So, since the second partition is storing /data, Android reports it as the internal storage.

This setup means that Link2SD is actually no longer really necessary as its main purpose is to move apps to the second partition of the SD card to free up space in /data but we store apps there by default. It is still a great tool for freezing apps, convert to and from system apps, etc.
[Samsung Galaxy S (4G Model)] DerPuGNa:
Complete installation...

like after we follow the instruction in the OP, where do we create 2nd partition?

in the TWRP or something?

what must we do after installing the gapps and the rom?

what will be the first?

create a 2nd partition then install (rom and gapps) or install(rom and gapps) and then create 2nd partition?

BTW thanks for the hard work! :good: :good: :victory:
[Samsung Galaxy S (4G Model)] xc-racer99:
Whoops, looks like I forgot to hit save after editing the "What to take note of" section for the new partition layout. The 2nd partition is created before any flashing takes place. Flashing will not compete successfully if there is not a second partition.

Some recoveries (both TWRP and CWM) do have an option to partition the SD card. Be warned, using this method will wipe the SD card. On Windows, the MiniTool partition wizard should be able to create it, make sure it is created with an ext4 or f2fs filesystem and as a primary partition. On Linux, gparted should work well. Please make sure that the disk that you're creating another partition on is indeed the SD card, and not the hard drive on your computer....
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
If anyone is interested, I found a way to get rid of most of the lag, once GAPPS are installed. I installed a light weight launcher (Zeam is what I used because it only uses 388kb) then disabled the launcher3 from running (freeze or uninstall) reboot phone. It seems to run quicker and with less lag at least for me anyway!
[Samsung Galaxy S (4G Model)] xc-racer99:
Zeam... That brings back memories. I used that launcher back in the stock Ginger Bread days :D Great minimalistic launcher though.

Thanks for the info!
[Samsung Galaxy S (4G Model)] FBis251:
Don't forget that you need to make sure the recovery supports f2fs, I think recent versions of TWRP do, but I'm not sure about CWM
[Samsung Galaxy S (4G Model)] xc-racer99:
Thanks for the reminder. I haven't tested it myself, but on the i9000 it was working no problem. I'm using the same (base) kernel and recovery (latest TWRP) as they are and also using their aries-common tree which picks up the "TARGET_USERIMAGES_USE_F2FS := true" option.

Since I just returned to BML to try to figure out the 720p recording bug (working backwards - if I can introduce the problem there, then maybe I'll be able to fix it in the new kernel. A long shot, but I haven't had any luck working on it from the forward revision). When I go back to Omni later today I'll format my partition as f2fs and see what happens:fingers-crossed:

Edit: I just booted with f2fs as the filesystem for /data and it seems to work just fine. In terms of performance improvements, it seems a little quicker but it might just be the placebo effect. Encryption however doesn't work (I haven't tested on ext4 though, so it might be broken...)

Edit 2: Nope, encryption on ext4 is broken as well.
[Samsung Galaxy S (4G Model)] DickyG:
I put a SIM card in my OmniRom phone and actually used it this week-end. A little laggy but the basics...calls, texts, brower...worked fine.

However, when I powered it up this afternoon, I got a force close on android.phone. And when I clicked "OK" it popped up again...and again...rendering the phone useless. Tried to re-flash without wiping and it did no good.

Finally, had to start over and do complete wipe, etc.

I did flash the new build...also installed GPS Test and a GPS app (Waze). I'll see if it works tomorrow.
[Samsung Galaxy S (4G Model)] Ophidian_DarkCore:
You think I can make a fascinatemtd build out of this?

EDIT: we're on lvm..... and i think different disk size.

Thoughts?

Should i port your 5.1 work to my 4.4 trees then?
[Samsung Galaxy S (4G Model)] xc-racer99:
Yes, it would probably be possible to do a fascinatemtd port of this. However, I'm not sure how the kernel would do as there have been some major changes to 5.0 done to it by Humberos. I'm not sure if he broke any of the fascinate stuff. With regards to lvm, that's not too much of an issue as the i9000/Vibrant/Captivate all use that so look at their trees instead. As well, in the kernel, if you're basing the config off of mine, make sure you use the "CONFIG_SAMSUNG_ONENAND" instead of "CONFIG_SAMSUNG_ONENAND_AUDI". The Galaxy S 4G is a little odd in that regard. If you're okay with flashing a probably not working build, I can try to create one for you, probably in the next couple of days. You're more than welcome to use any/all of my trees if you want to port it yourself.

Hmm, that's weird. I wonder what happened. I've been running builds of this as my daily driver for a couple of weeks now and haven't had any force closes (well, other than running out of RAM...)
[Samsung Galaxy S (4G Model)] Ophidian_DarkCore:
I've already been stealing from your trees hehe but thanks

I have 2 fassys to toy with. Let me get my kernel working and you can compare.

I was gonna do a meld anyways.
[Samsung Galaxy S (4G Model)] DerPuGNa:
im agree with this. but, there is something weird happen. when i reboot my phone, there are still have recent app. like if i open the browser, then i rebooted it after a couple of minutes of waiting to boot, when i long press the home key, the app browser is still there... pretty weird?