yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] MorphiousGX:
I

I don't like to argue. I don't like drama. I don't like to belittle anyone even if their question is noobish or stupid. I only gave snark and attitude because I got one. That particular member has been giving people attitude instead of helping or giving helpful answers. If he has nothing to add value then he should just keep to himself.

Reporting an issue even if only few people see it means it's an issue. As a software engineer we take any issue seriously. And No bad download here. Downloaded it over 10 times and checksum checks and same issue.

Anyway, the ROM is solid with the exception of the issue. If Beans chooses to fix it then great, if not, my solution is out there to help others.

Please if you have any comments about my post then PM me directly and keep it out if the thread
[Verizon Samsung Galaxy S III] jonathan413:
How do I get multi window to show all apps? Multi window app doesn't work
[Verizon Samsung Galaxy S III] Wrngway:
I didn't mean to imply tjat the note 2 camerea fc in hdr mode is a problem with the rom. I searched and didn't see it mentioned previously in this thread or in the i535 forums. Before anyone flashes it though it would be nice to know since it's included.

Thanks for the info though.
[Verizon Samsung Galaxy S III] james:
i am just guessing by the size of this rom that gapps are built in anyone know for sure
[Verizon Samsung Galaxy S III] Gutsman:
Yep, they're built in.
[Verizon Samsung Galaxy S III] james:
Thank you
[Verizon Samsung Galaxy S III] layvin1:
Thanks! This rom is pretty nice so far. I used twrp to install and it went flawlessly. I have always used apex launcher and made backups of everything so it was a quick switch around. You definitely improved some things and I enjoy the full control.....after all, isn't that the point. Keep up the good work!

---------- Post added at 04:23 PM ---------- Previous post was at 03:35 PM ----------

OK........I have a black and yellow case. My icons are custom and black and yellow. My keyboard is black and yellow......you get it. I used the xtheme engine and installed a yellow theme which worked on some more things......but.....I can't stand the Ics blue battery/wifi/lte and dial pad. can anyone help me change this ?

Sent from my SCH-I535 rocking beanstown build 19.
[Verizon Samsung Galaxy S III] james:
I have a question how do I get my backed up apps from rom tool box pro
[Verizon Samsung Galaxy S III] cr6:
Hey guys, just wanted to post an update regarding the "Talkback" issue that started a few months back.

As some of you may or may not know, there was an issue that started with the latest OS update and corresponding Beans build 17, where Talkback would automatically activate after a reboot, if you were running any number of "notification apps". (NoLED, DynamicNotifications, etc)

Well, I finally found a solution!

When using a notification app like the ones listed above, you're required to go into the accessibility menu in your system settings and turn the app on.

After much trial and error over the past couple of months, I recently discovered that if you simply don't turn on your notification app in your accessibility menu, your app will still work properly, but more importantly, Talkback WON'T enable itself after a reboot.

A few of us on the S3 forums have verified this works with most notification apps. So if you've experienced this yourself over the past couple of months, give this tip a try and see if it works for you too.

Good luck! :beer:

tap'n
[Verizon Samsung Galaxy S III] blkhrt13:
THANK YOOOOOUUU!!!!! lol
[Verizon Samsung Galaxy S III] hoodieNation:
No prob, glad that helped
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Nah, I have added them in my build.prop before via the "qemu.hw.mainkeys"

line but I do not have them currently. Adding that line (and rebooting) will reveal the soft keys but they'll be recent apps, home, and back I believe.

I use the Xposed MultiWindow apk from a Note or Note II thread and it works great. Been using that for multiple builds.
[Verizon Samsung Galaxy S III] SoCalSpecialist:
Beans...just wanted to say thanks for being prolly one of the last Dev's to keep TouchWiz alive for us!

seems like either everyone bounced to the S4 or all Dev's are focusing on 4.3

props tho! :good:
[Verizon Samsung Galaxy S III] supercell2000:
Do you use xposedmultiwindow or xposedmultiwindow240?
[Verizon Samsung Galaxy S III] madjokeer:
acore process again error when trying to sync contacts on build 19? tried clearing contacts and contact data in app manager but still no go.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
XposedMultiWindow.apk

See below. He's the one with the extended problem and a fix.
[Verizon Samsung Galaxy S III] madjokeer:
I just tired that, clean install, all settings to default when in aroma and still no go when syncing contact... very odd! :/
[Verizon Samsung Galaxy S III] WestOkid:
N2 HDR was FCC on previous versions too. That was the only reason I would select S3 can and give up N2 features.
[Verizon Samsung Galaxy S III] Hans5849:
Talkback got turned on on me. That was a horrible 10 minutes.
[Verizon Samsung Galaxy S III] Artimis:
Settings -> Custom Settings -> JellyBeans OTA/addons -> Settings -> Disable ROM auto-checks.

This works too without freezing any apks -- I'm a little late in the response but thought I'd point it out just in case.
[Verizon Samsung Galaxy S III] Juice3250:
Is there any way to remap the hard keys on this rom so that when I long press menu or home it opens google voice search? I'm currently on the tw 4x5 launcher. I see I can turn on long press menu to kill all. Also the double tap to open google now voice search doesn't work.
[Verizon Samsung Galaxy S III] nujackk:
why is that annoying a-- talkback not removed ?
[Verizon Samsung Galaxy S III] unhappybirthday:
Change the Long Press to Kill Button to Back and then the Menu button should revert to Google search.

Or hold down the Home button and flick upwards onto the "g" soft button that appears.
[Verizon Samsung Galaxy S III] BeansTown106:
agreed coming from aosp it is the best practice to wipe internal undoubtably

i strongly suggest runnung the firmware that the rom was made for aka bmf1

looking into a more customizable carrier label. will let u guys know and battery percentage is tied into the new battery picker mod

ya i made the afh download hours after i uploaded this time.. and ya i gotta put ur download for carrier label as a flashable zip in addon installer

ya absolutely murdered syscope it even says official binary in download mode :) big thanks to [MENTION=4041997]dwitherell[/MENTION] and [MENTION=220868]Ottoman[/MENTION]
[Verizon Samsung Galaxy S III] Jihoonie:
As far as something minor to look into for b20, i use some custom notification sounds that don't show up when i copy the file into system/media/audio/notification. Tried fixing permissions and cache wipe. I have no idea what would cause this not to work since I'm not even half a dev. I can figure out a few minor things on my own but this has me stumped.
[Verizon Samsung Galaxy S III] BeansTown106:
are they .ogg files? and did u make sure they have the same permissions as the other ones in the folder?
[Verizon Samsung Galaxy S III] Jihoonie:
Yes to both. I only mention it because my method works on other roms, including the one I'm on now. Not sure What's different with this one. Like I said, not a deal breaker but wanted to mention in case you weren't aware. Anyway you can test it out and see if it sticks for you?

http://db.tt/oW6SJyKc
[Verizon Samsung Galaxy S III] prdog1:
I flashed it into notifications folder. Shows up in folder but not in settings. have seen this before with fonts. Don't know what causes it. Have also only seen it on MF1 roms. May have to inject into rom zip and flash with rom. Shouldn't have to but whatever works. :cool:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yea we do have all apps enabled but I started using the xposed mw mod cuz it doesn't have that drag/drop bug that you mentioned. Working good since build 16/17 I believe for me. Rom is always running great as always bruh, no complaints on my end.
[Verizon Samsung Galaxy S III] jackrabbit72380:
EVERY TIME I GO IN TO SETTINGS/STRORAGE

I get this!

I have a sandisk ultra 32 gb micro sd card and have never had a problem with it.

also at the bottom of the screen it says error failed to retreave information.

I can also no longer mount my sd card in clmr but yet in rom works and ican hook the phone up to my computer and it works.

but cant open the SETTINGS/STRORAGE

what is this?
[Verizon Samsung Galaxy S III] Juice3250:
I was looking for the option to long press menu and it opens voice search, not just Google search. I switched to Nova to have this option.

This is what opens on tw launcher when menu is long pressed:

BTW double tap home does nothing for me no matter what I select in settings.

This is what I can customize to open when I long press menu in Nova:

I would love in build 20 to have the option to remap the hard keys, if it's even possible on TW Roms. I've yet to see them on any TW Roms out there. Is it only available on AOSP Roms?
[Verizon Samsung Galaxy S III] fastbenny:
I've been using this rom for the past week, and love it! The signal has been amazing compared to previous roms. The Battery actually last me to when I get in bed. And I still can install Samsung apps and have the option to return to Samsung Touchwhiz. Love it! Only thing now is to update the Android firmware to 4.2, then after that 4.3. Because KitKat will be coming up soon so need to prepare for that as well.

I had Cyanogenmod 10.2 (Nightly) previous to this rom. It had Android 4.3, ran like butter and pretty quick for unlocking, booting, all around good. But the battery life wasn't better than this one. And the signal was horrible compared to JellyBeans rom.

So that's the only thing I see this rom needs so far, update to the latest android firmware. ;)
[Verizon Samsung Galaxy S III] Tone Capone:
Anyone else experiencing notifications running through the clock (centered)?

Also, is there a way to make the clock text smaller?
[Verizon Samsung Galaxy S III] prdog1:
This is a Touchwiz rom and is updated to latest Samsung/TW software/firmware. 4.3 won't be available for another 1-6 months. 4.4 maybe another year if at all. Can't just upgrade TW with AOSP source. Don't work that way. :cool:

---------- Post added at 09:56 AM ---------- Previous post was at 09:54 AM ----------

There is a mod for that that is not incorporated. I just clear notifications if needed. Smaller text would have to be coded into rom. :cool:
[Verizon Samsung Galaxy S III] fastbenny:
Ahhh! That makes sense then. Pitty Touchwhiz hasn't already upgraded. Then that means I mark this the best Rom for Verizon's S3 :good: :cool:

Oh and perhaps add more Jellybeans Addons. Like All the samsung apps out there or something (Chaton with Video Chat, S4 themes etc..)
[Verizon Samsung Galaxy S III] Tone Capone:
Anybody having trouble with Google Voice outgoing texts getting stuck in queue? Incoming texts work fine. Weird.
[Verizon Samsung Galaxy S III] Metalhead520:
Installed this rom just about an hour ago and love it so far. Only question I have is has anyone installed and got Google wallet to run then return their build.prop back to the s3? If so let me know and what were the apps and steps you took to do so. I love wallet and am quickly loving this rom.
[Verizon Samsung Galaxy S III] talon4x4:
The only time you get CC spam is when you click on those stupid Facebook posts saying click here to get 10,000 lives + 5000 striped candies + all this other **** that you really aren't going to get. My poor gullible Mom fell for that one.

---------- Post added at 08:35 PM ---------- Previous post was at 08:26 PM ----------

Maybe this will help.

http://xdaforums.com/showthread.php?p=34848407
[Verizon Samsung Galaxy S III] prdog1:
HaHaa. She got bit big time. It asked for Google+ login and started spamming everything had to change all passwords. It also uses a lot of resources so if **** laggy that is why. :cool:
[Verizon Samsung Galaxy S III] Juice3250:
This ROM is definitely my daily driver go to ROM when I'm done trying out other Roms. I keep getting lured into trying 4.2.2 and 4.3 AOSP Roms, but they just aren't as stable and I have less of a signal. Therefore, I have issues sending and receiving mms on them. This, in my opinion, is my favorite ROM. In the end I still need phone to be.....well a phone.

My opinion is that custom Roms, or AOSP Roms, are best used and utilized on tablets or phones that you're not heavily reliant on the data.
[Verizon Samsung Galaxy S III] OMG_VTEC:
i was browsing the s4 forum the other day and noticed this neat little tidbit of information

its a fix for their issues with the wifi mms switchoff. something about the mf1 update blocking csc edits? devs, does that sound right?

anyway im not around a useable wif so i never use it but i tried this last week and sent a picture while on wifi and it switched over fine for me.

might be worth trying

http://xdaforums.com/showthread.php?p=45260401#post45260401

someone with wifi readily available should try this and get back to us
[Verizon Samsung Galaxy S III] Artimis:
Yes, I used the google wallet installer to install it (http://xdaforums.com/showthread.php?t=2125300). I used an older version but after everything installs, you need to go back into the app to restore your build.prop.

I have not had any issues with the app or phone after doing this.
[Verizon Samsung Galaxy S III] fastbenny:
1. Go to Play Store and install Busybox installer, install latest one inside xbin.

2. *if you haven't already* make sure you have openscript recovery installed (CWM or TWRP)

3. Download the Wallet Installer from here http://xdaforums.com/showthread.php?t=2044362 and use the options "JB TW" and "VZW" if you are on verizon of course.

It will prompt for Root access, click grant and it will reboot. Once rebooted, open Google Wallet and it should say give it 5 minutes to prepare. During this time it will be downloading and installing the latest Google Wallet from the Play Store. This is perfectly fine and needs to be done. Once it has updated, then reopen Google Wallet, give it a couple of moments to open, and then run through the setup guide.

And it should work now! ;)

Hope this helps!
[Verizon Samsung Galaxy S III] prdog1:
Yall's Wallet is obsolete. :p:laugh::cool:

Just gotta see if works.

http://www.androidpolice.com/2013/0...pports-all-android-phones-across-any-carrier/
[Verizon Samsung Galaxy S III] fastbenny:
I never heard of that version. Just installed it OVER the previous apk and it still works fine. Thanks for the update :) :good:

Here are screenshots of it working on my S3

http://i.imgur.com/YSpFuaC.png

http://i.imgur.com/9giFnVS.png

http://i.imgur.com/6zQxPLm.png

So yep it still works even with the new one.
[Verizon Samsung Galaxy S III] Artimis:
Is the new version still supporting NFC payments on a VZW S3 on the original build.prop?
[Verizon Samsung Galaxy S III] fastbenny:
I just checked, and while I was installing the new apk over the old one, my build was set to Galaxy Nexus. After I installed the new wallet and was able to run it, I changed my build prop back to the SCH-I535. And it still opens without an error. I have not tried NFC transaction yet, but it says it's ready to "Tap and Pay" on the homescreen. So I "assume" that it will work without any problem.

Here is a screenshot.

http://i.imgur.com/DqRP1zN.jpg
[Verizon Samsung Galaxy S III] MorphiousGX:
I replaced

com.android.contacts

com.android.providers.contacts

com.google.android.syncadapters.contacts
[Verizon Samsung Galaxy S III] STLRamsFan1k:
Hey guys, just flashed this rom a few days ago and all is well for the most part. There is a small issue I am having however. When using google.com on the browser, there are times when it just flat out doesn't want to work. I'll try to search something and nothing will happen, every after refreshing the page and trying again. It takes a complete shutdown of the browser in order to get it to work. Even trying to search something on the address bar will do nothing (just sends me to google.com).

Now, I did delete the google search app so the menu button wouldn't take me there anymore (never used it anyway). Would that possibly be the reason it doesn't want to work properly?

Much appreciated!
[Verizon Samsung Galaxy S III] vudugan:
I've seen this mentioned in these forums, someone metioned it possibly being the adblock file option in Aroma. You could make a nandroid, dirty flash and uncheck the option and see if it continues. I also experienced this on build 17. I thought it was Chrome beta and started using stock but seen issues with that too. Flashed 19 without the option and installed adaway. Haven't run into that issue yet...
[Verizon Samsung Galaxy S III] STLRamsFan1k:
Hmm strange, I actually had that option unchecked. :| Might need to see what happens if I disable the adblock app I have on my phone.
[Verizon Samsung Galaxy S III] Juice3250:
I have had issues using xposed framework, namely the xblast tools module 1.5.8. I changed the notification background and had ui fc's. Also, xquicksettingstoggles module doesn't work on this ROM. I have had success changing app DPI and icon themer as well xtheme engine.
[Verizon Samsung Galaxy S III] prdog1:
That is most likely because you are trying to mod the xmls in systemui that have already been modded for toggles, clock and trans and exposed is breaking the mods. Lot of the exposed modules have to be used on stock files or they break. :cool:
[Verizon Samsung Galaxy S III] Stupifier:
That makes sense...but also implies a rather large limitation on xposed module tweaking. In short, only one xposed module tweak can be properly applied per xml. Lame.
[Verizon Samsung Galaxy S III] prdog1:
Actually none may work if modified by rom dev dependent on the mod. Exposed is designed to work with stock files and exposed tweaks should be compatible with each other. :cool:
[Verizon Samsung Galaxy S III] Juice3250:
I have no problem with xposed not working 100%. Just letting people know not to expect it to work. I kind of suspected that it wouldn't work on modded Roms for those reasons.
[Verizon Samsung Galaxy S III] unhappybirthday:
It really depends on the types of modules you use. I'm currently running 5 that all work as described. I don't use any that modify graphic/theme elements.
[Verizon Samsung Galaxy S III] prdog1:
SystemUI mods are the most likely to be non compatible. That is where most the xml and smali mods are. :cool: :cool:
[Verizon Samsung Galaxy S III] Óðinsdagr:
Bandit-Moto V2.0_Jelly Beans.zip .... Was this the Bandit theme you were talking about earlier ? Sorry for changing the topic up. This ROM is running incredible and I'm seeing what themes I can throw at it now. Thanks for whatever help you can give me
[Verizon Samsung Galaxy S III] prdog1:
It still works for Version 19. At least with the basic setup. Not sure if anything in Rom control will break it but don't think so. :cool:
[Verizon Samsung Galaxy S III] daimerion:
Anyone not getting fb notifications? I get them on Hyperdrive but not on Beans for some reason.
[Verizon Samsung Galaxy S III] Juice3250:
I get fb notifications just fine.
[Verizon Samsung Galaxy S III] mav3rick478:
I get FB notifications just fine.
[Verizon Samsung Galaxy S III] xbiker321:
I see under the features its says "enabled group messaging" does this mean group messaging with iPhone users will work?
[Verizon Samsung Galaxy S III] dpeeps74:
Yes

Sent from my Slim GS3
[Verizon Samsung Galaxy S III] cgrugger:
What!!!!! You mean my friends won't automatically reply with, "John can't read this."?
[Verizon Samsung Galaxy S III] Giphtid2705:
Only if you're named John. :beer:
[Verizon Samsung Galaxy S III] cgrugger:
Well I am screwed then
[Verizon Samsung Galaxy S III] Jason Roach:
I was lurking the forums and found this security problem found here:

http://xdaforums.com/showthread.php?p=43630850

I ran the app that checks for the exploit and beans 19 seems to have one of them fix but not the other. I ran the master key duel fix apk in the exposed installer rebooted, rescaned and the exploits were repaired. Hopefully the fix can be implemented on the next rom update. Its sucks we have to worry about this crap, hopes this helps.
[Verizon Samsung Galaxy S III] prdog1:
Will have to look at it. We change apks all the time as themers. This could cause a problem. No inverted apps would suck. :rolleyes::cool:
[Verizon Samsung Galaxy S III] mav3rick478:
That second fix wasn't implemented because it was not fixed by Verizon via update to system software and it came out shortly before Beans put out version 19. No harm though because of the xposed app you can install. I applied it on 18 & 19.
[Verizon Samsung Galaxy S III] Jason Roach:
Just thouht I would share this, beans 19 with faux oc kernel, full brightness, stock battery, cfq schedule, intelldemand governor.

Having trouble with trickser mod holding my cpu settings after reboot. I may try faux app since using his kernel, just an fyi.

This is a fantastic rom build, props to you beanstown. Thanks
[Verizon Samsung Galaxy S III] prdog1:
This should be in the kernel thread. :cool:
[Verizon Samsung Galaxy S III] zachf714:
[MENTION=4538493]prdog1[/MENTION] hey man, what causes "Android System" to be at the top of battery stats ?
[Verizon Samsung Galaxy S III] prdog1:
From what I've seen it always 2nd behind screen if using device. Depends how long and usage since flash. Android if click on it is almost everything systemwise running that is not an app. Mine recently flashed so can't really tell. Click on it in settings /battery and make sure nothing locked keeping wakelock up. Locked kernel could keep it awake. :cool:
[Verizon Samsung Galaxy S III] zachf714:
It seems that it has a small wakelock :cool:
[Verizon Samsung Galaxy S III] prdog1:
Wipe dalvik and cache and reboot. Fixes most system and kernel wakelocks. :cool:
[Verizon Samsung Galaxy S III] hoodieNation:
Yeah, where nobody would have read it.

I like it with the helmet on.
[Verizon Samsung Galaxy S III] prdog1:
Does no good here. The devs may supply 3rd party apps and kernels but don't support them. :cool:
[Verizon Samsung Galaxy S III] hoodieNation:
Was he looking for support or just giving an fyi about his very good battery life? I don't follow kernel threads and I don't mind getting updates like this whatsoever.

I like it with the helmet on.
[Verizon Samsung Galaxy S III] Jason Roach:
It was just an fyi. No comments were needed.
[Verizon Samsung Galaxy S III] prdog1:
Just for transparency and not to confuse other members. It had nothing to do with battery life or this rom. It had to do with kernel problem not doing what it was supposed to do. It is called Faux Kernel for a reason. ;) :cool:
[Verizon Samsung Galaxy S III] Jason Roach:
How do I get the media players (music and video) to read the files on sd card. And yes its mounted and I can play the files with a file explorer. For some reason the players are only looking for the internal card. If there is a setting somewhere to change I haven't found it yet. Running Beans 19 and stock media players. Thanks in advance.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
What's your sdcard formatted to and which kernel are you using? I use PowerAmp and I can view and listen to music with that and stock music player. It detects the music automatically. Also, are you checking after a fresh boot and it's just not loaded yet or has it not loaded into the music player at all without any recent reboots?

Ironically enough, my headphone jack just gave out on me this weekend and now only plays audio out of the left ear bud of whatever I plug in.
[Verizon Samsung Galaxy S III] OMG_VTEC:
you might also want to try turning on the media scanner and reboot. then wait a little bit and turn it back off.

i had that issue for a while