yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] daothanhduy1996:
So your interested in Building/Porting for another device?! Follow this guide! **Please make sure to give proper credits and Use the layout i have in the first post.** - If you need assistance, please send me a PM, do NOT post questions in this thread. I may open a general porting/building thread in another section depending on how this goes. You must have some general experience/knowledge in this area to complete this. Building from Linux platforms. In particular Ubuntu 10.04

If you have building/development concerns or issues, Please visit the BeanStalk Development Thread to avoid cluttering this thread.

Setup to build - This section can be skipped if you've ever built anything before. This is for first time build setup.

1. From your root terminal location, type the following: sudo apt-get install curl git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline5-dev gcc-4.3-multilib g++-4.3-multilib

2. Type: mkdir ~/bin

3. Type: PATH=~/bin:$PATH

4. Type: curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo

5. Type: chmod a+x ~/bin/repo

From terminal

1. type 'cd'. This will bring you to your root folder.

2. type 'mkdir beanstalk'. This will create a folder named beanstalk.

3. type 'cd beanstalk'. This will take you to the beanstalk directory created from previous step

4. type 'repo init -u git://github.com/scotthartbti/android.git -b cm-10.1'. This will setup the folders to be synced.

5. type 'repo sync'. This will sync the folders to your beanstalk directory. Note - This will take some time depending on internet connection. Be patient!

6. After the repo sync finally finishes, all you need to do is add your device, kernel, vendor specific files for the device you are building for. (You must know what these are, dont bother asking me if your not sure.)

7. Make sure all your device specific files are setup as if you were going to build for CM.

8. Outside of terminal, navigate to beanstalk/vendor/cm. Double click on the get-prebuilts file and select run in terminal. This will fetch necessary files needed to build and place them where they need to be.

9. Type '. build/envsetup.sh && brunch "device name"'

10. Previous step will start building beanstalk for your device. The process takes anywhere from 1 - 3 hours depending on your computer.

11. Once completed, it will say package complete and you will have a beanstalk named zip file in your out folder.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
CAUTION!!!!!!!! At the moment, the ROM size is too big to have space for Gapps, so please IF YOU WANT to ENJOY this ROM with Gapps, FOLLOW my INSTRUCTION:

1. Open the ROM zip: BeanStalk-4.4.205-20131231-galaxys4gmtd.zip via WinRAR or Winzip or 7z,... on your PC/laptop

2. Browse to /system/app and delete these files:

GooManager.apk

HoloLauncherHD.apk

Nova.apk

QuickSearchBox.apk

3. Download my Moded Slim_minimal gapps - I just deleted the Hang out, Youtube, Google Music player and Gmail which you can install it via playstore - put it in your sdcard and flash along with the ROM.

4*. For advance users only, AFTER doing all those steps, you can even delete the LatinIME which is 40MB @ /system/app via RootExplorer and install Google keyboard - as user app - instead via Playstore or find the apk @xda :).

Enjoy using it everyone!​

Or simplier: download this gapps insted, only 17.4MB, I just found it but haven't tried: http://www.androidfilehost.com/?fid=23269279319195954
[Samsung Galaxy S (4G Model)] ithunter:
frankly suggest me which is better Beanstalk or Slimkat ?
[Samsung Galaxy S (4G Model)] christoophat:
I should think that the end user would be the best one to determine that answer.:silly:

All the options/feature for each ROM are listed for you in OP first posts. Decide & try.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
One thing I can notice w this rom, the meamory leak seems tp be better than on Slimkat even after flashing gapps.

Originally (w/o gapps) the ROM only uses 52MB RAM for apps (not include caches), sounds crazy.

And FYI, I will support this ROM even with Sabermod/Linaro toolchain soon along w Slimkat and I will only support these 2 ROMs. No CM11 due to limited hard disk on my laptop so dont ask for it. If u want to have CM11, feel free to build as all of my commits are online and open. If u need help for building, feel free to pm me but just warn u that even tho I have good temper with requests/reports but I am such a jerk with instructing ppl (as I am easily go mad somehow, even tho I used to be a noob asking for help back then) so feel free asking for help but forgive me if I say something wrong. Thanks!
[Samsung Galaxy S (4G Model)] Link119:
Would you say that this is more stable than SlimKat? That is my main concern because ive had many freezing issues with SlimKat.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Nope I didnt say so. This ROM still has some graphical glitches with the Quick Setting but other than that, it is cooler than Slim with features. But IMO, I still prefer using slimkat as slimkat is slimmer (obviously), purer and has the better TRDS compat (as beanstalk hasn't meraged all the TRDS commits tho). I just flashed Slimkat for 2 more ppl :p and my Mom, my friends and I haven't seen any reboot/freeze with the original set up config on slimkat tho so IDK what was wrong w ur phone. Anw, choice is yours so choose what u like to run then ;).
[Samsung Galaxy S (4G Model)] graycow9:
Browser?

I'm not sure if maybe this is just me, but I have tried flashing this ROM a few different ways, and still the browser won't open when installed? Any ideas? Also, excellent work on SlimKat and BeanStalk4.4 ;D
[Samsung Galaxy S (4G Model)] daothanhduy1996:
New build is up on my Goo.im. Enjoy everyone!

New: New NiLTMT kernel - v14.01.01, Camera buggy fixed.
[Samsung Galaxy S (4G Model)] Rebel_X:
It happened to me also, I don't know what fixed it, but I recall that I wiped everything (system/data/dalvik/sd-ext) except SD card and reflashed, also

don't flash Slim-minimal Gapps, I think it is the culprit. Instead flash the one provided in the first post (only google play) which works.

On a side note, this rom is much more stable and feature rich unlike Slimkat. I like it, it only needs working GPS and it would be perfect. (I wonder if porting the Vibrant's GPS drivers would work, since they have the same gps chip and they have it working in kitkat and JB).
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
I dont have any issues with the browser. But I did notice that everytime I boot, or reboot the phone, I loose all of the widgets that I put on the home screen. Not sure why it does this, and it is not hard to put them back on, just annoying.
[Samsung Galaxy S (4G Model)] DerPuGNa:
maybe you can change your laucher>?

i have no issue about that, im using apex launcher btw

BTW this rom for me hahhaha has no reboot issue?

it is a bit lag but no reboot issue

HOW?
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
I have no reboot issue with this rom, this happens when I reboot the phone. I also run Apex launcher. I have the Facebook widgets, a clock widget, and Weatherbug widget. They all do not reload after reboot.
[Samsung Galaxy S (4G Model)] DerPuGNa:
reflash it ? that is the only answer.
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Been there done that! LOL. Still a great Rom, and how often do you actually reboot your phone, maybe once a week? I can live with this issue.
[Samsung Galaxy S (4G Model)] DerPuGNa:
it depends. when i am experiencing lag. i will clear cache and dalvik. or if my battery runs out.

sometimes, to install, (like installing system apps or private apps ) that require boot to be seen in my drawer
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Glad u guys enjoying beanstalk. Fyi, the lag on beanstalk is caused by the swipe to switch feature which caused lag on some other kitkat ROMs as well (but there are still some also have swipe to switch feature w/o lag). Swipe to switch let you swipe across the notification tray to switch to Quick Settings. Btw I am setting up a linaro/SaberMod Slimkat build that hopefully wont have the issue w reboot/freeze. Glad to know that it doesnt exist on beanstalk.
[Samsung Galaxy S (4G Model)] DerPuGNa:
i like slimkat more but this rom is much stable than slim so i use it for now till slim get fix :D
[Samsung Galaxy S (4G Model)] Link119:
Same here, although i mostly prefer SlimKat because it is a little quicker although i am not a fan of the reboots so i moved over here (to the dark side ;) ). On the other hand, i do see much potential with this getting a little less laggy.

By the way, great work Dao! I cant thank you enough!
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Dispite the little lag, I got bored at work today so started playing. I multitasked the fire out of this ROM and it handled everything well! I was sending and recieving texts while listening to music as well as surfing the web. I was also posting on this forum using the mobile app. The ROM was solid through all of this! very impressive. I am done testng this ROM, am now switching back to Slimkat and waiting for the next ROM update there that will hopefully fix the reboot issue.
[Samsung Galaxy S (4G Model)] Rebel_X:
Guys, this rom is so smooth, I have like 300 apps installed without lag. I even customized

everything. I love the lockscreen bat mod. Battery life is amazing too (I use greenify).

Basically, if you want lag-free Beanstalk, follow this guide: Here :)
[Samsung Galaxy S (4G Model)] ithunter:
what about freez and reboot ?
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Never had this issue with Beanstalk. Just a little lag occasionally.
[Samsung Galaxy S (4G Model)] DerPuGNa:
does not have it ;)
[Samsung Galaxy S (4G Model)] Link119:
What makes SlimKat freeze and reboot makes BeanStalk lag for a second or two. So rather than rebooting your phone will just take a little to respond which is much better IMO.
[Samsung Galaxy S (4G Model)] Damian2013:
Does art work?
[Samsung Galaxy S (4G Model)] DragnzKlaw:
Yes. Been on it since last Sunday. No reboots and no lags. Smooth. Awesome work Dao.
[Samsung Galaxy S (4G Model)] Zixx:
So far this Rom was just awesome no reboots or issues. If T-MO had reception where I live I wouldnt need wifi calling so I would So stay with it,since it was super smooth .

Thanks again Dao!
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
Keyboard

I did find one minor issue. I like the swype keyboard. I downloaded the swype trial with dragon and installed it. After it is installed it does not show up under the language and input screen, so it cant be selected. REboot phone and it is there. After selecting sywipe, it is fully functionable,
[Samsung Galaxy S (4G Model)] hutson23:
Will we ever be able to flash these 4.4 builds without having to one click back to stock...I have been working out of town and can't access my computer?
[Samsung Galaxy S (4G Model)] jeffsf:
Well, I'm considering giving this a shot. Has anyone successfully returned from KK to ICS with their system-app data intact? In particular, I'm talking about things like accounts, sync settings, call logs, and SMS/MMS and associated content.

I'm guessing this was built off git://github.com/scotthartbti/android.git -b kk44 -- I'd like to be able to mess around a bit with internal/external storage to get this to the point that I can install my apps. I've gotten a bit spoiled with a huge /data partition on my microSD.

"Yes."

OK, all kidding aside, it's killing me already to be switching between Gingerbread and ICS on a regular basis. I'll look into what an updater script would look like to also deal with shifting partitions boundaries might look like. I don't know that I'll get to the point of making it totally automatic, but I'll see what might be reasonable.
[Samsung Galaxy S (4G Model)] hutson23:
Great....It would be much appreciated by all I am sure.
[Samsung Galaxy S (4G Model)] jeffsf:
I'm still getting a copy of [MENTION=4571512]daothanhduy1996[/MENTION] build environment running on my machine, and thanks to him for his help in getting matching guru incantations so we're working on basically the same thing.

From what I can tell, if you don't want to "start over from scratch" when flashing one of these ROMs with a different MTD partitioning scheme than the one that you are on, here's an outline that is worth trying. It's in the "works for me" state now, not really a guarantee.

Boot into recovery with your current ROM

Back everything up

Use tar to copy the contents of /radio and of /efs to your microSD

Flash the new ROM

Reboot into recovery

In the new recovery

Wipe (format) /system, /data, and /cache -- you need a real format for all your partitions, not just deleting files

Manually format /efs and /radio (unless your recovery lets you do it directly)

Flash the ROM and, if needed, Gapps of some sort

Restore the /efs and /radio from the tar you created (alternately restore /efs and flash one of the modem zips [MENTION=3833556]FBis251[/MENTION] prepared)

Reboot into the new ROM

If that seems like a pain, or you need explicit command-line instructions, I'd suggest sticking with the heimdall-to-gb approach.
[Samsung Galaxy S (4G Model)] HolyGhostBoy1:
What's the purpose of heimdall one click to bml rom?
[Samsung Galaxy S (4G Model)] systemunknow:
Hi After following instruction on the first page:

Install TWRP,

Wipe all expect SD card,

Install Rom via D/L link provided both newest rom and the GAAPS beta

All Successful:

Reboot,

And get back in TWRP screen everytime.

Any idea why?
[Samsung Galaxy S (4G Model)] ithunter:
Install Beanstalk again !!
[Samsung Galaxy S (4G Model)] daothanhduy1996:
As I wrote man, please read everything in OP carefully b4 asking. Everything u need to know is in the OP. Anw, here is why: since I changed the partition table and not using the old layout that had been using in ICS and JB anymore so, u should back to BML if u don't want to lose or even HARD BRICK, ye, I said HARD BRICK not soft brick, your phone due to the mismatch of the offset for partitions like /boot /recovery /system /data that might make the phone to wipe everything else (include /efs, bootloader,...).

Even tho I think flashing the KK kernel from JB and then reboot to recovery and use format option/command will work but I am NOT SURE and NOT GUARANTEE that all the change will be applied properly so I advised ppl to be back on BML and start fr scratch like what we did on ICS days.
[Samsung Galaxy S (4G Model)] HolyGhostBoy1:
Sorry about that and thanks for still explaining
[Samsung Galaxy S (4G Model)] DerPuGNa:
its awesome BUT,

I figure out that ART MODE, when im on dalvik mode, my internal memory uses 80mb [include gapps (core) and (genie widget) ] but when i turn into art mode, the usage of my internal doubled!. its 160 or 150mb. its awesome rom but it is giving me a headache to put it in all my apps in art mode without running internal storage. :crying:
[Samsung Galaxy S (4G Model)] daothanhduy1996:
ART is well-known for respuorce hogger ^^
[Samsung Galaxy S (4G Model)] DickyG:
Just installed Beanstalk...it is running absolutely perfectly...no problems whatsoever...I must have done something wrong.

Many thanks to Dao and the rest of the developers.
[Samsung Galaxy S (4G Model)] HolyGhostBoy1:
hello when i run oneclick it stops at the installing kernel and then reboots is something wrong?
[Samsung Galaxy S (4G Model)] jeffsf:
First, I'd try clearing the Dalvik cache. At least as I understand ART, the contents of that cache are "useless" for you and just consuming space on /data. The Dalvik cache is generally just a bit smaller than all your installed APKs. I'm assuming when you say "internal memory" you are talking about the data partition, and neither active RAM nor the system partition.

Past that, ART is experimental at this point. At least from what I've read, it is a little better on performance overall, but the perceived improvement is that there isn't the brief JIT compilation lag when you're asking for an app to do something "new."

One reasonable review of ART -- http://www.infinum.co/the-capsized-...ntroducing-the-new-android-runtime-in-kit-kat
[Samsung Galaxy S (4G Model)] ariesgodofwar:
I saw the same behavior with Slimkat, even after clearing my dalvik cache. Slimkat runs just fine other than the known reboot issue in Dalvik mode.
[Samsung Galaxy S (4G Model)] Link119:
So that was the reason why i kept getting crashes on SlimKat? What does ART mode mean and why is it more stable?
[Samsung Galaxy S (4G Model)] ariesgodofwar:
Well, if you are trying to convert from dalvik mode to ART (Android RunTime) and do not have enough room in your system data partition for the expanded size, then your phone will crash, however, there is a somewhat random reboot issue with Slimkat which is completely unrelated to dalvik/ART modes and due to a module which appears to be missing in the build. Dao is working on fixing.
[Samsung Galaxy S (4G Model)] jeffsf:
First, while I wouldn't recommend it if you find you have any problems, I've been OK going from my CM9/TWRP builds to this ROM (after appropriate backups, of course) by

Flashing ROM

Reboot recovery

Wipe /system, /data, /cache

Re-flash ROM

Boot into ROM

I'm still working through how to get ICS data in for the system apps, so I haven't run much with it.

I am seeing "strange" directories being created on the microSD:

drwxrwx--- 2 root sdcard_r 8192 Jan 14 22:00 DCIMD?ó.·?
drwxrwx--- 4 root sdcard_r 8192 Jan 14 22:34 DCIMDBª.·?
drwxrwx--- 4 root sdcard_r 8192 Jan 14 21:36 DCIMDà¼è.*?
drwxrwx--- 2 root sdcard_r 8192 Jan 14 20:44 DCIMDæÑë.*?

drwxrwx--- 2 root sdcard_r 8192 Jan 14 21:59 LOSTDy»é.DIR
drwxrwx--- 2 root sdcard_r 8192 Jan 14 20:44 LOSTDçÑ}.DIR

so something funky is going on there, at least for me. A clean install didn't change the behavior.

Additional note -- BeanStalk-4.4.205-20140103-galaxys4gmtd.zip is built for "aries" so you can't flash anything using its recovery that looks for the older list of device/product names, such as ICS kernels or ROMs.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
Howdy [MENTION=3770444]jeffsf[/MENTION] I saw funky folders on my Mom's phone, too but not those u listed, mine was funky backup folder name when I backup using TWRP and I was unable to c my backup on sdcard due to that. I had to rename the folder manually anw. Just wonder what caused this thing :/.
[Samsung Galaxy S (4G Model)] DerPuGNa:
this is what im pointing about my post on slimkat.

i said that " do u experience this multiplying LOSTxxx.DIR folder."

ithunder said no so i think this is my fault but! i found SOLUTION FOR BOTH OF THESE

first CREATE a folder called LOST.DIR (create on ur pc) then delete the rest of punk folders!!( do this on ur file manager)

DONE!

well this TWRP is worst!

well to fix this multiplying TWRPrsqwe1231231awda

is to leave on 4.4 rom.

you must do this before you install the 4.4 rom

first!

IGNORE those TWRPxsxxx (not in 4.4 rom maybe on stock rom. im doing this after i oneclick)

CREATE folder called TWRP (create on your pc)

well flash 4.4 rom then after a boot. delete ur TWRPxxxx folder !( do this in ur file manager)

DONE

do the steps on DCIM also :D
[Samsung Galaxy S (4G Model)] systemunknow:
Did like 80 billion times each time when the phone reboot it goes back to TWRP and give me the same screen again and again, tried to install CWM but it doesn't really work since everytime I reboot it goes back to TWRP, and I can't delelte or remove the TWRP either.

RIght now I have installed and reinstall many many times following the steps no matter what I install it always goes back to TWRP after the start up logo....
[Samsung Galaxy S (4G Model)] DickyG:
OK...what ROM were you on prior to flashing Beanstalk? If you tried to flash directly from your previous ROM, you might encounter problems. Secondly, you don't have to install TWRP...the Beanstalk kernel does that for you.

I suggest you go back to the original instructions:

1. Use Heimdall to get back to GB

2. Use Heimdall to root the phone by installing Anton's kernel

3. Do the necessary wipes and flash Beanstalk by using CWM recovery

4. When TWRP magically appears, wipe again and reflash the ROM & Gapps

I followed these steps and had a clean install first time...and I'm not all that experienced.
[Samsung Galaxy S (4G Model)] AgainstTheFlow:
I have been getting these too. I have reformatted the sd card to get rid of them, and I also re-installed the rom twice. Still comes back
[Samsung Galaxy S (4G Model)] jeffsf:
I've got a bit of a theory as to where they might be coming from. Next time you do install, would you check the time of creation of the file against the time that you booted the freshly installed ROM the first time? Minutes definitely count, and seconds, if you have them, would be helpful.
[Samsung Galaxy S (4G Model)] DerPuGNa:
LOSTxxx.DIR appear after you eject your sd card.

DCIMxxx appear when you use camera

TWRPxxx appear when you boot to recovery

Backupxxx appear when you back it up? i think?

and to prevent all of there you need to use LOST.DIR, DCIM, TWRP and backup folder and you can stop multiplying them.
[Samsung Galaxy S (4G Model)] jeffsf:
OK, this is what is working for me to go to/from Team Acid CM9 and has been pretty reliable so far:

Make sure you have backups of /efs put away somewhere safe!

CM9 to Beanstalk (make full backups first, at least TWRP and hopefully Titanium Backup or equivalent as well)

Reboot recovery

Install Beanstalk

Reboot recovery

Advanced Wipe; /system, /data, /cache

Install Beanstalk

Make TWRP backups

Boot into Beanstalk

Once you have TWRP backups of your "target" build, you can flip/flop reasonably easily

Reboot recovery

Restore TWRP backup of Boot of target build

Reboot recovery

Advanced Wipe; /system, /data, /cache

Restore TWRP backups of target build

Boot into target

This should work as long as /efs and /radio haven't moved.
[Samsung Galaxy S (4G Model)] daothanhduy1996:
New build is up with newest Beanstalk 4.4.225 and my kernel changes - no LINARO yet.

P/s: seems like theme engine is implemented now - I haven't tested this build.
[Samsung Galaxy S (4G Model)] mataflakitas:
Dao what Rom this is best, benstalk vs Slimkat...:confused:
[Samsung Galaxy S (4G Model)] jeffsf:
The ROMs are different, not that one is "better" than the other. It is personal preference, to a great extent.
[Samsung Galaxy S (4G Model)] DragnzKlaw:
Confirming that theme engine works.
[Samsung Galaxy S (4G Model)] inimeg81:
Ive never gone back to stock first. I just flashed eriks proton2 kernel factory reset then wipe everything.. Install kk reboot factory reset wipe install kk.
[Samsung Galaxy S (4G Model)] inimeg81:
Someone corrected me the secgps.conf is under /etc/vendor/samsung-agps/
[Samsung Galaxy S (4G Model)] daothanhduy1996:
I said once in slimsaber thread that I would build a new build for beanstalk. But unfortunately I whack off the slimkat source, which has been the reference for slimsaber and beanstalk, that means I have to whack off the slimsaber and beanstalk, too and resynce everything again so it's gonna delay a bit, hopefully just 24 hours :).
[Samsung Galaxy S (4G Model)] caspboy:
this rom is awesome:D
[Samsung Galaxy S (4G Model)] DickyG:
After being on SlimSaber for a while, went back to this one...just seems to work better on my phone. Everything is working fine except:

1. Lockscreen wallpaper...can it be changed?

2. Text messaging by voice: That little microphone doesn't appear on the keyboard.

Anyone have any ideas on these two?

I really like the Halo feature.
[Samsung Galaxy S (4G Model)] graycow9:
Preferences

I much rather prefer this ROM over Slimkat, mostly because of features and Youtube video quality. However I do believe it is known that the camera is incomplete? I don't understand it, but when taking a video it records and even seems to have the correct size in file, but the video taken will freeze upon playing. /:

Great work though dao! Much appreciated :) :good:
[Samsung Galaxy S (4G Model)] inimeg81:
Install vplayer until camera probs are fixed