yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] draexo:
Google Camera isn't compatible with 4.3??!! Any work around?
[Verizon Samsung Galaxy S III] pyrite123:
When your phone reboots without being powered down properly (battery pull, battery died, crash, etc) ktweaker settings don't load properly and give that message the next time you open it. Until then your phone uses the kernel defaults. In my case the ktweaker defaults cause random reboots because the kernel voltages are under clocked, meaning I always raise them by 10 if I use that kernel.

prdog's solution should fix the slowdowns :)

did you try googling 'Google camera apk' and installing it outside of the play store? Same thing happens with Google Now Launcher.
[Verizon Samsung Galaxy S III] supercell2000:
I had the same issues as you. It was definitely Swiftkey causing the lagginess. When I switched to Google keyboard the problems went away.
[Verizon Samsung Galaxy S III] aypeeootrek:
Swipe had the same problem. What's with all the keyboard lag?
[Verizon Samsung Galaxy S III] supercell2000:
and why is happening only recently?
[Verizon Samsung Galaxy S III] aypeeootrek:
I second this. Think it's a tw 4.3 thing? Feel like I noticed it once beans updated to 4.3
[Verizon Samsung Galaxy S III] prdog1:
My Swiftkey goes as fast as i can force it. I run stock base so it's not 4.3. If wiping caches don't fix don't know where lag is coming from.
[Verizon Samsung Galaxy S III] draexo:
Ugh..... There goes Google Maps closing on me when I need it
[Verizon Samsung Galaxy S III] pyrite123:
All the popular keyboards started adding the new emojis and that's causing a lot of people lag and fc's. Also did you make sure to disable the swiftkey notifications and do you use swiftkey cloud? Have you tried changing to a different theme? It's usually something minor making the difference.
[Verizon Samsung Galaxy S III] aypeeootrek:
I've switched themes but I'm going to look into the other two things. Wish I could go back to swype but that lag was unbearable. This is some what bearable
[Verizon Samsung Galaxy S III] pyrite123:
Have you tried uninstalling the keyboard, making sure all the data folders are deleted, and reinstalling? I'd make sure to go into recovery and delete dalvik and cache before reinstalling the keyboard. You could try the same with Swype, too. You can also try clean master or something similar.
[Verizon Samsung Galaxy S III] aypeeootrek:
Thanks for the tips. When I get the time I think I made need to do a fresh install. Seems like a lot more aside from the keyboard is lagging. I used to have this same problem on my dx. After a month or two would just get crazy lag. And I never mess with voltages or anything
[Verizon Samsung Galaxy S III] pyrite123:
You said you're on ktoonz? You need to open ktweaker and do the following:

1. Go to CPU voltages, hit menu, raise all voltages by 5 and raise by 5 one more time for a total of 10. This should help your hardware to become more stable.

2. Try using a different governor and IO scheduler. I would recommend ktoonservative if you know how to disable mpdecision. If not try Wheatley or Interactive and see if the lag goes away. For IO schedulers I only use vr or sio. They appear to give the quickest results and best benchmarks when I tested all of them.

3. Try enabling auto hotplug

Hope this helps! The first will definitely help I'm sure. I don't like when people underclock kernals by default. Not everyone's hardware is the exact same and some may have very slight defects that prevent them from being stable at those levels. And underclocking doesn't save as much battery as people think.
[Verizon Samsung Galaxy S III] aypeeootrek:
Hey man, thanks for the advice. For kernels, i've always only messed with the frequency levels, governors and scheduler. Barely ever the villages. I did everything you said and I'll see how it goes for a while
[Verizon Samsung Galaxy S III] pyrite123:
No problem. I've gotten loads of help here so it's only right to return the favors and share what I know when I can. Hope it works out for you :)
[Verizon Samsung Galaxy S III] royalflush5:
That happens to me when I use it, at least once per session, it drives me insane.
[Verizon Samsung Galaxy S III] pyrite123:
You need to completely remove maps and dl a fresh version. Worked for me one time.
[Verizon Samsung Galaxy S III] LegoFarmer:
Will this be rebuilt on the KK base now or no? I'm just curious what the word is on that at the moment.
[Verizon Samsung Galaxy S III] pyrite123:
Every time someone asks that question Beanz takes a one week break from working on the next build.
[Verizon Samsung Galaxy S III] LegoFarmer:
Message received. I am sorry haha.
[Verizon Samsung Galaxy S III] daimerion:
Not even possible at this point...unless he does it for the locked safestrap people
[Verizon Samsung Galaxy S III] pyrite123:
I don't even care about kitkat, I'd just like to know if he's still alive and hasn't abandoned the ROM. Not asking for a release date, just wondering what to expect. Love his work :P
[Verizon Samsung Galaxy S III] mav3rick478:
He and a bunch of developers are trying to get the OTA to work for unlocked bootloaders. There's a thread to watch but not comment on in this same section of the forum.
[Verizon Samsung Galaxy S III] pyrite123:
Do you have a link? I'd like to check it out but I can't seem to find it.
[Verizon Samsung Galaxy S III] prdog1:
http://xdaforums.com/showthread.php?t=2793084 :cool:
[Verizon Samsung Galaxy S III] xm41907:
I keep trying KK roms, but continue to return to this one. It's got all the features I want and works well. Still hoping for a KK version of Alliance, but I doubt it will happen. :(
[Verizon Samsung Galaxy S III] droidxxxxx:
This is one bad ass ROM..I'm the same way. When I'm tired of stuff not working right I always come back to this one. lol
[Verizon Samsung Galaxy S III] Stupifier:
What is the general consensus these days on the best/preferred kernel for this ROM? I know everyone a couple builds back was sticking with the stock kernel.....is it still the best?
[Verizon Samsung Galaxy S III] vmancini3:
I don't think there's a way to give you a definitive answer on this....each phone will react differently to the different kernels available, so my advice to you is.....make a Nandroid backup and then flash away and see what works best for you! You can always restore your backup if you're not satisfied with the results!
[Verizon Samsung Galaxy S III] pyrite123:
*still using ktoonz with that tweak* lol it's safe on aosp using kt's 4.4 aosp kernel right? I was about to test it.
[Verizon Samsung Galaxy S III] Mylt1:
ok guys, what am i doing wrong? using CWM to install the modem and rom everything goes fine with the install but when the phone reboots it just gets stuck at the "galaxy SIII" screen. battery pull, reinstall, nothing is getting me to an actual boot up. i installed the modem from the link in the OP. any help?
[Verizon Samsung Galaxy S III] Stupifier:
What tweak are you referring to....just +10 on all voltages??? Or something else?
[Verizon Samsung Galaxy S III] egore93:
Does anybody have the modem they could post? The link is down and i'm not able to download the modem.
[Verizon Samsung Galaxy S III] prdog1:
http://www.androidfilehost.com/?fid=23329332407591786
[Verizon Samsung Galaxy S III] egore93:
Thank you! Your a life-saver! ?
[Verizon Samsung Galaxy S III] funkpod:
Hey, ever have any problem recording video during a live concert? My phone on AOKP gets CRAZY distorted. Don't know if it's my ROM or my phone. Thanks!
[Verizon Samsung Galaxy S III] mav3rick478:
Rom, most AOSP roms have issues with video. At least whenever I ran aosp.
[Verizon Samsung Galaxy S III] funkpod:
Thanks! Never knew that was a downside. Alliance again maybe!
[Verizon Samsung Galaxy S III] LazerDino:
Are you giving it enough time? When I installed it on my phone, it took a long time on the 1st boot.

Sent from my VzwS3 chewin' on 6/18 Gummy.
[Verizon Samsung Galaxy S III] Mylt1:
it was "booting" for almost 10 mins. i figured that was more than enough time. i flashed a 4.1.1 rom and it booted up in less than 2 mins.
[Verizon Samsung Galaxy S III] LazerDino:
That's definitely too long. Assuming you followed the steps in post #13025, I'm not sure what else to tell you.

Sent from my VzwS3 chewin' on 6/18 Gummy.
[Verizon Samsung Galaxy S III] Mylt1:
bless you my friend. up and running now. thank you.
[Verizon Samsung Galaxy S III] enohand:
so yeah...I messed up..

not in a bad way, but I got colorizing happy...

now a lot of app dialog screens & **** are in a state where the background is dark & the text is dark & impossible to read...

(the photowall app is completely black when I try to connect it to my chromecast)

I tried numerous things to fix it,,,but cant get it back to "stock"

short of trying to restore this rom, or a different one anyone have any pointers?

also switching themes did nothing for my problem
[Verizon Samsung Galaxy S III] 47th_Ronin:
You could try to dirty flash the rom, just wipe cache and dalvick.
[Verizon Samsung Galaxy S III] enohand:
on a sde note....

anyway for this to happen?

For those STILL having issues,

Check /system/lib/hw directory for the file "audio.r_submix.default.so".

If it doesn't exist, ask your device maintainer to add audio.r_submix.default to

the product_packages in the device.mk file. (You may not know what it means, but they will.)

trying to get the mirrorcast working, but wont, this is apparently the fix....

it woud be great.
[Verizon Samsung Galaxy S III] flooritnfly:
Anyone noticing slow LTE speeds lately? I always tether every night when I am home and my phone stays on a little ledge in my window every night where I get 4-5 bars of LTE and usually at LEAST 15mbps down (as much as 35) and now I randomly can only get 4-5 mbps down.....

I am using this rom on Safestrap, I even went into Safestrap and booted to CleanRom to try some speed tests on that and there was no difference......

wtf?? :confused::confused:
[Verizon Samsung Galaxy S III] prdog1:
That file is in stock base. Should be in rom. You can check with root explorer. Doubt if that is the problem. :cool:

Call Verizon. That is your tower. :cool:
[Verizon Samsung Galaxy S III] enohand:
^^ im not talking about the color issue with my last post.

according to the Dev that released the mirror enabler, that is what the problem is being reported about the S3.

however, I noticed that alliance is on 4.3 & not 4.4 so that may/probally is the actual problem.....

looks like ill be jumping over to a 4.4 build....unless alliance gets released with a 4.4 build?
[Verizon Samsung Galaxy S III] vmancini3:
Unless the awesome devs here can figure out a way to boot 4.4 on an unlocked device, I (sadly) don't think we'll be seeing ANY custom 4.4 TW ROMs!
[Verizon Samsung Galaxy S III] enohand:
is that the restriction? 4.4 canot be loaded on unlocked devices?

looks like the CM guys have it working
[Verizon Samsung Galaxy S III] vmancini3:
Sorry, let me be a little more specific....they haven't been able to successfully boot 4.4 "TW" on an unlocked device yet.
[Verizon Samsung Galaxy S III] vudugan:
Just want to say thx to this community of GS3 users and techs for the wonderful and welcoming forum. Time for me to move on after having mine since launch. Big props to Beanstown on all he's done and will continue to do and also props to those who've worked along with him. Prdog1 along with other familiars who've taking the time to step up and share their knowledge also deserve and receives a token of gratitude and thanks!!

LG G3 is my next device. Cya's on the other side!
[Verizon Samsung Galaxy S III] prdog1:
[MENTION=2988437]enohand[/MENTION]. As I stated before that audio file is in 4.3. The fix is for AOSP based roms or custom kernels as modding the makefile is only used when building kernels and roms from source. :cool:

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] ccoager:
I have a few questions...

Is this ROM de-knoxed? I have an unlocked boot loader and I'd like to stay unlocked.

Is this ROM root enabled?

Does this contain the binary RIL and not the open source RIL?
[Verizon Samsung Galaxy S III] pyrite123:
This won't lock your boot loader. Yes it is root enabled.
[Verizon Samsung Galaxy S III] prdog1:
#1-- Knox has nothing to do with locking the bootloader.

#2 -- All roms are root enabled unless it's broke.

#3 -- Open source RIL is an AOSP base only thing. All OEM roms have the manufacturers RIL. That is why they have better signal than AOSP based roms. Signal is equivalent to device stock rom.

:cool:
[Verizon Samsung Galaxy S III] thatotherguy..:
Could you port this to t mobile?
[Verizon Samsung Galaxy S III] prdog1:
Beans won't unless he moves to T-Mobile and and gets bored but you can. It is possible. :cool:
[Verizon Samsung Galaxy S III] tsachi:
He did move, didn't he? Has a version for the s5 on T-Mobile.
[Verizon Samsung Galaxy S III] prdog1:
Would probalby have to pick up S3 for testing if he decided to port it. If he builds for S3 he would build for 4.4.2.None of us tend to work backwards. That is why unless we get 4.4.2 booting on Verizon S3 is pretty much EOL. None of use want to lock our bootloaders to run SafeStrap. :cool:
[Verizon Samsung Galaxy S III] tsachi:
Safestrap isn't that bad, would have been happy with 4.4.2 that works that way. I get your point, though. Bad move for developing.
[Verizon Samsung Galaxy S III] prdog1:
SafeStrap is available for 4.4.2 but no one is building roms that are SafeStrap specific. Roms are built for open devices and then ran on SafeStrap.:cool:
[Verizon Samsung Galaxy S III] pyrite123:
I'd just like to see a TW 4.4 rom just so I can have a 4.4 rom with decent signal. :P

Beans and everyone else working on getting 4.4 to load are taking donations right?
[Verizon Samsung Galaxy S III] thatotherguy..:
Oh okay well I just downloaded and flashed the rom and it works and booted just fine so guess he don't need too
[Verizon Samsung Galaxy S III] prdog1:
We all take donations but that don't help us fix it. Surge and other devs into low level coding and kernel developement are looking into it. It is a long process. Lots of files in a kernel.:(:cool:
[Verizon Samsung Galaxy S III] pyrite123:
I just figured a few donations would help raise morale :P

I really hope this will be doable. Really want 4.4 with decent signal...
[Verizon Samsung Galaxy S III] prdog1:
HaHaa. Wouldn't we all. Have had base deodexed rom built and waiting since Odin Tar was available. :cool:
[Verizon Samsung Galaxy S III] royalflush5:
Is it possible to access the camera from the lock screen? I've looked through the options and haven't found anything
[Verizon Samsung Galaxy S III] mav3rick478:
I believe it's in the lockscreen settings, did you allow widgets? It's a swipe from the right side.
[Verizon Samsung Galaxy S III] vmancini3:
Yup....you have to check the box to "allow multiple widgets", then you have a choice between camera or favorite apps. What will happen is you'll turn your screen on and then slide to the right on the top part of the lockscreen!
[Verizon Samsung Galaxy S III] pyrite123:
Came back to this rom again thanks to all kinds of random but serious problems that always sprang up in aosp roms... And I think I'm going to stay here for the rest of my gs3 days. This is definitely my go-to ROM for many reasons. And after flashing the mf1 firmware before installing the ml1 modem and rom fixed every stability problem I ever had. Thanks again Beanz and everyone involved with this thread :) I'm loving it.

---------- Post added at 01:40 PM ---------- Previous post was at 01:34 PM ----------

Is it possible to have this feature on a pattern lock screen? I got torch mapped to the volume up key but I'd like to quick-access camera as well without all the hassle.
[Verizon Samsung Galaxy S III] vmancini3:
It appears that stock behavior is.... the ability to swipe in any direction to view various lockscreen widgets gets disabled when you implement the pattern lock! I just tried it!
[Verizon Samsung Galaxy S III] Gordo1603:
I was able to get it working with an xposed module....
[Verizon Samsung Galaxy S III] pyrite123:
What module if you don't mind me asking? Im assuming *gravitybox or wanam?
[Verizon Samsung Galaxy S III] Gordo1603:
Samsung multiple widgets
[Verizon Samsung Galaxy S III] royalflush5:
Perfect, I had multiple widgets checked but I didn't see the camera option, thanks.
[Verizon Samsung Galaxy S III] stunning:
loving your old build rom Jelly 'Beans' Build 20

awesome rom with long battery timing

having not a single issues

Thank u
[Verizon Samsung Galaxy S III] hoodieNation:
It's still my daily driver.
[Verizon Samsung Galaxy S III] pyrite123:
Thanks mate!
[Verizon Samsung Galaxy S III] Artimis:
So I just upgrade from Beans 18 to Alliance 23 today. One issue that I have noticed immediately is that I am not able to Bluetooth tether when connected to wifi. When trying to enable the BT tether option, there is a pop up saying I must disable wifi in order to enable it. This restriction was not there with Beans 18 (4.1.2).

Does anyone know a workaround?

I like to Bluetooth tether internet for my Galaxy Gear and this prevents that if I'm on my home wifi connection (which is the majority of the time).
[Verizon Samsung Galaxy S III] markkal123:
ok. i just migrated from a andybones.and i am having issues with wifi working in build 23. i am unable to enable wifi. everytime i attempt to turn it on it turns right back off. i installed per directions in OP with total wipe. everything else appears fine. just no wifi. any help please. thanks!

I searched for a fix and found the followoing, but i am not running safestrap. i did select the VRUCML1 stock kernal option when flashing the rom and have also tried the other kernal choices. .

i have pulled battery and rebooted, cycled airplane mode several times, reflashed the rom etc. additionally i nandroided back to previous ROM and have no wifi issues. so i'm guessing the issue resides somewhere within alliance rom. perhaps a setting or two which i may have missed?

SOLVED: deleted data/misc/wifi/wpa_supplicant.conf then rebooted and POOF! all is well. "wpa_supplicant.conf" stores wifi SSID and passwords.
[Verizon Samsung Galaxy S III] Manwthgun:
I hope this doesn't come across as a noob answer. Are you sure your not trying to turn on WIFI Hotspot/tether instead of just BT? I get the exact message if I attempt to turn on tethering as well as WIFI. Which defeats the purpose due to tether utilizing 4G and broadcasts it to other devices.
[Verizon Samsung Galaxy S III] Artimis:
Yes, I'm positive this is for BT tether and not WIFI. The message makes sense for WIFI as it needs to disconnect it from a network in order to use it as the vehicle for sharing the mobile connection.

It does not make sense for BT because you can use BT to share the phone's wifi connection (which is what I am trying to do). After testing on a few devices I have at my disposal, this seems to be a 4.3+ issue (happens on my wife's G2 running 4.4). I cannot replicate on my 4.1 or 4.2 devices. I just tested with my tablet (which has no mobile radio and running 4.2) and it allows me to share the wifi connection via BT tether.

I'm suprised at how little information I've been able to find on this when googling it either. Can't seem to find any Xposed modules or hacks to get around it. The best I've been able to do is use FoxFi/PDAnet but that has other drawbacks.
[Verizon Samsung Galaxy S III] Manwthgun:
I apologize I can confirm the same issue. Can't say I use those two in conjunction together. I will continue to dig around to see if I can find a solution. I know prdog1 still checks in from time to time in here he may be able to give you an answer as well.
[Verizon Samsung Galaxy S III] BPHusker:
What setting do I need to change to make the black text white so I can read it easily?
[Verizon Samsung Galaxy S III] prdog1:
I never use wifi or bluetooth. Only tether my laptop for large uploads. No help here. :cool:
[Verizon Samsung Galaxy S III] pyrite123:
[MENTION=2296281]Artimis[/MENTION]

I never use bluetooth either. If you want a better shot at someone helping with your problem, some quick info from the phone status screen may help. Just go to settings > About Phone and scroll down to the bottom and take a screen shot like this. It will give me enough info to rule out several theories.
[Verizon Samsung Galaxy S III] Artimis:
Not sure how this will help. I'm running the same ROM and Phone and this is a common screen. The only difference is the kernel version -- I'm running LeanKernel bundled with the ROM but this is not a kernel issue AFAIK.
[Verizon Samsung Galaxy S III] pyrite123:
Have you tried another rom to confirm it's not a bad priece of hardware or tried flashing the ROM once more over the current install? I've seen that correct similar problems with wifi and 4g. I wish I could be of more help but I've never really used wifi for anything besides sharing a picture, ringtones back in the day, and linking a galaxy gear.
[Verizon Samsung Galaxy S III] Artimis:
It's not bad hardware. As stated, this works fine on Beans18 (which is a 4.1.2 ROM). It seems to be a limit added as of Android 4.3 (my wife's VZW G2 running 4.4 shows a similar message).

1) Enable Wifi

2) Go to Settings -> Wirelesss and Networks -> More Settings -> Tethering -> Bluetooth Tethering

3) See toast notification "Tethering Disabled. WIFI is connected."

As a workaround using "Bluetooth Auto-Tether" from the market. Or by enabling BT Tether while wifi is off:

1) Enable Wifi

2) Connect bluetooth device to start tether

3) Phone shows tethering icon active for a split second and then immediately disables it and displays "Tethering disabled. WIFI is connected".

Again, this seems to be some limit added to 4.3+ ROMs (including this one -- there was some discussion about this in the S4 forums as well).

This is exactly why I want the feature to work as it did in 4.1.2. I currently have a galaxy gear (running null_23 rom) and the only way to get it connected to the net for play store downloads, google calendar syncing, etc. is to BT tether. Unfortunately, my house gets a crappy 4G/3G signal which is why I'm always in Wifi when at home. On 4.1.2 ROMs, the wifi connection was shared over the bluetooth tether. On 4.3+ ROMs, this restriction was imposed for some unknown reason.

I was hoping someone knew of an Xposed module or a modified jar file/framework-res.apk that patches this. I've gone so far as decompiling framework-res.apk, services.jar, and framework.jar and going through the smali code but so far have come up empty. I can't even find reference to this string/toast message to see where it is coming from.
[Verizon Samsung Galaxy S III] pyrite123:
Huh wow. It's doing it to me as well. What I did was turn on wifi, activate bluetooth and nfc and the gear had Internet access. So idk might just try that?
[Verizon Samsung Galaxy S III] prdog1:
Don't even need NFC. Also shouldn't need bluetooth tether either. It should be no different than pairing with a headset. Phone is using wifi. Gear is using bluetooth. Your reading from and controlling phone not wifi. :cool:
[Verizon Samsung Galaxy S III] pyrite123:
The gear refused to pair with my phone until I turned nfc on and touched them together. It had to pair at least once then I only needed bluetooth aafter the first pairing.
[Verizon Samsung Galaxy S III] prdog1:
That could be possible. My Bluetooth PC speakers work the same way. 4.1.2 doesn't support Gear anyway. That is why they gave us 4.3. :cool:
[Verizon Samsung Galaxy S III] Artimis:
Not entirely true. Depends on how crafty you get with 4.1.2. The Gear will pair on 4.1.2 using GearManager 1.2.

Phone calls work, media controls work, "find my phone" works, SMS/MMS can be done through tablet talk which works......and of course, bluetooth tethering works. (e.g access google play or browse a website from Gear while phone is connected to wifi)

I updated to 4.3 for the enhanced notifications and more seemless call handling transitions. And it seems BT tethering while connected to wifi was the trade-off.

I was able to get it working via FoxFi/PDANet but that drains the battery quicker, has limits, and eats up unnecessary memory.

Guess I'll keep searching for a smali hack.