yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Master Cylinder:
Just flashed 6/13 with CyanDelta on Friday - not a good idea for me. :silly:CPU is out the roof and I can't charge (using more power than what's coming in?) and can't get data, even after rebooting (re"Optimized" 46 more apps??) and pulling the battery. Had to shut it down just to charge it enough to restore my backup.:crying:

First Swiftkey was peggin' the cpu, after shutting it down and watching with OS Monitor, it was churning up 45-55%, and UI and System were pushing that, too. It's out-of-whack that's for sure.

May try it again without the CyanDelta which I hadn't used for awhile that also flashed Xposed (This can screw up things, too.)
[Verizon Samsung Galaxy S III] phonetool:
No problem here. I don't use xposed, though. Maybe that's the cause?
[Verizon Samsung Galaxy S III] AyUaxe:
Anyone come up with a fix for Google play services crashes? I've tried a full wipe/clean install of 6/10 with current euroskank's banks gapps and it got worse, with play not installing at all. Also tried tkruzze's new tk gapps (the new pa gapps), using his wipe system approach, but also failed to install a compatible play. Finally just went back to my 6/2 backup, where it isn't too bad, if location is set to device only. Can't get cm gapps to download. Click the link in dolphin or stock browser and it just says the file's too large to display, but won't download. Any help will be greatly appreciated!
[Verizon Samsung Galaxy S III] Burdman2006:
Verizon Data Issue

Anyone else having issues with data not being available? I clean flashed 6/11 and seem to have intermittent issues with data not being available and the phone shows Verizon with an !. Anyone else have that issue or have any ideas on what I can try to do to fix it? I have tried rebooting, switching between airplane/normal mode and removing/inserting the SIM card.
[Verizon Samsung Galaxy S III] phonetool:
Small issue with the snooze function of the alarm clock. I usually have four or five alarms set and rely on snooze to keep them going. It seems that each alarm rings initially, but when snoozed does not ring again. A notification says "snoozed until 4:50", but no action occurs. Anyone else see this?
[Verizon Samsung Galaxy S III] XdrummerXboy:
I have had mobile data issues for a looong time. For me, I think it's a hardware issue of some kind.

---------- Post added at 06:21 AM ---------- Previous post was at 06:19 AM ----------

Do your times overlap at all? Maybe that would cause an issue?

I don't use snooze though...
[Verizon Samsung Galaxy S III] phonetool:
Well, sure they overlap. It wasn't an issue with any of my previous phones. Gnex on lollipop had no problems like that. I'll run some tests a bit later under some less groggy circumstances. ;)
[Verizon Samsung Galaxy S III] XdrummerXboy:
Haha alright. What I meant by overlap was one snoozed alarm going off at the exact same time as another alarm, not just overlapped (which gives the possibility of offset), if that makes sense. But sounds good, maybe I can try some tests of my own
[Verizon Samsung Galaxy S III] Master Cylinder:
I had this on 6/13. Not on 6/9 or 6/14. Why not dirty flash up to 6/14 which seems pretty solid?
[Verizon Samsung Galaxy S III] Burdman2006:
Data Issue

I will give that a try, thanks for letting me know it is not just me :)
[Verizon Samsung Galaxy S III] AyUaxe:
Agreed, 6/14 seems solid after about 24 hrs of use. Still seeing occasional play services crashes, so still hoping for some good info re: gapps, but it's not as serious a problem, as it was with 6/2 or 11.
[Verizon Samsung Galaxy S III] Master Cylinder:
What version of play services are you running?
[Verizon Samsung Galaxy S III] Burdman2006:
Data Issue

Booted up and still had the issue. I went into Settings --> Mobile Networks --> Access Point Names --> It was set to Verizon Internet, I changed it to Verizon IMS and it seemed to connect and then switched itself back to Verizon Internet and has been good since. Seems kinda strange but I will keep an eye on it and see if I have to do this "fix" again later.
[Verizon Samsung Galaxy S III] XdrummerXboy:
FWIW, I'm pretty sure I'm using Banks gapps filename "gapps-L-4-21-15" with no play services crashes. If you guys want to try it I can link you to it

Play services *is* part of gapps right?

I attach a screenshot of my Play services version, its probably after some updates
[Verizon Samsung Galaxy S III] XdrummerXboy:
Here it is
[Verizon Samsung Galaxy S III] AyUaxe:
SMH-sorry, G Play services is 7.5.71 (1955121-436), store is 5.6.8, GSF=5.1.1-1914015. Think these are from banks 6/6 or 6/11 gapps.
[Verizon Samsung Galaxy S III] Master Cylinder:
Your gsf is different than mine, seemingly newer. The other 2 are the same. Do you have an app manager of some kind? You could possibly put this older one live.

Do me a favor - copy that framework apk and share it. I'll load onto mine and see if I get the same problem. You can roll yours back if you have an app manager, or flash or install this one that's current on mine. ( don't know yet which way you have to do it)

EDIT: Actually, I guess I can get the package and extract it myself.
[Verizon Samsung Galaxy S III] slick_shoes:
Thanks for all the hard work on the GS3. I've finally jumped shipped and got me the G4. Love everything about it but its pretty big compared to the S3.

Thanks to master cylinder, mastamoon, invisiblek, and for all that kept my S3 running like a champ.
[Verizon Samsung Galaxy S III] Master Cylinder:
Awesome! Adios! By the way, I have to defer to Nardholio - he's our device maintainer. I'm just a bystander. ;)
[Verizon Samsung Galaxy S III] AyUaxe:
Haven't been able to extract the gsf apk yet, but here's the latest crash report:

java.lang.IllegalArgumentException: Wake lock not active: android.os.BinderProxy@b7c7f33 from uid 10021

at android.os.Parcel.readException(Parcel.java:1550)

at android.os.Parcel.readException(Parcel.java:1499)

at android.os.IPowerManager$Stub$Proxy.updateWakeLockWorkSource(IPowerManager.java:500)

at android.os.PowerManager$WakeLock.setWorkSource(PowerManager.java:1213)

at com.google.android.gms.stats.c.a(SourceFile:393)

at com.google.android.location.reporting.service.f.a(SourceFile:754)

at com.google.android.location.reporting.service.d.handleMessage(SourceFile:463)

at android.os.Handler.dispatchMessage(Handler.java:102)

at android.os.Looper.loop(Looper.java:135)

at android.os.HandlerThread.run(HandlerThread.java:61)
[Verizon Samsung Galaxy S III] Master Cylinder:
Hmmm... I'm not sure how to decipher it. Location reporting service in there... Power manager not happy.

PS - No need to hook me up with that file. I flashed it from banks gapps so that I have the same setup as you. For the moment, no problems. Location in Battery Saving Mode.

PSS - What happens if you put your location setting in 'Battery Saving Mode', as far as crashing?
[Verizon Samsung Galaxy S III] AyUaxe:
Unfortunately for the investigation, I tried two things--wiped GSF cache and data and switched to battery saving mode. No play services crashes since doing so, but haven't had chance to navigate, which is where it seems to be the worst. Guess I'll just run maps for a walk around my work place over lunch. Thanks very much, MC for you're help!
[Verizon Samsung Galaxy S III] AyUaxe:
Well impatience got the better of me, even though I wasn't having play services crashes on battery saving location setting, as suggested by MC. Just had to try banks' 6/13 gapps. Flashed it over cm 12.1 6/14 & dpk 6/8. Wiped cache partition and dalvik. Seems super smooth, stable so far. No navigation, but did a few searches and poked around in new maps (updated right after reboot-watch out for unwanted settings change to auto updates--I hate that) and no play services crashes so far. Think most of my tinkering now may be through kernel adiutor, instead of flashing. Yeah, that'll last a day or two. Maybe.
[Verizon Samsung Galaxy S III] phonetool:
Things just keep getting better. Previously too-dark links and addresses in texts just went to the proper highlight in tonight's update.

Got a text from out of the country and it came out afu.

"&iJÇ+&ÅH)tJÑØ&ÅæΠ PΩΓ'åÄ4cPΩsùd_6öG-;WNÄ9cP£QW.ΔGJÇ+'ÅÑ9tBæØΦ¤òΔIF!¥rÅ?7sF!+ùèQ4r¡ècF-Y9 Σ%+&,ΘΔuÖ_¥r(æ:e¡TsFøò2afM¥B,Z2 &=sf-ΘΔfxK¥B(Z1h¡Lù-Y4nh£QS%

ΔWRI¥2.Ξ:zJ9¥ΦMΔeR9+&ΔKÖΩKù.ΘΔiÖ£aD§X2cV£)g

ΘΔiF!¥BNÖ4nVΩ¥Φ,æ3 òΩKf

H+oP1S¥èΛ9ofQØ$¤U6ad5+gmΘΠ ΞéΓΨ-"

I should try to run it through Google or something.
[Verizon Samsung Galaxy S III] AyUaxe:
Looks like a character set or encoding incompatibility. Sorry, no idea how to change it in android.
[Verizon Samsung Galaxy S III] phonetool:
Yah, must be something like that. I don't know what to do with it, either. Got the message eventually via email, so don't need to decode it. Language of origin is German. Funny thing is when they wrote again in English it wasn't scrambled.
[Verizon Samsung Galaxy S III] realicet:
Firmware and modem

I have been out of the rooting world for a while and have stayed on a rooted 4.1.2 with VRBMF1, and I have twrp installed. My "noob" question was in regards to getting the NE1 modem on the device do I just install this zip in twrp after I factory reset and before installing the cm 12.1 zip? Sorry if this is not the place to ask this.​
[Verizon Samsung Galaxy S III] Master Cylinder:
(No need to quote the OP...)

No, don't do that. First upgrade to the latest TWRP. Then flash VRBMF1 firmware (which has it's own modem,) then flash the NE1 modem. Then you're ready to rock and roll! :cool:

Make sure to flash the latest GApps from that link in the OP, after your ROM before you boot, that says "Other Possibly Useful Files - Google Drive Stash" that has the date of 6/2, as the GApps link in the OP is causing some confusion at the moment,. There are other versions of GApps that you could use.:good:

EDIT: I just put links to TWRP and BaNkS GApps in the OP.

PS - Welcome Aboard!
[Verizon Samsung Galaxy S III] phonetool:
This. Hit the edit button and clean up!

That!
[Verizon Samsung Galaxy S III] realicet:
Firmware and modem

Yeah I already have the newest TWRP 2.8.6. I was just making sure you could load the VRBMF1 firmware and then the NE1 modem within TWRP. I didn't know if it was something you had to load somewhere else like in Odin or some other program. So since I am already running the VRBMF1 firmware do I still need to reinstall it first in TWRP after I wipe my old system out?
[Verizon Samsung Galaxy S III] Master Cylinder:
Nope! Just flash the NE1 modem with your TWRP and you're ready to flash the latest nightly - don't forget the GApps. It's take about 20 or more minutes to boot the first time.:)

EDIT: Oh, you might want to power off and pull the battery after flashing that modem, just to be sure.
[Verizon Samsung Galaxy S III] Master Cylinder:
It just occurred to me, how much are you going to wipe? Because if you keep your sdcard like it is there might need to be some shenanigans needed to make it visible to your operating system since you're coming from 4.1.2.
[Verizon Samsung Galaxy S III] ItsMeSri:
boot loop "Optimizing app.." and restarts again.

Today I tried again on CM 12 and 5.0.2 and flashed with [ROM][Official]CyanogenMod 12.1 Nightlies for the Verizon Galaxy S3 (d2vzw) and http://wiki.cyanogenmod.org/w/Google_Apps . Still it is the same.

It is on boot loop "Optimizing app.." and then rebooting again. I don't know the solution to fix. Anyone had this issue before and resolved?
[Verizon Samsung Galaxy S III] Master Cylinder:
Yes, I had this. I had to reflash the VRBMF1 firmware and NE1 modem in the OP - that fixed the problem.

Why not flash a latest 5.1 nightly?
[Verizon Samsung Galaxy S III] ItsMeSri:
can you share me link to latest 5.1 nightly. sorry, what you mean by OP?

---------- Post added at 11:30 PM ---------- Previous post was at 11:04 PM ----------

hey guys.. I was able to flash "VRBMF1 firmware" and then applied "NE1 modem" which throwing error to update.
[Verizon Samsung Galaxy S III] Master Cylinder:
OP = Original Post, the first post on the first page where all of the instructions and links are to the software.

What recovery are you using? What ROM did you have working before? Can you please type out exactly what the error is and when it shows up?
[Verizon Samsung Galaxy S III] ItsMeSri:
Thanks Master Cylinder, Initially I had CWM recovery. But now I changed TWRP recovery and installed firmware and modem. Both installed properly.

One more question. I am using T-Mobi SIM card in Verizon S3. I know LTE did not work. But in KitKat I used to get incoming and outgoing. after upgrade to CM12.1. I am not getting Incoming call, I can hear ring from dialed phone (I tried from my another phone). Do you know what could be the problem?
[Verizon Samsung Galaxy S III] Master Cylinder:
I think I know the answer, but I don't want to say without more research and I'm going to bed right now (maybe someone here will chime in?)

However, there are 2 links leading to threads for cm12 for the d2vzw in the OP, one by mastamoon and the other by Invisiblek. I think this issue may have been addressed there. Go to those threads and "Search This Thread" on that issue and see what you come up with. :good:
[Verizon Samsung Galaxy S III] ItsMeSri:
Thanks Master Cylinder, I just searched on both forums. Really I couldn't get correct answer. mastamoon said , he fixed the issue in one post. Do I need to install his ROM again? Please let me know if your research find something. Now I can't use my phone except for browsing.

Another issue is outgoing calls, I can't hangup. it is says hanging up. if other party don't respond it goes voice to them. because I can't hangup.
[Verizon Samsung Galaxy S III] AyUaxe:
My guess is you need proper APN for your region and carrier. Mastamoon posted US vzw APN zip as I recall. The problem with hanging up a call was discussed in the cm12.1 d2vzw development forum, I think.http://forum.cyanogenmod.org/topic/...-lessons-learned-etc/page__st__40#entry524244

Hope this helps. Happy Friday to all!
[Verizon Samsung Galaxy S III] Master Cylinder:
There is a possible solution on this page. If this applies to you, the file mentioned is in the 'd2vzw ROM extras' link in the OP:

http://xdaforums.com/showpost.php?p=57497869&postcount=1970

Take a look at the last post on this page and the following page, which presents a solution with some warnings:

http://xdaforums.com/showthread.php?p=58921224

I can't help but wonder what would happen if you rolled back your modem by reflashing the VRBMF1 firmware with the MF1 modem in it? It will work on this ROM normally if you pull the battery after. You might also have to do that again after booting the ROM to get everything working again.

EDIT: Also, sometimes with these builds people have had to do various tricks to get phone/data/mms working again normally, like switching APNs and such. Airplane mode ... pull that battery if you haven't already. This will fix some of these problems.

That apns-conf.xml fix file is in the 'd2vzw ROM extras' link in the OP if you want to try it. Might backup your existing file first.

Let us know how it goes.:good:
[Verizon Samsung Galaxy S III] ItsMeSri:
Thanks you very much @Master Cylinder for helping me to resolve the issue. I flashed d2gsm_rilblobs.zip with TWRP. It resolved my incoming calls issue and outgoing call issue. Thanks alot.

Thanks for @mastamoon for d2gsm_rilblobs.zip file. It help me a lot.
[Verizon Samsung Galaxy S III] Master Cylinder:
Oop! Missed your post. Glad that worked for ya! Awesome!
[Verizon Samsung Galaxy S III] ItsMeSri:
I think it is same thing "bypass ROM assert". http://www.reddit.com/r/cyanogenmod/comments/32ohnm/i605_vzw_note_ii_no_incoming_calls_on_cm12_or/. I did update script and re-flashed still dont work. Anyway d2gsm_rilblobs.zip worked for me.

I have question Edge network on Verizon S3 with TMO SIM card. Is it possible to improve data from EDGE to LTE on Verizon S3 with TMO SIM card? If you have any clue, please let me know. [MENTION=5519140]Master Cylinder[/MENTION]
[Verizon Samsung Galaxy S III] Master Cylinder:
Clue -1 = Clueless. Sorry. :silly:

I was interested and found some answers as to why - old equipment, poorly maintained, and not intended for modern data speeds - but no solutions.
[Verizon Samsung Galaxy S III] ItsMeSri:
Everyone says TMO radio and Verizon Radio completely different. Can't we override Verizon radio with TMO? Is it always edge on verizon s3 with TMO Carr?
[Verizon Samsung Galaxy S III] Master Cylinder:
You'd probably be better off posting this question in the Q & A, Help section to get a wider audience.

EDIT: And even on the Tmo Q & A site.
[Verizon Samsung Galaxy S III] Master Cylinder:
On the other hand, you might want to look more carefully at that link I posted http://xdaforums.com/showthread.php?t=2539794 Those instructions are for utilizing different networks on the same phone, changing kernels, then switching out /system of different ROMs for different carriers. Sounds like it might be worth a shot. The assert check changes are only to make sure it installs.

If I'm missing something it's because switching out SIMs and such is out of my (EDIT: infinitesimal) experience and knowledge.
[Verizon Samsung Galaxy S III] realicet:
SD card issue, SD card format

Thanks for mentioning that, I backed up the sd card anyway but after cm 12.1 install everything looked fine system and card wise. Then I tried to access the download folder on the sd card and it won't open but every other folder and file will. I hooked the card to my pc using an sd adapter and drive boots and says it has errors. Put the sd card back in the phone I booted in to TWRP and wiped the sd. It was in exFAT, now after wiping in TWRP it reads FAT32.

My question, what is the best file system format to keep the sd in? I read in other posts stating cm 12.1 on other devices will work with NTFS, any truth to that? I know TWRP has EX2, EX3, EX4, and FAT, any thoughts appreciated. I just want to get the card on the most reliable, user friendly, format going forward.

Thanks
[Verizon Samsung Galaxy S III] LLStarks:
No. The modem is locked down and secure boot gets in the way. Everything that can be tried has been tried.

If a full VRALE6 firmware had leaked, maybe we could've had 3G.
[Verizon Samsung Galaxy S III] Master Cylinder:
I should've been more careful and specific - I was referring to the internal storage which is also labelled sdcard. It sounds like TWRP took care things anyway.

Regarding which format for the external sdcard, FAT32 is standard and the most interchangeable, user friendly for cards the size we're using. NTFS is really for much larger drives and ExFAT is good for files larger than 4gb, like movies and stuff. Can the Linux kernel we're using make use of the extended permissions of NTFS? (Can TWRP read it? I don't think so.) This has been one of the problems of the exernal sdcard, and why Google wants to put an end to it - lack of permission control. Samsung has caved in on the S6.

ExFAT would be good if the ROM supported it - have not checked into that. Don't know if TWRP does, though I think there was a flirtation with it for awhile. FAT32 is probably the most interchangeable to linux, Windows, Mac, etc ... though I know ExFAT can go to those now with added utilities.

Since you're the one with the freshly wiped card, why don't you experiment and let us know?
[Verizon Samsung Galaxy S III] ZiQn3zZ:
Is anyone else having issues with VOIP? For some reason, when people talk, it's all broken up like a stutter. I never had this issue in KK.
[Verizon Samsung Galaxy S III] AyUaxe:
64gb microsd exfat here, working fine. Came that way from sandisk. My understanding is exfat is necessary for partitions >32gb and to handle files >4gb.

My old vista laptop required an update to r/w it. Fat32 remains a good, but size limited option. IMO, manufacturers stopped allowing external storage, bc it allowed us to upgrade cheaply and securely for the user, but the phone manufacturer didn't get a piece of that action. Compare the cost between a 32gb and 64gb current, no-ext-sd phone. It's a good deal more than a good 64gb micro SD card. Mire reasons to keep these fine d2s.
[Verizon Samsung Galaxy S III] Master Cylinder:
Awesome! Might give it a go myself. I'll have to install utilities in Linux. The ease of interoperability with Windows, Mac and Linux out of the box has been one of the advantages of FAT32, though it can be slow on the phone compared to other formats. However, I've only popped it in to a computer couple of times in over 2 years. Good way to back it up , though.

Problem with exfat, from Wikipedia:

"Restrictive licensing and software patents

Microsoft has not officially released the complete exFAT file system specification and a restrictive license from Microsoft is required in order to make and distribute exFAT implementations. Microsoft also asserts software patents on exFAT which make it difficult to re-implement its functionality in a compatible way without violating a large percentage of them.

This renders the implementation, distribution, and use of exFAT as a part of free or open-source operating systems or of commercial software, for which the vendors could not obtain a license from Microsoft, legally difficult, especially in countries that recognize United States software patents

. Although exFAT is now widely supported in consumer electronic devices (citation needed) and Mac OS X, initially these could only handle FAT12, FAT16, and FAT32. The situation had formerly rendered exFAT, and flash memory formatted with it, impractical as a universal exchange format. Native Linux support for exFAT is still limited. As of September 2014, a working implementation under FUSE exists."
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Build: 06/22

GApps: Banks 06-13-2015

Having bluetooth issue. One of my earpiece can pair up but nothing is coming through. I'm still testing the other bluetooth earpieces.

EDIT: Ok, it was only that one earpiece that was having problems. The other one works just fine.
[Verizon Samsung Galaxy S III] :
If you're using Linux, I think you'll get better results with ext4 or f2fs
[Verizon Samsung Galaxy S III] realicet:
SD card format

I tried out exFAT, FAT32, and NTFS. NTFS is by far and away the fastest transferring a 2 gb movie in a few seconds, BUT TWRP can not read it so that's basically bogus unless you run 100% of recovery installs off of the internal sd, if you go that route not a bad idea in that sense.

Both fat systems are close on speeds with ExFAT being slightly faster. I noticed some odd mounting issues with ExFAT though. I would unmount and mount a few times and sometimes the card would not pull right away( still less than a minute in response). I feel like FAT32 is probably the way to go if you are looking for the most reliable and never have the need to transfer 4gb+ files on your to your sd.

If you do run ExFAT just remember to keep a backup, seems to be a little buggy here and there. Hmmmm wish I had the 32 gb version of this phone with the 16gb I keep a TWRP backup and titanium bu on the internal sd and the drive is 3/4 full. :(
[Verizon Samsung Galaxy S III] Master Cylinder:
I just put ext4 on my card!

Hey [MENTION=2044079]Nardholio[/MENTION] - can I put you in the OP as the device maintainer/contributor? Maybe we can get some donations going your way?

Thanks!
[Verizon Samsung Galaxy S III] Master Cylinder:
EXT4 should be as fast or faster than NTFS. I'm gonna put an easy guide on how I switched it anyway, in the "d2vzw ROM extras" link sometime today...
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks, mc! Was interested in ext4. Do the d2 and twrp r/w it?

BTW, are you using latest twrp 2.8.7 or still on 2.8.5? Open recovery or the other one. Tried 2.8.6, seemed OK initially, but backup turned out to be corrupt and sorry of lost root, though could still get into recovery. Got it all righted and updated to 6/22 with cwm.