yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, that's very odd. I can't reproduce the problem on my end. Some questions for you:

Have you installed a previous version of this ROM and did the Camera work?

Have you installed a different custom ROM (4.0+ or CM7) and did the Camera work?

Do you have gapps installed?

How much RAM do you have (go to Settings, Memory, and read off how much there is)?

Also, how did you get the SIM toolkit icon to show up? I've never had it show up...

Hopefully we can figure out what's causing the issue. Some other ideas: Download the ROM again and re-flash (potentially just a bad flash/download), go to Settings, Apps, Camera, and allow all permissions for Camera, and you can also try launching the Camera from some other app (eg from the lockscreen, from the Messaging app, etc).
[Samsung Galaxy S (4G Model)] rich@rd:
Hi, thanks for your prompt response, I'll answer your questions in the same order:

1. Install the version of February 29 and the camera works.

2. I currently have installed CM11 and the camera also works.

3. gapps are not installed.

4. The memory has a total of 386 MB.

5. sim card icon appears without any change I miss him, the screenshot sent by me is with the newly installed ROM, I will certainly not cast any change.

Right now I'm going to download the rom to install it again, and I'll try the advice you gave me, I will comment further on the results.

Thank you so much for your attention
[Samsung Galaxy S (4G Model)] rich@rd:
download and re-flash the rom but the same problem remains, plus probe also give all permissions and still the same.

Thanks in advance
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, Ok. Maybe there was an issue with the T959V build that I uploaded. I'll try to upload a new build in the next few days (I need to as there was a new set of security fixes as well).
[Samsung Galaxy S (4G Model)] rich@rd:
well thank you very much
[Samsung Galaxy S (4G Model)] xc-racer99:
Yep, definitely a problem on my end. I moved some things around the source code and accidentally removed the camera.

As a workaround, you should be able to copy from the previous zip /system/lib/hw/camera.aries.so to the same place on the new ROM.

Sorry for the mistake, I'll still try to upload a new build in the next few days...
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Changelog for 2016/04/08

Fixed camera on T959V

Security patch level of April 2, 2016 (latest to date)

Headset buttons fixed

T959V md5sum: 2b1560b99402c73275d1f69b3ceb9a22

T959P md5sum: e102cce0d624383fb85a32321c98c645

Otherwise, not much new. Currently its only on Google Drive but I hope to mirror it shortly... EDIT: FBis251 has mirrored it for me, links are in OP
[Samsung Galaxy S (4G Model)] mciahelwang32:
Would the CMA kernel work on this new build?
[Samsung Galaxy S (4G Model)] xc-racer99:
Yep, it should. Note that it is based on a slightly older revision so headset buttons won't work, it won't have the latest security patches, and /proc/last_kmsg won't work.

I can probably upload a rebased CMA kernel if you want...
[Samsung Galaxy S (4G Model)] mciahelwang32:
'

I dont need an rebased CMA kernel but can you tell me how to get to download mode so I can flash hemdall back to stock ROM?

Because I tried to get to Download Mode on all of the custom ROM's I had tried, but I dont think I had made it to download mode.
[Samsung Galaxy S (4G Model)] xc-racer99:
Check the thread you created, I just replied:)

(for future reference, located at http://xdaforums.com/galaxy-s-4g/help/how-download-mode-custom-rom-t3357570)
[Samsung Galaxy S (4G Model)] rich@rd:
Very good this new build, I've been using for two days and I have not found any fault in this.

Thank you so much.
[Samsung Galaxy S (4G Model)] graycow9:
So I have a long-stalled follow-up again. And to keep it short I only have a couple major bugs that happen hear and there-- then this ROM is a dream come true.

1. Sometimes I have a freeze occur (see next issue #2) and simultaneous battery drain occurs- all ending in a reboot to a drained battery. EH, I just charge it up again but makes it hard to leave home without a charger.

2. I love Nova Launcher and I have it installed, in it's most recent update the launcher informed me that there is a bug in 6.0 that causes laggy notification pull-downs. (Which also happens to be the point where I get reboot/drain most often.) but then Nova applies a root-level workaround to keep it from happening so often. :)

3/Last. The camera used in OMNI (which I think is RadCam or at least it's icon) takes pics fine, but when you snap a pic in portrait it flips the image 90 degrees. That's not really a huge problem but it's one I noticed.

Bluetooth works fine as long as you only enable it through your notification quick-settings. :)

I'm loving this ROM still, thanks for the updates :D

(btw, is there a decent CMA kernel I could explore?)
[Samsung Galaxy S (4G Model)] xc-racer99:
Thank you for your very thorough review. I will try to answer in order:

1) How old is your battery? If you take it out, is it still flat or does it "rock" a bit if it place it on a flat surface? I have never run into the bug you're mentioning, but I do get the occasional freeze (nothing I can do about this, it is related to the old PVR drivers we have (designed for 4.1.2 but they mostly workin 6.0....) This typical just ends in a reboot but my battery level is fine.

2) Never ran into this myself, but I don't use a custom launcher. Not something I'm willing to make changes on if the workaround in Nova works well (another thing to try is changing the Animation scale to 0.5 or 0 in the Developer Settings).

3) The Camera included by default is called "Camera2" and is the default AOSP camera. RadCam must have stolen its icon.... I also see the bug, I'll do a bit of testing and see if I can find out why. Edit: Doesn't happen with OpenCamera...

4) Bluetooth is a little bit odd, we don't support all the parts of the Bluetooth stack that Android defaults to. Unfortunately, the opt-out is broken in many places so I thought I had fixed it but maybe not. I'll do some more testing and see if I can get it working when going to it through Settings. Edit: This is indeed related to the fact that we disable parts of the bluetooth stack as when we go through Settings it tries to enable GATT which we don't support...

5) I was planning on merging the CMA commits into the main kernel for the upcoming release (which I should do sometime, just haven't gotten around to it...). While there are the occasional crash (ie forced reboot) (not quite sure why and its mostly above my level to fix) and the camera sometimes needs a couple of tries to open, the speed improvements due to the more RAM make up for it.
[Samsung Galaxy S (4G Model)] graycow9:
1 - - Brand new :) just bought a new SGS4G again because it's my favorite device and grabbed an extra new battery. Though I'm suspicious now that it has to do with the Battery Calibration app's methods. I.E deleting the batterystats.bin file. (I can't uv/ov btw, if that's important. The values just won't apply at all. O.o)

3 - - It's funny you mention OpenCamera, I switched to that myself xD amazing camera app right? It's got everythangg. Also funny that RadCam is actually the imposter. lol

5 - - That sounds exciting, will governors be included? Because I think this ROM will fly with a little SmartAssv2 under the hood. ;)

-- And as for Nova Launcher, it runs very smooth I'd say, the fix speeds up the notification pull for sure, but when I'm in the web browser it sometimes straight crashes with a screen fade. *shrugs* I'd imagine that it has something to do with the RAM flooding?

No problem, if I'm helping out then I'm glad to be of assistance :) :good: :highfive:

Edit: The battery issue might just be a fluke, because come to think anything with a battery level indication including TWRP- says that the battery is drained to about 6% but then it stays there or moves up to 7% and doesn't die for another hour or so of use. I think it's lying to me. :P lol
[Samsung Galaxy S (4G Model)] xc-racer99:
Odd that you can't oc/uv. How are you trying to do this? You should be able to do it through the "Performance" menu in Settings (may need to activate Developer Settings first - go to About Phone, click on Build Number repeatedly). Shouldn't have any effect on the battery... I'm not quite sure on the battery end as I have some difficulties myself (after I pass around 50% of battery it starts dropping a lot quicker) but I figured this was just my battery....

The straight crash is almost undoubtedly due to a lack of RAM, hopefully the CMA kernel helps with this....
[Samsung Galaxy S (4G Model)] graycow9:
I should have specified a bit more, I can overclock the cpu fine in the performance settings + edit the KSM settings etc- but when it comes to just voltage changes themselves, the apply values button doesn't work- it doesn't ask for SU permission either.
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, got it. I had never tried to modify voltages before so I never ran into the bug. Its just a permissions problem and will be fixed in the next release.

Doing some more looking at the Bluetooth error, but no guarantees for next build (if at all). Don't think I'm going to bother with the Camera bug.
[Samsung Galaxy S (4G Model)] graycow9:
It doesn't really hinder performance much, just something I noticed. And yeah I think the camera bug is fine, you can flip it with gallery anyway. :)
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Changelog for 2016-05-09

Uses CMA kernel by default

Performance Control can now modify voltages

Systemless SuperSU is now supported

WebM playback is now working

EFS backup in TWRP now works

Data on boot should now work - no need to toggle airplane mode anymore

md5sum for T959P - 118789dd68760d9fd18cc961398bf346

md5sum for T959V - f9375a8d9792c3a0d222c113213c014d

If you don't want to use the CMA kernel, then you can backup the current boot partition in TWRP and then restore it after installing the update. With SuperSU, I've manually built systemless support into our kernel, known to work with 2.71 but in theory all versions should work. If you're still having problems with data not working on boot, please let me know. I didn't test this change very thoroughly but I believe it should work.

A lot of the CMA implementation was taken from the OMAP4-AOSP group and their work on the Galaxy Nexus. Their thread is located at http://xdaforums.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574 and their github at https://github.com/OMAP4-AOSP/ (see the tuna kernel).

With the bluetooth not enabling, I'm not planning on fixing this bug as it can still be enabled from the pulldown menu (the easiest way to fix it would be to break most BT connections, so I'm not going to do that...). Also, I'm not planning on fixing powered-off charging as its an Omni bug, not one related to our phone.
[Samsung Galaxy S (4G Model)] mataflakitas:
Thanks ....?
[Samsung Galaxy S (4G Model)] rich@rd:
Hello,

I install this new version of Marshmallow May 9, 2016 and this runs very well but the phone has rebooted a couple of times and the call is not end when you press the button to hang.

The model is a SGH-T959V
[Samsung Galaxy S (4G Model)] xc-racer99:
Hmm, ok. The call not ending when pushing the button means I've messed something up when cleaning things up (and attempting to fix the no data on boot), I'll look into it later today (but won't push a new build for a few days yet at the earliest).

The reboots are almost undoubtedly related to implementing CMA in the kernel. If, after getting one of the reboots, you send me a last_kmsg (see http://xdaforums.com/showthread.php?t=2185929), then I can make sure. If you want more stability, I would recommend restoring the boot partition from a previous backup. I also get these random reboots, about one every two days (but I'm a very light user).
[Samsung Galaxy S (4G Model)] graycow9:
I just gave the new build a whip, it seems like it's from a build before the 0408 zip- is the security patch supposed to be April 2nd? Or the date might have changed.

Also, has bigmem been removed? It's grayed out in the Advanced tab. O.o And I have also experienced a couple of extra reboots like rich@rd- compared to the last build. Not sure what's up yet though. Seems faster though- while using the browser for instance. :)
[Samsung Galaxy S (4G Model)] xc-racer99:
Yep, bigmem has been removed (and I should hide it from the Advanced Tab). This is because what it did was not reserve memory for the camera when booting up, but with CMA we dynamically allocate memory for the camera when needed and allow it to be used when not (not sure if I'm explaining this very clearly).

Odd that the security patch is April 2nd, it shouldn't be (on the T959P, its May 1, 2016 - but I am running a slightly newer "development" build right now).

With the random reboots, if you send me a last_kmsg (link to directions a couple posts ago) then I can find out why its rebooting. I suspect its graphics driver related (and as that's a binary blob I can't do anything about it). It could also be CMA related, but that stuff is mostly beyond me as well...
[Samsung Galaxy S (4G Model)] asmalldharma:
Battery issues

Having the same battery issue. 60-70% battery, phone crashes, usually under 10% after reboot. Charging for 10+ minutes results in battery reading 70+% again. Battery about a year old i think.
[Samsung Galaxy S (4G Model)] xc-racer99:
To be honest, I think this issue is a lot larger than I know of. I believe its related to

Unfortunately, this is over my head. I have noticed that some things were not ported to the 3.0 kernel quite properly (ie we're currently using the Captivate's ADC and temperature data values while they were different for us in 2.6.35 along with a couple of minor GPIO changes). Unsure of how much of a difference these things will make.
[Samsung Galaxy S (4G Model)] xc-racer99:
[MENTION=4538057]graycow9[/MENTION] [MENTION=6842051]asmalldharma[/MENTION]

Can you please test the attached kernel and tell me if you still get the battery error? I've changed a few things about which may or may not mitigate the problem.
[Samsung Galaxy S (4G Model)] asmalldharma:
I can try this weekend. I somehow managed to corrupt my data partition being impatient and won't have time to fix it til then.
[Samsung Galaxy S (4G Model)] graycow9:
Just gave it a try last night, can't say for stability yet- because I charged it to 100% and let it sit for the night. I wake up- completely dead.[emoji14]So I'm charging it now again xD but it looks like the battery actually drained this time.

Edit:Editt: Although I just noticed charging from a dead point- the powered off charge animation now seems to be fixed. --- If I flash the test kernel on my 0408 backup it turns into butter. Very smooth and much less hiccups along apps. The web is even better now. Voltage works animation appears to be fixed. This looks good [emoji106] [emoji106] [emoji41]
[Samsung Galaxy S (4G Model)] Daltonyx:
I CANNOT cannot cannot get this or 5.1 to install. With CWM5 on GB (as well as TWRP with CM11) I get assert failed: run_program ("/tmp/updater.sh"), then it goes into a status 7 error. Wth am I doing wrong? I know it's gotta be user error :eek:

side note: I have a t959v
[Samsung Galaxy S (4G Model)] xc-racer99:
Alright, do you have a second partition on your SD card (and formatted to ext4/f2fs)? This is necessary as /data is on that partition. If you do and you're still getting errors, then can you post the output of omni_bml.log and/or omni_mtd.log (whichever exist on your sdcard). This will let me know what's going wrong.

Sidenote: I do have an alternative partitioning scheme ready where the entire SD card is formatted to ext4 when installing. I do not plan on updating this ROM to it as it would require a data wipe, but am saving it for Android N (IF I can get it working when it is released).
[Samsung Galaxy S (4G Model)] Daltonyx:
I believe so? I did it in TWRP with a 2048mb size and a 64mb whatever the second one was. I don't recall. I just booted up my linux to check on that tbh. By the way, sorry about the late response. I've been at work all day. Thank you so much for the help!

---------- Post added 24th May 2016 at 12:40 AM ---------- Previous post was 23rd May 2016 at 11:54 PM ----------

Okay, so the answer to having two partitions on my SD card is no. I've tried through linux on GParted, disk utility and whatnot, on Android on three phones with AParted and Apps2SD, and a whole bunch of other ways. My SD always shows up as unsupported v.v What am I doing wrong? I tried a primary fat32 partition with both F2FS and EXT4 respectively. Neither one functions and shows up as a damaged SD card. Ugh. I know I'm being an idiot about something. Also, I don't have any logs on the SD card when I try? or do they disappear upon reboot out of recovery?
[Samsung Galaxy S (4G Model)] Daltonyx:
Holy **** I did it. Yeah, I didn't realize the ext4 partition would fail to be created when I used twrp, apparently the screen timeout causes it to become unresponsive so I would always do a battery pull :oops: I checked the log and got it, thanks SO MUCH for your help!
[Samsung Galaxy S (4G Model)] Daltonyx:
Ugh I spoke too soon. Does this mean I have a bad sd? What exactly are the size requirements for both partitions?
[Samsung Galaxy S (4G Model)] xc-racer99:
Well, the second partition (/dev/block/mmcblk0p2) is your /data, so it should be at least 512MB - but roughly 2GB is best (IMO). When creating the partitions with TWRP, you don't need to create a swap partition, this would just be unused space (but shouldn't cause any problems).

Have you ever actually managed to boot up the 6.0 ROM? The "SD unsupported" message sounds like one that I had after booting up - to fix it, I reformatted the 1st partition on the SD card using gparted.

Another error that you're running into is that the parted utility in TWRP is not being able to inform the system about changes to the partition layout - so while the SD has a new layout, the system still thinks its the old one. To work around this, immediately after repartioning, reboot (to recovery).

However, the very last error in your recovery.log is not related to the second partition, but rather /system not having enough space. I think this is likely due to a bug in the updater.sh when coming from a previous MTD ROM (my fault, I'll have to check it). Try again flashing from BML (GB) this time.

P.S. You're also having some badblock errors which means that the NAND on the internal storage of your phone is starting to die - but there should still be a sufficient number of good blocks left.
[Samsung Galaxy S (4G Model)] Daltonyx:
I haven't gotten anything further than CM11 to boot on the damn thing, honestly. It throws errors at symlinks now, and the log yells about space. I'm flashing it to GB now. About to head to work though so I'll get back to ya with the details. I'm gonna go to GB, keep it partitioned the way it is on the SD, and then I'm gonna try from cwm5
[Samsung Galaxy S (4G Model)] Daltonyx:
Haaaaaay heck yeah man. It worked from BML. Cool beans (:

THANK YOU SO MUCH FOR YOUR HELP
[Samsung Galaxy S (4G Model)] Daltonyx:
So, an update to this, I got it to boot coming from BML, (with CWM5) no issues whatsoever. In fact, it's running rather well since I put it on ondemand. I have a 166xMb ext4 partition, with a gig and a half fat32 on the sdcard. As a sidenote, it's pretty BA that ya did this, not gonna lie. haha.
[Samsung Galaxy S (4G Model)] DarkFrenzy:
what will happen if put the galaxy_s_series.xml after repo sync ? the i do repo sync again

is that a problem?
[Samsung Galaxy S (4G Model)] xc-racer99:
Yep, there's no problem with that, running repo sync again will make sure all the necessary files are there.

Which device are you building for, just out of curiosity?
[Samsung Galaxy S (4G Model)] DarkFrenzy:
i was trying build for s4 mini and couldnt start the build because of

build/core/product_config.mk:222: *** Can not locate config makefile for product "omni_serranoltexx Stop.
WARNING: Trying to fetch a device that's already there
Traceback (most recent call last):
File "build/tools/roomservice.py", line 352, in <module>
fetch_device(device)..................

so i was searching how to build omnirom and came here, and found "before sync put the ...xml file" so to clarify that i posted here.
[Samsung Galaxy S (4G Model)] xc-racer99:
I don't support the S4 Mini - its not one of the "aries" series of devices which is basically all first-generation Galaxy S devices - these are the only Samsung devices I've worked on. While there appears to be an unofficial build of 4.4 for your device (see http://xdaforums.com/galaxy-s4-mini/development/rom-omnirom-builds-silesh-nair-t2807876), you would need to do the bringup yourself if you want 6.0.

Basically what putting the ...xml file is doing is telling repo to sync the device specific repositories. Since these are unofficial builds, just running "breakfast galaxys4gmtd" would not download the needed repositories (if this were an officially supported device, it would). Each line of the xml is a repository - the vendor blobs, the device trees, the kernel, and the needed hardware repo.

Hope this kind-of makes sense.
[Samsung Galaxy S (4G Model)] socalrokk:
thanks for this. I've been running for a couple days and I really like it.

my settings, however, are only giving me an option for 2g and 3g. Is there anyway to use 4G capabilities?
[Samsung Galaxy S (4G Model)] xc-racer99:
New Build Uploaded!

Changelog for 2016-06-07

Security patch level of June 1, 2016

Microphone mute now works when in call

Battery now charges to 100% and should read properly after a system crash

Standby times should be improved

Slightly less RAM - but should result in better graphics performance

CMA crashes fixed (at least, I haven't crashed once since I started testing the patch a week or so ago)

PowerHAL is back - CPU is boosted when turning screen on to avoid delay

md5sum for the T959P: eeed77fb84189e84f2264e32d18ce454

md5sum for the T959V: b6457319d248029429183c342514b072

With the PowerHAL, it only works when the governor is interactive, otherwise it has no effect. Also, on boot it resets the maximum frequency to 1000Mhz. If at all possible, please check the md5sum of the build before flashing as I used a different method for uploading this time.

Well, our phone has "fake" 4G. This is HSPA+ (up to 21.1Mbps) which is faster than regular 3G and was marketed as 4G. When 4G LTE came out, Android started treating HSPA+ has 3G hence why it only shows 3G. You can do a speed test and you're still getting the faster speeds.

Also, as I don't use data, I can't even verify that the 2G/3G toggle in Advanced settings even works:o My advice: just leave it at the default;)
[Samsung Galaxy S (4G Model)] xc-racer99:
Testers wanted!

So, I've had this idea of trying to create a unified build for both the T959P and T959V. I've hit a snag - in the kernel, I can't figure out how to change the initial UART setup and the two devices have different values. The difference is on UART1 which is for the GPS. The T959V values do not work on the T959P but the opposite might be true.

tl;dr

So, can someone on a T959V test the attached kernel and see if the GPS works?
[Samsung Galaxy S (4G Model)] mataflakitas:
Thanks
[Samsung Galaxy S (4G Model)] Targaff:
xc-racer: I was able to install the ROM without a problem (once I got my partitions sorted), but whereas with all previous versions - including the last 5.1.1 omnirom, which I'm running currently - I had no issues with phone reception, whereas 6.0 would rarely find my network. Is there something specific that might be the cause of this?