yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] BoxyBox:
I didn't choose AOSP MMS, but prdog1's solution fixed it completely. Thanks!
[Verizon Samsung Galaxy S III] prdog1:
Good. Glad to be of assistance. :cool:
[Verizon Samsung Galaxy S III] yznhmr:
any thoughts from any one? thanks..
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Could have sworn I responded to at least part of this before or someone else did? Are you referring to the IME switcher in the notification bar? That should only show when you have the keyboard open. Can be toggled with Settings/Custom Settings/Rom Control/Status Bar mods

I'm not too familiar with the Voice to text issue. I don't use it actually. Which keyboards do you have installed? Have you tried installing the official Google Keyboard to see if this improves any? Or updating your language packs (if at all possible) in Settings/Language & Input. Everything set to Google or English (US)?

Corporate email sync. Is it possible there's a limit placed by the tech admin of your job? When you say this "used to work on CM" does it not work now?
[Verizon Samsung Galaxy S III] ucpro:
Does morphology work with 19?
[Verizon Samsung Galaxy S III] james:
Does dlna work on build 19
[Verizon Samsung Galaxy S III] Hans5849:
Somehow I got multi window support enabled. The thing is when I try to add new apps there's a problem. Say I drag the Facebook app over, well once I drop it it becomes a different app. Any suggestions?
[Verizon Samsung Galaxy S III] GreenMunky:
Yes, it's a very strange bug that exists in the modified multiwindow window support that allows all apps to be added. What you have to do is add every app you have to the drawer, starting at the top of the list, then remove the ones you don't want. I know it sounds like a pain in the ass... because it is... but you'll be thankful if multiwindow is something you think you'll utilize.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
That works but it gets old fast. Yall should try this xposed MW module then reboot. Works great whenever, wherever. Been working great on each build since 16/17. I use the standard apk and have not bothered with the MW240 apk.
[Verizon Samsung Galaxy S III] GreenMunky:
Nifty! Haven't used multiwindow in a while. Might have to give this a try.
[Verizon Samsung Galaxy S III] ucpro:
By the way, morphology doesn't play well with this Rom
[Verizon Samsung Galaxy S III] tampaboy1984:
Themes for this rom?

I saw a Jelly Beans build22 for another phone, is this gonna get updated for S3?
[Verizon Samsung Galaxy S III] fastbenny:
Haha, guess what! My grandmother had to take back the Galaxy S3 from Alltel because they cut off the tethering on it. Like WiFi/Bluetooth/USB all didn't work. It's because Alltel now charges $20 to unlock the tethering. She has the old Moto Milestone X2 which has gingerbread on it, so she can USB and Bluetooth tether, but not WiFi. She has the grandfather-unlimited data plan. Cost alot, but she like it. She uses over 4GB every month because thats the only source of internet she has.

But anyways, she is thinking about switching to Verizon with us because they allow WiFi tethering, but it will cost her the unlimited plan. Also, at her house is only 1-2 bars of 4G because she's outside the city limits. It's been crazy over here lol!

But if she does come over to Verizon, she will get the S4. So is it possible for the "AWESOME" dev who made Jellybeans Build 19 so also produce a similar one for the S4? Of course it won't happen in a week, or even a month. But just wondering if it is in the agenda? :D
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Idk about themes. Besides that, what are you missing in the rom? Also, what bug do you have with the rom? It was updated three weeks ago mind you, which is good.

Beans already has a rom out on the S4. Couple stock ones as well.
[Verizon Samsung Galaxy S III] fastbenny:
Okay. Thanks!
[Verizon Samsung Galaxy S III] Gutsman:
Loving build 19, but just a quick thing: the MD5 in the downloads section is wrong. It's the one for build 18.
[Verizon Samsung Galaxy S III] droidxxxxx:
For some strange reason and I notice it only on this rom so far when I have the wifi tether up and my tablet connected I cannot stream Hulu or Netflix for anything from the tablet. Other ROMs the wifi tether will allow this. I don't know why it would have some sort of cap or something?
[Verizon Samsung Galaxy S III] Hobson318:
If your grandma is running this rom on her S3, how is she not able to wifi tether with trev-e mod? I have no issue tethering using it. Even if she isn't running this rom and just roots her phone she should be able to install the mod and tether.
[Verizon Samsung Galaxy S III] unhappybirthday:
Have you undervolted your kernel?
[Verizon Samsung Galaxy S III] makos101:
I haven't tried it. What voltage do you recommend?
[Verizon Samsung Galaxy S III] prdog1:
If using custom kernel it is already undervolted too much for your device. :cool:
[Verizon Samsung Galaxy S III] makos101:
I'm using the stock for the Rom
[Verizon Samsung Galaxy S III] prdog1:
Then don't know how to fix. Usually stock kernel fixes it. :cool:
[Verizon Samsung Galaxy S III] S. Prime:
Sim Card Corruption

I searched, but did not find a specific answer, so I will try a post. As I am new to installing Custom Roms on a Verizon phone, with a sim card, is there a chance that installing the Jelly Beans ROM will corrupt your sim card and if so what precautions should you take? Thanks in advance.
[Verizon Samsung Galaxy S III] cr6:
Open up system settings, go into custom settings, ROM control, status bar mods, choose your battery icon, scroll down to "cyan chronic".

Profit.
[Verizon Samsung Galaxy S III] prdog1:
he wanted the png files. Hooked him up already. :cool:
[Verizon Samsung Galaxy S III] cr6:
Oh ok....thank you sir! :thumbup:

tap'n
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Sure it's possible, but that goes without saying anything that happens is not Beans fault. As it stands, not a single person has commented saying this rom has done so. Not really any precautions to take in regards to the sim card just makes sure your contacts are on Google and they'll sync once signed in.
[Verizon Samsung Galaxy S III] griz.droidx:
You might want to look into backing up your imei, I think that's what it's called. I would read through some of the general how to posts at the very least. But I agree, you should have no problem flashing this rom.
[Verizon Samsung Galaxy S III] S. Prime:
Thanks, I have already backed up my imei by copying my efs folder to my external sd card and to external storage.
[Verizon Samsung Galaxy S III] kmsck5:
soft touch home button

Is there a way enable and/or does jellybeans rom even have a softtouch home button? Can I get in a theme and which one. I've looked but can never find.
[Verizon Samsung Galaxy S III] prdog1:
Not sure what you mean by soft touch but there is a mod somewhere to add onscreen buttons and disable hard buttons if desired. Most everything in stock Android is in TW including Holo theme if you enable the option. :cool:
[Verizon Samsung Galaxy S III] kmsck5:
The onscreen buttons is what i think it is. You have the home button, back button etc.. Where do I find it in the settings?
[Verizon Samsung Galaxy S III] prdog1:
It's not. It is a mod and has to be hacked. I'm looking at old mod to see if still works or if I have to update it. The mod is by Mentose457 in the theme and mods thread. Hasn't been updated since Beans 13 I think but probably still works. Takes a build prop edit for your rom and then the image files and xml edit if want to rearrange the order or disable the hardkeys. :cool:
[Verizon Samsung Galaxy S III] prdog1:
Here is the softkey mod thread. It still works on Beans 19. Will require you to mod your buildprop before flashing the mod. Will make the TW camera a PITA to use. :cool:

http://xdaforums.com/showpost.php?p=39528704&postcount=1
[Verizon Samsung Galaxy S III] ancora76:
Uconnect option for messaging?

First off this is by far the BEST Rom available for this phone AWESOME JOB and thank you for making my phone better than Samsung could. I have tried many Roms out there but this is just awesome! Now.... i have a brand new Dodge Charger with the Uconnect audio video system and one of the big options on this system it the ability to view and text via bluetooth on the main 8 inch screen. The only problem is that nobody is able to do it. Every owner that belongs to the forum that i chat with get the same error message that states that the phone is not compatible. The only people that have ever had success with it were owners of the Motorola Razor. So my question is and i know im probably the only one that wants this but is there any way possible for Beans to somehow figure out how to make this work in my car or even why only 1 phone out of many that came out will not work? It just puzzles me why i cant figure out what made that 1 phone work when even the Razor Max which i believe was the follow up does not. I love this ROM and dont want to leave it at all and would live without it but i just dont get why only the Razor is the only phone that works with this Uconnect system. I have sent many emails hoping to get Uconnect to update the software but from what i have seen the last update that came out was in 2011. Needless to say i am not counting on this feature to ever work if i continue to wait for them. Thanks again for an AWESOME Rom!!! :good:
[Verizon Samsung Galaxy S III] Hans5849:
It would be nice to have a separate flashable kernel. If I try another kernel and want to flash back it's annoying to have to reinstall the whole Rom.
[Verizon Samsung Galaxy S III] Eggsnbacon:
You can download and install any kernel separately, you just search for the kernel thread, download and flash. The kernels included with the rom are just that, included. There may even be an updated version of your preferred kernel when you search it:highfive:
[Verizon Samsung Galaxy S III] unhappybirthday:
Any TouchWiz kernel, that is.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Has anyone seen the VRBMF1 stock kernel zip? I always run custom but noticed I haven't seen that outside of the rom. Maybe that's what the other user s referring to.
[Verizon Samsung Galaxy S III] prdog1:
Beans MF1 kernel.

http://www.androidfilehost.com/?fid=23159073880933525

Stock MF1 kernel.

http://www.androidfilehost.com/?fid=23159073880933522

:cool:
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Appreciate it man!
[Verizon Samsung Galaxy S III] mav3rick478:
Weird issue the last couple of days and I wanted to see if anyone else has seen this, running build 19 with latest LK, randomly the toggles in the pull down will change showing less and then change back to normal later in the day or after a reboot.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I've noticed it too but it haven't bothered to point it out. Pretty sure was like that on the last build or so but it's not easily reproducible. I get this with the seven toggles option in Aroma. I just rotate the phone to landscape then back to portrait and it goes back to seven toggles.
[Verizon Samsung Galaxy S III] Shrt Bus:
I have noticed that as well.. since build 17.. also I noticed that view options that I have saved like under the phone app (viewing certain contacts) that it will reset to show all and most recent with this build 19 that every time I reboot it will ask me which launcher I want to use even tho I have picked one as always.

Rick
[Verizon Samsung Galaxy S III] hoodieNation:
Speaking of the toggles. Maybe I missed this, but I remember Beans saying he was gonna make a zip or something to remove the lines under the toggles. Did that ever happen?
[Verizon Samsung Galaxy S III] mav3rick478:
Thanks guys thought I might have messed something up because never had that issue before. Only started after I tried getting tap to pay on Google wallet to work and got black screen and had to reinstall my Rom.
[Verizon Samsung Galaxy S III] jlyle:
Do you mean like this ??
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Hmm, not sure about the contacts issue. I only view all contacts at once. I use Nova Prime and this doesn't happen to me. I chose Nova in Aroma though. Did you choose TW and then use a different launcher? I haven't noticed anything reset it's default for "once vs always" with this rom upon reboots.

No problem bud.
[Verizon Samsung Galaxy S III] Ridl3y:
I have a HUGE emergency. I cannot get past my lock screen. I was setting up a passworded lock screen for tonight and it happened. I'm not sure if ripple effect was on, but I picked the AOSP one and it freezes every time I touch the lock icon. I have super important information that I must absolutely get off of this phone. PLEASE HELP ME! This is a terrible bug that has been around for almost a YEAR! Please tell me there is a way to bypass it so I can turn it off!!!!!!!!!!!!!!!!!!!
[Verizon Samsung Galaxy S III] SlimSnoopOS:
It's included per user request and unsupported beyond that. Just keep trying until it let's you get through. I've played with it before and laughed when I was "locked out" my own phone cuz it was freezing/rebooting.
[Verizon Samsung Galaxy S III] Ridl3y:
As soon as I touch it, the phone does a quick restart. Nothing is working. I'm about to cry!

I can't believe something THIS BROKEN is included in the settings. This could potential cause my life some harm professionally because all of my data was backed up on here ready to transfer. Please tell me there is a way to disable this lockscreen so I can get to the pattern code screen.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Several people requested it which is why its included and there's been a disclaimer in the first post for months. Ripple effect and AOSP lockscreen are incompatible. Unless you can get through the lockscreen then all I can suggest is a dirty flash without wiping to see if you'll get through. It's been quite a while since I messed with AOSP lockscreen from what I remember, I either

-let it reboot then sit for a minute which took quite a few tries OR

-dirty flashed without wiping OR

-clean flashed

Your options are quite limited if the first two don't work. I'm unaware of any other way to get through your lockscreen directly to the pin.
[Verizon Samsung Galaxy S III] Ridl3y:
I don't care about any disclaimers. This feature should be REMOVED from this mod because it is BROKEN! There should be no combination of features allowed in the settings that can completely LOCK YOU OUT of your phone for good. I have no way of transferring any files onto my phone in order to do a dirty flash. I am so furious right now! There has to be a way to remove this damn lockscreen. Is there a file I can remove from the system settings?
[Verizon Samsung Galaxy S III] unhappybirthday:
When you say "backed up" what do you mean? Files on the "internal sdcard"? If so, that should survive a wipe of data (which should get you back to working condition). If your critical data is stored within applications (in internal memory), you'll lose it.

I hope someone has other ideas for you. If you rely on your device professionally, you may want to consider sticking with stock in the future. Not trying to be a d*ck - just know Samsung focuses on stability over all else.
[Verizon Samsung Galaxy S III] Ridl3y:
Maybe Beans can send me a file to dirty flash without the lockscreen option? I don't know what else to do. I cannot transfer Beans 19 to my phone in any way because my phone is locked out. This makes it impossible to try a dirty flash.

Is there any way to access my files with my pc so I can try to pull off the things I need from my external memory?

Can someone chat with my live somewhere? This is something I need to fix ASAP and I can't sit here and wait for replies.
[Verizon Samsung Galaxy S III] prdog1:
It is not impossible if you wipe and flash in recovery. Wipe data and system. All sd cards will remain intact. Original Beans file should still be on SD card. Will clear the pin code and AOSP lockscreen. . The boot menu to recovery is just a convienience. Boot manually into recovery and dirtyflash or reflash whatever you want. Or-Pull the sd card. Plug it into PC with adapter. Change what you want. Then boot into recovery and flash what you want. I Don't see a problem except operator error and inexperience. Long as rooted and custom recovery you can't be locked out unless you brick it. And this has been disclaimed on every rom since AOSP was made available over a year ago. :cool:
[Verizon Samsung Galaxy S III] unhappybirthday:
If you have TWRP recovery, you might be able to go into the file manager and rename the lockscreen file. I don't know what it is but maybe someone else does.
[Verizon Samsung Galaxy S III] prdog1:
That will just cause a FC since the lockscreen would no longer be available when it calls for it. Maybe if swapped both names but there are several files for each screen that it calls for. If he is this lost doubt that is in his experience level. Just needs to wipe and reflash. No big deal. . :cool:
[Verizon Samsung Galaxy S III] Ridl3y:
I have text messages that were not backed up, files on the internal memory. Tons of settings set for apps that I will not be able to recover again.
[Verizon Samsung Galaxy S III] zachf714:
I remember you said on the bones thread that normally you back up just the data partition and clean flash, then restore that .. Do you think that will work for him
[Verizon Samsung Galaxy S III] prdog1:
Nothing we can do about that. Dirty flash is never recommended in the first place. That is why we have TIBU, MyBackup Pro ect. I still never restore any app data. It all corrupts sooner or later anyway. Still no reason can't try another dirty flash just so can open phone. My guess is won't work without clearing system/ data since the settings won't change way rom is set up. Nothing on sd cards is affected anyway unless you wipe them. Pull sd card and save is same as not wiping sd cards. Wiping system and data will not clear cards either. Since no backup, loss of app/system data is part of the game. If made backup nandroid of system before flashing new rom would still have all that available. Now it is down to whatever it takes to open device gonna have to live with the consequences of your actions. Live and learn. :cool:

PS. If jump between AOSP and TW messaging you gonna lose all MMS anyway.
[Verizon Samsung Galaxy S III] Ridl3y:
Okay so how am I supposed to but the zip file on my sd card? I don't have a card reader.... What am I supposed to do?

I guess what I'm saying is that it has been AGES since I've rooted my phone. I forget how to sideload this zip file on here.
[Verizon Samsung Galaxy S III] hoodieNation:
Yes, in that there are no indicator lines, but I'm just wanting stock white icons.
[Verizon Samsung Galaxy S III] prdog1:
You delete it after the original flash? If not it still there where you left it. lol Flash same way you did first time. :cool:
[Verizon Samsung Galaxy S III] Ridl3y:
I deleted it a while ago. Didn't think I'd need it on there anymore. Oh well.
[Verizon Samsung Galaxy S III] Artimis:
I created a flashable zip to get rid of the indicator lines on mine.....the only problem is there is still a gap from where they used to be between the icons and the notifications area (I don't have the brightness slider).

I can upload it for you to try if you'd like but I made it for beans18 as I have not yet updated to 19 so I have no clue if it will work for you or not. You can try at your own risk.
[Verizon Samsung Galaxy S III] prdog1:
2 choices. Run to radio shack and get a cheap adapter or Odin back to stock and for sure lose it all anyway. nandroid backup was put in recovery for a reason. 3 actually. Crank phone with USB cord attached to phone. Don't touch screen and sd cards should show up on PC unless that stupid pin code blocks it. :cool:

Edit: Yup. Pin code blocks it.
[Verizon Samsung Galaxy S III] Ridl3y:
Here's a question. Is there a file in the systems folder that I can edit to a different lockscreen? Surely there is a file I can unzip and change the value.
[Verizon Samsung Galaxy S III] prdog1:
Can try swapping the names of files but would have to change at least 2. Stock is Keyguard_circlelock_clock_widgit.xml. AOSP is keguard_unlock_tab.xml. They are both in system/framework/ framework-res/layout. There are also layout and other files that go with each. Not sure if have to change all to keep from FC. Could try those 2 first. Must be renamed perfectly. Should have been able to open even with ripple and ink. Reboot is usually caused by custom kernel altho you device just may not be able to handle it.. Ripple and ink usually jack with it when have lockscreen rotation enabled and it hangs on landscape. :cool:
[Verizon Samsung Galaxy S III] Ridl3y:
Do I need to resign the APK?

I was thinking more along the lines of changing the android settings file to pick a different lockscreen value.
[Verizon Samsung Galaxy S III] prdog1:
No. If resign it will for sure FC. You not changing code just name. Still not sure it will work. :cool:
[Verizon Samsung Galaxy S III] Ridl3y:
[/COLOR]Just tried it... it just freezes and restarts. SO close
[Verizon Samsung Galaxy S III] prdog1:
Radio Shack fixing to close in Texas. Walmart open 24/7. :p:laugh::cool:

---------- Post added at 08:10 PM ---------- Previous post was at 08:05 PM ----------

More than likely won't work cause there are a lot of xml and smali changes made so it works on the fly. That is why I don't like on the fly mods. I hard code what I want since not gonna change it anyway. :cool:
[Verizon Samsung Galaxy S III] vmancini3:
Only way I can think of for you to fix your problem and not lose any data is for someone to somehow be able to upload their WHOLE nandroid backup for you...you download it and put it on your external sdcard via a card reader.....then manually boot into recovery and choose advanced backup and restore...then choose restore system only! Maybe someone who has a devhost or android file host account would be nice enough to do that......or it could even be a nandroid of a fresh install.....you just need to have the system partition reflashed/restored and you should be good to go!
[Verizon Samsung Galaxy S III] prdog1:
That is the problem. He has no card reader. That is why Radio Shack and WalMart post. Actually may only need to reflash secSettings so it resets to default. Not sure where the settings data is stored. :laugh::cool:
[Verizon Samsung Galaxy S III] Ridl3y:
I am able to transfer files. I found my card reader. I've been messing with the settings.db files and seeing if it changes. No luck so far
[Verizon Samsung Galaxy S III] prdog1:
If have card reader you know what to do. Dirty flash/wipe data and dirty flash/why syatem and flash. Or pull secSettings and see if flashing it only fixes. I will upload a nandroid. It up to you to make it work but must be on TWRP and open backup file and place in folder under your serial number. If never made a backup may not have the required folder to make work. :cool:
[Verizon Samsung Galaxy S III] Ridl3y:
I've tried a dirty flash and the setting still stayed. (Same lockscreen selected) Where is secsettings located?
[Verizon Samsung Galaxy S III] prdog1:
System/app. Probably won't matter since dirty flash flashed it anyway. Need to backup what you can and wipe system/data and reflash. :cool:
[Verizon Samsung Galaxy S III] Ridl3y:
I always used clockword to back up my phone.
[Verizon Samsung Galaxy S III] prdog1:
I don't use CW. Sucks on this device unless have to use since parts built into CM. :cool:
[Verizon Samsung Galaxy S III] Ridl3y:
I sent you a pm.
[Verizon Samsung Galaxy S III] prdog1:
You gonna play around all night and get nowhere. Make a backup now. Wipe device and reflash. Then will have phone. Make a backup of clean flash. Then try restoring data only in advanced restore. Will give app data back. May lock it back down and may not. At least then can try later to save data from the bad backup. :cool::cool:
[Verizon Samsung Galaxy S III] vmancini3:
Dude, if prdog1 is uploading a nandroid, then you should be golden....just do an advanced restore and choose to restore system only!