yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] hutson23:
I can record and playback videos fine with MX player...

After installing the custom codec..on SlimSaber..
[Samsung Galaxy S (4G Model)] jeffsf:
I continue suspect it is a kernel problem that is triggered by using the standard OMX codecs. As such it will be an issue with any ROM built using the current kernel. Similarly, installing a product that doesn't use the standard OMX codecs has a good possibility of bypassing the problem.
[Samsung Galaxy S (4G Model)] inimeg81:
Yeah that's kind of an understatement. I think it was clear I'm just trying to hold someone over til its fixed. Its actually a memory issue with the PVR driver. Some things aren't declared in the android manifest as well that need to be. If you read up the media.camera has an autohide property that needs correction for video playback

If you want to read back at my earlier post. I gave a suggestion so the poor guy could play his movie. As I stated 'until' video is fixed. All of this extra I wish I had ICS Aries is cluttering the KitKat thread(s)
[Samsung Galaxy S (4G Model)] daothanhduy1996:
New build is up, gps should work now along w newest improvements that we, by far, have beeb able to do. Still video issue exist but hopefully we can sort it out soon. Cheer and happy flashing :).
[Samsung Galaxy S (4G Model)] DickyG:
Flashed new build...working fine...thanks!

The only thing I can't get working (same with previous builds) is the ability

to text by voice. On the keyboard there is a comma where the microphone

usually is.

In the meantime I have installed another app which lets me text by voice

(Write SMS By Voice). I have tried lots of stuff and can't get that little

microphone to pop up.

But its only a small inconvenience...everything else works.
[Samsung Galaxy S (4G Model)] inimeg81:
New beanstalk i am so happy! Move in 2 days!
[Samsung Galaxy S (4G Model)] williambs:
Thanks!
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Thanks @johnadelic for the build box so I can make a beanstalk build once a week and not feel lazy to do it anymore :p. So, no more lazyness, no more delay, no more 8-hour build. YOLO. :D

P/s: I'm feeling so lucky that I have had supports from people around me :). Thanks all of you guys tho. I will never forget how we had such time being here like in the past and in the present also :p.
[Samsung Galaxy S (4G Model)] Rebel_X:
dao & everyone: Unlike the previous version, it seems Xposed Installer 2.4.1 included as a system app, but I cannot access it to activate any modules for greenify, xblast, or xposed additions. I cannot even update it to the newer version 2.5 beta, version mismatch.

To solve this, uninstall it anyway by deleting the apk from /system/app using ES file explorer with root, reboot, and install the newer version, then run it, install xposed framework and reboot.

Edit: Originally, Xposed Installer is needed for the system app "App Settings", i.e, change DPI per app..etc! that is why it was there.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
I just made a build w clean kernel based off noiphonehere's source. I meant to start again from scratch so please test it tho.

That's mean, all of my commits as well as DJLamontageIII's are reverted, only clean kernel with my nand table - to ensure u wouldn't brick ur phone flashing this over the previous builds - and GPS's script. Please tell me about camera, video playing, gps,... Thanks

P/s: logcat should work fine on this build

DL: http://goo.im/devs/daothanhduy1996/beenstalk/BeanStalk-4.4.275-20140401-galaxys4gmtd.zip
[Samsung Galaxy S (4G Model)] Rebel_X:
It bricked my phone!!! :<

No just kidding, not good with April 1st fools day jokes..

GPS working .... and Video is working using the gallery video player.. Nice job :laugh::good:

All issues are fixed :)
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Thanks man, so now I can carefully start it all over again tho. Thanks so much for reporting me :p. Actually, it bricked my phone, too. And my phone was Galaxy Note lmao :p. Happy April fool ;).

P/s: how about camcorder man?

Sent from my phone.
[Samsung Galaxy S (4G Model)] Rebel_X:
Lol, forgot to say, Camcorder working too, I was able to record and play the video using the gallery video player. Taking photos working too. :)

The boot screen looks awesome and classy. Also, this build seems blazingly fast. No lag whatsoever, I just don't know if it is because of this build or because of the included Holo Launcher though. :)

Edit: Also, somebody mentioned over the troubleshooting forum that the link for Gapps Core is dead, you might wanna fix the link with this one if you would like: Here
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Thanks, just update the OP w new gapps link. And hey, do you mind if I restore the kitty boot screen? the one w NiLTMT? cause I like that pic plus this is just a new init for doing my whole work again and that kernel is dedicated to my gf :p - NiLTMT.
[Samsung Galaxy S (4G Model)] Rebel_X:
Lol, its your ROM dude, why you're even asking, I like the Kitty part too, I'm a cat lover you know! Thanks man. ;)
[Samsung Galaxy S (4G Model)] jeffsf:
Stoked you got the kernel working for video!
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Lol I must admit that I was wrong and stubborn not to reset my changes sooner. Yup, there were changes that caused the conflicts that I didn't aware and thanks for warning me b4 Jeffsf :p

Now I will start over again, slowly merge in good mods, not a bunch w/o knowing tho.

Sent from my phone.
[Samsung Galaxy S (4G Model)] jeffsf:
Sounds like you've got a solid base for your great ROMs!

I checked the head of the cm-11.0 branch from https://github.com/noiphonehere/android_kernel_samsung_aries

commit f51d386f5a737a9d206874b7d460a725204c44e4 (noiphonehere/cm-11.0, noiphonehere-cm-11.0)

Merge: 0cb67f8 99929ab

Author: noiphonehere <noiphonehere@gmail.com>

Date: Wed Jan 8 20:21:51 2014 -0500

Merge remote-tracking branch 'upstream/cm-11.0' into cm-11.0

with a couple changes to get the partitioning to line up with my "CM9" partitioning and a couple very minor things related to how it builds, and it looks good in the early OmniROM builds I'm doing. That it works in both trees is a good sign.

OpenGL libraries load

RIL fires up and loads modem

RIL appears to be functional (no SIM right now)

Touch sounds (click) work

GPS will try to get AGPS info from RIL

GPS will send NMEA data

Both cameras render previews properly

Video playback using OMX MP4 codec no longer crashes

WiFi seems to work

selinux logging seems to work
[Samsung Galaxy S (4G Model)] inimeg81:
Ffc isnt working... Xposed issue as well. Someone double check this. Also if u select keyguard speech fix it will fc continually. Otherwise all good.

* gps works - launch_gps.sh script from stock implimented

Rear camera works
[Samsung Galaxy S (4G Model)] Rebel_X:
Yeah, FFC is not working properly, showing the same symptoms (image repeated with scanlines or interleaved) when we first got CM7. I think FB or m4xm4n fixed it though, so it should be similar and fixable. I am not a fan of taking a picture of myself nor using FFC for anything, I could live without it, but that is just my opinion, still the ROM is great and that issue is not a deal breaker for me.

Same issue as CM7's back in 2012, here with picture It was fixed on release 11 by FB, iirc.

Xposed is included by default with this build as a system app, to activate the Framework, you have to go to "Settings->BeanStalk Options->Display and Animations" to configure it first and install the framework, otherwise it won't be activated. It took me awhile to find it.

There is a small issue, my guess is that it is beanstalk upstream issue not specific to this phone, is the transparency of the notification drawer, which works fine until you reboot, then it becomes solid black and you have to activate it again, nuisance, not a big of deal again.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
About the FFC, thanks for reporting me. I know where the issue is, honestly, but... i don't know how to fix yet.

It is actually just a cherry-pick that solve the problem but it's not what I want. Since from latest build I have used the upstream aries-common and I want to keep that custom in mind. Modifying libcamera will break what I want so I'm trying to find a way to move the libcamera into our device tree (which has already been messy) and make the box to build w our custom libcamera instead. Somehow I will have to trick the makefile to avoid conflicts. Or, I can simply ignore what I personally want and make a custom aries-common repo again.

Second method will be used only if I can't find a way to do the first one so FFC will be surely fixed but not now yet ^^.

P/s: second thought, not sure if the cherry-pick will solve the problem lol :p but worth a try to find a way to bring any customized things in aries-common b4 into our own device tree tho.

Sent from my phone.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Here is the newest build from John's build box: http://goo.im/devs/daothanhduy1996/beenstalk/BeanStalk-4.4.275-20140403-galaxys4gmtd.zip

Read the post above to see my idea and this build is for testing if the concept of adopting the libcamera from aries-common to local device tree work or not. Among that, there is also a commit affects FIMC from DJLamontagneIII and the fixes for FFC that were in aries-common before and I didn't merged in the previous build. Test the FFC/camera/camcorder and tell me its behaviour, please. Thanks!

I'm slowly merge back the changes and this time, I will do it wisely, under Jeffsf's advice if necessary - Thanks Jeffsf for helping me, man :).

P/s: I want to thank all the donators as I just received the images of your transactions from my friend whose paypal acc I'm sharing with and she is very reliable so don't worry. I will thank individually also :).

Pp/s: Camera doesn't work at all, can't connect to camera hmmmm.
[Samsung Galaxy S (4G Model)] jeffsf:
Yep, I think you're headed in one of the two directions to to go resolve the problem.

The driver for the front facing camera (FFC) of the SGS4G is index-swapped relative to that for the aries-common devices, that is also index-swapped relative to the rear camera. So you might say that the SGS4G FFC is "right" in that it is the same as that of the back. Index-swapping makes some sense as it is a rotate and mirror of the image -- just what you would do if you had a landscape-mode camera in a portrait housing and acknowledge that people are uncomfortable looking at themselves live without mirroring.

The "classic" fix for this on the SGS4G when using the aries-common libraries is to flip the FFC in the libcamera code. I've got it on my "to do list" to check the kernel code and see if the changes made relative to the "real" aries kernel are also doing an index swap. It may just have been that the libcamera that people like [MENTION=1949378]bhundven[/MENTION] and [MENTION=1949659]m4xm4n[/MENTION] worked with was flipped relative to the ones that the kernel devs for the early aries-common work had. The more you look at the source code and ROMs, the more you confirm that Samsung isn't really a consistent dev house.

But all that said, the aries-common build tree already has a make variable you can use to replace the "default" camera.aries, TARGET_PROVIDES_LIBCAMERA

I've attached a couple git patches (git format-patch => git am) that first bring in libcamera from aries-common to your tree, then the mods I made past that for the index flip in the three routines needed.

I haven't done it yet, but I was going to change the human-readable name of the module in at the end of SecCameraHWInterface.cpp to "Seira Camera HAL" to make it clear in the logs that the module is from the flippable source, not the aries-common source.

As you've probably gathered, I'm a big proponent of staying close enough to the aries-common trees that applying improvements that may appear there is reasonably easy. Unfortunately, most of the devs have abandoned both Samsung devices (apparently the Exynos 4 is equally annoying) and CyanogenMod. From what I understand, there are still two working on the older Samsung devices and I'm hoping to get our ducks in a row so that we can take 4.4.3 when it is released, along with any near-term improvements in ART.

.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
[MENTION=3770444]jeffsf[/MENTION]: do u have any idea why the camera couldn't start when I did that? I mean bring the libcamera into our device tree and change the lib nam.

Sent from my phone.
[Samsung Galaxy S (4G Model)] jeffsf:
Depends on what you change the name of the file that contains the library to. As I understand it, the loader will look for, in order:

<library>.aries.so

<library>.s5pc110.so

<library>.generic.so

to resolve a dependency of this type.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
The only thing changed was camera.aries.so -> cameragalaxys4g.aries.so. apart from it I didn't touch anytjing, coulnd't get the log since it's my mom's phone ans hardly I can borrow it.

Sent from my phone.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
New build is up. Changes: Set a flag to build custom libcamera in BoardConfig - Thanks @jeffsf for showing me - and rename the lib back to original one - libcamera and camera.aries instead of putting "galaxys4g" in the lib name.

Please test whether the camera work now and if it works, please report how the FFC/camcorder/camera behaves. Thanks!

http://goo.im/devs/daothanhduy1996/beenstalk/BeanStalk-4.4.275-20140404-galaxys4gmtd.zip

Edit: sadly, the camera is still broken.
[Samsung Galaxy S (4G Model)] johnadelic:
Indeed the camera is broken.

Sent from inside the time vortex
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Yep, some how it skipped building libcamera tho (look into system/lib/hw and u will see there is no camera.aries.so) I am trying to fix the build process. Once it's done, we would have camera work properly ;).

Sent from my phone.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
New build is up now. I managed to fix the build process to build our custom libcamera inside the device tree, thanks to Jeffsf for helping me - I learned something from your patch man. Camera should be fine now, hopefully.
[Samsung Galaxy S (4G Model)] DerPuGNa:
SLIMSABER have also a bug, when taking photo on FFC the camera FC?

is that normal or i just mess up my flashing?

i just found it 5 hours from now.

hahahaha. i just dont took pics everytime..

SORRY FOR THE OP V(^_^)
[Samsung Galaxy S (4G Model)] Rebel_X:
I installed this using goomanager's openscript, flashed fine, But....

I hope it is just me, but I got boot loop between the kitty part and Galaxy S4G part, I can't go to the recovery. right now I flashed one-click kernel, and going back to the April 1st build.

Somebody else test it please, since I can't try it again my PC is nuked waiting for replacement parts, and I am borrowing my friend's PC to fix the phone. Scratch that, it doesn't work, tried again clean by formatting everything, same thing.
[Samsung Galaxy S (4G Model)] christoophat:
Same thing here...:(
[Samsung Galaxy S (4G Model)] johnadelic:
Same here, I flashed it via TWRP. :(

Sent from inside the time vortex
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
I flashed it, and it booted. Had a difficult time getting the "GApps" to load, and the camera is still out of service.:(
[Samsung Galaxy S (4G Model)] daothanhduy1996:
After flashing it, bootloop (idk why tbh since I didn't touch anything else apart from libcamera). But u all can heimdall the previous build's kernel and it will boot fune w camera working. Inimeg81 told me that :)

Sent from my phone.
[Samsung Galaxy S (4G Model)] inimeg81:
If u use heimdall and enter the command wrong it will soft brick the phone and ull have to revert to kj6 then go back. Also you will most likely lose WiFi or will need to copy the modules from that kernel over. Sometimes WiFi and everything stuck... And everything works great. Sometimes u lose WiFi. If u one click back first u have a good chance of keeping it

So u flash 5 or 6 release then gapps then power off. Then put phone in download mide . extract boot.IMG from 04 or 01. Then heimdall flash --kernel boot.img or wait a lil bit til its figured out dao pm me on hangouts

I'm going to make a zip of previous kernel with correct modules but that makes me feel kinda lame as jeffsf recently tought me to do things the right way
[Samsung Galaxy S (4G Model)] Theraze:
Losing wifi on ICS usually meant that the flasher wasn't properly mounting system and so the modules weren't all right. Rebooting into recovery and reflashing would sometimes get it working. If that wasn't enough to fix it, then rebooting and toggling the system mount before reflashing would usually fix it...
[Samsung Galaxy S (4G Model)] inimeg81:
It seems that flashing heimdall 01 build the first few times on 05 build got it working with WiFi. U can flash 05 do backup of boot and recovery. Reboot recovery factory reset restore boot recovery flash gapps reboot OR

Just heimdall the boot.IMG from 05 after flashing 05 but usually loses WiFi. I checked the modules files in builds 5 and 6 that had 4 or 5 files compared to the previous 4 3 and 1 that had 8... Which I think don't copy over because of the target_recovery error early in the make bacon

---------- Post added at 12:13 AM ---------- Previous post was at 12:10 AM ----------

I think the twrp settings in the board config or the fact that the 4 variables early on in the build.sh are later returned with an un expected error because they are unset by a different config that is loaded later as an env variable set addition

---------- Post added at 12:16 AM ---------- Previous post was at 12:13 AM ----------

I could be completely way off about the last bit there... Its just weirs the md5sum matches for it to flash right but recovery is not compiled in completely (or something)
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Damn, tbh, I still can't find out what is the cause kf the bootlooo. I didn't touch anything else than libcamera tho. And fyi, I have been back to school regularly crazy schedule so can't do much or literally nothing til May 19th. Sr y'all.

Sent from my phone, I9300.
[Samsung Galaxy S (4G Model)] johnadelic:
Not sure if this is old news. But I can get build 4/5/14 to boot if I flash kernel 4/1/14 after the ROM.

Sent from inside the time vortex
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Cool. Anw, I deleted all the builds after 0401 due to stability and will try to solve the bootlooo after May 19th if I luckily have time then. To others: pls flash 0401 insted as it's cool enough to use except for camera but only FFC.

Gửi từ GT-I9300 của tôi bằng cách sử dụng Tapatalk
[Samsung Galaxy S (4G Model)] inimeg81:
Did u have WiFi after flashing
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
WiFi works perfectly after flashing, Never had an issue with that.
[Samsung Galaxy S (4G Model)] johnadelic:
Yeah no problem with WiFi here.

Sent from inside the time vortex
[Samsung Galaxy S (4G Model)] inimeg81:
Thanks
[Samsung Galaxy S (4G Model)] 404glitch:
If I'm running 4.4.225 with the GPS fix, is there a need to update to 4.4.275?
[Samsung Galaxy S (4G Model)] inimeg81:
Okay i flashed 01 kernel then 04 kernel so 2x kernel flash usuall fixes if wifi break for 05 or 06.

To the question about updating... I would. There are so many more features. Camera works pie halo more settings kernel rollback. Solid. Get 05 and flash 01 kernel through heimdall after then flash 01 again or 04 again. Some reason my wifi works flashing 01 then 04
[Samsung Galaxy S (4G Model)] christoophat:
Anyplace to get the newer builds, since Dao took them down from goo?
[Samsung Galaxy S (4G Model)] DerPuGNa:
im still confuse about the flashing method.?

and where is the 04 build? dao deleted?

if i flash 05 then 01 there is a WIFI issue?

and if i flash 04 then 01 there will be no WIFI issue?
[Samsung Galaxy S (4G Model)] johnadelic:
Safest thing is to just install the 01 ROM that is currently available. If you have the 05 ROM and want to install it the method I used was I batched, in this order, 05 ROM, core gapps, 01 kernel in TWRP. That seemed to work fine for me. Camera is busted though.

EDIT: sorry everyone I am dumb. The camera does work but video playback doesn't.

Sent from inside the time vortex
[Samsung Galaxy S (4G Model)] inimeg81:
Del
[Samsung Galaxy S (4G Model)] DerPuGNa:
i try the kernel to the slimsaber,

i have the wifi issue but i fix it.

i just copy also the system/lib/module of beanstalk to the slimsaber and also the boot.img then the wifi issue FIX
[Samsung Galaxy S (4G Model)] inimeg81:
Fixing do not dl recovery.img or boot.img in op of this edit
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
I have been getting quick reboots, then I get errors until I do a complete reboot. Anybody else experiencing this? I was able to extend the frequency of this by changin the kernal. This was on the 01 build.
[Samsung Galaxy S (4G Model)] nevkuril:
For some reason I cannot use Link2SD with 04/01 build to mount 2nd ext4 partition on SD card. I'm getting "Mount script cannot be created" error. I rolled back to a previous version an it works fine. Something is wrong with ext4 support in the kernel in this release?
[Samsung Galaxy S (4G Model)] inimeg81:
That doesnt have to do with the kernel. Or it shouldnt. I think the answer is in the beginning of the links2sd description in app store. What does your sdcard say when u type mount in terminal ? I will get a good zip up with 04/05 kernel with 05 rom. Its been difficult lately doing this without dao... And just today johns box is down. But a good zip to come within next 24 hrs. Promise
[Samsung Galaxy S (4G Model)] inimeg81:
Beanstalk repack update

For those who would like both back and FFC working as well as the kernel from 04-05 && 05 release, i repacked the zip with the appropriate libs & boot/recovery that all match with 05 release. So if you already have 05 installed with 05 recovery, please flash the kernel in dao's goo.im dir with the extension REPACK... or download and reflash the new Beanstalk image i uploaded ending in REPACK. So, to put more simply, the best kernel to flash is in his kernel dir on goo.im, the filename with REPACK, and the best and full beanstalk release is in the beenstalk dir, the file with REPACK. please download, test, and enjoy great release, ffc working, with correct kernel compiled & libs.

beenstalk/

-rw-r--r-- 1 daothanhduy1996 devs 219602880 Apr 23 05:56 BeanStalk-4.4.275-20140405-galaxys4gmtd-REPACK.zip

NiLTMT/

-rw-r--r-- 1 daothanhduy1996 devs 8817713 Apr 23 05:34 NiLTMT-v14.01.01.REPACK.zip

Thanks dao always for your hard work, and awesome kernel.
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
I am still getting the "soft" reboot issue. By "soft" I mean it just returns to the Beanstalk splash screen instead of going back to the Galaxy Splash screen. After this reboot, everything I try to do gives me an error saying " Andriod Process Media not responding" So to correct this, I have to do a full reboot, then it works for awhile. But it will still randomly go into this "soft" reboot., and the errors come back.
[Samsung Galaxy S (4G Model)] inimeg81:
I had this but after reformatting sd. It went away... But it never soft rebooted. Im talking about the process.acore. i dont have it anymore tho

The process.acore has to do with the media scanner running and usually only pops up if u are running links2sd

Oh. Suggest always factory reset, wipe system between 01 and repack. And flash repack kernel with repack rom after
[Samsung Galaxy S (4G Model)] johnadelic:
Sorry everyone about the delay on getting my build box back up and running. I have been super busy with work lately. I will try and get it up and running soon so the devs(inimeg and dao) and get cracking again.

Sent from inside the time vortex
[Samsung Galaxy S (4G Model)] inimeg81:
Heres a link with why the media.acore fails relating to externalstorage setting

https://groups.google.com/forum/m/#!topic/android-platform/c_dG3O8xfHs