yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 4 Unified Development] chrisc93:
Just to let you know, I'm still working on this build.

I get an alert saying "Unfortunately, the process com.android.Phone has stopped." with the latest build.

I did a full wipe so I don't know what's causing this.

Anyways, I am rebuilding it as I type this, so hopefully that problem will be gone.
[Samsung Galaxy S 4 Unified Development] jellymonster442:
Loving all the features, and not too many FC's, but there's a problem when I make a phone call, it doesn't go through, then FC. Once that gets fixed this will be the perfect ROM.
[Samsung Galaxy S 4 Unified Development] chrisc93:
As of now, the only bugs I know of are the BT and headset phone audio.

I was hoping that today's build would fix that, but when I boot it up, I get an error saying, "the process com.android.phone has stopped."

I have asked around to see if I can get any help with this issue. But for now, I'll just keep the 5/31 build up because it seems to be working fine.
[Samsung Galaxy S 4 Unified Development] chrisc93:
Can you provide a logcat?

I just tested the phone, and it works great...no FC!

What apps were FC on you?

I suggest doing a complete wipe (format data and cache too).
[Samsung Galaxy S 4 Unified Development] jellymonster442:
Really? Whenever I would make a call, I would not be able to hear the other person, and they would not be able to hear me, and then after they hang up it would freeze, and after a couple seconds tell me that the phone had stopped working. I'm going to go ahead and do a complete wipe and flash the rom again. Hopefully it works. :)

Also, it only happened twice when I was on the ROM, but randomly while I was using it, my phone would say, "Unfortunately, the process com.android.Phone has stopped." I just pressed ok, and then restarted my phone and it would work.

I'm going to try and reflash the ROM, hopefully it works this time. :)
[Samsung Galaxy S 4 Unified Development] chrisc93:
Were you ever able to make a phone call?
[Samsung Galaxy S 4 Unified Development] jellymonster442:
No, not once.

I wiped data, cache, dalvik, flashed the ROM. Not one FC. Phone calls going and coming. Best ROM I've ever used! :)
[Samsung Galaxy S 4 Unified Development] chrisc93:
Sweet! Glad I could help you out.

Still working on the BT and headset audio. It will be perfect with those completed ;)
[Samsung Galaxy S 4 Unified Development] tavito05:
Used it on the infuse since day one and just handed it over to my dad and he loves it !

Can't wait to see this here ! Scott is an amazing dev and thank you for taking on this ROM ! Is a very high scale that Scott has created with this ROM !
[Samsung Galaxy S 4 Unified Development] sholsten:
BeanStalk refuses to install on my SGH-I337. It fails as soon as it executes to install using the Loki CWM 1.035
[Samsung Galaxy S 4 Unified Development] aturbs:
For some reason I can't get the phone to boot up when I flash this rom with the 4.3 gapps. It sits on the Galaxy S4 splash screen until I give up and boot back up into recovery. I've tried restoring the 4.2.2 Beanstalk nandroid I made, but after reaching about 75% of the restore, it says restore failed. i'm on TWRP. I suspect it might have something to do with mounts, but I'm not entirely sure.

Is anybody else experiencing this or have experienced this? I need some help getting it to restore.

EDIT:

what i did to get back to 4.2.2 is I booted into recovery and instead of just factory resetting I did a data wipe too (might be called something else I can't remember right now). Be careful doing this as it will wipe your internal SD card. Luckily I had all my backups and stuff to flash on my external SD card so I flashed them and I booted up to 4.2.2. I am now going to try getting to 4.3. Wish me luck!

EDIT EDIT:

I successfully got to 4.3 but upon reboot I got stuck on the splash screen. Now back on 4.2.2
[Samsung Galaxy S 4 Unified Development] suchevent:
i'm also seeing boot issues on my i337m (canadian). after installing the 4.3 rom, it boots fine. but if i try rebooting the phone, it just hangs at the splash screen. it looks like several others are having similar issues. i've tried installing the rom with three different recoveries (CWM 6.0.3.6, TWRP 2.6, and 2.5) and the problem persists. this leads me to think that it is a rom issue and not a recovery issue. i just wanted to share.
[Samsung Galaxy S 4 Unified Development] Little Bigboy:
i was having that issue too until i flashed the supersu zip i found here

http://download.chainfire.eu/345/SuperSU/UPDATE-SuperSU-v1.51.zip
[Samsung Galaxy S 4 Unified Development] suchevent:
thanks. i will try this.

EDIT: tried without success. reverting to the 4.2.2 rom for now :(
[Samsung Galaxy S 4 Unified Development] Little Bigboy:
My latest battery stats running ktoonz stock
[Samsung Galaxy S 4 Unified Development] gordopa1:
I found this solution in the CM 10.2 thread:

I found a solution in case anyone else has this issue

To fix this issue, set TitaniumBackup to use the legacy path. The easiest way to do this is to go into TitaniumBackup, press "Menu" and then "Preferences". "Backup folder location" a bit down and click it. Click "DETECT!" and TitaniumBackup will ask you where to scan for backup locations. It's very important that you here choose to scan your whole device and not just the SD card.

After scanning is complete, you might as in my case see that TitaniumBackup presents two paths that seem almost identical (in fact they sort of are). Choose the path that has the string /legacy/ in it, in my case it is /storage/emulated/legacy/TitaniumBackup — which should replace a path similar to /storage/emulated/0/TitaniumBackup.

After TitaniumBackup has been reconfigured to use the legacy path, restoring apps will work as normal. Thanks to necropuppy for this solution.
[Samsung Galaxy S 4 Unified Development] jaythaovadose:
Anyway to change the lock screen challenge icon from the beanstalk to Tue original lock?
[Samsung Galaxy S 4 Unified Development] Soup_Nazi:
You can use custom rings if you want by using zipthemer, tons of custom ones out there.
[Samsung Galaxy S 4 Unified Development] JDOT87:
i flash this rom but my asop keyboard keeps forcing closing ?any idea anybody?:confused:

in fact everything force close
[Samsung Galaxy S 4 Unified Development] Soup_Nazi:
Did you follow the OP instructions? Did you flash the correct GApps? Some more info is needed here... Keyboard is working flawlessly for me, everything is for that matter.
[Samsung Galaxy S 4 Unified Development] cogcaviz24:
I had the AOSP keyboard issue as well. I loaded slimbean gapps as suggested. To fix it, well more of a work around, I loaded the Google keyboard apk on my SD card from my PC. Popped the SD card in my phone, skipped the setup and installed the apk, then setup my Google account
[Samsung Galaxy S 4 Unified Development] chrisc93:
As an alternative, you can download the stock AOSP keyboard from the play store. That's what I did anyways. I'll try to find a better gapps package for the next release.
[Samsung Galaxy S 4 Unified Development] JDOT87:
Yes I did every like the the op said but my keyboard kept force closing and some other app too like when I go to my contacts it force close
[Samsung Galaxy S 4 Unified Development] Soup_Nazi:
Did you use GApps from the op?
[Samsung Galaxy S 4 Unified Development] sholsten:
Mine has the same issue, but every 4.3 & 4.2.2 10.2 has some kind of issue to keep me from using them.
[Samsung Galaxy S 4 Unified Development] mrsexypants:
I used this gapps i didn't have any problems...

http://goo.im/gapps/gapps-jb-20130813-signed.zip
[Samsung Galaxy S 4 Unified Development] matty1whit:
Is there a setting that I'm missing to shut off the pull from left or right on the notification bar to show you toggles or notifications??
[Samsung Galaxy S 4 Unified Development] cinnabar:
I'll be coming from Task650(4.2.2) using KTweaker and Ktoonsez's recommended settings. I can currently get about 12-13 hrs of use before it even gets to 50% (BTW my On time is usually around 2-3 hrs). Do you all get similar results on this ROM? I saw someone had around 15hrs which wasn't very promising to me.
[Samsung Galaxy S 4 Unified Development] aturbs:
I know you probably don't want to hear this, but the best way to figure it the answer is to just try it out yourself. If you don't like the result, switch back. simply as that :)
[Samsung Galaxy S 4 Unified Development] cinnabar:
...OK :o lol
[Samsung Galaxy S 4 Unified Development] aturbs:
EDIT: My HDMI cable doesn't work so I was probably wrong when I said HDMI is broken.
[Samsung Galaxy S 4 Unified Development] stingdude:
Anyone know why the PNG icon for messaging is smaller than the rest?
[Samsung Galaxy S 4 Unified Development] Little Bigboy:
Sounds like the messaging app doesn't even lift
[Samsung Galaxy S 4 Unified Development] hartford:
Cannot save APN info when creating one (default install show no APNS at all). Anyone experience this?
[Samsung Galaxy S 4 Unified Development] stingdude:
I have not, just making sure, did you do a full wipe or did you dirty flash?
[Samsung Galaxy S 4 Unified Development] mrsexypants:
Anyone figure out how to get Torch to stop FCing?
[Samsung Galaxy S 4 Unified Development] hartford:
Yes.. full wipe of everything and flash. Everytime I create the APN and choose save, it's gone.
[Samsung Galaxy S 4 Unified Development] stingdude:
faulty APN maybe? What APN are you trying/ what's your service provider?
[Samsung Galaxy S 4 Unified Development] hartford:
AT&T... same APN settings I've used on lots of other roms ... ATT LTE. I know my settings are correct.
[Samsung Galaxy S 4 Unified Development] wally3614:
Please please merge this on new build !! http://review.cyanogenmod.org/#/c/48398/
[Samsung Galaxy S 4 Unified Development] stingdude:
Why don't you merge it, if its so easy to do?
[Samsung Galaxy S 4 Unified Development] CamFlawless:
KT's recent kernel builds solved the FCs for me.
[Samsung Galaxy S 4 Unified Development] wally3614:
R u being serious...? Think u need to step back a second and evaluate what I typed and what you read and what you typed and why you typed it and what you think you were trying to accomplish by typing what you typed....
[Samsung Galaxy S 4 Unified Development] stingdude:
The fact that you can't type the word "you" or "are" out explains to me that you don't understand that the person who has this ROM for the Galaxy S4 ports it from the Samsung infuse, he doesn't create or merge the code, it be great if he could do it, since I know he can, but it would also be great if other people would help him, that's why I wrote what I did, because you made it seem like it was the easiest thing to do.
[Samsung Galaxy S 4 Unified Development] wally3614:
The fact that you read *please please* as assuming something is simple explains a lot..:) this is too childish...peace...
[Samsung Galaxy S 4 Unified Development] stingdude:
I wasn't trying to come off like that, I was just making a simple suggestion
[Samsung Galaxy S 4 Unified Development] chrisc93:
Haha, I saw that last night. I'm running it now and it works like a charm! I'll try to get a new build up tonight.
[Samsung Galaxy S 4 Unified Development] ChuckDaEngineer:
Bless your heart. Way to stay above the fray.
[Samsung Galaxy S 4 Unified Development] Little Bigboy:
ive seen you posting this everywhere, what exactly is this ? is this the call issue where you cant hear the other party on the other end or is this a headphone jack thing where it only matters if you use the headphone jack ?
[Samsung Galaxy S 4 Unified Development] stingdude:
Any idea on the messaging PNG? Jw
[Samsung Galaxy S 4 Unified Development] wally3614:
Well on 4.3 the mute call issue seems to have dissapeared but when on wired headphones it uses the phone mic on calls instead of headset mic, this merge from CM fixes it...meaning for me at least finally full functioning ROM action bam! Lol
[Samsung Galaxy S 4 Unified Development] stingdude:
Anyone else keep checking back here for the update? I think I'm a flashaholic
[Samsung Galaxy S 4 Unified Development] chrisc93:
Been busy lately. Here is the build

Beanstalk 4.3.00
[Samsung Galaxy S 4 Unified Development] wally3614:
Thanks bro...DL..headset mic still holding?
[Samsung Galaxy S 4 Unified Development] stingdude:
Its all good man, we all have lives
[Samsung Galaxy S 4 Unified Development] CamFlawless:
Thanks for the frequent and super solid builds! :D:thumbup:

Also, your download speeds are excellent!
[Samsung Galaxy S 4 Unified Development] wally3614:
Running solid as fuggn rocks! Thanks bro...first complete aosp ROM on xda imo

Edit: so far only thing is Torch FCS won't work from home screen nor lock screen
[Samsung Galaxy S 4 Unified Development] chinesestunna:
Can we flash this over CM10.2 nightlies without formatting Data or is that a must? Seems like this is CM based so should work?
[Samsung Galaxy S 4 Unified Development] mbc663:
Didn't mean to hit your thanks.

Wipe cache and dalvik, u should be ok.

Just nandroid and try
[Samsung Galaxy S 4 Unified Development] chinesestunna:
Just did it, dirty flashed from CM10.2 nightly to BeanStalk4.3, only cleared Dalvik and Cache so far so good, everything seems just where I left them! thanks!
[Samsung Galaxy S 4 Unified Development] Locklear308:
Man this is so solid. Battery so far is insane! :D Man you rock!

The only thing I notice is stutter when opening apps sometimes. Speed isn't affected, it just looks strange. I presume this is just a bug?

Either way, thanks so much man.
[Samsung Galaxy S 4 Unified Development] 1weener:
Beanstalk 081813 running beautifully. The Torch not working is the only issue I've seen so far.
[Samsung Galaxy S 4 Unified Development] Little Bigboy:
What kernel are you rocking ?

---------- Post added at 12:34 AM ---------- Previous post was at 12:06 AM ----------

thanks man, this came in very useful after i flashed the new update
[Samsung Galaxy S 4 Unified Development] gordopa1:
Flashed the newest update after wiping cache and dalvik and noticed that a few of my apps had disappeared. When trying to reinstall from the play store I get a "missing shared libraries" error. Has anyone else seen this behavior?

Sent from the Galaxy
[Samsung Galaxy S 4 Unified Development] jaythaovadose:
Danm never seen that sorry
[Samsung Galaxy S 4 Unified Development] Locklear308:
Oh god, I just flashed Ktoonsez's kernel and the phone has just became garbage. Random reboots, it doesn't always boot fully. 1 out of 3 times to get it on. Lost cell service.

Wiped and reflashed WITHOUT that damn kernel, had horrible choppy lag and 3 second home button delay.

Wiped and flashed again and I am waiting to see in a few minutes.

God... My phone is ruined. I'm praying it comes back to it's old self after this last reboot.

What the hell did I do?
[Samsung Galaxy S 4 Unified Development] IEndz:
Did you format system, cache, and data? After full wipe and wipe cache and delvick cache after flashing hope that helpes
[Samsung Galaxy S 4 Unified Development] Locklear308:
...

10-4. She seems ok now...but I feel like something is off. Ugh, this is the first time in a long time flashing has failed me somehow
[Samsung Galaxy S 4 Unified Development] mbc663:
Don't blame ktoonsez. There are thousands of people running his builds with zero issues, reboots and DEFINITELY not cell issues. Don't post unless you fully wipe, especially if you're gonna come off like a young school girl complaining.
[Samsung Galaxy S 4 Unified Development] Locklear308:
What are you talking about? When did I say anything about Ktoonsez? I said nothing negative about him or his work.

I always fully wipe. That's the first rule of Rooting.

You need to check your attitude good sir. You make the good folk of XDA look like jerks. Cut out that tough guy nonsense. Don't post on xda if you are going to be a rude moron.

If your $600+ device suddenly go kaboom, after following all the same rules and procedures as you've done for years. You are going to flip out. That's a normal human response. Unless you just have too much money and no sense.

Honestly your post is just embarrassing.

Now, back to business.

Things seem to be back to normal now. So staying with just stock BeanStalk.

Everything is fast again, LTE works, calls work, no home lag.

Now if I could only figure out that strange random stutter on app opening and closing animations. So strange.

---------- Post added at 12:17 AM ---------- Previous post was at 12:15 AM ----------

I haven't seen that. Sounds like a good old wipe and reload is in order. I actually started downloading everything on my desktop and then moving them over via USB just to be 100% sure I've got the right files.

Do you get any strange random stutters on the app opening and closing animation?
[Samsung Galaxy S 4 Unified Development] 1weener:
Switched from KT's kernel to Chronic, and Torch works perfectly now. Beanstalk doesn't seem to have any faults that I can find, and I worked it pretty hard today. Thanks! :good:
[Samsung Galaxy S 4 Unified Development] wally3614:
Wth? Yeah confirmed crazy...KT just updated to 8/20 gonna try it...but yeah chronic good.:)

EDIT: 8/20 KT works with torch :)
[Samsung Galaxy S 4 Unified Development] egandt:
FYI missing shared labrary error on 8/18 build

Installed the 8/18 build from this thread. After installation I lost the following programs:

Paypal, Flight Tracker, Tasker, Secure Settings Helper, Digical and Google+

All of which refuse to install throwing a "Missing shared Library" error, as such I'm back on 8/12 for the moment.

ERIC
[Samsung Galaxy S 4 Unified Development] wally3614:
Rewipe and reflash
[Samsung Galaxy S 4 Unified Development] egandt:
I'd love to, but it normally costs me 3 to 5 hours doing so.

Even with a tibackup zip file to restore, there are still accounts, setting up AV, replacing lost files back on the SD card (this really is the worst can require 1 or 2 hours), repairing programs that have lost data such as games with large downloads, redoing all widgets (since the boxes show, but they are all blank) ... I'm sure I'm missing something as it can not be this difficult, but over the years this is what I've found is required everytime I wipe the device, any suggestions as to how to make it less painful?

Thanks,

ERIC
[Samsung Galaxy S 4 Unified Development] phidung3721:
Which Rom did you come from. If any different than beanstalk itself you have to do a full wipe. If you come from an earlier build try to reflash gapps. If problem still exists, then do a full wipe.
[Samsung Galaxy S 4 Unified Development] wally3614:
KT 8/20 is no where near as fluid as the new chronic for some reason...:)
[Samsung Galaxy S 4 Unified Development] Locklear308:
Chronic? Anything special about it combined with bean stalk? :D
[Samsung Galaxy S 4 Unified Development] wally3614:
Not sure just noticed it is all...been using KT then switched to chronic and notice right away
[Samsung Galaxy S 4 Unified Development] The Kurgan:
Was on 1.3 running very well, did a full wipe, flashed 4.3, flashed new KT, everything seemed good.

Camera seems to work better, but didn't like the loss of full settings menus.

I couldn't get the lock screen shortcuts to stay modified, kept reverting to default instantly.

And the headset Mic seemed to work, but I just had 2 mute calls happen and was forced to restore back to 1.3.

This happen to anyone else? Ideas?
[Samsung Galaxy S 4 Unified Development] wally3614:
Yup, I went back to try KT and had several muted calls then went back to Chronic Kernel and all is perfect
[Samsung Galaxy S 4 Unified Development] Locklear308:
It would appear that flashing any kernel kills my cell service, and rebooting causes a boot loop. Any ideas?
[Samsung Galaxy S 4 Unified Development] wally3614:
Yeah def sounds like a clean reflash is in order..try downloading the Chronic Kernel easy over sight make sure its the newest 4.3 Aosp version
[Samsung Galaxy S 4 Unified Development] Locklear308:
Did so again. reflashed and the results are the same.

This is very strange
[Samsung Galaxy S 4 Unified Development] wally3614:
What r u using to flash? I went back to TWRP 2.5.0.2 as 2.6 fubard a lot of stuff

xda bichiz!
[Samsung Galaxy S 4 Unified Development] 1weener:
Are you hitting the "save" button after setting your lockscreen shortcuts?

I'm using Chronickernel with Beanstalk and have had zero issues along with great performance and battery life with Intellidemand and Row. This kernel is light and fast. 6.2MB compared with 9.2MB for KTs. Don't get me wrong, I love KT's work, but Chronic is kicking A right now.
[Samsung Galaxy S 4 Unified Development] 21cdb:
I'm loving this ROM right now. I came from AOKP, but this has a lot more features. I can't get either KT or Chronic kernels to work, though. Both result in no cell signal and reboot issues. Not sure what's going on. There is some visual lag/stutter with the ROM, but I turned off transition animations and that helped. I did the same for AOKP to be fair. Not sure how anyone is getting these other kernels to work?
[Samsung Galaxy S 4 Unified Development] 1weener:
Are you wiping caches and fixing permissions in recovery?
[Samsung Galaxy S 4 Unified Development] 21cdb:
I wiped cache and dalvik, but I can't fix permissions since I'm on CWM 6.0.3.6 which no longer has the ability to fix permissions. I guess the CWM developer says it's just placebo these days.
[Samsung Galaxy S 4 Unified Development] JRW 28:
Having issues as well when flashing either KT or Chronic. Both result in loss of cell service but I'm losing my baseband when flashing as it says unknown after flashing either kernel?? I'm not doing anything different from what I always do so IDK what's going on?
[Samsung Galaxy S 4 Unified Development] 1weener:
Yeah, I was grasping at straws. So Beanstalk is working for you but you are unable to flash a different kernel? And you're sure that it's all 4.3?
[Samsung Galaxy S 4 Unified Development] 21cdb:
That's correct. I got the latest 4.3 builds for both. They both flash OK and boot up the first time with no problems, but there is no cell signal. Then when I try to reboot, they both get stuck on the boot animation.

Other than that Beanstalk is working great. Even the torch is working fine with the stock kernel.
[Samsung Galaxy S 4 Unified Development] 1weener:
Have you re-flashed with a clean install? And sometimes data or settings left on the internal SD from other ROMs can hose the function of one thing or another. If all else fails, try formatting your internal SD... just make sure you save your stuff first.
[Samsung Galaxy S 4 Unified Development] JRW 28:
Yea I came from a fresh install from it was first updated to 4.3. I only started having this issue after this last build. SD card is fine. Just never seen thus issue before of flashing a kernel making the baseband become unknown as if it's losing the radio upon flash.

Just flashed new 8/20 KT and everything is working now...was flashing 8/09 ...so who knows what's up ??
[Samsung Galaxy S 4 Unified Development] toxicpaulution:
I came back to this with no issues. I don't see what everyone's issues are about restoring your apps and such. If you don't want to reset everything or want to have to restore things then stick to stock. Don't complain about no wanting to do a full flash. It is always recommended to do a full wipe before installing. I have never dirty flashed and I have never ran into problems with roms I have tried. No one else is having the issues you are so that must mean it is on your end not the rom.
[Samsung Galaxy S 4 Unified Development] 1weener:
Agreed it is not the ROM, but that doesn't mean it's their fault... sometimes flashes just don't do right, clean or dirty.

Rule of thumb: If something works for everyone else, keep flashing until it works for you too! :good:
[Samsung Galaxy S 4 Unified Development] JRW 28:
Def not saying there is anything with the ROM, it was running great stock. Was just stating an issue when flashing other kernels. Seen something about maybe CM update on 8/18 and the kernels not being updated for it maybe causing the issues but IDK some things are just way over my head :p