yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] 7175:
I can confirm that this process, steps 1-4, definitely fixes the boot issues a few of us were having where any reboot clean or not gets stuck with a black screen or boot animation loop after the Google logo. I finally figured this out last night and I'm 90% sure these boot problems are from the way beanstalk needs to be installed. It doesn't have to do with settings or dirty installs. I've finally been able to boot/reboot beanstalk no boot loop!!!!!! Here are the steps I took:

0-boot to twrp recovery

1-superwipe

2-flash beanstalk.zip, flash gapps-2013-03-01 or aroma latest (I used this)

3-factory reset

4-restore backup (bootable or not, mine wasn't booting from 1.25)

5-****repeat step #2*****

6-wipe dalvik and cache

7-(optional) flash kernel, I'm using ASKP now (fancy base + working hotplug!! No SODs!!)

8-reboot, should get to lockscreen and be good to go

*Its important to flash gapps on top of ROM here along with most other ROMs currently. I don't know why but this fixes a lot of problems with quick settings not showing up, browser crashing, home button not working, etc. This is what I've figured out lately. You need gapps for keyboard swipe from latinime.lib, GV. If you hate gapps like me use aroma midnight to pick what you need and delete the rest after a successful boot.

Hope this helps. I really like this ROM, think it's the best out there, so I'm pretty ecstatic to get it working nice n tidy.

Big thanks to csking33 for the latest release, donation when i get my paycheck!! Privacy guard is great and works, tested it.
[Samsung Galaxy Nexus] NeverSeparate:
For the record, I was just offering info I recalled from somewhere else and stated that it may not apply to this case. I was trying to help. So bang your head all you want, but I wasn't asking a question that reading would have answered for me. I was citing something that I already read in hopes maybe it would be helpful. Good day to you sir, and thank you for such kindness that keeps us all wanting to come back :)

From high upon the Beanstalk
[Samsung Galaxy Nexus] geomonroe:
Hey man it's not that he is being untoward. You have to put yourself in his shoes. To respond to every q that has been covered in opening statements these devs would never have time to compile. You should try running Arch Linux and see what happens when you ask a q that's in the documentation!

John 3:16
[Samsung Galaxy Nexus] iconaw1:
So I don't see any Changelog information on the 20130701 build. Just wanted to make sure there is a deference between this and the 20130630 build I flashed the other day?
[Samsung Galaxy Nexus] NeverSeparate:
I was merely pointing out that I was the one quoted before the :banghead: when I didn't ask a question. I was trying to help answer one. I don't usually ask questions if I haven't looked. I know the rules. I help run a few threads that people ask the same things over and over, so I get it.

From high upon the Beanstalk
[Samsung Galaxy Nexus] csking33:
Change log is for the 7/1. The only difference between the two is dine fixes. You'll notice a couple things on the build you're on not working.
[Samsung Galaxy Nexus] Requills:
First of all, I'd like to say thank you for your work! Much appreciated.

Now to my question..I was wondering if it is possible to disable the status bar in the lockscreen? Perhaps I'm missing it, but it redraws coming from the lockscreen when having expanded desktop mode enabled.

Thank you!
[Samsung Galaxy Nexus] cd95yj:
Only question I have, my PRL is listed as a 53*** (3g) is this a bug or did my PRL get messed up during flashing? I have not done the *22899 update, and even after a forced PRL check it still lists as 53***.
[Samsung Galaxy Nexus] 7175:
Your phone most likely auto-called *22899 sometime after installation bootup. This happened for me but I cancelled since I already have the latest 53162. You're good man.
[Samsung Galaxy Nexus] xzero425x:
Random question, what's the stock clock speed for the phone? Like 1200ish?

Will with whatever kernel I'm using and putting it up to 1300ish make it run better or kill my battery fast
[Samsung Galaxy Nexus] cd95yj:
Every phone is different, some run great over clocked and some get unstable. Ultimately over clocking will use more battery though.
[Samsung Galaxy Nexus] 7175:
+1 It's much better to just force GPU rendering than overclock. The first thing I do when booting up a new ROM is pull down notifications, go down to developer settings, and check off force gpu rendering. My phones never slow even running 3d games uc'd to 900 MPU. This really helps save battery too at 307 or 384 GPU.

On another note I think Ive found another link to boot loops. I was messing around with some init.d customizations and found that adding a basic file system mount optimization script solved an infinite boot animation loop, or 9hr bootup as some people have reported. Just add this code to a new file in /system/etc/init.d, name it 00fsmounts or whatever so it's first alphabetically, and set permissions to 755 or rwxrxrx.

#!/system/bin/sh
# pulled from DHO's CNS-b5

# File System Mounts
#
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /dev
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /proc
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /sys
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nodev,data=writeback,barrier=0 -t auto /system
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /data
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /data/data
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /cache
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /acct
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /dev/pts
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /dev/cpuctl
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /mnt/asec
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /mnt/obb
busybox mount -o remount,noatime,nodiratime,discard,noauto_da_alloc,nosuid,nodev,data=writeback,barrier=0 -t auto /data/media/0

Edit: forgot to mention, this can replace the beanstalk stock 98tweaks init.d script in 1.261 which also works. This just has some extras and narrowed down a bootup issue.
[Samsung Galaxy Nexus] xzero425x:
Does clicking that box only help when playing games though or change the overall performance of the phone with daily use?
[Samsung Galaxy Nexus] Phazmos:
gui is handled by the gpu instead of cpu. I've been told by some devs that this can cause trouble with some apps. can't remember which, none that I use so I didn't bother remembering. this is also the first thing I do when loading a new rom along with setting animations to .5 so everything pops. for more 3d performance, not much more with like open gl 2.0 stuff, oc your gpu. newer Franco kernels, which I use exclusively, have gpu oc'd to 512mhz, and are supposed to run at 307mhz voltages, so battery drain is minimal. actually, I've gotten my best battery life with Franco, also best performance, bit I'm not a big 3d gamer on my phone, not with an nvidia 680 driving a 60 inch tv in my living room.
[Samsung Galaxy Nexus] dr_w:
bump..looking forward to the next build.
[Samsung Galaxy Nexus] Sheetzie03:
I seen in the Xlouder thread some1 was running a 7-4 version of this.( xlouder only works on 6-24 and b4, a user stated in his maguro 7-4 the mod now works as it normally should(

Afaik, 7-1 is the latest toro. If I'm missing something, please please fill me in bec I'd love to have it.

Ty

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] csking33:
7-1 is the latest. Syko built a few days after I did, after those fixes were merged. When Scott updates I will :)
[Samsung Galaxy Nexus] Sheetzie03:
Very good. Tyvm Much appreciated!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] dr_w:
Think the newest build to come will have the camera quick settings tile?

Sent from my Nexus Prime
[Samsung Galaxy Nexus] csking33:
Updated! :)

BeanStalk1.275-20130712-toro.zip - 178.30 MB

* New dialer

* Make contacts aware of blacklist settings

* Option to hangup and dialback from incallscreen

* Prompt when MMS storage is full

* Third part installing while HALO is active has been fixed

* Make shutdown receivers a priority

* Specify notification types for auto hide statusbar

* BeanStalk battery style and BeanStalk percent style. Thanks skyliner!

* Specify notification types for QS quick pulldown check

* Make Go to sleep tile/widget act just like the power button

* HALO - Keep apps in recents

* Recents RAM circle

* halo can save last position now

* activate qs and notifications toggle for navring

* Add an option to allow a (subtle) notification vibration during calls

* Add option to hide music controls in lockscreen

* add reset option to clock color and cleanup

* Changed the way that date format selector is shown

* Allow user to trigger a volume rescan

* Introduce Privacy Guard Manager

* Removed unnecesary tweaks and set some options at boot (similar to CM setup)

Now go throw some thanks Scotts way!! He's a hard working man.
[Samsung Galaxy Nexus] csking33:
FYI: Sound mods work again :)
[Samsung Galaxy Nexus] Sheetzie03:
Cool bra,

U told me you would update as soon as that other dude, couple days later, BOOM.

Haha thanks

Hope there are no major issues. Previous build ran great

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] csking33:
If you think the last build ran great then this will blow your mind hole. With askp kernel this build is flying.

And by the way "that other guy" is scott.hart.bti, the developer for this ROM, I simply hit a few buttons to build it then share with you guys. All credit goes to him.
[Samsung Galaxy Nexus] NeverSeparate:
I dirty flashed the update and all seemed OK except the dialer. I've stated the issue with the dialer before, but this is a bit different. Certain contacts wouldn't show up by spelling the name with t9. For example dispatch. I could hit every number to completely spell it but it wouldn't show up. If I just put in the phone number it would. I hit 3 to start (letter d) and could go through the whole list of names it pulled with a d, and dispatch isn't there. Oddly, it was there the first time. Then I selected it, and tried again, gone. Name first and t9 were enabled. I did wipe data on phone and contacts but no luck. I may try again with a clean install and see what happens. Just wanted to report my experience. Is the new dialer something about Scott built or is it coming from CM or AOSP? It looks familiar, like a 3rd party app I've seen somewhere but don't recall where?

Anyway thanks for the update. I thanked Scott too :)

From high upon the Beanstalk
[Samsung Galaxy Nexus] Sheetzie03:
HOLY ¢_¢^_|==<|<\¢\¢=¢×##-#-#!!! HAHA [MENTION=4265137]csking33[/MENTION] you weren't kidding even a little.

Thank you for doing this Yo [MENTION=4265137]csking33[/MENTION] I donate a lot simply because I don't have a lot of $. However, I will try my best to send you a little something, whatever I can, I will try.

I Havent yet been able to test battery life(I'm running ASPKv12) BUT Performance is sick fast. [MENTION=4265137]csking33[/MENTION], I know you mentioned the combo of this/ASPK kernel flying, it indeed is, but I would like to please ask you a few specifics regarding settings with the kernel

Ive been trying to follow the ASPK thread. Some were saying to run hot plug along with a few specific settings for the best battery life. In doing that, random reboots and freezes were happening, and I read others were experiencing the same.

So can you please tell me how you run your ASPK combined with this ROM, I don't need all of it, just the changes that you make that you think are most important. If screenshots are easier, I'm perfectly fine with that.

As always, I appreciate all of your work and help. Thank you.

Oh and please send a thank you to 'the other guy' Scott.Hart.bti for making this all possible.

Hope to hear from you soon [MENTION=4265137]csking33[/MENTION]. Keep up the great work and please don't ever abandoned toro :D

.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Phazmos:
fwiw - hotplug and gnex don't mix well. sods and hot boots are the signs. I tried askp, didn't like the performance, tried to go back to my usual Franco, and askp leftovers killed performance with Franco. had to wipe and start from scratch. hate when that happens!
[Samsung Galaxy Nexus] csking33:
I just tested what you were talking about and you're right, it's really strange. Sometimes people don't show up when you type it in right 0.o

I use Reno, deadline, interactivex. No multi core power saving, and bump the gpu up to 384mhz and put the min and min screen on to 192000.

And if you want to donate, give it to the devs. Scott, cyanogenmod team, aokp, I don't care. Just not me lol, like I said I just hit a few buttons and share, while trying to learn in the mean time.

I agree, however interactivex has been treating me very well with that kernel.
[Samsung Galaxy Nexus] NeverSeparate:
Yeah. It's odd. I would still love to find a work around (not another dialer) for the issue I mentioned before, but the dialer on this one broke the deal for me. I was learning to deal with the other issue by just typing an extra number or 2. I may mess with switching dialers, but the previous build was doing fine so I just went back for now. Is that going to be the 4.3 dialer? Or so we know?
[Samsung Galaxy Nexus] iconaw1:
any chance you could post on a mirror site. I have been trying to download the update for two days now and it times out every time. I have tried it on my phone and PC and both take like and hour to download and then errors out every time. notice only 43 downloads maybe other having the same problem?
[Samsung Galaxy Nexus] Phazmos:
wonder if cpu power saving set to 0 is helping. load balanced across all cores all the time = less idle time per core. no chance to shut a core down.
[Samsung Galaxy Nexus] nalanotae:
So far I'm loving this rom only issue have seen is trying to send a text it will not let me put the contact i want it to send to

Edit: OK so i figured it out. I was used to clicking up top to add recipient I just had to start typing and there it was. One thing i have noticed is my notification drawer has a gap at the bottom
[Samsung Galaxy Nexus] cd95yj:
Ok, weird thing happening on this build. Let me start by saying I did a clean install of the latest build. When I add a new app my phone freaks out. My battery shows a big red 0, my nav buttons disappear and my phone freezes up anywhere from 30 seconds to three minutes to where I can't get my touchscreen to work properly.

I've tried the Franco and Imoysen lean kernels and get the same result.

Any ideas?
[Samsung Galaxy Nexus] NeverSeparate:
Redownload and reflash . Did you format system too? If not you might try that? Maybe try a different Gapps? Just suggestions, may not help.

From high upon the Beanstalk
[Samsung Galaxy Nexus] mldiroff:
I have had this happen on a couple of ROMs, most recently on Axiom. I found that when I ran a theme it was worse. But to be honest, it led me to get rid of each of the ROMs that caused me that issue. Just frustrating.
[Samsung Galaxy Nexus] xzero425x:
Any reason my phone would die then when I turn it on my any dash is gone from the lockscreen and my pictures and ringtones disappeared :( I found most of them through the file explorer but the gallery is wiped
[Samsung Galaxy Nexus] csking33:
Try restarting the phone? Never heard of that happening, sorry.

Try Askp or ak kernel? My phone slows down a bit, but not nearly as bad as you described.
[Samsung Galaxy Nexus] iconaw1:
+1 happens to me occasionally.
[Samsung Galaxy Nexus] digitallure:
I'm on day 2and this rom is great. I did my "stress test" if you will. Played subway surfers for 10 minutes And no lag during or after. Like stock performance. I'm impressed!
[Samsung Galaxy Nexus] Sheetzie03:
Hey [MENTION=4265137]csking33[/MENTION]

Question brother, did you update to ASKP v13?

If so, what changes did you make in trickster?

Especially since interactiveX was removed

Thanks

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] csking33:
Yeah I updated, rocking ondemandplus for now, everything else is the same. Idle drain is a little high, but I still got 12 hours uptime with 2 hours screen on. Excited to see what ampheric can do with that kernel.
[Samsung Galaxy Nexus] Sheetzie03:
OK cool

Appreciate the reply

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] xzero425x:
Woo there's a new build coming! Was hoping it was a 4.3 one bahaha, this ROM gets better and better every build
[Samsung Galaxy Nexus] Sheetzie03:
How do you know there is a build coming???

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] NeverSeparate:
Scott put out an update, and csking is always soon to follow :)

From high upon the Beanstalk
[Samsung Galaxy Nexus] Sheetzie03:
Nice! I was just wondering if it was a definite. Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] 7175:
Awesome sauce, this is the #1 rom I'm looking forward to with 4.3. I've been tempted to flash the vanilla 4.3 betaish releases tweaks, but I'm just gonna sit back and enjoy my last days on 4.2.2 beanstalk. It's a good time to backup your sdcard, ROM apps, data, init.d, build.prop addons, etc in preparation for 4.3 as well.
[Samsung Galaxy Nexus] NeverSeparate:
I can't say it's definite as I'm not porting it, but I figure it will be done.

From high upon the Beanstalk
[Samsung Galaxy Nexus] csking33:
New build is here! BeanStalk1.300-20130725-toro.zip - 178.54 MB has been released. - Change log is as follows:

* More HALO changes and fixes.

* Make quiet hours options better. Ringer options and general fixes.

* Selinux support merged into frameworks/settings

* Added options for touchkey light duration (devs this requires overlay config in device side)

* Added fast charge tile and power widget (devs this requires overlay config in device side)

* Added external GPS options

* Option to automatically reply to sms while in quiet hours mode

* Numerous fixes and improvements throughout the build.

* Im sure i forgot alot of other things that ill probably think of eventually

Note: I haven't had time to flash so let me know how it goes.
[Samsung Galaxy Nexus] xzero425x:
Woooooo! So quick!

EDIT: the download is going waaaaay slow. And keeps failing for me :(
[Samsung Galaxy Nexus] csking33:
Problem is on your end.. no issues here :)
[Samsung Galaxy Nexus] xzero425x:
You were right! Rebooted my phone and got it, flashing meow
[Samsung Galaxy Nexus] NeverSeparate:
I'm downloading now, does this still have the new dialer? I tried replacing it in the previous build several times but it wouldn't work. I'm sure that was an error on my part.

From high upon the Beanstalk
[Samsung Galaxy Nexus] csking33:
Old dialer is back. Not sure if it's exactly the one you're looking for but it's not the newest one.
[Samsung Galaxy Nexus] NeverSeparate:
I'm OK with the previous one. I'm always hopeful it gets fixed to work like it used to, but I've learned to deal with it taking a few extra taps. I did see something about the 4.3 dialer having a predictive feature, which sounded to me like what I was used to. So maybe. Thanks for the reply and thanks for the update.

From high upon the Beanstalk
[Samsung Galaxy Nexus] dreitzell78:
Anyone else having trouble sending texts? I got one last night, but can't send this am. Wondering if it is just me. Thanks

Edit: OK, I can receive, but not send. I tried clearing data, also tried a different MMS apk I have. Not sure.
[Samsung Galaxy Nexus] elliot2112:
fast charge on/off is not in my list for quick tiles. anyone else missing it?
[Samsung Galaxy Nexus] jpin321:
Yup not there for me either. I just came here to post that up. Lol
[Samsung Galaxy Nexus] elliot2112:
fast charge on/off is not in my list for quick tiles. anyone else missing it?

---------- Post added at 10:43 AM ---------- Previous post was at 10:41 AM ----------

sorry didnt mean to post twice.
[Samsung Galaxy Nexus] 7175:
1.300 is running great on fancy r36 and ASKP B14, dirty'd 1.300 over 1.275 (over 1.261 over 1.24? over initial release). I encountered some boot loops/ infinite loading animation by just flashing 1.3, wiping dalvik/cache, fix.permissions, and then trying to boot up. I ended up just following this procedure I posted a few weeks ago, flashing askp 14, and I booted right up. Android...phone had one initial crash cause I was using the phone.apk from 1.261 on 1.275 (incompatible phobe settings), but it fixed itself.. cool stuff. No problems after that, multiple reboots have all been perfect. Phone and messaging app working great.. Btw, awesome job with the newly included Voice+ system app that allows you to use the default messaging app receive and send all texts through Google Voice!!

I definitely recommend using DHO's Gappz zip on top of this rom. Each apk is cherry picked down to the release version; no gallery-camera included;

extra apps included: Amazon store, adobe flash, terminal, tibu, file manager, apex launcher, Google voice, thinkfree doc viewer, Calendar, Chrome, Contacts Google sync adaptors.

So here's what's worked for me with three updates so far to avoid boot loops or infinite boot.animation/black screen:

0-boot to Phil's cwm touch recovery or TWRP, BACKUP system, data, efs (boot and cache if you want)

1-flash superwipe.zip OR do factory reset and wipe system, data, cache, dalvik cache

2-flash beanstalk.zip, flash tiny's no-cam gapps-2013-03-01 OR DHOs gapps

3-factory reset

4-restore backup from step #0 or an older one (bootable or not)

5-****repeat step #2***

6-(recommended) flash Fancy or ASKP kernel (ASKP has extra hotplug gov's, lots of TCP congestion algorithms, and dynamic fsync

7-wipe cache and dalvik cache

8-reboot, should get to lockscreen and be good to go

Troubleshooting in recovery if bootup still a problem (wipe dalvik/cache after each one, then try rebooting)

- fix permissions (make sure you mount system and data)

- flash fancy kernel or askp

- restore efs partition backup

- restore boot partition backup

- Mount system, open file manager or flash aroma 'live' file manager, go to /system/etc/init.d and delete all files

- replace build.prop file in /system with build.prop.orig in /system if there is one and set permissions to 0755, or -rwxr-xr-x

- Try pulling battery for about a minute, go to recovery, wipe dalvik/cache, fix permissions...reboot, pull batt if problem persists (repeat up to 5 times)

Just wanted to throw this back out there for anyone having problems. :)

*Its important to flash gapps on top of ROM here along with most other ROMs currently. I don't know why but this fixes a lot of problems with quick settings not showing up, browser crashing, home button not working, etc. This is what I've figured out lately. You need gapps for keyboard swipe from latinime.lib, GV. If you hate gapps like me use aroma midnight to pick what you need and delete the rest after a successful boot.
[Samsung Galaxy Nexus] NeverSeparate:
I dirty flashed this new build over the one 2 builds back and it gave me the new dialer. Are you sure it was reverted?

From high upon the Beanstalk