yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] bryank29:
A few questions.

1. Using CyanDelta...do I need to wipe the dalvik cache manually? I am now using TWRP and so it installed the nightly for me and rebooted itself and now is optimizing all the apps.

2. I used the July 7 GAPPS off Vendor / Google. If I am staying up to date with the PlayStore, is there a benefit to flashing a more recent GAPPS?

3. Is there a setting to make the stock theme darker (for battery life) or I simply need to install a new theme?

EDIT - just saw the comment above mine lmao

---------- Post added at 02:03 PM ---------- Previous post was at 01:55 PM ----------

Not sure what a high amp charger is.... this morning while the phone was off, I plugged mine into my 2.1A car charger and the phone just kept vibrating. I plugged it into the 1A slot (it's a duel charger) and the charging icon popped up. I then swapped to the 2.1A and the charging icon came back up.

---------- Post added at 02:05 PM ---------- Previous post was at 02:03 PM ----------

This one doesn't look too bad either https://play.google.com/store/apps/details?id=apps.wadhwa.reboo
[Verizon Samsung Galaxy S III] Deliquified:
1. If it optimizes apps, that means cache was wiped. No need to wipe again.

2. The only time you'd need to flash a more recent gapps is if you're suddenly getting force closes and all kinds of bugs/errors

3. You need to install a theme. The darker everything goes, the more battery life you save. Black/darker colors take less battery than white/brighter colors.
[Verizon Samsung Galaxy S III] bryank29:
Wow, my theme got reset because of multiple app crashes. I didn't think having a theme + style would cause that. I kept the default fonts, icons, etc.. and used the style, status bar, and notifications from another theme. My Quickpic gallery wouldn't open.

Also, I did a TWRP backup. I've considered formatting my internal SD card. Would it wipe out my root access and twrp?
[Verizon Samsung Galaxy S III] Deliquified:
Themes can cause all sorts of issues if they aren't kept updated with the rom. I'm not 100% on the twrp issue, but if I had to guess, it likely would. Maybe someone else will chime in to confirm this
[Verizon Samsung Galaxy S III] Master Cylinder:
Ditto on what [MENTION=3082999]Deliquified[/MENTION] said about themes.

What are you trying to accomplish with wiping the internal "sdcard?" Using TWRP to do that would take out everything on /dev/block/mmcblk0p15, which is where all of the user space is, including /data, or rather it is mounted as /data, but everything in that dir would go. The recovery partition is /dev/block/mmcblk0p18 and would not be touched. But, where do you store your TWRP backups? If they are on the external sd then they are safe. There is a TWRP settings file on internal card but won't hurt to lose it. In the 'd2vzw ROM extras' link in the OP is a partition table with explanations. (You have to reduce the visual font when looking at it to get the rows and columns to line up.) There are other txt files in there: part, mount, and recmount (what the 'mount' command produces in recovery vs live ROM) that show mount and df info from my phone.

Still, it's a pretty drastic step. If you copy stuff back you would also have to do some ownership and permissions stuff. Maybe there's another way to accomplish what your trying to?
[Verizon Samsung Galaxy S III] AyUaxe:
The last few updates to Nicholas dark theme produced severe instability and boot loops. It was great before that and probably still is for phones with a lot more hp than a d2. My personal experience was that the boot animation alone ate up enough ram and CPU to prevent proper loading of necessary os code/modules. In short, that excellent dark theme is effectively too up to date for our older phones. If anyone still wants to use it, recommend not using it's boot animation.

I'm now using material glass, an interesting transparent theme. Stock boot animation. It's great and generally pretty dark.

I'd really like to get the "fire flies" boot animation that MastaMoon gave us but don't know how to get it or install it in place of the cm stock creepy droid head. Any ideas, links would be appreciated.
[Verizon Samsung Galaxy S III] Master Cylinder:
Can't you just put any boot animation in the /system/media dir as long as it's labeled bootamination.zip and has 0644 premissions? I'm using a really cool one from AICP ROM that I made a little patch for after flashing a nightly. I put it in line for flashing via TWRP Manager Install feature, though if you use Cyandelta you can do the same there.
[Verizon Samsung Galaxy S III] phonetool:
Cyandelta doesn't overwrite your custom boot animation with stock each time you dirty flash. So there's no need to automate reflashing the same boot animation every time (if that's what you are suggesting). I'm using "minima android" by chummy. Easy Playstore install, free, very light.
[Verizon Samsung Galaxy S III] Master Cylinder:
Good point!
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks gents! That's exactly what I needed to know.
[Verizon Samsung Galaxy S III] bryank29:
Yea after researching I have realized it was drastic. I used ES File manager and went to clean up some folders/files I didn't need. My internal seems to have 12GB available (16gb internal) but I assume its cause there is a safe partition in there or something. Apps: 2GB, Media: 837MB, system data: 3.7GB, free 5.7GB.
[Verizon Samsung Galaxy S III] Master Cylinder:
I forgot about the other part of your question : I've looked in to nandroids I have from mastamoon's builds and all I see is the old cyanogenmod stuff in there. However, I have a really cool one I put in the d2vzw ROM extras link in the OP you could try. It's from AICP ROM but it's pretty awesome!

16GB has always been a little deceiving. And was complained about when this phone came out. There was fine print. If you look at one of those files I referred to you'll see how much that is partitioned and used, including for the ROM, leaving 12gb at /data.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Same here, 2A charger I believe. My issue started LONG ago though, somewhere around the first of the 5.0 nightlies

It claims to be charging. It has an equilibrium at about 50% if I leave it overnight, but if I'm using it it loses charge.
[Verizon Samsung Galaxy S III] ryanstfl:
please share this "patch", it says the size of the one you shared is 3.4 megs and the old one is 1.5 megs... wouldn't that make it larger in resources?
[Verizon Samsung Galaxy S III] bryank29:
My 2.1 A charges, but if I use power from laptop via USB to power the phone, it's a 50 / 50 ratio as well.

When I was messing with i/o schedulers, I had personally noticed my phone struggled to charge using SIO on my internal sd. don't know why and no clue if that was the actual connection, but was an observation. Using Zen for both Internal and external and getting great results out of it.

---------- Post added at 04:10 PM ---------- Previous post was at 04:05 PM ----------

I'm currently using the System default theme for alarms, fonts, lock wallpapers, boot animations, icons.

I then purchased DarkMTRL CM12 and use their status bar and style. I then found a dark wallpaper as I don't like any provided for the themes.

Do these themes come with multiple wallpapers because when I try to change via MENU > Wallpapers, my choices are limited.
[Verizon Samsung Galaxy S III] Master Cylinder:
Modem Downgrade

After accidentally finding a post on xda regarding my data never on after boot, I reverted to the MF1 modem (by flashing the firmware only) and now my data is active after every boot.

¯\(°_0 )/¯

I'll see what else works - or doesn't.
[Verizon Samsung Galaxy S III] bryank29:
I know there is a known bug that requires going to the Mobile Data portion, going into "Access points" and selecting another. Within 1-2 seconds it reverts back but enables the Data.

Curious if downgrading modems would cause other issues.
[Verizon Samsung Galaxy S III] phonetool:
Since last night's nightly I'm not getting the data that I was getting for the last couple weeks. It's not as good, is what I'm saying. 1x where I had 3g.
[Verizon Samsung Galaxy S III] Master Cylinder:
PM.
[Verizon Samsung Galaxy S III] jonny30bass:
The calendar app hasn't worked for me in a while. It always asks me to add a Google account even though my Google account is already on my device. So I can't add any new events because of this. I'm using Banks Gapps if that has anything to do with it.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Try deleting your Google account from your phone and then re-add back on. :confused:
[Verizon Samsung Galaxy S III] bryank29:
Just saw this in the most recent nightly. Do you think it's meant to be a fix for the crashing camera issue?

https://github.com/CyanogenMod/andr...mmit/c4204b516ecfe696e95003dc39cd00085c45c477
[Verizon Samsung Galaxy S III] Master Cylinder:
Occasionally people who've been using Banks have had this - look at this post: http://xdaforums.com/showpost.php?p=61771910&postcount=401
[Verizon Samsung Galaxy S III] justinnotjason:
I've also been having alot of issues charging. It's gotten to the point where I rotate two batteries through an external charger.
[Verizon Samsung Galaxy S III] bryank29:
Mine is so sporadic and I am convinced it was a cord I was using.

I installed xposed and amplify yesterday. I had done a nandroid backup, and after updating the nightly and installing those, I tried charging and it just struggled. said 2 hours to charge like 20%.

But today it had no issues charging back up. I have done so many things to my phone with the intent of battery saving (greenify, amplify, kernel (DKP), underclocking /volting) that I get surprised when it struggles.

Hoping it was just the cord.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I rotate 4.... ?

---------- Post added at 11:29 AM ---------- Previous post was at 11:27 AM ----------

Its not just the cord for me. It will say its charging but will even out at around 50% if I'm not using it. If I AM using it it will eventually drop to 0. Honestly its almost like the charger isn't helping at all, that's how quick it is.

I've also gone back to using the stock adapter and it had the same results basically.
[Verizon Samsung Galaxy S III] bryank29:
are you able to charge it to 100 ever? consider downloading the root app Battery Recalibrator, charge to 100...see if the numbers stop rising, then clear it. After wards, I will usually discharge it to 2%, let the phone shut off, and recharge to 100% uninterrupted.

I use the 7000mah zerolemon though so the phone is heavier, but with moderate use I can use it for 2+ days. With heavy use, I am below 50% by end of day. (reddit, hangouts, youtube, etc.)
[Verizon Samsung Galaxy S III] bryank29:
I'm trying a test right now. I just updated to the july 28 nightly, I flashed my DKP kernel, flashed the xposed framework, and cleared dalvik cache. Charged to 100% and reset battery calibration. My phone has been unplugged for about 30 minutes and is still at 100%. normally it drops to 99 and 98% fairly quickly once I start using it.
[Verizon Samsung Galaxy S III] XdrummerXboy:
My battery always discharges completely, so I don't think it's a calibration issue.

Here's a screenshot from a particularly bad instance earlier today, only about 2 hours worth of use, only 1% battery used by screen

I don't know much about wakelocks, but considering the phone says "awake" almost the whole time I'm thinking that's definitely one issue.

But that wasn't while charging, so I can't say that's the issue.
[Verizon Samsung Galaxy S III] jonny30bass:
Yeah it turned out that Banks Gapps was the culprit. I reinstalled the rom with a different Gapps package and it works now.
[Verizon Samsung Galaxy S III] AyUaxe:
Which gapps did you use. Enquiring minds want to know!
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I use GApps provided by TKruzze (Micro version).
[Verizon Samsung Galaxy S III] Master Cylinder:
Can't go wrong with these. What I used normally as PA GApps until they disappeared for awhile and mastamoon suggested the CGApps.

The CGApps in the OP also are without issue. I installed them a couple of weeks ago - no problems. Banks are removed from the OP, but can be found in the "Smorgasbord" if you just gotta have 'em, just don't come complainin'.! ;)
[Verizon Samsung Galaxy S III] phonetool:
Hmmm, seems the stock messaging app is borked after flashing tonight's nightly. Can't send. Don't know about receiving.

Any ideas?

I'm about to try wiping the app's cache.
[Verizon Samsung Galaxy S III] Master Cylinder:
Mine works, but I had to change to it to try since I use a different app. Sent one to myself, and received it. Sent one to someone else.
[Verizon Samsung Galaxy S III] bryank29:
interesting observation. I haven't gotten the Camera can't connect message in quite a long time, but I have been using the 3rd party FL-5 camera app. Decided to give OpenCamera a try again and thus far, no camera breaks...so not sure if it was fixed or I just haven't run into it yet.

Now, my observation. I noticed any pictures taken with the FL-5 camera app which I store onto my external SD card wouldn't get picked up in the "Recent" menu or "Images" when it came to uploading / attaching files for various reasons (Drive, email, etc.). I set OpenCamera to store onto the external, but pics taken with it show up immediately in the Recent menu, images, etc. I wonder if it has to do with how these camera apps tie to the build in camera connection. Maybe FL-5 bypasses something, so the media scanner is never triggered. Having to run the media scanner 3rd party hack I downloaded is annoying and may consider sticking with OpenCamera for now as long as it doesn't give me connection issues.

Wanted to share.
[Verizon Samsung Galaxy S III] phonetool:
Ok, it's working today. Not sure why. I did wipe cache on the message app and services. Then wiped all app cache via TiBu.
[Verizon Samsung Galaxy S III] justinnotjason:
Anybody know when stagefright was patched out on the nightlies? I'm running a very old nightly(beginning of june) and was curious.
[Verizon Samsung Galaxy S III] Master Cylinder:
Glad you brought this up after the recent news regarding a vulnerability in Android through Stagefright. You can check the change log in the OP - I know they were patching it quite a bit in the last 3 weeks.

From the CyanogenMod Google+ Page regarding Stagefright dated 7/29:

"The following CVE's have been patched in CM12.0 and 12.1 nightlies for a couple weeks. If you haven't updated already, we strongly encourage you to do so.

... We are actively following all the DefCon events and announcements and will be keeping tabs on other disclosures that could impact CM and its derivatives. "

https://plus.google.com/+CyanogenMod/posts/7iuX21Tz7n8
[Verizon Samsung Galaxy S III] justinnotjason:
Thanks for the follow up. Clearly a concern for all android users. This really shows the advantage of using cyanogenmod and devs ability to quickly add patches.

I've been following the "if it ain't broke don't fix it" approach to these nightlies. Suppose it's time to update.
[Verizon Samsung Galaxy S III] jonny30bass:
I just use the recommended CGapps now. I haven't ran into any problems with this gapps package yet.
[Verizon Samsung Galaxy S III] Superman2015:
Play time

:highfive::confused:

[QRCODE][/QRCODE]
[Verizon Samsung Galaxy S III] :
Anybody having issues with their phone overheating?
[Verizon Samsung Galaxy S III] AyUaxe:
Haven't noticed any heat issues after about 24 hrs on 7/30 build and 7/29 dkp. Wondering what temp to set on Adiutor thermal throttle. Seems odd not to have any pre-programmed options.
[Verizon Samsung Galaxy S III] phonetool:
Nope. I'm flashing each night and haven't had any problems like that.
[Verizon Samsung Galaxy S III] AyUaxe:
Wowsers, just tried GPS for the first time since 7/30 flash and the improvement is dramatic. Also installed new cgapps, so not sure what to attribute this to, but after marginal function for almost a year, this is like manna from heaven!
[Verizon Samsung Galaxy S III] Master Cylinder:
Like [MENTION=4602329]phonetool[/MENTION], I've been flashing most nightlies but have not experienced any heat, or pain of any kind, really. Lovin' these builds!:D
[Verizon Samsung Galaxy S III] Deliquified:
Not overheating, but sometimes things get a tad warm. The only real issue I've seen among the nightlies being sometimes the phone will just randomly shut itself off. May be because my power button is flaky though.

Sent from my SCH-I535 using wXDA Free mobile app
[Verizon Samsung Galaxy S III] stevet86:
I have some power buttons on order.
[Verizon Samsung Galaxy S III] phonetool:
Ok, what I'm seeing is this:

Write a text, click send

"sending... " stays there

Eventually get a "not sent" error.

Try again a few times with same results.

Friends say they get multiples.

Could be my signal is too weak at the house.
[Verizon Samsung Galaxy S III] Master Cylinder:
Oooh! That's a problem. You're on the latest firmware, modem, etc ... It definitely does seem to be a one of. No complaints here or on the d2att thread.

However, over there they're noticing that 'Live Display' doesn't adjust automatically. I'm having that same problem. Just have to manually adjust it.

PS - I may have had a heat problem earlier in the week - don't remember what nightly or even ROM I was on (playing with another CM derivative some) I thought it was from sun exposure, and may have been but it took quite awhile before I could get it nominal. Had to leave it out of my pocket for awhile.
[Verizon Samsung Galaxy S III] phonetool:
Yup, latest firmware and radios, followed the OP closely back in late May. It's probably just a signal issue.
[Verizon Samsung Galaxy S III] phonetool:
I guess my messaging issue has settled down. One problem was an "unsendable" text stuck in the queue. I was able to delete it by installing handcent, which has queue visibility. Uninstalled it afterwards and am back on the stock messaging app.

I've been loving the last couple of nightlies - strong 3g. I see LTE pop up more often, I think.
[Verizon Samsung Galaxy S III] matt_man:
I'm getting this same problem with hangouts when I have a week signal. I have the straight talk variant.
[Verizon Samsung Galaxy S III] Ghost Protocol:
REF: Not Able To See Pics or Images Sent To Me.

Hello and Good Evening,

I have been having a major issue with CM-12 based ROMs lately. When someone sends me an image/pic it just says ~ "Downloading". Nothing downloads. I believe the issue is with GApps. I am currently using TK GApps package. I reflashed this ROM and flashed other ROMs trying to pin point the issue. After flashing this ROM I received the image and was able to view the image/pic. Then I flashed TK GApps and now I can not view any image.

What GApps package is everyone else using? Am I missing something here? Is anyone else having this issue? :confused:
[Verizon Samsung Galaxy S III] XdrummerXboy:
I have had downloading issues in the past. Try downloading it with a different browser or app, usually fixes my problem
[Verizon Samsung Galaxy S III] Gibscreen:
8/6 nightly caused system profiles to no longer allow you to disable the lock screen. For example, I have a profile for home that disables the lock screen security. Worked great until 8/6 and now it's greyed out and says it's disabled by device administration policy. Didn't find anything in settings, security, development, lock screen. Any ideas on how to re-enable?
[Verizon Samsung Galaxy S III] brandonb0013:
I've been running 6/3 since, well, 6/3, and am thinking of dirty flashing to a newer nightly. What's a good one people have been having the least amount of issues with? The only reason I'm updating is for the call recording that came out on 6/18 build and that privacy text message "hack" thing. Thanks guys.
[Verizon Samsung Galaxy S III] Gibscreen:
Cleared credentials and it's no longer greyed out.
[Verizon Samsung Galaxy S III] phonetool:
I'm only experiencing each nightly for a day. My phone demands are not extensive enough to really test all aspects each day. Mostly I worry about data signal. Some days seem to be better than others, but in general things work out.

I'd say hop on anything recent. There haven't been any glaring issues. It gets better and better.
[Verizon Samsung Galaxy S III] brandonb0013:
Awesome. I already downloaded 7/31 and figured I'd see how that goes.
[Verizon Samsung Galaxy S III] AyUaxe:
8/5 nightly seems good

Seems there were some minor issues with data and messaging in a couple of late July builds, but either resolved by the next build or user action. Just browse back a few pages and you'll see. I think 7/31 was after the little hiccup. I'm on 8/5 and it's great. Be aware, if you're using dkp kernel, after 7/26 cm nightly you need to use the latest dkp. Check [MENTION=4932679]decimalman[/MENTION]'s forum for details. And don't forget to thank [MENTION=2044079]Nardholio[/MENTION] for bustin' balls, building awesome builds, solving crimes, breaking hearts.
[Verizon Samsung Galaxy S III] brandonb0013:
So I'm running 7/31 and haven't had any issues. I flashed dkp right away no issues. Thing is though that I'm running the same dkp as I was on the 6/3 build. It seems to be working, what happens when it's the wrong one?
[Verizon Samsung Galaxy S III] exdiei:
Llama, not polling cells

After doing a proper wipe of my sgs3 I flashed the latest nightly and everything works, except for minimal glitches which I think will be fixed soon.

When I had CM 11,Llama worked with no problems at all, but now that I installed it in CM 12.1, it's not doing what it's supposed to. Not even when I run the events manually within Llama. is anyone else having these problems? Any other solution besides Tasker.
[Verizon Samsung Galaxy S III] XdrummerXboy:
7/17 version drops WiFi data sometimes, doesn't even show an exclamation point most of the time. I have to toggle WiFi to get it to work again.

I realize that 7/17 is semi-irrelevant at this point, I thought I was on a newer nightly. Figured I'd share anyways.

Edit: also, random freezing when composing a Facebook message on messenger
[Verizon Samsung Galaxy S III] phonetool:
After flashing tonight's nightly, my phone signal was so weak - 0 bars.

I had trouble getting a text.

So I tried something that I haven't done in a while: dial *228 and update roaming.

After that and a reboot, I have two bars.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Isn't that what can fry SIM cards?
[Verizon Samsung Galaxy S III] Shakes The AssClown:
*228 will cause you to lose LTE.
[Verizon Samsung Galaxy S III] phonetool:
Interesting. I'll have to stop by the local Verizon store now to reactivate.
[Verizon Samsung Galaxy S III] phonetool:
I noticed that wake by volume buttons is working since a few days. So that's good.
[Verizon Samsung Galaxy S III] Jaws4God:
I'm having issues with MMS.. specifically group MMS... anyone have a fix?
[Verizon Samsung Galaxy S III] phonetool:
I don't send them, but have trouble getting them to download and sort correctly. And don't even mention multimedia- downloads just don't want to download.
[Verizon Samsung Galaxy S III] Roger W:
Does anyone know the status of Bluetooth A2DP MP3 codec support in current builds?

For background, A2DP is the mode where a device can stream digital audio to a receiver. At a minimum, it can use a so-so codec called SBC, but it can support MP3 and more if both devices support that, and stream MP3 files without recompression.

I've used the bluetooth snoop log in Wireshark to verify that my car's head unit reports that it can receive both SBC and MP3, and that MP3 files are being recompressed using SBC anyway. This suggests that the phone doesn't support MP3.

In older versions of Android, this could be tweaked by editing an audio.conf file under Bluetooth, but in the past few years, that file went away and there are vague reports of build.prop supporting some settings to enable this, and also conflicting reports that Android has to be recompiled to support it.

Does anyone know if CM12.1 can be tweaked to support this without using a private build?

thanks