yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] garrettcorn:
Hey guys just wanted to report for me after using the update zip thing that was released (without flashing anything) I dirty flashed from stock to ziggy and have seen a huge decrease in screen lock ups I had one right away like 5 mins into the flash and havent had one since been a day so far havent had a random reboot either use to get them quite frequently! I know I read for some people it didnt help at all but so far it has seemed to help for me! I hope the issue is solved for me because I love zigs kernel so much better then the stock!
[Verizon Samsung Galaxy S III] BillBauman:
Any time I make changes to the kernel settings, I usually get fewer lockups for a short while. Inevitably, things go back to the way they were.

I'm considering trying a once-a-day Dalvik Cache Wipe to see if that helps.
[Verizon Samsung Galaxy S III] Ryezen:
QUOTE=nucher;40339364]It's the connector in the upper left hand corner that is circled (picture from your link). It is a little different than the GS2 but I was able to bend mine up (carefully), then re-attach the back plate. It helped with my GS3 GPS. I was trying to explain the concept to the non-believer than be technically accurate in my explanation.[/QUOTE]

Hope this explains the real issue with GPS

Via my Google Galaxy S3 running magic beans[/QUOTE]

Okay, so I haven't posted in a long time, but I tried this, since the screwdriver fix didn't work for me (neither did any of the software GPS fixes, either--GPSfix, GPS Test, etc.).

Using GPS Test, I normally could see 20 or so satellites pretty quickly, but couldn't lock on to them. It would take a LONG time and slowly it would connect to a few. I was lucky if I ever saw it connect to double digits, even outside on a clear night. When driving, it would sometimes take minutes to get GPS lock on a clear day.

After following the pictures and instructions in this post, I put the phone back together, and BAM--GPS lock in just a few seconds. I stepped out back to run GPS Test again, and connected to 20 satellites!! I was in shock. I was able to get accurate down to 3 meters in Google Maps, which is unheard of for me.

I just had to bend the connector up a bit, like in the pics, and it worked perfectly; very simple to do. Think of bending a battery terminal out a bit to make a better connection; that's pretty much all this is doing. Hardest part was finding a screwdriver small enough.

Feel free to PM me if you have any questions; but this prevented me from having to return my Verizon SGS3. Huge THANKS to the OP!

P.S. I guess you'll have to view the original post to see the pics; they didn't show up in my reply. It's post number 22041 in this thread.

~~Ryezen
[Verizon Samsung Galaxy S III] silver1882:
The pics arnt showing up in that post either.
[Verizon Samsung Galaxy S III] Ryezen:
Allshare Cast Issue

Hello Esch,

So I did some research and found out why Allshare Cast isn't working on Synergy (or most other custom ROMS). It has to do with the custom recovery causing the flash counter to return a "1" even if you use triangle away to set it to set it to zero. Only way people have gotten it to work is by flashing stock recovery, then using Triangle Away. If you later flash a custom recovery, the flash counter is set to 1 again, which breaks Allshare Cast.

Do you think there is a way to circumvent the flash counter being set to "1" when booting from a custom recovery? Or is there maybe a way to adjust the value during the boot process to change it to zero while starting up? Only other thing I could think of would be a hacked/modded version of the AllShare Cast software that doesn't check the flash counter.

To clarify: The Allshare Cast settings open properly, and it even allows you to scan for devices, but won't allow device detection for output. If you don't have an enabled TV or dongle, you could just walk into a BestBuy and try it with their Samsung Smart TVs--stock recovery will allow AllShare Cast to connect with them, so long as flash counter is set to zero and device reports "normal".

As always, thanks for all you do. I love my Synergy DD, and have been rocking it since first release on the S3.

~~Ryezen
[Verizon Samsung Galaxy S III] eueyj:
Hmm I find that a bit weird since I'm running synergy and have allshare cast working with no problems.

I don't use triangle away. I've also treated with ziggy as well as stock kernel. Works every time.
[Verizon Samsung Galaxy S III] Hobart!:
I am in a little town called Harrisonburg Va and this is what I just got...HOLY CRAP!
[Verizon Samsung Galaxy S III] tower_gilead:
You got a blank white square? Holy **** !

Nm....it showed up.

:beer:

Sent while sleeping in chair.
[Verizon Samsung Galaxy S III] Ryezen:
Interesting. One possible reason could be a missing "bloatware" file called wfdbroker.apk

Could you check you "All" listing in application manager and see if you have that one installed? Thanks!

~~Ryezen
[Verizon Samsung Galaxy S III] Hobart!:
I only usually get 4-10 mb on a good day 4g...so this was a little surprising
[Verizon Samsung Galaxy S III] jamminjon82:
That's what I usually get, but I'm only about 3 hours from Harrisonburg
[Verizon Samsung Galaxy S III] Jihoonie:
I live in somewhat rural upstate NY and recently had 4G expansion on a tower about 500 ft from my backyard. Check out these stats
[Verizon Samsung Galaxy S III] lastly:
Great Work Guys !

:good:

Boo-Yah !

I'm so happy right now I could cry :highfive:
[Verizon Samsung Galaxy S III] Ryezen:
Interesting. Can you tell me more about your setup so I can try and narrow down the problem, ie:

1) Did you dirty flash/clean install?

2) Did you install Pdroid upon flash, and if so, did you have to change any settings in it to allow Allshare Cast to function?

3) Are you connecting through a dongle or Samsung Smart TV?

4) Do you have to start an app to use it, or does it connect to your device after just enabling Allshare Cast in the phone's settings?

Thanks much for your help; I really want to get it working. Any other hints/suggestions you can think that might help?

~~Ryezen
[Verizon Samsung Galaxy S III] eueyj:
1) Clean flash ie wiped everything, also downloaded all apps again as opposed to from restoring from backup. Bit of a pain but I seem to have less problems than what other people have.

2) have installed pdroid but didn't change any settings in there.

3) using the allshare cast dongle which I bought off Amazon.

4) I typically use the widget but that just links to the allshare cast toggle in the settings. I have noticed that if multi Window is currently open it will disconnect straight away. That is the only limitation I've found.

I loaded all the Samsung apps in through aroma, don't know what affect that may have. Have you changed the default clock speeds? I have left mine as default.

I can create a YouTube video next week to show my setup.
[Verizon Samsung Galaxy S III] Digital DJ:
I'm trying to use Swype keyboard as my default, but when I reboot my phone it switches back to Samsung keyboard which keep force closing...ugh. can I get rid of the Samsung keyboard?
[Verizon Samsung Galaxy S III] prdog1:
If Samsung keyboard is FCing you got a bad install. Sounds like dirty flash and fixing permissions may help. That being said. Can delete or freeze the keyboard in system app or can make a TIBU backup and then restore the swype keyboard and it will maintain default on reboot. :cool:
[Verizon Samsung Galaxy S III] bad355camaro:
I had similar issues, as well as with the Google apps. I did a factory reset as well as cleared all cache and that fixed all issues I was having. The only pain was reinstalling all the apps, I didn't want to risk backing them up and getting in the same boat again so I did it one by one for the play store.

Hope this helps.
[Verizon Samsung Galaxy S III] pelo88:
Just run fix permissions to clear the fc's. As for the default keyboard there's a trick to that as well. Check this thread. I wrote a script to set mine and saved it in ROM Toolbox Lite set to run as root on startup.
[Verizon Samsung Galaxy S III] bad355camaro:
It didn't work for me, I contacted Esch and what I suggested is what he suggested for me to do.
[Verizon Samsung Galaxy S III] pelo88:
The script approach will definitely work to set ur keyboard. Here it is for SwiftKey:

#!/system/bin/sh
ime set com.touchtype.swiftkey/com.touchtype.KeyboardService

In terminal run ime /help to get some commands. One of them lists the ime options u have. Use the one u find for Swype or whatever.
[Verizon Samsung Galaxy S III] prdog1:
To set any 3rd party keyboard to stick as default do as I posted and backup with TIBU. Uninstall the app and restore with TIBU. Play store installs to wrong place to maintain permissions on reboot. TIBU reinstalls to data/app where it can maintain the permission. :cool:
[Verizon Samsung Galaxy S III] bad355camaro:
I'm not sure if you misunderstood me or I'm misunderstanding you but the factory reset worked for me. I thought I made that clear in my first post regarding this, I apologize if I did not. I was just telling "dead batteries" what worked for me.
[Verizon Samsung Galaxy S III] Sgt Fury:
For those of that asked about foursquare try adding the widget to a home screen. Once you successfully access your account through the widget you should be able to have no problem with the app.
[Verizon Samsung Galaxy S III] jefmoody1:
I may have screwed it up but it's time for me to move on... I've only been successful with 2 out of the 7 builds I've tried (Both not using Ziggy).

I think my phone and Ziggy kernel hate each other.
[Verizon Samsung Galaxy S III] prdog1:
If using wifi need data enabled also for MMS. :cool:
[Verizon Samsung Galaxy S III] prdog1:
MMS uses a different Verizon data server. Just enable data in toggles and it should go. SMS will go over wifi but not mms.:cool:
[Verizon Samsung Galaxy S III] prdog1:
Then you have a flash problem or Verizon is down. You can try clearing the app data for messaging app. I just sent 2 with no problem. :cool:
[Verizon Samsung Galaxy S III] mmalkin:
You, sir, are a genius! I did it just by adding the shortcut widget. It gave an error message. Then tried the app and it let me log in!

here's some search terms so we don't see a million more posts asking: foursquare fc force close solution app crash
[Verizon Samsung Galaxy S III] wildnux:
Hi, I am sorry if this has been asked before, but I could not find with search on this forum and google search as well. I am trying to turn off 4G LTE on this rom, so I tried to change my Network mode to GSM/WCDMA/auto, but it does not stick after pressing back. Network mode currently shows "Preferred network mode: GSM/WCDMA/LTE". Whenever I am on 4G LTE area, my phone just dies on me in minutes. I was hoping there was some way to just disable 4G LTE easily. The only information I found so far on google is that we can turn off 4G LTE using some app called "Phone info" but I see a lot of people saying they could not get it back after turning it off. Is there a way where we can just turn on/off the LTE when we want?

I am on ATT Samsung Galaxy s3 with synergy rom r484.
[Verizon Samsung Galaxy S III] Sgt Fury:
Sweet! Glad it worked for you.
[Verizon Samsung Galaxy S III] xxdjvalexx:
I'm using a Cricket S3 and I've trying to get this to work to no avail. No wifi, no 3g/4g and it keeps rebooting. Did a clean flash, tried using both kernels and nothing.:(
[Verizon Samsung Galaxy S III] uberbdon:
Did you select cricket in the aroma installer? Hell, is there even a cricket option in the aroma installer still? You asked that question and I answered like over a month ago...
[Verizon Samsung Galaxy S III] xxdjvalexx:
Yes I did. the option is still there in the aroma installer but it doesn't work. :( Did I ask a question? My bad if I didn't answer, I didn't get the notification.
[Verizon Samsung Galaxy S III] uberbdon:
Are you not the one that originally asked if this would work on cricket? I'm on my phone and didn't bother going back to see if it was you or not. Whoever it was asked a hell of a long time ago though. lol
[Verizon Samsung Galaxy S III] xxdjvalexx:
Lol!! No man, it wasn't me. But thanks for the quick reply. It just doesn't work. No wifi and no Data. Phone calls work though. This sucks :eek:
[Verizon Samsung Galaxy S III] Zenoran:
Anyone have a fast mirror? The download links on OP are terrible
[Verizon Samsung Galaxy S III] prdog1:
No mirrors. Mine says 8 min on the IL server. Worst server was 22 minutes. :cool:
[Verizon Samsung Galaxy S III] Zenoran:
Hmm not me. Been trying for hours. I tried all mirrors and it moves about 1pct per minute. I actually waited one out and it ended up failing at 99 :(
[Verizon Samsung Galaxy S III] prdog1:
Must be using the phone. Need to use a different browser. Firefox, Opera Mobile or Chrome. :cool:
[Verizon Samsung Galaxy S III] rodstar87:
Soooo... Who wants to try the new 4.2.2 that was leaked by the good old folks at SamMobile.

Sent from outer space, from my mars curiosity rover. :sly:
[Verizon Samsung Galaxy S III] klin1344:
That is only for the exynos i9300. It will not work for our galaxy s3's.
[Verizon Samsung Galaxy S III] prdog1:
Don't see it on SamMobile. Will let you try it. I9300 4.2 was dumped by the Chinese a while back. No good for us. :rolleyes::cool:
[Verizon Samsung Galaxy S III] rodstar87:
Its on the frong page. But realized its only for i9300. Has a bunch of nice features.. Some from the s4 as well.

Jumped the gun. I do see its for the international only.
[Verizon Samsung Galaxy S III] prdog1:
Yea. 4.2.1 was leaked a while back. No one touched it if that gives a hint. :laugh::cool:
[Verizon Samsung Galaxy S III] rodstar87:
PR what's leaked is 4.2.2 not 4.2.1
[Verizon Samsung Galaxy S III] prdog1:
Both have been leaked. Doesn't do us any good. If it was worth trying to port we would already have 4.2.1 a long time ago. Nobody going to touch either one from International. Got a better chance of getting a port from a S4 dump this week once Verizon releases the device. :cool:
[Verizon Samsung Galaxy S III] rodstar87:
Gotcha :thumbup:
[Verizon Samsung Galaxy S III] Stam2000:
Pr are you going to S4?

Sent from my Synergized Galaxy S3
[Verizon Samsung Galaxy S III] prdog1:
Nope. Not enough upgrade to justify $700 out of my pocket. I still have unlimited data. :cool:
[Verizon Samsung Galaxy S III] rodstar87:
I'm with you on that one. If I had the s2 it woulda been a must have for me. Most of the features will be ported over in due time anyways, esp with the great devs on here, certain features might even work better on the s3 once their done stirring up the pot.

Sent from......
[Verizon Samsung Galaxy S III] Digital DJ:
Ok so I read all of your posts on how to fix this. What I ultimately had to do was uninstall titanium (want working properly) reinstall it, then use it to uninstall any keyboard I didn't want. Now when I reboot my phone my lovely Swype keyboard is there :)

---------- Post added at 02:53 PM ---------- Previous post was at 02:52 PM ----------

I'm definitely not going to the s4, and by the time I'm due for an upgrade the s5 will probably be out...

I'm actually do in love with my S3 I sometimes have chapped lips when I wake up in the morning from my nightly make out sesh with my phone.
[Verizon Samsung Galaxy S III] prdog1:
You can have as many keyboards as you want. With 3rd party keyboards you just have to uninstall the one you want to be default and restore it with TIBU. It is not the app or the rom. It is Playstore installing to wrong place since JB. It installs to data/data instead of data/app. TIBU restores it to data/app. :cool:
[Verizon Samsung Galaxy S III] MAD450r:
p plese one of you smart guys.

Ok heres the deal. My original verizon s3 screen died at about year insurance replace 3 tiems now. This one was brand new black one and it came with 4.1.1 installed, the store that swapped out broken for new after all these issues made it update to 4.1.2. Not a big deal I unlocked bootloader rooted and reran bootloader as you suppose to and all was fine.

I installed r484 choosing Ziggy kernal and yesterday after runing it for 2 days now I noticed it was at stock clockspeed then I look at about phone and I see its still on stock kernal. So my dumb ass goes out searching for just the ziggy kernal to flash over rom. I made backup but my dumbass didn't pay attention to it going to internal storage. once I flashed ziggy upon reboot I got the verizon detected unauthorized software. I was pissed but wasn't scared figured I'd just odin back to 4.1.1, I did so and updated to 4.1.2 then rooted again . Now trying to install Synergy I get this every time. [any other rom I try to install trips verizon crap.]

I try to paste pic of the error in recovery, im legally blind so I cant really read thoroughly.

Im in process of trying to odin back to 4.0.4 instead then root then try install from there. praying that works or im stuck with stock or trying to return yet another and I dont get why this is happening I used same method to root all and I have redownloaded and recheck the zips

What do I do next.
[Verizon Samsung Galaxy S III] prdog1:
Your bootloader is locked. Unlock it. That message is sure sign that it is locked and Synergy will also give you stock kernel if you are locked regardless of what you chose. There is also no standalone Ziggy kernel for the last few builds. Part of the kernel script is in rom so can't be flashed on it's own. Rooted 4.1.2 OTA is fine. That is what I run. It is just still locked.:cool:
[Verizon Samsung Galaxy S III] SpyroDazee:
Before you change ROM from fresh rooted stock, you need to unlock your bootloader. There are many ways, but easiest for me was EZ unlocker from the market. I've tried several root methods, EZ has worked for every one. :thumbup:

You could always just take ziggy's source & compile it on your own. :rolleyes:
[Verizon Samsung Galaxy S III] MAD450r:
roms

Now i've tried to install even my AOKP even that trips verizon crap. That ziggi kernal I made sure was for verizon variant not sure why it did this to me. I'll paste the name to see if I did screw up but I spent a few hours hunting and double checking I was getting what I thought Synergy r484 was suppose to install alone with rom. I should have left well enough alone. Now I cant do anything but run stock which I hate. Now missiing multiwindow and all other addons you get so use too when running roms.

z471-VERIZON-SGS3-JB-122812-1545.zip

thats the file I ran and caused all this issue :(

all cause I wanted to overclock a bit

---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------

I did unlock first thing with odin file

VRALEC.bootchain.tar

then I run this to obtain root

CF-Auto-Root-d2vzw-d2vzw-schi535.tar

then after I run this again to reset bootloader I guess

VRBMB1_Bootchain.tar

Thanks for quick reply though

---------- Post added at 03:42 PM ---------- Previous post was at 03:37 PM ----------

Is first thing I though was bootloader so I reran the exploit and does not fix, only fix is to oden back to either 4.0.4 or 4.1.1, I havve both files tried both hoping for different resuls. Im guessing the kernal flash messed with something that this does not fix. Im so pissed at myself over this just cause 2 friends have gs4 and HTC ONE I felt i needed more speed sigh :(
[Verizon Samsung Galaxy S III] prdog1:
It is definitely locked. That is what that message means. And that is one of the original JB kernels before they split the script out although It won't relock bootloader and may still even run. This is the root and unlock thread you should be using. :cool:

http://xdaforums.com/showthread.php?t=2046439
[Verizon Samsung Galaxy S III] MAD450r:
thats how I did my original one

Bu the method I used on this one I meantioned worked fine until I flashed that kernal seperately from the aroma installed since I thought aroma was messed up since it not put it in when I seleted it. Just phone was working ok had a slight lag from time to time but I had all my apps in installed over 200. They were all on my first one and it ran that way for year about

im so confused cause even after full clean restart now no matter what method I use I cannot run any rom

if I stay stock even rooted its fine

so im at a loss. Never in my time working with android did I see where a clean odin reformat didnt put it back to out of box running.

thanks for you help I jsut starting over i'll use your suggested method i'll report my results after my dinner ;) starving been messing with this for hours.
[Verizon Samsung Galaxy S III] prdog1:
Did you root JB before with that method. They broke the old root and unlock methods with 4.1. :cool:
[Verizon Samsung Galaxy S III] MAD450r:
yes but

That is why I meantioned that I do have both odin files one to go all the way back if need be to ics. I rather just go to 4.1.1 and root as I did with one saturday. It worked flawlessly.

I just dont get how this kernal killed roms. Stock is fine with or without root

for installing recovery saturday I used goomanager,

but right now im going to use the method you posted just for ****s and giggles I pray it gets around whatever piece of theat left over kernal install that seems to be messing with me.
[Verizon Samsung Galaxy S III] prdog1:
Stock kernel won't set off the Verizon message because it is signed. Will get the message with any custom kernel. Bootloader does not have to be unlocked to run stock kernel. That is why all roms with custom kernel give the error. Stock rom or custom rom w/stock kernel won't because stock kernel is secure. Flashing an insecure kernel forces the error. Go ahead and update back to 4.1.2 and follow that tut step by step and should be good. I have used it several times. :cool:
[Verizon Samsung Galaxy S III] MAD450r:
your not getting meI

I cant even run rom when I chose stock kernal

it will not run unless its on stock rom. I never seen this before

I dont get it either

I been rooting android since the droid OG and only time I ever came close to this type of thing was original htc incredible, since it had write access to system in recovery at first

ok im in with root on stock rom used the method you paste link too should I run the bootloader to restore partitinos. before I try to install rom.

seems to be running just it does when I used other method to root.
[Verizon Samsung Galaxy S III] prdog1:
Did you flash the root and unlock zip. There are different versions. Should be the combination zip. Flash counter will be tripped so now is time to flash Triangle Away if want to fix. If don't have it it is free on XDA. Can also update TWRP with GooManager. And yes you can flash the bootchain as long as you flashed the unlock zip. Another way to test for unlock is reboot. First Samsung splash should be very short. Like i-2 seconds. Also their should be no unlock image on second splash that says custom. :cool:

http://xdaforums.com/showthread.php?t=1494114#
[Verizon Samsung Galaxy S III] MAD450r:
yes

yes I ran the do it all version

supersu_bootloader__fixed

just in case I even redownloaded the rom and checked file checksum
[Verizon Samsung Galaxy S III] mapatton82:
I would start from scratch and use this instruction in this thread, it has worked several times for me. This will get you stock rooted and unlocked. Keep in mind that this does trip the flash counter, you can use the use the Triangle Away app the prdog linked to reset that if you want.

http://xdaforums.com/showthread.php?t=1974114
[Verizon Samsung Galaxy S III] MAD450r:
I am stock rooted and unlocked

thanks for all your help it worked this time I did force it to stay on stock kernal too but im back running on synergy which is what I wanted. I really appreciate you taking time to help me out.
[Verizon Samsung Galaxy S III] prdog1:
That link is obsolete now. There is new one dated March for 4.1.1 and 4.1.2. :cool:

---------- Post added at 04:24 PM ---------- Previous post was at 04:20 PM ----------

Don't worry about that one. Forget what actually makes that disappear. But first splash screen that just says Samsung in block letters should just blink. Just long enough to read it. Locked it will stay for several seconds. :cool: