yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, can you please tell me what error you're getting when trying to install? Then I'll be able to help you much better.
[Samsung Galaxy S (4G Model)] jkiran2may:
Hi

I got below error:

Assert failed: run_program("/tmp/update.sh") ==

E: error executing updater binary in zip '/sdcard/omni-5.1.1-20151015-

Updating partition details...
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, I don't suppose you happen to have a number after

Assert failed: run_program("/tmp/update.sh") ==

That should tell me what the problem is. If I had to wager, I would bet that you don't have a second partition on your SD card. I made the decision to put the data on the second partition of the SD card so that the Play Store would work (Lollipop bug) and so that it could be larger than it otherwise could.
[Samsung Galaxy S (4G Model)] jkiran2may:
Let me try by making another Partition in my SD card..
[Samsung Galaxy S (4G Model)] jkiran2may:
Hi ,

Thank you for the tip. Partition of SD card worked!!!

I am able to partition my SD Card using TWRP and copy the OMNI ROM Zip file.. installed OMNI Lollipop on my Samsung Galaxy S 4G successfully...

But, having issue with Google Play Store, I am not able to download and install any apps and OMNI is restarting my mobile several times.

Getting 491 error when I try to install some thing from Google Play Store.

Cleared my google account , removed and restarted and tried several times but nothing is working.
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, I would suggest looking through the earlier pages of this thread. I know some people solved it. I personally don't use gapps on it, I manually download any apps I want (not many) from https://apps.evozi.com/apk-downloader/ and use Fdroid for some as well.

The other thing to try is to create a file called .nodatadata in /data/data (from and adb shell or a terminal, run "touch /data/data/.nodatadata" or just manually create the file with something like ES File Explorer.

This problem is not unique to our variant, it also occurs on the i9000 (the international version of the phone).
[Samsung Galaxy S (4G Model)] jkiran2may:
Hmm .. Lollipop in sgs4g is too slow and went back to CM11 kitkat... I love kitkat for now....
[Samsung Galaxy S (4G Model)] xc-racer99:
Yes, Lollipop is a lot slower than KitKat, particularly if you install gapps.

Use what you like best!:)
[Samsung Galaxy S (4G Model)] jkiran2may:
Thank you for the ROMs.. Excellent work and thanks for the contributors
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Not much new here, just updated Omni source - mostly security fixes. Likely the last build unless some new security issues come up.

Download from Google Drive, link is in OP.
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Can't seem to root the latest build.
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, I hadn't noticed yet but I can verify that. Its strange as I don't remember really changing anything between this build and the last one.

Does the SuperSU zip flash? It didn't flash for me (caused a reboot) but that might just be my phone as I think the nand is going on it...
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
No, it keeps causing a reboot
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, thanks for letting me know. I'll have a look into it and see if I can determine why.
[Samsung Galaxy S (4G Model)] xc-racer99:
Ok, I've had a look at the rooting issue and I can't figure it out:D If you must have root, use an older build.

However, I've also had a look at Marshmallow, and that is now booting!!!

There is a lot of work left to do, namely

1) RIL

2) SDcard (currently not working...)

3) Probably GPS

Initial impressions are that it seems much faster than Lollipop, about the same speed as KitKat. However, this is without gapps (I haven't tested with them yet).
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Link? I will play with it, and try some GAPPS
[Samsung Galaxy S (4G Model)] xc-racer99:
I haven't created a build for the T959V yet, only the T959P. I have a new build that I'm testing right now.

Here's my status (on the T959P)

Current Bugs: Built in Camera app (but if you use a different camera, like Open Camera it works), powered-off charging animation. Plus of course the standard bugs such as laggy 720p recording and no TV-Out.

I'm hoping to create a build for the T959V shortly, I just want to speed things up a bit first (it seems a little faster than Lollipop, but I'm not sure). The GPS may or may not be working on the T959V - it may need some more compatibility fixes.
[Samsung Galaxy S (4G Model)] xc-racer99:
Ok, I created a build for the T959V

Known Bugs:

Rotation broken

Camera only working in 3rd party apps

Powered-off charging animation not working properly

selinux in permissive mode

zRam not enabled

I haven't tested this build, the GPS may or may not working. Just flash SuperSU to get it rooted. I haven't had any gapps working on it (if you find some that work, let me know. I only very briefly gave it a go).

Download it from https://drive.google.com/file/d/0B7vXjzo0Hj-iZXFxd1kwTjJ1OHM/view?usp=sharing

Let me know if you find any more bugs.
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Downloading now
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
The first Impression is AWESOME!! Marshmallow on the old sgs4g! It does seem faster than lollipop. I can not find any 6.0 or 6.01 GAPPS to work on the rom. They all seem to just reboot the phone when trying to install. Not done playing with GAPPS yet. Camera will work, if you choose "Do not use my location" when you initially set the camera up. The GPS does not work, because of that I believe that is part of the reason the camera crashes if you choose to use your location. I have manually added some apps using APK files and they all loaded and operated. The Rom is AWESOME just a few tweaks and this phone will have Marshmallow!

Thank you xc-racer99 for your dedication and work
[Samsung Galaxy S (4G Model)] xc-racer99:
Thanks for testing. Due to a workaround for a different device, I have auto-rotate working now on my local builds. Unfortunately, the hack was removed upstream, so I guess I'll try to fix it properly this time.

I'll have a look at gapps again - I think its because we're using the internal Nand on the device for /system which is yaffs2-based - and Marshmallow dropped support for it.... I'll see if I can make a special package that flashes properly.

With the GPS, can I get some logs (see here)? As I don't have a T959V, I can't test it. There is one idea that I have that may fix it (it fixed it for the i9000 and Nexus 10, but the T959P didn't need the hack).
[Samsung Galaxy S (4G Model)] DickyG:
I think a working Marshmallow would be awesome, especially since the Samsung folks gave up on this phone years ago, saying that ICS was more than it could handle. I still use this phone quite a bit. As far as GPS goes, it worked fine on OmniRom although frankly I don't use it much since I have units in all my cars..but working GPS seems to be key in having people use a ROM on a daily basis.
[Samsung Galaxy S (4G Model)] xc-racer99:
Merry Christmas!

Alright, so I have uploaded a new build of Marshamllow. It is now quite stable - I've been using it as my daily driver for at least a week now with no issues. Download it from https://drive.google.com/file/d/0B7vXjzo0Hj-iNUhOSnprSHVfbVU/view?usp=sharing

Notable changes from the previous build:

Repartitioned - please wipe data, cache, and system in recovery prior to installing (even if coming from the previous build)

auto-rotate is now working

zRam is now enabled

Potential GPS fix included

The camera still only works in 3rd-party apps, selinux is still permissive, and powered-off charging animation is still broken.

Also, gapps should now be able to be installed (note that I haven't tested). The issue was twofold: insufficient space on /system (hence the repartition) and the same issue as SuperSU install on the last 5.1 build (this was because in the mount command (from busybox) was "updated" but tried to use blkid on the mtd partitions - which induced the crash).

Since I have discovered the issue with the previous 5.1 build, does anyone want an updated 5.1 build? Or a 6.0 build for the T959P? Let me know and I'll upload one.
[Samsung Galaxy S (4G Model)] DickyG:
Just downloaded the zip...where do I get Gapps? I'll install sometimes tonight and report back. If I can get Playstore working, I'll also download another camera app. This is way cool.....
[Samsung Galaxy S (4G Model)] xc-racer99:
Try http://opengapps.org/ - their pico package will fit (and perhaps the nano one too, I'm not sure). Make sure to do a full wipe after installing them - you may get force closes otherwise. Note that I haven't tested this.

Edit: Note that if you're on a recovery that crashes when installing SuperSu/Gapps, you will need to flash the new ROM zip once, then reboot to recovery, then flash everything including the gapps and/or SuperSU.
[Samsung Galaxy S (4G Model)] DickyG:
Big problem...installation failed. Tried it 3 times (downloaded the zip file twice). I'm getting the error message "Updater process ended with ERROR:7. This has never happened.
[Samsung Galaxy S (4G Model)] xc-racer99:
Darn, guess I messed up the T959V zip or else it got corrupted during upload. Let me play around with it a bit more. You're coming from Lollipop, right?
[Samsung Galaxy S (4G Model)] Wish39:
Marshmallow for this phone? Cool! Good job. Will try if I have time to play around with this.
[Samsung Galaxy S (4G Model)] DickyG:
Cancel my last transmission, Scottie! The error message might have been my fault...I really don't know. Anyway, I one-clicked back to stock, re-rooted, and re-flashed. It booted! Since the wife is calling me to dinner, haven't done anything else, haven't tried any Gapps packages...but it booted! Back in the game.
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, probably some leftover cruft from lollipop :). I managed to get gapps working on my phone, first boot took at least 15min though. I used the pico package from opengapps.org.

First impressions after installing gapps - (and a couple of reboots), ram usage stabilized to around 30MB more than without gapps. Definitely still usable but not quite as good as without.

Thanks. In my opinion, its much faster than Lollipop, but it does still get extremely laggy if RAM is pushed to its utmost limits.
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
The rom flashed fine. I had this trouble with GAPPS. Here is a set of GAPPS that I did get working

https://www.dropbox.com/s/7uw0x5q6hcf5ml0/gapps-600-base-20151107-1-signed.zip?dl=0
[Samsung Galaxy S (4G Model)] DickyG:
I finally got the rom to flash...I think there was a problem with TWRP because it wouldn't let me flash the zip for SuperSU either and also borked my attempt to restore my previous rom. At any rate, it seems to be working OK now...I'll try your Gapps version sometimes this week. Good job.
[Samsung Galaxy S (4G Model)] xc-racer99:
I'm assuming that the trouble with gapps was installing them? As in the phone rebooted when try to install?

Yes, the issue is with TWRP - or rather, the mount command with the busybox that TWRP uses. We're probably one of the few devices to run into the bug as most other devices with MTD partitions have been "retired". This bug is present (at the very least) on the last build of 5.1 and the first build of 6.0. It _should_ be fixed on the latest 6.0 build.

Glad that you guys have found some gapps that work. Any report on the GPS?
[Samsung Galaxy S (4G Model)] DickyG:
The phone did reboot when trying to install the SuperSU zip and the Titanic Backup zip. I have now placed the apk files of both on my SD card in case this happens again. But the Pico Gapps just ran for about 30 minutes and never installed. When I get some time, I'll test the Gapps that AgainstTheFlow used. If successful, I can test GPS, a third party camera, etc.
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, looks like my "fix" didn't work or at least not reliably. Unless you didn't reboot to recovery after initially installing the ROM and thus were still using the broken TWRP?

BTW, you do need to use the SuperSU zip to install the superuser binary in addition to the app, just installing the APK won't root the phone.
[Samsung Galaxy S (4G Model)] DickyG:
Man, I'm getting frustrated...worked on it last night...finally got the Gapps to boot after numerous attempts. It connected to my WiFi and then completely locked up while "checking connection". I seriously think it's a problem with TWRP. I wonder if there's a way to flash via CWM anymore?
[Samsung Galaxy S (4G Model)] xc-racer99:
Nope, that's not a TWRP bug - that's the initial Google Setup using way more RAM than the phone can handle. I found it was easier to get through the initial gapps setup if I hit skip on everything rather than trying to set everything up at once. Once through to the homescreen, I reboot. Then, I give it 5-10min to settle after the reboot. Manually adding a Google account can be done later in Settings.

I've found that the biggest bottleneck on this phone is the RAM. While the processor is pokey, it is sufficient. The RAM is frequently all used up (ie, when I initially flashed gapps on my phone and looked at the Memory usage after the setup wizard was complete, it read 99%- not good and no wonder the phone locks up)

As for using CWM instead of TWRP, that's a non-starter. CWM has been all but abandoned.
[Samsung Galaxy S (4G Model)] DickyG:
OK...I'll try that next time. But I also think that TWRP screws up somewhere down the line...no problems with going through the wipe and flash process but won't let me restore 5.1.1 from nandroid backup so I'm doing clean installs of 5.1.1 after each session...very time consuming.
[Samsung Galaxy S (4G Model)] xc-racer99:
Ah, yes. I guess I should have mentioned that. A side-effect of the partitioning is that you can't directly restore a nandroid with a different partition layout. The "workaround" for this is (when the 6.0 is installed) is to wipe cache, data, and system, then install 5.1. Instead of rebooting, reboot to recovery and then restore your nandroid.
[Samsung Galaxy S (4G Model)] uLose:
I flashed this with supersu and open gapps pico and I cant get past the "491" play store error people mentioned earlier in the thread, even after trying the suggested solutions. Currently, I just have it without gapps. Anyhow, thanks xc-racer for still working on this old phone!
[Samsung Galaxy S (4G Model)] xc-racer99:
Too bad that you're still getting the error with the Play Store. I don't actually run gapps, but I suspect that the error is not something that is fixable on our end - its likely Google not liking such an old phone...

I'm still working on Marshmallow, screen-off charging is now working, selinux is much farther along, and I think I've figured out the Camera crash. Building the fix right now...

Edit: Yep, Camera crash fixed. That means that its only the GPS that may not be working. Everything else should be working (well, save the removed TV-Out, 720p video recording being laggy, and the microphone mute button not working). If someone wants a new build, let me know.

Edit 2: Just found out that video playback is busted. Oops...
[Samsung Galaxy S (4G Model)] DickyG:
Here's how to fix the "error 491" problem...at least this worked for me:

1. Go to settings/accounts and delete your Google account

2. Go to settings/apps and wipe data from Playstore, Google Play Services, Google Framework, and Download Manager

3. Go back to settings/accounts and re-install your Google account.
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
I will try the new build
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, I'll try to upload one tonight. I'm struggling a bit with the Video thing - I've found out that Video recording isn't working either (although this may be a regression as I'm trying to free some more RAM).
[Samsung Galaxy S (4G Model)] robonxt:
Wow! I am amazed that you ported Lollipop on this ol' phone and now you got Marshmallow working too?!

I am so going to give it a try
[Samsung Galaxy S (4G Model)] xc-racer99:
Yeah, but wait until I have the next build of Marshmallow uploaded - the first few have some quirks. Its still building so it won't get uploaded until tomorrow.
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, new Marshmallow build uploaded. Download from https://drive.google.com/file/d/0B7vXjzo0Hj-iSlp2dHVtOXJMV2s/view?usp=sharing Installation instructions are as follows:

If coming from 4.0+: Wipe system, cache, dalvik cache, and data in recovery. Flash zip - if it reboots automatically reboot to recovery and try again - its a bug on one of my previous builds. Install SuperSU and a tiny gapps package (if desired). If you installed a gapps package, then skip everything when setting up the phone (you can manually add an account later). Then reboot and things should start getting smoother.

If coming from a BML (stock-based ROM), then just flash zip in recovery.

The GPS may or may not be working, I need someone to test that for me. Everything else should be good to go. Let me know if you run into any problems.
[Samsung Galaxy S (4G Model)] mataflakitas:
Wooooow thanks racer99
[Samsung Galaxy S (4G Model)] DickyG:
Great...thanks...just finished downloading...will work on it this week-end. I've got the 600-base-20151102-1-signed.zip gapps package on file. I'll also see if I can find a newer version of SuperSu (I've got 2.46 but I think there's a newer version). Thanks for all your hard work.
[Samsung Galaxy S (4G Model)] DickyG:
OK...the ROM boots fine...also flashed Titanic Backup zip and SuperSU zip...both flashed fine. However, I've tried 3 Gapps packages. Every one goes through the entire bootup process and then I get an error message saying Setup Wizard has stopped..and the boot never finishes. I don't have enough technical knowledge to work around this. After booting the ROM, I seem to have plenty of excess internal memory so I doubt if that's the problem.
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, after installing the gapps packages, can you do a data wipe? Marshmallow brought with it a new permissions system - and if the system has already been booted up and then gapps are installed, the permissions are not granted resulting in FCs. I think that's what's happening in your case.

Its not internal memory that I was talking about being the problem, its the RAM (random access memory). Marshmallow isn't designed to work with the little amount of RAM that we have.
[Samsung Galaxy S (4G Model)] FBis251:
I've seen this problem before when the /system partition is completely full and the gapps package didn't get fully installed. Make sure there's some free space.
[Samsung Galaxy S (4G Model)] robonxt:
Just wondering, are you going to start a new thread for 6.0?
[Samsung Galaxy S (4G Model)] DickyG:
Success! Wiped cache, dalvik, & data before and after flashing Gapps...finally booted up. The initial setup was excruciatingly slow. Kept attempting to restore from previous backups. Finally, I just set it up as a new device. Initial problems: Flashed Titanium Backup from a zip and it kept force-closing. Finally did a fresh install from Playstore and it's working now. When I opened Link2SD, it said that it couldn't find the mount file. I just rebooted and it starting working. Due to space limitations, I'm restoring about 10 apps at a time, linking them, then restoring 10 more, etc. Have not tested GPS yet. I'll open GPS Test and let the phone sit outside for a while. Other than that, everything seems to be working fine. Not tested bluetooth because I don't use it. Great work!
[Samsung Galaxy S (4G Model)] robonxt:
Just tried the 1/7 6.0 build. Working fine so far.
[Samsung Galaxy S (4G Model)] xc-racer99:
Yep, I was just dragging my feet (and waiting for Marshmallow to get a bit more stable). I have now created one at http://xdaforums.com/galaxy-s-4g/development/rom-unofficial-omnirom-6-0-galaxy-s-4g-t3290395/. Please move all Marshmallow related topics there.

Good to hear!
[G3 Q&A, Help & Troubleshooting] Feche:
I was on a Moto G before and runs really cool vs. this LG G3.. here is a screenshot with CPU usage at 100%

I am a little worried about this.. is this normal for this phone? Also when using the phone the area where the buttons are gets warm-hot.. should I sent it to warranty? thanks :good:
[G3 Q&A, Help & Troubleshooting] Illogi.xbone:
Same thing here, went from an S4, rooted and clocked the CPU a little lower but it still warms up quite a bit.
[G3 Q&A, Help & Troubleshooting] JulianMarku97:
Same thing for me with the D855 32GB, temperature from 60° to 75°. So difficult to use the phone in this condition. Any fix found yet or i simply have to send to warranty?
[G3 Q&A, Help & Troubleshooting] Illogi.xbone:
I lowered the voltage a bit on Skydragon kernel and it isnt nearly as bad.
[G3 Q&A, Help & Troubleshooting] Feche:
Yeah I did some reasearching and indeed it looks like it's a normal temp for the G3.. Snapdragon 801 is powerhungry
[G3 Q&A, Help & Troubleshooting] Illogi.xbone:
It is. There is a thermal mod which ups the temp for throttle which does help.
[G3 Q&A, Help & Troubleshooting] lippo38430:
I noticed something, on cpu z and cpu temp i have 40 to 65 degrees celsius. When my phone sleeps it says 40 to 45 degrees but the phone is'nt even warm.

But cooler master doesn't show the same results, between 30 to 45 degrees.

I think there's something wrong with the temp sensor.
[Galaxy S 4 Mini Q&A, Help & Troubleshooting] xqee:
Hello guys!

I have problem with my GT-I9195.

Phone just turned off and I was not be able to turn it on. It was hard bricked.

Now I managed to unbrick it with SD card and debrick.img. Problem is, phone is in bootloop now.

I tried:

- Flash few firmwares with Odin, everything goes OK but I am still in bootloop.

- Flashed few custom recoverys with Odin. (After flashing I am still at stock recovery and No command).

Is there any way to rid of that bootloop and put custom recovery to mobile phone?

Sorry for my bad English.

Thanks!
[G4 General] legend221:
*If at all possible please donate to the person that created the application, you can pay via PayPal within the app*

No root required. I was able to install app from the Playstore, disregard that it mentions a Samsung phone. This website pretty much advises what settings to use and all.

Works in the meanwhile until an official fix is released for all of us G4 owners. Night and day difference.

You don't have to use the specific settings in the website, I've found some values myself that have worked well but it's a good starting point.

1.) Enable parameters

2.) Don't forget within the app to 'start service on boot'

3.) Reboot phone and enjoy a better phone experience

http://www.wiredchronicle.com/easy-fix-lg-g4-slow-touch-screen-response/

Test the difference within your phones settings: http://www.cnet.com/how-to/how-to-access-the-android-lollipop-easter-egg/

My Settings:

.: Sent from an optimized 'ANDROID til I die' device :.
[G4 General] Eric618:
I tried it and saw no difference. Even tried extreme settings, just to see what was altered. Not a bit of difference.
[G4 General] legend221:
After setting the parameters and checking the enable on boot you must restart the phone.

If you still see no difference I would look into exchanging the unit

.: Sent from an optimized 'ANDROID til I die' device :.
[G4 General] Eric618:
I'll try again...
[G4 General] Red_Baran:
I tried all kinds of configurations, I notice no improvement.
[G4 General] Z3ldaFan88:
I tried this app before and found no difference either. What did seem to help though (at least in my experience) was I just opted to do a full system reset, since then I have had no lag or missed touches or anything negative with my device.
[G4 General] shook187:
I saw the title seen than seen there was no thanks to the OP... I won't even bother trying
[G4 General] Phone_Junkie:
This app actually made a big difference for me. Thank you OP. I'd been thinking of a factory reset as I've seen a few people mention that clearing the issue but I'm good for now.

As you said, night and day difference.