yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] prdog1:
Yea. Will have to hack it like you did for 4.1.2. lol The roms are working as designed. I imagine the shutdown of bluetooth to wifi tether was another ploy by Verizon to collect more data money. :rolleyes::cool:
[Verizon Samsung Galaxy S III] enohand:
So Prdog

you seem to be the "most Knowledgeable" person active in this thread anymore...

any chance to get the mirror cast working with this rom & chromecast?

I downloaded the #Mirrorenable app which there is a thread for here on XDA, & followed the instructions but it does not work.

I then posted what the OP of said thread said was the problem for the S3 in this thread, which you then said was already "in/working" & wasnt the cause.

so ....yeah...

how to get mirroring enabled. ??
[Verizon Samsung Galaxy S III] prdog1:
You either have to flash to Stock Kitkat and lose bootloader (which probably wouldn't work anyway if need that fix) or flash an AOSP KItKat rom. :cool:
[Verizon Samsung Galaxy S III] enohand:
dang...i was hoping to get it working on alliance....
[Verizon Samsung Galaxy S III] prdog1:
Don't know. When app starts says need KitKat. Also the roms that are working on International S3 are CM11. Only AOSP roms are built from source and allow changes to make file. Seeing as how Chromcast apps such as Youtube work on stock 4.3 screen Mirror must be exclusive to KitKat. :cool:
[Verizon Samsung Galaxy S III] F'n Amazing:
just a shot in the dark, but anyone having trouble with phone calls. all of a sudden the people on the other end of my calls cannot hear me at all. I can hear them clear as day, but they get nothing on my end. i know its not the microphone because voice commands for google now and voice to text works perfectly fine. not sure if its rom related so i figured i'd ask here first.

any help is much appreciated.
[Verizon Samsung Galaxy S III] pyrite123:
Sometimes I found the mute button to get pressed somehow. Check to make sure that isn't happening to you lol
[Verizon Samsung Galaxy S III] vmancini3:
I have never experienced that before.....the easiest and first thing I would try is to boot into recovery and wipe the cache and dalvik cache....seems to work for a lot of problems and can never hurt to do it anyways!
[Verizon Samsung Galaxy S III] F'n Amazing:
yeah i thought of that, wasnt it

tried this as well, didnt make a difference.

so weird, just randomly happened out of the blue
[Verizon Samsung Galaxy S III] pyrite123:
Did you try flashing a different modem?
[Verizon Samsung Galaxy S III] erisx:
How necessary is it to install the modem? I'm messing on a phone that's on cyanogenmod at the moment and the link for the modem doesnt work.
[Verizon Samsung Galaxy S III] travisjshepherd:
is this SS compatible?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Yes, if you accepted the VRUCML1 4.3 OTA.

No if you accepted the VRUDNE1 4.4.2 OTA.
[Verizon Samsung Galaxy S III] rlreddy:
Crickets? I never like when a forum goes quiet - doesn't make me feel warm and fuzzy about my favorite ROM! :crying:
[Verizon Samsung Galaxy S III] phillipmckinnish:
Man this rom is solid...I've been going back and forth between this and 4.4 roms,But I always come back...This time this has been my DD for over a month,and I have not flashed anything else....I don't know about you but for me that's a record for me..LOL :laugh:
[Verizon Samsung Galaxy S III] prdog1:
Reading the 4.4 AOSP/CM threads don't think it takes much more than stock TW to beat them. :p:laugh::cool:
[Verizon Samsung Galaxy S III] Hobart!:
Just came back to this and noticing something familiar.... When I hit the home button to go home in my tw launcher from an aop or browser it alwaudys pulls up my task manager. Like I long press the home button when I didn't. Seems very sensitive. Anyone else experience this? Is there a setting?
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Could it be am exposed module like Wanam messing with the home button
[Verizon Samsung Galaxy S III] Hobart!:
I haven't enabled it....I'll check though
[Verizon Samsung Galaxy S III] ImYoungxD:
I also get this problem when I'm in an app. I thought my button was defective. While in the home screen, the home button doesn't bring up the task manager unless I hold it for two seconds.
[Verizon Samsung Galaxy S III] ATGkompressor:
I was getting that too. I never found out what it was. I went back to stock Rom and running Wanam and XBlast. Had a problem with Wanam decreasing my volume on its own when I had my headphones in and when I was in the messaging app it would make my text larger. Had to disable the expanding volume option. But the home button thing is crazy...
[Verizon Samsung Galaxy S III] Hobart!:
OK so I am not the only one! I'm not crazy!!!! What I did is go to recovery and clear cache and dalvik...also went to settings and changed the long press home to medium or whatever. I did settings first and nothing changed but after clearing cache and dalvik it seems to have gone away. Not sure if I fixed it or not but it seems to have gone away for now. I wonder what could cause that? Maybe a Dev would know...A setting in ROM maybe????

And yes it happens only when in an app not on home screen. Long press works normal on home but when in app short press acts like long press and hold brings up task manager.

I have clean flashed this several times over the last several months and this bug is there every time I flash..just fyi
[Verizon Samsung Galaxy S III] stueycaster:
When the thread is quiet it means the rom runs right. The real active threads are where people are all looking for help with their problems.
[Verizon Samsung Galaxy S III] sk2:
Or an update drops
[Verizon Samsung Galaxy S III] enohand:
an update would be sweet.

I really dont want to go to a AOSP. but would like to do the mirror cast stuff..

please dont make me go back to cyan....i really love this rom
[Verizon Samsung Galaxy S III] unhappybirthday:
Nobody has been able to get the KitKat TouchWiz kernel to fully boot with the unlocked bootloader/firmware yet.
[Verizon Samsung Galaxy S III] evertking:
any device?

Any device..?? Can I flash this to a straight talk s3? Sorry if this has been asked before.
[Verizon Samsung Galaxy S III] DuhCiphered:
Color Guide

Anyone know why I would have issues flashing the color guide via recovery? I did it fine the first time I installed alliance but I was using CW to flash it, I have since switched to Philz Touch and now when I try flashing it it says installation aborted. I have tried moving it to internal and flashing, side loading, changing permissions, downloading a fresh copy and tried all those methods again and get the same thing. Any Ideas?
[Verizon Samsung Galaxy S III] pyrite123:
Anything d2lte can be flashed but if it says d2vzw then it's only for Verizon s3's
[Verizon Samsung Galaxy S III] Hobart!:
So today my media sound stopped working...ringtones work..text work...but when I play a video no sound! Any ideas? All volumes up! Wiped cache...reflashed without wiping data...Can't figure it out?
[Verizon Samsung Galaxy S III] prdog1:
Probably corrupted video player. Dirty flash won't fix if data corrupted. :cool:
[Verizon Samsung Galaxy S III] Hobart!:
So clean flash?
[Verizon Samsung Galaxy S III] prdog1:
If wiping dalvik and cache and dirty flash don't fix not to many other options. Depends which video player also. Try clearing data only for it in app management. :cool:
[Verizon Samsung Galaxy S III] Psychotacon:
I too have the long press bug. I don't think I had it in the beginning either. This ROM is perfect, for me at least. I've been trying some 4.4 ROMs but their always missing a feature or two. Alliance was just becoming a hassle due to a few bugs like the long press one (perhaps some issues due to my own error) so I wanted to move away. I plan to get the S5 so I probably won't come back to Alliance until then.
[Verizon Samsung Galaxy S III] GeTex:
So i have a T-999 with a really messed up something. It lags, stutters, crashes, reboots, and has issues non stop. It's on 4.3, how would i go about a total clean flash of Alliance to help fix the phone to run super smooth and seem like new. I think it has a bad bootloader or a bad modem or bad something. It's just horridly bad though.
[Verizon Samsung Galaxy S III] kentompkins:
Nevermind.

:laugh:
[Verizon Samsung Galaxy S III] mytoy1:
unlock screen

anyone know how to remove the unlock options on the phone ever since I started using the mobile hotspot if made me put a lock code on the phone all features are grayed out to remove lock screen ty guys for any help u can give me
[Verizon Samsung Galaxy S III] pickaxe300:
I had to dirty flash to get rid of it.... Hope you find an easier way! I just use the built in hotspot now.
[Verizon Samsung Galaxy S III] GTvert90:
I wonder if it's the ported one from the original nexus 4 system dump or from aosp
[Verizon Samsung Galaxy S III] tnngng:
Yeah I love AOSP screen. Wish it has weather tho.

You could use Dafox mod method to change the lock icon to any image/logo you want

---------- Post added at 07:45 AM ---------- Previous post was at 07:43 AM ----------

It is the one from Nexus 4
[Verizon Samsung Galaxy S III] jlee08517:
Beans, Didnt build 3 have a working inverted gtalk. for some reason I cant seem to install that on my own in build 5..
[Verizon Samsung Galaxy S III] dpaine88:
Has anyone flashed this on the ROM yet?
[Verizon Samsung Galaxy S III] dukins:
Yep works perfectly. Flashed the aosp mms and have all the features, toonz kernel, kinda crap mods. I am now golden! :D
[Verizon Samsung Galaxy S III] ryan1977:
Are otas blocked
[Verizon Samsung Galaxy S III] :
I'm not sure if its because I had smart stay or rotation on, but when receiving notifications after the phone was on, it would freeze up and the only thing that worked was shutting the screen off. In order to turn off the phone I would have to do a battery pull

Besides that if it's because of smart stay I'll turn it off
[Verizon Samsung Galaxy S III] nativesmiley:
is it the aosp mms from the jellybean roms or is from a tw jb rom??
[Verizon Samsung Galaxy S III] GreenMunky:
I'm having the same problem, my SD card won't mount either. I have a 64 GB xc card. If there's not a fix this is a very disappointing deal breaker because otherwise this ROM is awesome so far.
[Verizon Samsung Galaxy S III] dukins:
This is how to install. Since you are already on a rom that has the option of mms messaging, SELECT it, then go to thread http://xdaforums.com/showthread.php?t=1998769 and flash the fix in the op and you should be golden.

If you selected the tw jb messaging you will need to install the aosp mms by selecting it in aroma or installing manually pushing it to system/app. It can be found here http://xdaforums.com/showthread.php?t=1921429. Then flash the fix that I posted above. Hope this helps! :good:
[Verizon Samsung Galaxy S III] RJFrank33:
Hmmm... My sd card is recognized fine. There's got to be something funky going on with your setup. It would seem if it was a rom problem it would affect everyone. I'd hate for it to be a deal breaker since this is such an awesome rom. I'm sure you already tried a full wipe and then did a cache and delvik wipe again before rebooting. Maybe try fixing permissions also. I don't know...

Sent from my S3 on Tapatalk.
[Verizon Samsung Galaxy S III] GreenMunky:
Yep, completely clean install... except for the cache wipes AFTER install and before rebooting... is that recommended? Are you using a 64GBXC card? Because it seems that myself and the person before me who reported this problem are using the same kind of card. My SD card works fine with CleanROM 5 so I know its not a JB compatibility problem. I dunno man...
[Verizon Samsung Galaxy S III] eman3316@optonline.net:
Can anyone confirm just flashing the fix will work on this ROM?
[Verizon Samsung Galaxy S III] GreenMunky:
Also, when using the TouchWiz 4x5 launcher I was unable to see the AOSP Lockscreen mentioned in the OP. Do you have to use Nova or another 3rd party launcher for that to work?
[Verizon Samsung Galaxy S III] Inkedadrenaline:
No I'm using TW 4x5 launcher and aosp. It's under lockscreen under settings

Tapatalk'd / Galaxy SIII on Jelly Beans
[Verizon Samsung Galaxy S III] GreenMunky:
Strange... under Lockscreen in options I don't see AOSP... just the normal TW ones.
[Verizon Samsung Galaxy S III] Jihoonie:
For the time being you can use Kindacrap mods 2.4 for flashlight in lockscreen. Only thing is that the light doesn't turn off when u let go of the home button, you have to unlock the screen
[Verizon Samsung Galaxy S III] vudugan:
Deleted
[Verizon Samsung Galaxy S III] Relentless D:
System Settings > Lockscreen > Lock Screen Options > Enable AOSP lockscreen
[Verizon Samsung Galaxy S III] Hobart!:
There is a lock screen option in settings..once in..lock screen options....all the way at top..check aosp option
[Verizon Samsung Galaxy S III] flooritnfly:
My GPS will not lock at all. I cleared cache and dalvik and it still doesn't lock.

Any ideas?
[Verizon Samsung Galaxy S III] Hobart!:
I had that problem too. Are you using GPS status to get lock on? Get from play store and open.Go to manage GPS state And download. Make sure you are in a clear area. I did all that and still didn't lock....but eventually it did. After first time I had no problems.
[Verizon Samsung Galaxy S III] flooritnfly:
I will try that thank you!
[Verizon Samsung Galaxy S III] griz.droidx:
GPS status has been recommended A lot in the past. Still have it on mg dx
[Verizon Samsung Galaxy S III] joe_blow_xbox:
Whence I have this I take off the phone back and tighten all the visible screws. I get lock afterwards. The gps antenna contact gets loose.
[Verizon Samsung Galaxy S III] OnceAMatrixMan:
If all else fails delete maps and reinstall. Solved the GPS lock and maps crapping out after an hour issues.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Jdelta9889:
Try this

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

The method discussed on this forum always works for me.. My GS3 is over 2 years old now and I have had to do this 3 or 4 times..
[Verizon Samsung Galaxy S III] mytoy1:
anyone know how to remove the unlock options on the phone ever since I started using the mobile hotspot if made me put a lock code on the phone all features are grayed out to remove lock screen ty guys for any help u can give me
[Verizon Samsung Galaxy S III] Manwthgun:
Pin Issue

Are you sure this is related to your hotspot and not Exchange security permissions? If you have your companies email on your phone they can force you to use a pin lock. You can test it by removing your email acct from your phone and see if it resolves the pin issue. There are ways around that as well if you want to reinstall your Mail app with the no-pin "hack" or a plug-in. But, of course you would then be breaking IT security policy so do so at your own risk as always. Does that help
[Verizon Samsung Galaxy S III] mytoy1:
No email from company
[Verizon Samsung Galaxy S III] Manwthgun:
Have you tried just dirty flashing the ROM?
[Verizon Samsung Galaxy S III] mytoy1:
Yes. Tried did not fix. I found a fix ty for your help with the the problem
[Verizon Samsung Galaxy S III] talon4x4:
Encryption

My company is now requiring that we enable encryption on our phones. I have the latest ROM installed and when I launch the Android encryption it runs for about 30 seconds and then the phone just reboots. I don't think it is actually encrypting anything that quickly. Anyone else able to get encryption working on this ROM??
[Verizon Samsung Galaxy S III] mav3rick478:
I actually think you need to wipe your phone and encrypt from the beginning before you do anything else, but I could be wrong.
[Verizon Samsung Galaxy S III] syst3merror:
In the install directions it states first to install the ML1 modem.....is this really important/necessary? because the link in the first post for the modem is dead. :eek:
[Verizon Samsung Galaxy S III] talon4x4:
I did try that. Wiped and flashed phone with ROM and then the first thing I did was run encryption. I really hope I don't have to go back to the stock Android ROM. :crying:
[Verizon Samsung Galaxy S III] gpz1100:
If you have the wrong baseband you won't have any service.
[Verizon Samsung Galaxy S III] vmancini3:
That's not true....however your service MAY not be the way you'd expect!

As for me, MF1 and ML1 give me the same results! And I'm not looking at the signal bars, I'm talking about the db level that measures the strength of your signal.
[Verizon Samsung Galaxy S III] prdog1:
NE1 seems to be about the same also. Some reporting a little better with NE1. Has more to do with the towers in area than anything. :cool:
[Verizon Samsung Galaxy S III] gpz1100:
Just went through this a few days ago with someone. They had an older modem with this rom. The phone still booted, but was unable to obtain any service.
[Verizon Samsung Galaxy S III] vmancini3:
Probably more obvious when you're already in a fringe area.....but all I can say is that all our phones react differently and for me it doesn't matter what modem I use.... LK3, MB1, MF1, ML1, NE1...... I still get exactly the same reception.
[Verizon Samsung Galaxy S III] prdog1:
Pretty much same result here. If flooded with 4G the modem won't show much difference till get out in the fringe areas. :cool:
[Verizon Samsung Galaxy S III] ATGkompressor:
I've noticed a considerable difference on NE1 as far as cell reception and 4g. Wi-Fi is crazy too. I love this kit Kat update. Already had a locked bl..didn't have anything to lose
[Verizon Samsung Galaxy S III] Benjamin1966:
This Rom is a big waste of time.

I'm wasting so much time playing with it, I've developed relationship troubles with GF.
[Verizon Samsung Galaxy S III] MIKEYSAKZ:
Whoa that's like my car insurance

Yo fault
[Verizon Samsung Galaxy S III] talon4x4:
In case anyone was wondering, you need to use a lock PIN of at least 6 digits. My company only enforced 4 digit PINs and that doesn't work with encryption. Would have been nice if the Android o/s actually came back and told you that but it doesn't
[Verizon Samsung Galaxy S III] Divey1130:
Getting ready to flash this rom and was wondering about the ML1 modem. The link in the OP does not work but I found 2 files elsewhere.

VRBMF1 firmware and ML1 modem. Do I need to flash the firmware first then the modem or just the modem.

Thanks
[Verizon Samsung Galaxy S III] vmancini3:
JUST THE MODEM!!!! :D:thumbup:

Here's another link in case the one you have doesn't work...

https://www.dropbox.com/s/3rkt5r62cpzv4m6/d2vzw_ML1_modem.zip?dl=0
[Verizon Samsung Galaxy S III] prdog1:
Only flash the firmware if you are on MB1 or lower. If already on MF1 don't need it. If on ML1 and/or using safestrap don't flash firmware. It will soft brick your device. :cool:
[Verizon Samsung Galaxy S III] vmancini3:
Yeah....I should've been more thorough and said that! ??
[Verizon Samsung Galaxy S III] prdog1:
I added even more for insurance. :p:cool:
[Verizon Samsung Galaxy S III] Divey1130:
It says I am on the VRLHE. It's been awhile since I have flashed my phone so I am trying to remember it all. Just finished a nandroid backup just in case.

Thanks
[Verizon Samsung Galaxy S III] prdog1:
I would flash the firmware and update Recovery. :cool:
[Verizon Samsung Galaxy S III] Divey1130:
Oh, so it's been that long. So update Clockwork Mod, flash the firmware, flash the modem, then flash the rom. This modem flashing is new to me but from reading the post it seems like it is a must for 4.3 and up.

Thank You for the help, much appreciated.
[Verizon Samsung Galaxy S III] prdog1:
Yea. Different bases don't play well together. If I'm not mistaken you are still on ICS. Ice Cream and Jellybeans not a good combination. :cool:
[Verizon Samsung Galaxy S III] Divey1130:
Ya, search for a good rom as a DD and usually stick with it. Now it's time for an upgrade and from reading this thread, it seems like a pretty stable rom.

Thanks again and hopefully I return with a :good::laugh: and not a :crying:
[Verizon Samsung Galaxy S III] prdog1:
Wipe dalvik, cache, system data and internal sd card. Put the zips on external. Internal sd needs to be wiped because 4.3 is gonna set up a different file format and will not be able to find some files if don't wipe and replace after. Samsung modem =HTC/Moto radio. They build new ones for a reason. :cool:
[Verizon Samsung Galaxy S III] Divey1130:
Worked like a dream. Very fast and responsive rom so far. So far no issues but I will mess with it some more. One thing I cannot figure out is the dam lock screen. I want to use the the one that has a google symbol in the center then you can swipe to certain spots to open the phone or open an app/shortcut. I can't get it to work.

Thanks
[Verizon Samsung Galaxy S III] mclane5:
Wow, amazing ROM so far. Beer on the way!
[Verizon Samsung Galaxy S III] flooritnfly:
I thought that for the longest time, but I just discovered and fixed the problem! :

There was a teeny tiny screw that was somehow lodged on top of the

antenna contact (or at least what I think was one of the contacts) and I

pryed it out of there, rebooted and now my speeds are BOSS! :good::good::cool:
[Verizon Samsung Galaxy S III] conquesoextra:
Hi guys,

This is my first day whit the S3, after a couple hours reading i have some doubts:

Currently im on 4.1.1 (stock) whit LK3 modem, rooted whit last version of CWM, if i understand i need to:

1.- Flash a newer modem (ML1) whitout firmware - via CWM.

2.- Wipe all.

3.- Flash rom (no gapps needed).

¿Its ok? thanks!
[Verizon Samsung Galaxy S III] Milly7:
Yes.
[Verizon Samsung Galaxy S III] conquesoextra:
Damn :(

Now I can not do anything , I can't load in to recovery mode.
[Verizon Samsung Galaxy S III] -somebody-:
can try using Odin with the stock MF1, then youll need to re-root, re-unlock your bootloader, etc.... but worth a try. i believe any stock tar after MF1 will lock you down permanently.
[Verizon Samsung Galaxy S III] conquesoextra:
Thanks bro, downloading full ML1 firmware...

For the record: this ROM can't be flashed over 4.1.1 stock.
[Verizon Samsung Galaxy S III] prdog1:
Don't flash ML1 full firmware or will be forever locked. Will have to use safestrap, stock kernel and never again AOSP. :cool:
[Verizon Samsung Galaxy S III] -somebody-:
yeah i caught that earlier and immediately corrected my post, ML1 is bad news bro. you want MF1 or lower.
[Verizon Samsung Galaxy S III] prdog1:
That Verizon message means the bootloader is locked. :cool:

#1-Need to Odin MF1 firmware.

#2- Root, unlock and install recovery using Beans Casual.

#3- Update Recovery.

#4- Flash ML1 modem.

#5- Flash Rom.
[Verizon Samsung Galaxy S III] jessenj:
I just threw this rom on my newish S3 I had sitting in my drawer cause my wife's got its screen cracked. I made a TiBu and a NAND backup, but after I installed Alliance on the my S3 and ported her apps, I can't get any media to play through the phone speaker. The speaker works just fine with notifications and ringtones, but when I try playing Pandora, LastFM, Spotify, Google Play, Youtube, etc, there is no sound through the speaker, but if I plug in headphones or connect to a BT device, the sound is just fine. What am I missing? Also, is there a built in volume hack or do I need to just flash the Volume Hack that I used to use way back when?
[Verizon Samsung Galaxy S III] prdog1:
Don't know why speaker not working but old sound hack still works.
[Verizon Samsung Galaxy S III] jessenj:
Thanks. Have a link handy? I can Google but figured if someone had it available, it'd be worth asking. As for the media sound not coming from the speaker, I've read some other threads from other roms saying that other people have had issues with Viper or the headphone port, but I tried an app that is supposed to force sound to the speaker and I tried that too but so far nothing seems to make the media audio come from the speaker. I can't figure out what else is left to try. I did a cache wipe, battery pull, toothpick in the headphone jack to see if there were any obstructions, and a few app uninstall/reinstalls and I still can't get it working. What's been the best kernel to run with this rom? I've always used Lean Kernel in the past when I worked on my S3, but since I've been on a Note 3 for over a year, I haven't had much involvement with the S3 and feel like I've lost touch.