yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] RoboJoe:
Holding down menu is the equivalent of tapping the search button on a phone with a dedicated search button (versus long pressing the search button). So, if the app you're in has a search function, it will activate it instead of Google Now.
[Verizon Samsung Galaxy S III] Relentless D:
Yes, but he was talking about launching google now, not searching an app. I should has clarified that I hold down the menu button when in the launcher...not just any app.
[Verizon Samsung Galaxy S III] Tazer2death:
I have it set to open text search while holding down menu. And open google now if I hit home twice (or just once if I'm on the home screen). This can all be set up with Nova Launcher.
[Verizon Samsung Galaxy S III] eakrish:
Holding down menu also gives me my search box. Then I say google and it goes to google now.
[Verizon Samsung Galaxy S III] tu3218:
Is there any fix for the screen flicker due to the crt on/off animation? I know this problem could have existed when I flashed it but was just wondering if there is anything I can do to stop it. I tried turning auto brightness off, but it still does it.
[Verizon Samsung Galaxy S III] rehpyc:
Who wants to to change their battery style, clock position, notification transparency, etc.? I've been working along side beans to give you guys a system that will let you guys make parts of the ROM look the way you want. Head over to the link below for the download, and a big thanks go out to beans (obviously), scrosler, boynamedstacy, and gzsmooth.

Enjoy!

http://xdaforums.com/showthread.php?t=1863765
[Verizon Samsung Galaxy S III] JMink:
Sorry if I'm overlooking it...but where can we download old builds? I'm looking for build 9 specifically. Thanks

Sent from my unlocked SGS3...f**k you Verizon!
[Verizon Samsung Galaxy S III] goodwidp:
The link below is where I'd imagine they would be, but there's nothing listed so perhaps Beans removes them whenever a new build is posted. Hopefully him or someone else can provide more insight. Best of luck.

http://myandroidfiles.com/beanstown106/oldbuilds/
[Verizon Samsung Galaxy S III] WizeGuyDezignz:
Hey guys, I was wondering if I could get some help. This is my first time trying Beans ROM, so I downloaded build 10. I was coming from the latest Synergy nightly (R64 I believe) and I had IMO's latest 0.6 kernel on there. I am unlocked.

So I did a full wipe of everything and installed build 10 with all of my options picked. I am getting constant FC's and I can't open the Play Store without it crashing. I keep getting pop ups of a gmail FC and gapps FC. I've tried absolutely everything I can think of with no luck.

I've redownloaded the ROM, reinstalled multiple times, etc. Any suggestions?? I am completely confused on what can be wrong. I've never had an issue like this before.

Any help? Thanks!
[Verizon Samsung Galaxy S III] krbernier:
Smilley message shortcut says app not installed. But messaging works from contacts

Edit: fixed deleted shortcut and dragged a new one from app drawer and all is good
[Verizon Samsung Galaxy S III] tu3218:
Yeah this has happened for many. Its the result of a particular selection while in aroma that leads to this. I want to say that if you select Maps in aroma it does this. I'm trying to find the post that states this but haven't had luck. You can try it without selecting Maps though.
[Verizon Samsung Galaxy S III] mpetruzz:
I've been using v10 for a few days and have been experiencing one issue. Each time I get a notification telling me I have updates available my phone flashes blank and then comes back.

Not major but its been happening quite often the past day.
[Verizon Samsung Galaxy S III] jmaiman:
Force Close

Im also having this same problem of constant force closing. I flashed imo v.6 over the custom kernel for build 10 i dont know if that is whats causing this problem:(
[Verizon Samsung Galaxy S III] capt8210:
On beans custom 10
[Verizon Samsung Galaxy S III] RoboJoe:
I selected Maps, and don't have this problem. It's probably not that.
[Verizon Samsung Galaxy S III] Desertburn:
Beans v10

i have been using Beans versions 6,7,8,9,now 10.i love it, a few small glitches which were quickley fixed by reflashing again, BEANS IS BEST!
[Verizon Samsung Galaxy S III] Karl:
Can someone give me the MD5 you got :eek:
[Verizon Samsung Galaxy S III] mysterysauce:
This is for build 10

cd691bb5ca57d5fa65da1ea180c8309e
[Verizon Samsung Galaxy S III] JPD19:
Anyone having issues syncing Google contacts? All other Google sync services work, such as calendar, email, Picasa, etc. It has not worked for me since 8/26.
[Verizon Samsung Galaxy S III] WizeGuyDezignz:
I think I had to go into accounts and sync and unchecked and rechecked the contacts box and it worked.
[Verizon Samsung Galaxy S III] JPD19:
Tried that. Also went into app manager and force closed + cleared data without improvement.
[Verizon Samsung Galaxy S III] bhags8:
Hi, I just installed Build 10, I came from Build 9. What I did was wipe cache and dalvik, I then selected Apex Launcher. Ive never used this before because Im new to this. Anyways, after that I flashed the Aroma Installer from this link

http://xdaforums.com/showthread.php?t=1863765

Now, I boot up and notice I have no wallpaper and no Notification menu, I know this happens everytime you flash Beans ROM, so I try taking a screenshot BOTH ways and nothing happens. I even got a few texts and I still have no notification menu. Was I supposed to flash Aroma after Build 10 or does it come with it? And was I supposed to wipe cache/dalvik after installing Build 10, then installing Aroma? Is this a problem with Apex Launcher?

Man am I confused...
[Verizon Samsung Galaxy S III] dividebyzero:
You did it right. Wait and it'll fix itself. You can also launch the app that selects the notification widgets and sometimes that jump starts it. You can choose and combination of options you want and it should work.
[Verizon Samsung Galaxy S III] bhags8:
What app launches the notification widgets?
[Verizon Samsung Galaxy S III] dividebyzero:
Quick panel settings
[Verizon Samsung Galaxy S III] bhags8:
Yeah, its still not showing up... I cant change my wallpaper either. Not sure whats going on?

If I just want to go back to Build 10 without Aroma? How about do I do that?
[Verizon Samsung Galaxy S III] Tazer2death:
Backup and then try to dirty flash beans.

Usually works when I try to undo themes I flashed.
[Verizon Samsung Galaxy S III] bhags8:
Ok. well I just factory restored, wiped data, cache, dalvik, and then installed Beans 10 again, and restored my stuff with TB. Is that a good way to do it or does that mess anything up?

Also, this time I installed Beans without Apex Launcher, can I just installed Apex Launcher from Play Store or will that not be compatible with my version?

And now should I try installing Aroma again? if so, what steps should I take?

Thanks dudes
[Verizon Samsung Galaxy S III] Tazer2death:
That will definitely get rid of the extra aroma stuff. Apex Launcher from Play store should work fine. I would do a nandroid backup in CWM before flashing aroma, that way if it messes up, you can just go back no problem by restoring your backup.
[Verizon Samsung Galaxy S III] bhags8:
Good plan. Hey, how many of those nandroids can you store? And is there a way I can move them to my external or somewhere else, I would think they take up alot of space... Oh and how do I know if Aroma is working? Like where do I go to mess with Aroma?
[Verizon Samsung Galaxy S III] Tazer2death:
You can store as many as you fit. Choose the option to back up to External SD card if you can. You can always delete old backups as well. I try to keep less than 3 at a time, and they actually don't take up that much. I think I read somewhere that common backup files are only stored once to save space with CWM.

You can only deal with aroma when you flash it, you can select the settings. It will be obvious if all of the settings are as you set them after flashing it that it worked. If you want to change the settings, just flash the zip again and select them.
[Verizon Samsung Galaxy S III] bsbabcock:
I'm having a time with the current build.. I'm a DX guy so I'm learning a new phone, unlocked loader etc..

Flashed in CWM on unlocked device and currently I have no status bar, no wallpaper (black), and no wifi (it will not toggle).

LED indicates I have some notification (probably gmail) but that did not force notification bar to work.

Downloading again, to try to re-flash, but certainly open for suggestions/help.. please. :crying:

Kernel says 3.0.41 lean kernel 0.4..

Build says Custom Stock Build 10..

Android version 4.0.4

What makes it bad is my nandroid turned out to be corrupt, or I'd run back to stock and count my blessings, but at this point I'm all in.
[Verizon Samsung Galaxy S III] droidstyle:
wipe data in cwm.
[Verizon Samsung Galaxy S III] bsbabcock:
Do you mean prior to flashing or now?

I did wipe all before flashing the rom including dalvik system data cache and battery stats.

---------- Post added at 11:05 AM ---------- Previous post was at 10:45 AM ----------

I wiped again in cwm but no fix.
[Verizon Samsung Galaxy S III] Relentless D:
You should try reading the thread of the rom you are posting. I know there are a ton of pages but as a general rule you should read at least the last 10-15 pages to see what problems people are having...

I don't mean to sound like a jerk but knowledge is power, my friend.

The short answer is to force a screenshot by swiping the screen, this will bring it back.
[Verizon Samsung Galaxy S III] luke1333:
Where is the boot animation located??
[Verizon Samsung Galaxy S III] schu9120:
Bootanimation.zip is in system/media.

Fun fact # 1

You can also place a bootanimation.zip in data/local and it will override the one in system/ media.

Sent from my GS³
[Verizon Samsung Galaxy S III] akimity:
When a Rom gets over 50 pages of comments it should turn into a sub forum. It's next to impossible to keep up with 190 pages of info.
[Verizon Samsung Galaxy S III] luke1333:
It isn't a boot animation.zip it's something different
[Verizon Samsung Galaxy S III] Relentless D:
If you are coming in to it late just read the last 15-20 pages, it won't take that long. All the earlier stuff will typically involve the older builds and isn't necessarily relevant to the current release.
[Verizon Samsung Galaxy S III] JPD19:
android.process.acore ERROR

Sorry to bring this topic back up again but still having issues with Google Contacts. I went into apps manager and cleared data/FC the following: contacts, contact storage, and google contact sync. When I did that, it obviously wiped all of my contact data. Interestingly, google contacts started to sync, but it only synced what was already available on the google server. I've had issues syncing contacts since 8/26, and I've had about 10 new contacts added to my phone that has not yet synced. Since I backed up my contacts using GO Contacts EX, I restored all of my contacts so that the 10 new contacts were available on my phone again. I then tried to resync with google, and I kept getting the error from android.process.acore, and the restored contact list did not sync. I read the Hobart's post on rootzwiki saying I have to format data and cache in mounts and storage as well as normal wipes and reflash. Is this honestly the only way to fix this? (some of you are thinking, it's just 10 contacts...just create them on the google server...which I have considered, but that doesn't fix the issue I'm having)

I'd appreciate any input!
[Verizon Samsung Galaxy S III] 1ManWolfePack:
I answered you on Rootz :)
[Verizon Samsung Galaxy S III] JPD19:
For those of you having similar issues, I found out that GO Contacts EX seems to be incompatible with Beans 9 and possibly 10. For more details, you may PM me or read the thread in Rootzwiki. Thanks to those who may have been brainstorming to solve this issue.
[Verizon Samsung Galaxy S III] vaffanculo403:
Is there any way to go back to the stock theme from the ICS/JB theme if we wanted?
[Verizon Samsung Galaxy S III] bsbabcock:
Thanks for the advice. To let you know I did. I, as a rule, wouldn't post until I exhausted searching the thread. I should have mentioned the screenshot palm swipe didn't restore or function at all. I doublchecked motion functions are on.

So at this point as I'm trying to get more time to myself to work it out, I hope to find the best S3 equivalent of an SBF in doid x terms to get back to stock since my CWM backup let me down.

Luckily my wife brought the laptop home as it appears the Mac running OSX won't do so well.
[Verizon Samsung Galaxy S III] vaffanculo403:
So I just flashed this ROM and I do not have a status bar at the top. Any ideas?
[Verizon Samsung Galaxy S III] mpetruzz:
1) do a search

2) reboot your phone
[Verizon Samsung Galaxy S III] vaffanculo403:
1. Don't be a smart ass

2. I'm on my 4th reboot now....

3. Still no status bar
[Verizon Samsung Galaxy S III] flameinthefire:
send ur self a text and it will bring back ur status bar
[Verizon Samsung Galaxy S III] bsbabcock:
We may (or may not) have the same issue..

Do you have black wallpaper that won't change?

Does your palm-swipe screenshot not work?

In my case, I thought it was just a bad download or bad flash, but reflashing with re-downloaded zip from ext SD multiple times and no fix.
[Verizon Samsung Galaxy S III] vaffanculo403:
Reinstalled. Wiped everything. Restated 6 times now. No status bar...

Going back to CM10...

---------- Post added at 05:22 PM ---------- Previous post was at 05:21 PM ----------

Dunno about the screen shot but yea every thing else is the same as you...
[Verizon Samsung Galaxy S III] mpetruzz:
Jeez bro don't be so sensitive;)
[Verizon Samsung Galaxy S III] schu9120:
Were you thinking of the stock Samsungboot.qmg ?

Sent from my GS³
[Verizon Samsung Galaxy S III] jmill75:
Never got notification to come up either so I had to ditch the rom.....
[Verizon Samsung Galaxy S III] afmracer6:
I fought the status bar thing for a couple of days. Finally fixed it by doing all touchwiz on aroma stuff did a screenshot by holding home button and power button at the same time for 5 seconds.

As soon as screenshot happened the status bar came back. BOOM!
[Verizon Samsung Galaxy S III] bhags8:
lol, maybe you should search, me and another guy had the same problem pages ago, and screenshot DOES NOT WORK. I actually flashed back without Aroma because we couldnt find out how to fix.

---------- Post added at 07:56 PM ---------- Previous post was at 07:53 PM ----------

You're lucky, I had the same problem (black wallpaper, no status bar, wouldnt come up with notification and BOTH screenshots wouldnt work). I went to Build 10 without Apex and didnt install Aroma this time, Ive been contemplating trying to install Aroma again.
[Verizon Samsung Galaxy S III] Stryker1297:
did a search and came up with nothing. anyone having issues with ktoonez kernel?
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
On the next update can you add the option to disable wake phone with incoming messages plz
[Verizon Samsung Galaxy S III] djras111:
I also had several occurrences of the notification bar going away and then coming back (for no known reason).
[Verizon Samsung Galaxy S III] luke1333:
Yes cause the new boot animation does nothing it's the Samsung boot right?
[Verizon Samsung Galaxy S III] didda:
Play store FCs constantly, or network error, or Wifi grayed, or Home button fails, or no status bar.

None of the fixes work.

5 reinstalls, different selections in Aroma, nothing changes. Even tried installing Gapps behind Bean. No dice.

Screw this ROM.
[Verizon Samsung Galaxy S III] WizeGuyDezignz:
Try not selecting maps in aroma. That solved all of those problems for me.

And to say screw this rom is extremely disrespectful. Nobody forced you to flash it and their are other roms available. Sounds like you need to move on.
[Verizon Samsung Galaxy S III] fix-this!:
this rom is awesome, great battery life too. do you plan on updating this to jb once it comes out?
[Verizon Samsung Galaxy S III] Tazer2death:
Nothing but stability on my end. I feel sorry for everyone that can't get this ROM to work right because it is a really great ROM, lots of options and for me runs very smooth and conservative with the 0.6 Kernel.
[Verizon Samsung Galaxy S III] chrisngrod:
Then we should all stop feeding the troll. "sounds more like user error on your end!" Only a little more subtle there. Back on topic then.
[Verizon Samsung Galaxy S III] KennyG123:
Thread cleaned

Troll warned

Friendly Neighborhood Moderator
[Verizon Samsung Galaxy S III] droidstyle:
ok
[Verizon Samsung Galaxy S III] Vagitarian:
It's unfortunate that a few people are having issues with this ROM. Been running Beans 10 since its release and haven't had any issues. I changed using touchwiz options because I use go launcher. Is it possible that people running into problems are reporting system data through TB by mistake? With force close problem are you running Fix Permissions first? And for those that haven't yet check out the theme installer for this ROM. I enjoy having the circle battery icon and being able to customize the transparency on the notification drop down. Great work everyone evolved. Best ROM I've used so far.
[Verizon Samsung Galaxy S III] anrichardson:
I am one that has no issues. I haven't read the ones that are having issues, are they unlocked or locked. I wonder if that has anything to do with issues.

I am unlocked, so I don't know the install procedures for who is locked. Does aroma have the the same options on install as the unlocked besides the kernel?
[Verizon Samsung Galaxy S III] luke1333:
I have had a few issues with beans 10 so I went back to 9. Great Rom and will probably try beans 10 later tonight or wait for 11!
[Verizon Samsung Galaxy S III] vaffanculo403:
I'll try again once the status bar thing is fixed...
[Verizon Samsung Galaxy S III] bsbabcock:
I hadn't retried the rom yet but I suspect the reason my install borked was because I wasnt flashing over stock but over MIUI alpha. Since I found myself wiped in CWM earlier and thought I had beans on sd but dudnt, then having trouble restoring a backup I flashed what i had which was the miui alpha downloaded by chance. So in effort to get back to a stock rom I went to Beans 10 from there.

What i shoulda done hindsight being 20/20:

1. Make sure i had the zip or

2. Unmount SD, plug into Mac and get the zip then mount back in phone

.. I guess.

So I may have to flash this one again just to redeem myself.
[Verizon Samsung Galaxy S III] anrichardson:
Another thing people could try if you are not dirty flashing, is to do a factory reset before ever leaving recovery. That's if you are doing a clean install. I have yet have any of this issues that users are having.
[Verizon Samsung Galaxy S III] DroidmanDan:
I would also like this as an option if possible. Thanks! :)
[Verizon Samsung Galaxy S III] RoboJoe:
As a general rule of thumb, always do a clean install before coming to the forums with an issue. I almost always perform a dirty install, because I'm lazy and impatient, but if there are any issues I reflash clean to see if that resolves them before I post.
[Verizon Samsung Galaxy S III] sbattosai:
FYI, Imoseyon lean kernel v0.7 available on rootz...
[Verizon Samsung Galaxy S III] lespaul0143:
So, my Facebook contact pictures won't appear in contacts or my messages. Any ideas why?

Sent from my (now amazing) Verizon Galaxy SIII
[Verizon Samsung Galaxy S III] RoboJoe:
Try clearing cache, or if that fails, all data for the Facebook app.
[Verizon Samsung Galaxy S III] lespaul0143:
That worked. Thanks. I'm not sure why I didn't think of doing that. Anyway, thanks a bunch.
[Verizon Samsung Galaxy S III] kench33:
Anyone know how to get blinking leds for texts to work?
[Verizon Samsung Galaxy S III] zombieplanalpha:
Light flow app. You can enable missed events in settings/led indicator but I don't think it blinks. Been using light flow since my Nexus.

Luck favors the prepared... Get a plan
[Verizon Samsung Galaxy S III] Hanoverfiste:
This just started this morning unplugged at about 6am and by 6:30 I was down to 50% battery. I just installed better battery stats what exactly should i be looking for after I charge my battery back up?
[Verizon Samsung Galaxy S III] RoboJoe:
Look for what it says is using the most juice. If it's something you don't really care about, uninstall it. If it's something that you do care about, see if you can minimize the juice it uses by wiping data for the app, or if it polls for data, increase the time between polls.

Wash; rinse; repeat until you have an acceptable battery life by your standards.

Edit: Also, you can install an app that controls your CPU and have it under clock the cpu when your screen is off, or all the time if you don't really do cpu intense operations. (games, etc)
[Verizon Samsung Galaxy S III] kench33:
Is there like a tutorial? When I used it last time it wasn't working at all
[Verizon Samsung Galaxy S III] swordphsh:
It's pretty straight forward to use. You'll have to make sure one of the two S3 modes are enabled in settings, for root or no-root. Most colors don't blink, but there is a pulsing blue and a flashing red option, although, they don't always work for me.
[Verizon Samsung Galaxy S III] i5aac:
Left beans for a short stint with clean Rom 2.0 (also good!). I came back to this to see what all the fuss was about (notification bar, maps, etc)

After flashing this without maps, I can't find a single issue! First boot had no notification bar, but first incoming...whatever...brought it back.

Fwiw, I always flash aroma Roms twice, the same way, after clearing cache and dalvik...works every time!
[Verizon Samsung Galaxy S III] JPD19:
What's the benefit in flashing twice? Is this just your personal good luck ritual?
[Verizon Samsung Galaxy S III] i5aac:
Yes, this is my personal ritual...it just works!
[Verizon Samsung Galaxy S III] JPD19:
In preparation for Build 11

So some people had issues flashing build 10, and it may be due to incomplete wipe as some of you have mentioned. People have suggested formating system in addition to the usual wiping of data, cashe, and dalvik. There are many options to "clean" your ROM/storage using CWM and TWRP:

CWM 6.0.1.2

-- Wipe data/factory reset

-- Wipe cashe partition

-- Mounts and storage --> format system, data, cashe, sdcard, external_sd

-- Advanced --> wipe dalvik cashe

TWRP 2.2.2.0

-- Wipe --> cashe, dalvik cashe, factory reset, system, external storage, internal storage, format data

What's confusing is that CWM and TWRP are not consistent in naming the certain types of "cleaning" methods. For an example, TWRP has "system" under "wipe," but CWM has "format system" under "mounts and storage" and no option for "system" under "wipe" category...which raises the question, is there a difference between wiping system and formating system? More importantly (since mentioned in threads over and over again), I'm also not quite sure what the difference is between wiping data and formating data, let alone which order you should perform them if you need to do both.

To prevent google apps FCs with Build 11, I was wondering if someone could comment on the questions raised above so that we have the cleanest of all internal storage prior to flashing BeansROM.

Thanks!

*** same msg posted in Rootzwiki ***
[Verizon Samsung Galaxy S III] Relentless D:
Never used twrp so I can't really comment on it but to answer your question about the difference between wiping system and formatting system in cwm, wiping system deletes user data but leaves the system intact (Resetting to rom defaults) and formatting system essentially deletes the user data AND the rom.
[Verizon Samsung Galaxy S III] JPD19:
So if you format system and don't flash a new ROM, what happens? Your phone will hard brick because you essentially have an empty internal storage?
[Verizon Samsung Galaxy S III] RoboJoe:
Your phone won't boot without system. If you've unlocked your bootloader and have installed a custom recovery, you can get into recovery by pressing power + volume up + home until the Samsung logo appears, where you can flash something to fix the lack-of-a-system problem.

It's very hard to brick a phone with an unlocked bootloader.