yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] arcsum68:
Agreed, it did in fact make my phone 3g only, literally, it would not let me turn 4g back on. Had to restore my backup.
[Verizon Samsung Galaxy S III] prdog1:
I had the same problem but there is a way around it as I found out later. Have to search cause I don't remember. Also have to find the app as it is/was no longer available in the market. :cool:
[Verizon Samsung Galaxy S III] hoodieNation:
Lol, I just got Carbon all setup and then I see build 19 is uploading... And I'm now coming back to Beans :) stupid perfect rom.
[Verizon Samsung Galaxy S III] prdog1:
That is what Nandroids are for. :rolleyes::p:laugh::cool:
[Verizon Samsung Galaxy S III] :
BEANS you are the man. Downloading now.
[Verizon Samsung Galaxy S III] dillonkem:
This is my first time using beans ota update. I usually do a full wipe and unlock bootloader etc. Just curious how the ota update works so I don't mistakenly install improperly.
[Verizon Samsung Galaxy S III] talon4x4:
Ohh s#$% one mirror is ready!! Downloading now, only 20mins left. I've really needed to reflash my phone because I'm getting ridiculously high Android OS usage and in turn not very good battery life, when I look at the battery stats.
[Verizon Samsung Galaxy S III] lennie paz:
I just got a notification for JellybeansOTA. I've never used a ROM that had OTA updates. Do you guys use the OTA updates? Can I dirty flash new updates?
[Verizon Samsung Galaxy S III] phatreno:
baseband

Are people having good luck on this rom running bmf1 modem ,ive been using b1 since it was released with great service, just not sure to change I've heard about issues bmf1 just curious how it works on Beans?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
You do a full wipe AND unlock bootloader? That's way too much bud. Format data and wipe system in recovery then flash for a clean flash. That's an ultimate (and unnecessarily lengthy) clean flash if you're unlocking the bootloader. You can dirty or clean flash these builds. Don't post bugs unless you clean flashed.

Yes you can. Just don't post bugs unless you clean flashed and the issue is still there.

If it ain't broke...
[Verizon Samsung Galaxy S III] lennie paz:
I'm getting the error message "There was an error in the file download" when I try using the OTA update.
[Verizon Samsung Galaxy S III] hoodieNation:
Just manually download it from the OP. Worked fine that way for me.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
If only there was an option to remove the carrier label on pulldown, and if battery percentage was fixed. The battery percentage worked in build 17 but anything above so far hasnt been fixed yet :(
[Verizon Samsung Galaxy S III] phatreno:
kinda what I was thinking just wasn't sure if F1 had better service
[Verizon Samsung Galaxy S III] prdog1:
Need to read. I supplied a trans no carrier label pulldown a while back and was also thanked by Beans for posting a couple days ago. It is there for the pickin. :rolleyes::cool:

---------- Post added at 05:06 PM ---------- Previous post was at 05:04 PM ----------

MF1 was better for a lot of us. It no big deal. Flash it. If it not good flash back to MB1. Modems are on different partition and be flashed and changed hourly if you want without affecting rom or setup. Can even change as fast as you can flash back to back. :rolleyes::cool:

---------- Post added at 05:11 PM ---------- Previous post was at 05:06 PM ----------

Not sure what's up Beans but I'm late to the party and you got 0 download count on AFH. :cool:
[Verizon Samsung Galaxy S III] lennie paz:
Thanks for the suggestion, but I was looking for a fix, not a workaround.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Yeah I had it back when you posted it. It worked for a while but whenever I flash it now, it has no effect. Not sure why?
[Verizon Samsung Galaxy S III] talon4x4:
FYI: The md5 on the first page is not correct (doesn't match). If you go to the androidfilehost.com site for your download you will see the correct md5, which is 5315e5c68408ebda0dcd0406b790901c
[Verizon Samsung Galaxy S III] prdog1:
Has to be a change in the update zip or your copy is corrupted. Samsung hasn't changed the location and it only a PNG change. :cool:
[Verizon Samsung Galaxy S III] ExcludedDroid:
Can confirm that is the correct md5. :)
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Yeah I redownloaded and it works fine. Thanks
[Verizon Samsung Galaxy S III] prdog1:
Kewl. Should always work untill maybe 4.3 upgrade. :cool:
[Verizon Samsung Galaxy S III] bryank29:
So going from Build 18 to 19, do I basically have to upgrade from scratch (wipe all)? Or is there an "update" process where I can keep all my accounts, settings, etc..?

I am using Rom Manager and it uses Clockwork Mod 6.0.3.1

Thanks
[Verizon Samsung Galaxy S III] Hobson318:
Here is the reason I found for that. The JellyBeansOTA updater is looking for a folder that doesn't exist. Go in to settings in JellyBeansOTA, click on Choose download dir. Then just type in the location you want the downloaded files to be saved in. For example mine is: /storage/extSdCard/Download. So it goes to the download folder on my microsd. Hope that helps.
[Verizon Samsung Galaxy S III] WestOkid:
[MENTION=418212]beans[/MENTION] or someone who knows. What is sysscope and what does it mean when you say "Killed" it? I have looked everywhere, all I see are people talking about how they want to get rid of it, but no one seems to know what it does.
[Verizon Samsung Galaxy S III] prdog1:
Well got 2 strikes against you to start. Using Rom Manager and CWM. :laugh: You can dirty flash anything. No one knows what will happen. Unless you clean flash you should not report any problems unless you wipe all and the problem persists. As devs and dev support we cannot support dirty flash especially when no one else has the problem. If it is a bug with rom everyone will have the same problem. Only takes common sense to figure that out. :cool:

---------- Post added at 06:08 PM ---------- Previous post was at 06:06 PM ----------

Killed it means all relevant calls for syscope in code have been removed. Syscope is spyware by definition. :cool:
[Verizon Samsung Galaxy S III] gregurbo:
OK updated to 19 and now I have this

thing in the left upper corner (0B/s) how do you get rid of it?
[Verizon Samsung Galaxy S III] WestOkid:
Thanks dog, but what did it do? and what gets affected by killing it?
[Verizon Samsung Galaxy S III] prdog1:
Need to Google it or search the forums for explaination. It is spyware/bloat. Affects nothing we know of except slows down device while it reads your ****. :cool:

---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------

Looks like the new dBm signal everyone want's that is already in system status and is actually irrelevant. You have signal or don't.. Would have to reflash and not pick in Aroma to kill it. May be wrong but haven't flashed rom yet. :cool:
[Verizon Samsung Galaxy S III] lennie paz:
I just changed mine to that same directory, and I'm still getting the error message.
[Verizon Samsung Galaxy S III] prdog1:
OTA updaters are hit and miss. When work they are good for minor updates. For full rebuilds they suck as you are dirty flashing. I haven't tested this one yet but it could be bad and I recommend a full wipe and do standard wipe, download and flash for optimal experience. :cool:
[Verizon Samsung Galaxy S III] hoodieNation:
Go into custom settings, Rom control, status bar mods, and then toggle "show network speed". It's not checked by default but still shows up for whatever reason.
[Verizon Samsung Galaxy S III] prdog1:
Lot of these mods require an initial toggle to work correctly. Eventually the smali will be worked out. :cool:
[Verizon Samsung Galaxy S III] Hobson318:
Do you have:

1. an external sd card?

2. do you have a folder on that sd card called download?

It is case sensitive I believe. The path needs to be exact.
[Verizon Samsung Galaxy S III] lennie paz:
I literally just put the previous version on my phone this morning, not knowing a new version was being released today. The reason I hate doing a full wipe, is having to redo my phone after it reboots. There's not a 1 click restore after flashing a new ROM, is there?
[Verizon Samsung Galaxy S III] prdog1:
There is no one click except restore data only in recovery. It is still same as dirty flashing and works if dev made no major changes. It is always a crap shoot when restoring data. Works sometimes. Breaks **** other times. If something is broke clean flash before reporting. If it is operator error and dirty flash only those that did same with same apps will have the bug. If it is rom bug all will have it. If someone posts that theirs works right then most likely you need to do full wipe and reflash as it is your fault for dirty flashing. Yall lucky. I learned on the Mik and we wipe everyone's data. If can't rewrite the script and want to run our roms your data gets wiped whether you like it or not. We had no irrelevant bug reports caused by dirty flash. All bugs everyone had and were quickly fixed. No goose chases. :cool:
[Verizon Samsung Galaxy S III] Evil Genius Jr.:
So can I dirty flash b19....

Sorry just had too lol :p

Installing right now, Thanks beans!
[Verizon Samsung Galaxy S III] prdog1:
Go for it but don't call us for problems. We gonna tell you to wipe all data and call us later.:laugh::cool: :p
[Verizon Samsung Galaxy S III] bryank29:
What do you use?

btw, I don't my S3 3rd party, and it had Build 18 already on it..so I suppose the previous guy is the one who installed CWM.
[Verizon Samsung Galaxy S III] prdog1:
I use TWRP all the way. I flash all by the hundreds. Between deving and theming I may flash 10-20 times a day. Always works. :cool:
[Verizon Samsung Galaxy S III] slvfox:
Toggle it on and off and the show network speed will be gone.

---------- Post added at 06:25 PM ---------- Previous post was at 06:22 PM ----------

Will Bandit work on build 19 ?
[Verizon Samsung Galaxy S III] prdog1:
I have to see. The MW works. Haven't tested whole theme. Thinkinging about doing a AOSP/Bandit hybrid . Have to make a run to liquor store and then will test to see what is broke. Doubt anything but with on fly mods can't guarantee everything. :cool:
[Verizon Samsung Galaxy S III] bryank29:
So I downloaded Twrp Manager from the Store. I saw a comment in the reviews that said I needed goo manager to deal with twrp..but when I open Twrp, it appears it has all the buttons I would need.

So with Twrp, I do a backup first. Then I go into WIPE, wipe the Dalvik, Cache, and data. Then install and select the Build 19 zip from my external? I don't understand why I would store a file on the internal drive if I "wipe data" as that sounds like it would nuke everything anyways.
[Verizon Samsung Galaxy S III] prdog1:
Don't need TWRP manager. Never heard of it. Everything else is basically same as CWM. Team Win did the touch for Koush on CWM. Just tell TWRP to backup to external and then wipe system/data/dalvik and cache as usual. Can also name backup at same time. Take your time and look at everything on each page. :cool:
[Verizon Samsung Galaxy S III] bryank29:
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en

Is that not Twrp?
[Verizon Samsung Galaxy S III] prdog1:
Yes but don't need that app. I have but don't use. Just need GooManager/menu/ update recovery script. Gives you latest version.
[Verizon Samsung Galaxy S III] bryank29:
there is a "install OpenRecoveryScript" if that is what you meant.
[Verizon Samsung Galaxy S III] prdog1:
Yes that installs latest version of TWRP. It will tadownload and take a while to flash. Don't rush it will tell you when done.:cool:
[Verizon Samsung Galaxy S III] kenbrownstone:
Yep
[Verizon Samsung Galaxy S III] bryank29:
Ok bit confused. I did a "Factory reset wipe" via the Wipe screen of Team Win Recovery. Then I go to INSTALL, and select my external which it sees just fine. Then it tells me to select a zip to install...except all I see are directories..no files.

what am I missing?
[Verizon Samsung Galaxy S III] prdog1:
You will see directories for whatever card you are on.What sd card did you put zip on. That is one you want to change too to flash zip. If put on external and are on internal will not see the zip. Can change sd cards on page you are looking at. :cool:
[Verizon Samsung Galaxy S III] bryank29:
Yea I know..I am bouncing between directories and cards..no "files" (aka that have an extension) show up anywhere..all I see are folders.

Can I mount my external drive from Team Win Recovery so that I can view the files on my computer (PC) and verify the zip is there (I know it is)
[Verizon Samsung Galaxy S III] prdog1:
Both card will show on PC unless you are running a kernel that don't support exFat such as KT kernel. Non exfat support will only show internal. TWRP sees exFat. CWM didn't. Not sure if it does now. If see folders may have to go up or down in root that TWRP allows. May be on wrong page of root. TWRP works like file explorer or manager.:cool:
[Verizon Samsung Galaxy S III] bryank29:
I am a f'ing idiot. Just restored my backup...looked at the files on my PC..and the zip was 0 bytes. I must have goofed on the copy over of Build 19.

but...via Twrp...I still didn't see my files on my PC while it was connected via USB.
[Verizon Samsung Galaxy S III] prdog1:
If picked the wrong kernel will not see them. Kernel has to support exFat. Unless been fixed I know KT kernel will not show. Many other kernels by sub kernel devs don't either. Will show with stock kernel. Should always see internal sd as phone/Kernel controls it and not recovery.the kernel devs use stock kernel for base so don't jack with internal. Phone is native exFat for external xd but devs have to program over the stock signature for kernel to read external exFat. :cool:

---------- Post added at 11:32 PM ---------- Previous post was at 11:20 PM ----------

When phone is plugged to USB and only see Phone (internal) on PC your kernel does not support exFat. If reformat SD Card to Fat32 will see both. Everything sees Fat32 but then are stuck with old school specs and held to 4GB file. That means no movies unless compressed below 4GB or split like old CDs For now movies are only thing that requires exFat although it is a faster file system and why phones are default to exFat. Fat32 is being obsoleted as fast as they can. Not compatible with the streaming/ download of data that carriers want to charge for.. :cool:
[Verizon Samsung Galaxy S III] bryank29:
So I copied the build 19 zip to my internal..as it seems to struggle making it 100% to my external for some odd reason..I did the factory reset option in Twrp, and went to go install and couldn't see the zip...I think the data wipe killed it.

sigh

EDIT - wait no, wtf...just restored again...loaded the phone drives onto my PC..and I still see the zip.

So why is TWRP "not" seeing my zip files after going to the INSTALL section?
[Verizon Samsung Galaxy S III] prdog1:
Go to PM and see if I can get you straightened out. No need to clog this thread. Give me what you were running before so I can tell you where you need to go from here. :cool:

Edit: TWRP sees them. You are looking at wrong thing. Zip is on external and sounds like you are looking at internal. Will not see it if looking at wrong card to flash zip. Just like if save all backups to internal will see no files backed up if looking at external. Have to change sd card look in TWRP. There is a small button to change cards on zip page.
[Verizon Samsung Galaxy S III] bryank29:
Just curious...anyone have a preference between the S3 stock camera..and the Note 2 camera?
[Verizon Samsung Galaxy S III] prdog1:
S3 camera built for the device always works right. ;):cool:

Edit: I have to put in the disclaimer that I don't believe in cross device ports. As good as our devs are there is always a deficit in performance. i pay full device price and I expect everything to work and then we upgrade. So you can guess that I never touch AOSP or I would have a Nexus. As far as themes it is not that hard. AOSP theme is built into all devices.
[Verizon Samsung Galaxy S III] cfish81:
The md5 shown is for build 18
[Verizon Samsung Galaxy S III] prdog1:
Use the md5 from download site (AFH). Not the one posted. It gives you the MD5 when you download. :cool:
[Verizon Samsung Galaxy S III] jackrabbit72380:
Great rom!

Recommendations!

0.phone boot up to unresponsive black clock I cant unlock (BIGBUG!)

1. I miss the dark aosp email mod what happen to it?

2.default app selection (this should have checkboxes to install more than one from each section) I want to install more than one launcher.

3.touchwiz 4x4 & 4x5 (this should have its own section

4.brightnees slider toggle should be in rom not in the installer

5.would like to see other options in (color of toggles) like htc

6.needs more wether wiget options like gs4 and transparent

7.option to make your own text in dropdown

I have more butt that's all for now!

Great rom!
[Verizon Samsung Galaxy S III] prdog1:
#0- Did not experience.

#1- All AOSP messengers can be found in Themes and Mods Forum.

#2- That is dev dependendent and can install any launcher you wish from the Market.

#3- All devs put launchers in same section. Can't run more than one TW launcher at a time. Why waste the time on free versions of custom launchers. If really need that launcher the pro version is available in the market.

#4- We all put in installer. The more that is in rom it is called Bloat. Requires a systemui change and is not a on the fly mod. Also a themer mod and not actually a dev mod. if dev does he is spoiling you.

#5- There are new HTC phones you can get. This would also be a systemui / framework mod that is not worth the time for vanity. This is actually a themer's mod and not a dev mod. This also would be an Aroma mod to not bloat the rom.

#6- See #4 and #5- Rom dev can add if want. This is actually a themer mod ad they are available in the Theme and Mod Forums.

#7- Can make your own text. Need to learn how to decompile and code.

:cool:
[Verizon Samsung Galaxy S III] jackrabbit72380:
8.system /status. my phone number displays unknown.
[Verizon Samsung Galaxy S III] prdog1:
#8- Sounds like a dirty flash from AOSP or running on a non-Verizon device.
[Verizon Samsung Galaxy S III] jackrabbit72380:
its not and I didn't have this problem in v18,
[Verizon Samsung Galaxy S III] prdog1:
I haven't flashed Beans except to build theme. Don't normally run it. Don't like built in mods unless I build. Wiped as we devs do and flashed 19. All mine good as always. Phone number intact. No black clock. Everything working as advertised. Has to be operator error from what I can see. give me more to check and will while I have it flashed. :cool:
[Verizon Samsung Galaxy S III] jackrabbit72380:
I keep getting a popup saying acore has stoped responding

whats that?]

I edit the pictures for gs3 default boot animation from the i9000 and removed the i9000 so it could be used for the other models but I cant get it to boot up I did sign it so I dont know whats wrong maybe someone can get it working here it is.

GS3Universal
[Verizon Samsung Galaxy S III] prdog1:
In the day it meant you had too many Facebook friends and got tired of syncing. Now it usually means you dirty flashed. :cool:

---------- Post added at 05:58 AM ---------- Previous post was at 05:37 AM ----------

@Beans. Looks like Bandit theme still works Homie. :cool:
[Verizon Samsung Galaxy S III] dragonfly1113:
Does build 19 fix group aosp sms period bug? Didn't see in change log.
[Verizon Samsung Galaxy S III] prdog1:
None of the TW devs actually support the AOSP messaging apps that are ported by other devs. Beans may try to theme them but base messaging questions should go to the AOSP port dev. We can theme anything but don't mean we can fix what the original devs broke. :cool:
[Verizon Samsung Galaxy S III] dragonfly1113:
Guess it's different on his note 2 builds because on my note 2 it's perfect.
[Verizon Samsung Galaxy S III] prdog1:
Probably just need to port to an S3 compatible zip. I9000 zips are not compatible. Same as data. :cool:

Have no clue. Note 2 and S3 two different animals. Use root explorer and delete one in S3 and replace with one from Note 2. 30 second fix if works. If been running TW messaging on 19 also need to delete the 3 DB (data base) files.:cool:

:cool:
[Verizon Samsung Galaxy S III] unhappybirthday:
Is it possible you are syncing "Internet" in your Google account settings but don't log into Chrome on a PC? If you see a red sync problem for Internet, try unchecking it and see if it the ACORE force close goes away.
[Verizon Samsung Galaxy S III] tampaboy1984:
This ROM is great! Could someone point me in the direction for some XTheme themes?? Maybe even a really nice Sense 5 theme.
[Verizon Samsung Galaxy S III] sd5500:
Does anyone use ESPN's "Streak for the Cash" app? For some reason it crashes a lot on 18 and now 19. Was using paranoid for a few days and the app worked fine.
[Verizon Samsung Galaxy S III] Legacystar:
So i just switched my brothers phone to this ROM and noticing really bad tether speeds and ping on both native and Trev. Anyone else getting this?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Are both on the same firmware? If not, put his on VRBMF1 then pull the sim card for thirty seconds so that it updates your PRL.
[Verizon Samsung Galaxy S III] Legacystar:
Well ones an s4 connected to the s3's tether. Prl has nothing to do with it . the s3 is getting great speeds, but whatever is attached through its tether isn't
[Verizon Samsung Galaxy S III] lynneddington:
Runs great Beans, super smooth.

sent from my slightly modified verizon S3
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Oh? I don't know much in this area since I don't tether. I've always thought when tethering, that the device pulling data would see slower speeds. Per your original question, I thought you were saying one S3 is seeing slower network speeds than the other with this rom.
[Verizon Samsung Galaxy S III] Legacystar:
Tethering doesn't cause slower speeds. If I do this in reverse and use the s4 as the tether source the s3 connects through it and sees full speed.
[Verizon Samsung Galaxy S III] talon4x4:
No dirty flash here and I got the acore message error. Only once though. Rom finished installing, I rebooted device and this message popped up. I ok'ed by it, rebooted and have never seen it again.

So far everything is running great!! Now I just have to finish reinstalling all my apps. What a PITA! :silly:

Anyone else get random lines going across the screen during the Google boot animation? Not that it really hurts anything but it wasn't something that was happening with last release.
[Verizon Samsung Galaxy S III] rogue5099:
I don't get those lines.

Beans GREAT work. Running smooth and you inspired me with the net speeds to implement that into a program I wrote to test PC's.
[Verizon Samsung Galaxy S III] ashtro:
Can anyone tell me the name of the default ringtone from build 18? I wouldn't mind using that for 19
[Verizon Samsung Galaxy S III] Hobson318:
quick question on this. shut the phone down, pull sim and boot phone, leave for 30 seconds, shut down phone, reinsert sim? or just pull sim while phone is on, leave out for 30 sec and then put back in?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Sim is below the battery so the phone goes off either way. Gotta pull sim, wait thirty seconds, reinsert, then turn the phone back on.
[Verizon Samsung Galaxy S III] icedventimocha:
Anyone interested in testing a multi theme installer for this rom send me a pm.

Sent from my Galaxy Note II
[Verizon Samsung Galaxy S III] Legacystar:
Can you give me a reasonable explanation as to why pulling a Sim on a phone that's off would fix tether lag?
[Verizon Samsung Galaxy S III] DerangedLoofah:
Its in custom ROM settings.
[Verizon Samsung Galaxy S III] bryank29:
I don't recall seeing this in Build 18...but YES YES YES I can finally take a picture with the volume key! I chose the Note 2 camera on install though.

Also, in the Rom Mod settings section there is a 4.3 Camera (Android 4.3 camera with Photosphere) available for download.

Has anyone tried it?
[Verizon Samsung Galaxy S III] hoodieNation:
Yep, I'm getting those as well. On the kt kernel. Not that that has anything to do with it lol.