yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] TinkerbeII:
Wow!! That is totally amazing!!! Mine still works too!! I have her sitting next to me... missing battery cover and all. Still boots up like a little lady, and is happy to help out whenever needed!! Thank you for the shout out bbolton!!! =]

Sorry about the idumb... never give up hope. She will come around. Show her your S III with the Synergy Rom!! Woo!!
[Verizon Samsung Galaxy S III] eschelon:
^^ This. That phone was hackers paradise and probably the sole reason analog is no longer used. You could clone a phone by doing almost nothing else than just standing by it. LOL

Trev likes his anonymity so you guys don't really know much about him, but since the thread has been mildly OT most of today, I'll take a few more minutes to digress and treat you guys to an actual pic of TrevE from a few years ago before we get back to all the boring Android dev talk :p
[Verizon Samsung Galaxy S III] innocent:
What rom did you run on that? XD
[Verizon Samsung Galaxy S III] TinkerbeII:
Wow, are you serious??? Are you pulling on my blonde roots? lol

Sorry for the OT. I feel like I am mostly to blame. Now back to the regular scheduled programing...
[Verizon Samsung Galaxy S III] eschelon:
Ha, alright alright...

I'll make an attempt to steer back on course by saying this: Trev does his best work when he tinkers. And he was tinkering in the AROMA config today and added a new light/AOSP style install option for you guys. A one tap install strips all Samsung bloat and sets up some AOSP stuff (MMS, lockscreen etc). It's a nice, lightweight option for those that want it. Plus we've got one more AROMA surprise for you that we won't reveal until the next official release ;)

I've got 3 more files to patch tonight (which I'm working on right now) and then I'll send them up to the Synergy repo at which point we should be close to a new build :good:
[Verizon Samsung Galaxy S III] TrevE:
Everyone modded them, All you needed to "root" was "menu, send, end, recall, store, clear". It had fancy menus that said nice Timing! then it enabled the most ridiculous features nobody should have. Ctek cable and an eeprm programmer just made it all gravy. Probably still find stuff on it on old newsgroups

And no, my hair is not grey yet :P thanks esc
[Verizon Samsung Galaxy S III] prdog1:
Don't worry your little roots. We have to do this now and then to break up the constant flow of repeat questions. Makes it harder for them to find the repeat answers. :rolleyes::laugh::cool:
[Verizon Samsung Galaxy S III] daclothe:
On Sprint GS3 r443 with ziggy kernel, I'm getting screen flicker once every 5 seconds or so with MHL (official OEM Samsung) to HDMI.

I think I'll flash the stock kernel and see what I get. Other than that I'm loving the recent enhancements!
[Verizon Samsung Galaxy S III] whatnow275:
Okay a little off topic but i figured if anyone could help it would be the people here...I just got a new GS3 in the mail to replace my old one (asurion), and it updated to 4.1.2. I'm following the instructions to root/unlock 4.1.2 but it fails every time when I try to flash a recovery in Odin. what am i doing wrong?
[Verizon Samsung Galaxy S III] TinkerbeII:
lol, thanks for your understanding. Close to a new build!! Woo!! Patch away my friend!
[Verizon Samsung Galaxy S III] prdog1:
Should be using this method. And asking in this thread.

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

That being said. When does it fail. Which recovery boot chain are you using. Did follow steps as listed and flash the hacked boot chain first. :cool:
[Verizon Samsung Galaxy S III] whatnow275:
I got it working right after posting :/ thanks anyway :)
[Verizon Samsung Galaxy S III] innocent:
Xd never used that im just 20 xD but woah didnt think you'd answer xD
[Verizon Samsung Galaxy S III] prdog1:
Us old folks like to teach. Don't let Trev fool you. He is getting grayer by the day. That probably why he shaves his head. ;):p:laugh::cool:
[Verizon Samsung Galaxy S III] innocent:
Didnt think he was old xd thought he was around my age.
[Verizon Samsung Galaxy S III] eschelon:
Trev's not old. He's younger than I am (smarter too!)
[Verizon Samsung Galaxy S III] prdog1:
Had to take the hit. Couldn't help myself. Sorry Trev but it was funny. :laugh::cool:
[Verizon Samsung Galaxy S III] Beejis:
Just so I dont screw anything up and after reading the OP twice, is there a separate version for Sprint or do I just flash the only one available that's the latest?
[Verizon Samsung Galaxy S III] prdog1:
Only one version to flash. It will check your recovery and if have a Sprint Recovery will get the Sprint version. :cool:
[Verizon Samsung Galaxy S III] eschelon:
The one rom.zip works for all carriers, but MMS and 4G have some issues. Hang tight, we're on it :good:
[Verizon Samsung Galaxy S III] innocent:
How old are you both if you don't mind me asking. And let me officially introduce myself, im Steven :). 20 yrs old, and I love your rom lol.

My online name is innocent and it dates back for a while since I was head staff on a game server called dark gunz xD
[Verizon Samsung Galaxy S III] TinkerbeII:
Nice!! This is such a cool feature. Just download and go...
[Verizon Samsung Galaxy S III] TrevE:
ha im only 26 ;) probably can find that out from when half the world tracked me down hah. Just been sticking wires into things since I could talk, my poor parents. Just always been interested in the "other side" of things
[Verizon Samsung Galaxy S III] Will32:
I love synergy! :thumbup:
[Verizon Samsung Galaxy S III] innocent:
Nice! What language do you have to know to do this type of work you do xD
[Verizon Samsung Galaxy S III] BoxyBox:
Just flashed the new build and noticed the old baseband version (K3) in settings.

Is it recommended to Odin back to VRBLK3 4.1.1 and then install the OTA before installing this ROM, or should I just go ahead and just install the new modem from here?

Thanks!
[Verizon Samsung Galaxy S III] prdog1:
It is up to you. Roms never change the baseband. :cool:
[Verizon Samsung Galaxy S III] eschelon:
I like my anonymity too, but I'll say that I'm just a couple years older than Trev. 30 or less ;)

Meh, you can just flash the radio and you'll be fine. No need to grab the OTA if you don't want to go through the hassle; everything will still work. Some like grabbing the newer firmware, but it's not required to boot and use the ROM
[Verizon Samsung Galaxy S III] krazie1:
Is GPS not working in Google Maps a known issue on 443?
[Verizon Samsung Galaxy S III] eschelon:
Hmm, working fine here... There's that new 4th location setting now. You've got the 3 in normal settings, then open Maps or Navigation settings and allow location access to Google apps too.
[Verizon Samsung Galaxy S III] jlyle:
Mine is working. Accurate up to 100 meters where i sit at work right now:cool:

Ninja'd by Esch :)
[Verizon Samsung Galaxy S III] krazie1:
Ok it was that Google Settings turning on the option to give Google Apps access. I never knew there was a option there, thanks for the help.
[Verizon Samsung Galaxy S III] eschelon:
Yea that's new. Google added that one or two Maps updates ago
[Verizon Samsung Galaxy S III] Stam2000:
Nothing wrong with Anonymity but if any of Team Synergy are ever out on Long Island. Dinner on me at my family's steakhouse

Sent by my Synergized GS3
[Verizon Samsung Galaxy S III] Kelton Rivas:
The one will do because this ROM is applicable across all platforms :)
[Verizon Samsung Galaxy S III] chitman17:
GPS Status

I was wondering why the GPS icon is always displayed in the status bar. It will only go away if i turn off GPS. I havent had any other problems with this ROM as usual Synergy is the best ROM available. Thanks again for an amazing ROM.
[Verizon Samsung Galaxy S III] eschelon:
You've got some app that's constantly polling your location. It shouldn't always be on unless something is requesting your every move
[Verizon Samsung Galaxy S III] innocent:
I respect that, xD well thank you again for being such an amazing Dev, both of you are really doing a lot. But also causing me a lot of trouble, my cousin and several of my friends are iphone lovers and lets just say I have peeing andy bootanimation with your rom ^_~
[Verizon Samsung Galaxy S III] megageek:
The default install works perfectly for me, but whenever I try to customize it, my data won't work. Maybe you guys can help me help myself. If I can just get it to match (and hopefully data will work that way,) I can try to add things one at a time to narrow down which option is causing me to not get data. I had the same problem with an earlier version of the ROM as well... default install works fine, but custom install leaves me without data.

What Aroma options would I need to select in order to get it to exactly match the default install? Is it even possible to get a custom install to exactly match the default?

I saw mention of known MMS and 4G issues. What are the 4G issues that people are seeing? Any idea if it is related to the data issues that I have?

FYI I have a Verizon Galaxy S3. Phone info says that my Hardware version is I535.10, if that makes any difference.

BTW, this is an awesome ROM.

Thanks
[Verizon Samsung Galaxy S III] innocent:
You answered your own question for the most part. Your rom is installing the rom set up, what are you clicking?
[Verizon Samsung Galaxy S III] eschelon:
Are you choosing the global APN option during custom install? If so, don't do that :)

You can pick anything else you want during custom install, just don't do the Global APN
[Verizon Samsung Galaxy S III] megageek:
I'm not sure what you mean that my rom is installing the rom setup. If I go to select the "Custom SyndergyRom Install" option, the boxes that are pre-selected match my previous "Custom SyndergyRom Install" attempt, which clearly doesn't match the "Default SynergyRom Install" because I can't get data to connect with any custom install that I've attempted so far.

Going through the different option screens:

Data Wipe Options:

Install w/out wiping (I know that although this isn't recommended, it appears to be what the "Default SyndergyRom Install" option does based on the log, maybe I'm wrong and that's the problem)

Full Fsck w/ Post Flash Optimize

Check to INSTALL apps: (things I have selected have a *)

AllShare

Google Talk

Google TTS

Kies

Paper Artist

S-Memo

S-Suggest

Polaris Office

Yahoo News/ Stocks

*Gmail

*Google Maps

Google Music

Google Plus

Google Street View

*Google Voice

*My Verizon

PDroidManager TrevE mod

*Titanium Backup

*YouTube Mod

*Wifi Tether TrevE mod

Please select any additional mods you would like to INSTALL: (things I have selected have a *)

*4.2 Camera / Gallery

*Samsung Camera / Gallery

Emoji Keyboard

Note 2 Keyboard

*Swype Keyboard

Use AOSP Messaging

Restore TW Messaging

Disable Boot Animation

Enable Lockscreen Rotation

Install Auss Weather

*Install Flash Player

Restore Samsung Media Files

Bypass Exchange Security

Block Ads

Zipalign /data/app each boot

Sqlite Tweaks

Advanced Customization Options: (things I have selected have a *)

*Block Charge at High Temps

*Enable Camera During Call

*Enable Camera Shutter Sound Menu

Set Email Background To Black

*Activation Bypass

Use Global APN

Shall we backup your hardware keys?

Yes

Which kernel would you like to flash?

Ziggy Kernel

Ziggy Kernel Customization:

<all synergy Recommended Settings>

Never Colors in Shell

Are any of my selections above different than the "Default SynergyRom Install" options?

(sorry about the long post)
[Verizon Samsung Galaxy S III] Biker1:
@ calaski8123 from the battery issue thread....

Just to keep everything related to SynergyROM in one place, which makes it easier for others to respond, and whose answers may help others, best to post in the link above.

But to answer your question,

- Download 443

- Install onto your extSdCard

- Move anything you want to save from your Internal to extSdCard

- Have a Nandroid installed onto your extSdCard

Boot into Recovery

Wipe Cache

Wipe Dalvik

Wipe Data

Flash ROM in Aroma

Superwipe (*which will vaporize your Internal)

* which is the reason to have the as described above installed onto your extSdCard

Read your options carefully regarding what you want installed and not installed.
[Verizon Samsung Galaxy S III] StormFreak:
Love the ROM, but has anyone been able to get Foursquare to work on it? It was working when I ran CleanROM, but after switching to Synergy yesterday it opens to a white screen with a blue bar, and then Force Closes. I've tried uninstalling/reinstalling, as well as clearing data.
[Verizon Samsung Galaxy S III] megageek:
Ok, this is crazy. After about 50 tries, I just tried the custom config above again and I have data! Now I'm off to figure out which custom check-box broke data for me. I'll post here if/when I find something.
[Verizon Samsung Galaxy S III] mmalkin:
I actually was having issues getting the location to report using triangulation. When I disabled GPS and wifi, would essentially say there was no location source.

The solution: I installed pdroid and set maps to "Allow all" and it seems fine now, even with pdroid installed. Might be some issue with default permissions.

Awesome ROM, BTW. I tried a little programming back in the C++ days. I'll just say that it gave me more respect for people who could actually make things work.

---------- Post added at 09:11 AM ---------- Previous post was at 09:06 AM ----------

There were some posts on this on Saturday. No resolution as of yet. I tried a lot of things but no luck.
[Verizon Samsung Galaxy S III] innocent:
Don't use global apn sir and you should be fine
[Verizon Samsung Galaxy S III] megageek:
I've never had the global APN option set. I got the hint that particular option wouldn't be helpful. Since I finally got data to work, I'm starting to change selections a couple at a time, so if the issue comes back I'll see which option causes it (although I might not know if it's a single option, or an interaction).

So far, no issues with choosing different bloatware/apps :fingers-crossed:

---------- Post added at 11:26 AM ---------- Previous post was at 10:45 AM ----------

Ok, it's definately one, or a combination of the last for selections that I made on this page:

Please select any additional mods you would like to INSTALL: (things I selected have a *)

4.2 Camera / Gallery

*Samsung Camera / Gallery

*Emoji Keyboard

Note 2 Keyboard

Swype Keyboard

Use AOSP Messaging

Restore TW Messaging

*Disable Boot Animation

*Enable Lockscreen Rotation

Install Auss Weather

*Install Flash Player

*Restore Samsung Media Files

->Bypass Exchange Security

->Block Ads

->Zipalign /data/app each boot

->Sqlite Tweaks

With all 4 of those selected, I don't get data. Changing nothing else, if I deselect all 4, I can get data.
[Verizon Samsung Galaxy S III] PyroXian:
In conjunction with SOME earlier modem versions, and on an earlier release (r290-ish) I would lose data when I chose the SQLite tweaks.

My money's on that.
[Verizon Samsung Galaxy S III] pelo88:
Ok, in TWRP I was able to unmount the data partition and in advanced run terminal commands. I had saved resize2fs to my system partition so I made sure that was mounted and used that as my start up. Before unmounting data I used cat /proc/mounts | grep "/data " to see what the new mountpoint was in TWRP and found it to be /dev/block/mmcblk0p15 and I confirmed this with tune2fs.

So my new code to execute in terminal (after unmounting data) was:

./resize2fs /dev/block/mmcblk0p15 3208184

I needed to run e2fsck to perform a file system check and needed the -p to run non-interactively due to the way terminal runs in TWRP.

e2fsck takes a LONG time to run. I started it and it seemed stuck at 4.8% processing 802,816 files, but after a few ps | grep e2fsck showing I only had the one process in state "S" (meaning sleep) or that my grep command shared the same process ID (shown right before the S), I felt fairly confident e2fsck finished.

e2fsck -p -f /dev/block/mmcblk0p15

Then I tried again:

./resize2fs /dev/block/mmcblk0p15 3208184

Same warning. I even tried:

e2fsck -p -f /dev/block/mmcblk0p15 && ./resize2fs /dev/block/mmcblk0p15 3208184

SO that all didn't work. I needed a different e2fsck. I opted to push the one in that same file that included an android friendly resize2fs. Makes sense, right?

For what it's worth, this is probably the better e2fsck command to use in terminal:

e2fsck -fDC0 -p /dev/block/mmcblk0p15

.... AND now I can't boot at all. I went back into recovery and wiped cache, dalvik, to no avail. Stuck at boot logo. Gonna dirty flash again and see how it goes.

Dirty flash worked. I'm guessing the fsck's that are part of the install work MUCH better than the cm9 versions that are included in TWRP's busybox.
[Verizon Samsung Galaxy S III] megageek:
Yup. I narrowed it down to that one option. I thought I had tried to enable/disable just about everything, but I must have been constantly enabling that option every single time.

I found the latest modem and RPM at RootzWiki http://rootzwiki.com/topic/34053-modems-vrbmb1-verizon-sgs3-sch-i535-recovery-flashable/. My current Baseband version is I535VRLF2, which is apparently the original shipped modem (according to that same link). I guess the real problem is that I need to update the modem then.

From what I've read, it's uncommon to include the modem and/or RPM with a custom ROM. That seems odd to me since ROMs are all based off of OTA updates, and the OTA updates will update the modem and RPM.

Thanks to everyone who helped!
[Verizon Samsung Galaxy S III] prdog1:
No rom has ever included modem or rpm or any other of the 15 or so partitions/sub-partitions that are updated. These are firmware. The OTA actually includes the firmware and a rom which is software and is what you see on your phone. The stock rom is extracted and modded. The devs do not mod the firmware unless on AOSP base and they have to build RIL and Kernel from scratch. :cool:
[Verizon Samsung Galaxy S III] markkal123:
MMS issues?

backtracked through some of the issues regarding mms. not sure if this issues is a part of the issue or something else. i realize the big boys are about to drop a revision on us that should take care of some mms issues. but agan i'm thinking my issues isnt totally related.

phone connected usb to laptop. was attempting to drop some pics on the external sd. got a notice that the files may not be compatible with my device. i decided to transfer nevertheless. after all they're simple .jpeg files.

now the weird... i can view these files in both galleries. but they wont even attach to a text. if however when i attach the same files with root explorer ezpz. they attach to text and transfer without issue.

on the other hand, i dont seem to have any other issues with MMS. i can send most any photo a-ok.

any thoughts?

mark
[Verizon Samsung Galaxy S III] megageek:
I didn't realize that the firmware was separate from the ROM. Should I be looking for any other updates for the firmware? Whenever I search for Samsung S3 firmware, the results I get are for custom ROMs or stock OTA updates. Is there a good source for official firmware releases that don't touch the ROM? I know that I could go flash to a stock ROM and then re-root, but I'd really rather avoid all that if possible.

Thanks again.
[Verizon Samsung Galaxy S III] snofrandy:
Hmm...I think I found the problem. It's not the process of sleeping that resets Llama back to "No signal/Unkown" but it seem that if I plug it into a charger of anytime, it will switch back to the default profile and Cell 1:1:1. When I quit llama and restart it, it would go back to normal operation of detecting cell towers

I thought it was "Developer Mode" so I disabled it. Same result

I tried plugging it in, then turn on Llama. It would go to "normal operation" then after 2 secs, go back to default profile and Cell 1:1:1

Any thoughts?
[Verizon Samsung Galaxy S III] yarsh:
Head over to rootzwiki dot com, go to the "Verizon Galaxy S III Development" forum, and look for the [MODEMS] post... Then flash the modem in recovery just like the ROM (wipe Cache/Dalvik) and you should be good to go :fingers-crossed:
[Verizon Samsung Galaxy S III] prdog1:
There is no way to update full firmware without killing rom. :cool:

I have Llama just to test for yall. Have not messed with it except to recharge and test. Still showing my local tower info. Plugged to charger still get my tower. Reboot and activate Llama and still get my tower. Can't duplicate. I have tried everything in your post and can't duplicate a 1:1:1. Get cell tower every time.
[Verizon Samsung Galaxy S III] Droid316:
Is there a fix for Netflix? Everytime I try to open it will go to black and say unfortunately Netflix has stopped.

EDIT: Nevermind I force stopped it then uninstalled then reinstalled now it works.
[Verizon Samsung Galaxy S III] tekhna:
Man this ROM has really screwed up my phone after clean flashing with default settings. Freezing and rebooting, and now the touchscreen won't work. Yuck.
[Verizon Samsung Galaxy S III] NightRogue:
Great release, only thing I am having problems with is random serious lag spikes at random times. Clean install. Anyone else having similar issues? Not hot boots or reboots but the phone will freeze for a while, get hot, then catch up with itself after a minute or so.
[Verizon Samsung Galaxy S III] andybones:
those having issues should try stock kernel, i use it cos i have a rev4 phone.. no issues
[Verizon Samsung Galaxy S III] prdog1:
Apparently you dirty flashed. And if dirty flashed from AOSP base you pretty much on your own. Lot of yall consider wiping dalvik and cache a clean flash. That is the definition of a dirtyy flash. :cool:
[Verizon Samsung Galaxy S III] tekhna:
Nope, sorry friend. Clean flash from stock rooted. Rebooted into recovery, wiped again, installed, rebooted, got a delightful SystemUI force close upon boot.

Jacked up.

Edit: and just so you can't be smarmy on your next post, I know what a clean flash is. Been around a while.
[Verizon Samsung Galaxy S III] prdog1:
You can be as swarmy as you want but there are thousands of downloads and installs that prove that it is an operator malfunction and not the rom. :p:cool:
[Verizon Samsung Galaxy S III] tekhna:
Nope. Try again.
[Verizon Samsung Galaxy S III] DatDude123:
Just redownload and reflash. If problem persists, find another ROM.

D
[Verizon Samsung Galaxy S III] tekhna:
So on it.
[Verizon Samsung Galaxy S III] TinkerbeII:
Humm... that is strange. Been running this 443 all day with no issue at all.
[Verizon Samsung Galaxy S III] xdreaper15:
Don't worry we have some tools that come through every once in a while. We try to help them, but if the problem persists and we ignore them they'll usually leave after a while.
[Verizon Samsung Galaxy S III] DatDude123:
All good I'm sure. Let's not name call and just flash ROMs instead.

D
[Verizon Samsung Galaxy S III] onemotodroid:
Install the Rom been running for 48 hours without one issue. Great job!
[Verizon Samsung Galaxy S III] bobcaruso:
Uncalled for comment here, the poster is having problems, and he stated he clean flashed the rom. It was prdog that accused him of dirty flashing from an AOSP rom, the guy just indignantly answered back at the misplaced accusation, that don't make him the tool, maybe prdog should apologize for his comment
[Verizon Samsung Galaxy S III] eschelon:
Sorry to hear, man. I gotta ask the basic questions: Did AROMA detect your phone as d2vzw? Did MD5 match? Did you restore any system data with Titanium backup? Any custom mods, flashables, or kernels? Which wiping option did you choose in AROMA?

I'm sure you understand, but I'll post this for others in case there's confusions: You can still flash custom kernels (including Ziggy's) when you have a rev 4 cpu. The ONLY difference is if you try to undervolt, the cpu will automatically bounce back to whatever the cpu wants it to be. That may sound lame, but it's not so bad since rev 4 actually forces the voltage to be pretty low by default - much lower than rev 0