yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] AyUaxe:
mms

I'm on 8/5 now and getting way more group MMS than I really want (group of friends are losing it about Jets qb getting punched). I use textra for all msgs. Only on lte, though. Have never gotten MMS on WiFi.
[Verizon Samsung Galaxy S III] brandonb0013:
I use hangouts and the xhangouts xposed module. Mms always send within two seconds, always receive, same with group mms. Plus some customization options for funsies.
[Verizon Samsung Galaxy S III] AyUaxe:
Looked back at op and page 1 of this thread:

"In 2 weeks this will have 15 pages and probably no need to go back," said [MENTION=6629594]mastercylinder[/MENTION] on 5/20. 15th page hit 6/02. And look where we are now! Forkin' Orsome! Mega thanks to [MENTION=2044079]Nardholio[/MENTION] and the whole community for keeping our d2s singing.

On 8/5, had a couple of reboots each after about an hour of blue tooth use. Anyone else? Otherwise great!
[Verizon Samsung Galaxy S III] Jaws4God:
yeah i read that hangouts works.. thats what i'm using right now... didn't do the xhangouts xposed.. not sure why that is needed?
[Verizon Samsung Galaxy S III] brandonb0013:
If you have access to xposed just go check it out, you might be excited. Biggest thing is it sends mms waaaaaaay faster and more efficient. Also can customize color of hangouts app. Also can send a message and lock phone with one tap. There's a bunch more, it's a great module.
[Verizon Samsung Galaxy S III] LLStarks:
I've been struggling to maximize battery life.

50% brightness seems to be the only remotely effective option.

Amplify, Greenify, etc don't seem to help much.
[Verizon Samsung Galaxy S III] AyUaxe:
Are you using stock or dkp kernel? I think I get better battery and performance with dkp. I've seen no difference in basic stability (except when I screw stuff up my own self). Be sure to read the whole op on decimalman's dkp thread.
[Verizon Samsung Galaxy S III] Master Cylinder:
If you don't get an answer here you might try noodling around and/or posting over on forum.cyanogenmod.org
[Verizon Samsung Galaxy S III] Deliquified:
Stock kernel on cm 12.1 has zero optimizations for battery life. Installing a custom kernel will help
[Verizon Samsung Galaxy S III] AyUaxe:
Is there any custom kernel that works for d2vzw on 12.1, other than dkp? Back on 10 or 11, there was a time that boeffla worked, but the last time I tried it, don't think it would even boot. Just curious, as dkp has been awesome.
[Verizon Samsung Galaxy S III] Jaws4God:
same here.. i'm just hoping my battery hasn't settled in since I did a ton of flashing the last few days to find the ROM i wanted... but EMAIL is the biggest hog... :eek:

---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------

Do you have the link for Xposed? is it stable for Lollipop?
[Verizon Samsung Galaxy S III] brandonb0013:
http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979

That's the link, I believe you have to flash it in a recovery for it to work. Also, I haven't had issues with it, but theres only certain modules that work, the list can be found with a quick Google search, but it steadily and quickly growing.
[Verizon Samsung Galaxy S III] :
Bull****.

Love,

Your kernel maintainer

---------- Post added at 05:06 PM ---------- Previous post was at 04:55 PM ----------

Answers to recent questions:

Lollipop is heavy on animation. Switch to battery saver or turn off animations in developer options.

SMS is programmed in the RIL to wait for acknowledgement from the tower before reporting as sent, I may reevaluate this for extremely weak signal environments. I need logs, pm me and I'll let you know what I need.

I haven't heard of any CM phone supporting mp3 direct coding over Bluetooth.
[Verizon Samsung Galaxy S III] Deliquified:
No? Decimalman posted this about a month ago unless things have changed significantly battery life wise since then?

"... CM12.1's battery life is terrible for a reason: the CM kernel currently has almost all CPU power saving features disabled. Since cores won't be powered off, and they can't enter a deep idle state, they just waste power and accomplish nothing. The end result is better performance, but (IMO) the cost to battery life is way, way too high."
[Verizon Samsung Galaxy S III] :
The second core does offline with mpdecision. He may be using a custom hotplug driver for better results.

The deepest power state is blocked for stability since it has problems waking up on Krait, leading to reboots. I am not convinced dkp has solved this, as it's a hardware bug.
[Verizon Samsung Galaxy S III] Master Cylinder:
oops
[Verizon Samsung Galaxy S III] Master Cylinder:
:laugh::laugh::laugh:

Hardy-har-har!!

Sorry, had to laugh at that one...

[MENTION=3082999]Deliquified[/MENTION], [MENTION=4670039]LLStarks[/MENTION]: If you have a process watcher that can also watch the cpu you'll see the second core going offline all of the time, n'est pas? Also Kernel Adiutor. In fact, why not use Kernel Adiutor with the stock kernel, though there are some limitations there, but still plenty of options.

EDIT: Actually, you can use the CPU Info option in Dev Options to put the cpu frequency activity over everything..
[Verizon Samsung Galaxy S III] phonetool:
Every time I flash a nightly (every day) there is a lot of time spent "optimizing apps" - like 20 minutes or so.

I think I saw in another lollipop thread (probably for the Gnex) that the stupid swirling icon that is displayed during this process actually eats up loads of cpu, slowing down the task at hand.

Anyone know how to disable that feature?
[Verizon Samsung Galaxy S III] kmoore11:
How stable are the current nightlies? I've seen recent comments about battery life, MMS, weak signals, etc. I'm still on the 6/5 build which has been pretty good and lasted me 2 months now, but I'm ready to see what's new.
[Verizon Samsung Galaxy S III] Master Cylinder:
Very very stable. :good:

Most people, like you, don't post when everything works great, and/or aren't updating frequently. You want to upgrade to the very latest to get the stagefright vulnerability patches. Might want to keep updating for awhile till they make sure it's completely solved, though CM is way ahead of the game on that I expect.

Google moves like an oil barge - CM like a jet boat!
[Verizon Samsung Galaxy S III] cyber_nicco:
Great so far, but where's the 1080p?

The ROM has really been running well so far - much smoother than other Lollipop ROMs I've tried lately. Thanks so much!

That being said, I hate the included camera app (poor me). Is there any way to make it aware that the camera on the phone can shoot 1080p video? Or is is just a limitation of the application? Is there a good 3rd-party camera app that someone can recommend — preferably open source, but whatever. :)

Anyway, thanks again!
[Verizon Samsung Galaxy S III] AyUaxe:
stage fright issues

Agreed, [MENTION=2044079]Nardholio[/MENTION] has done an awesome job consistently improving and addressing issues in thus ROM and for this community. By 8/12, 4/5 of the stagefright issues had been patched. 8/14 all 5 were resolved. That's according to the stagefright tester app recommended elsewhere on xda. I still do regular backups when it's running sweet, like now, bc this phone is still my DD, but haven't needed to restore from one in about a month and that was a gapps issue. Flash this ROM and dkp kernel=profit!
[Verizon Samsung Galaxy S III] Master Cylinder:
It's a limitation of the phone camera, isn't it? With Open Camera, you can set it for 1080 but it will record in 720.
[Verizon Samsung Galaxy S III] AyUaxe:
According to http://www.phonearena.com/phones/Samsung-Galaxy-S-III-Verizon_id7114 it should do 1080p @ 30fps. I also use open camera, so no idea what other app might get us there.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well caca!! :o Misread that one, though I did put Open Camera in 1080p but the video is reported as 720p.

None of my other cameras will set it there.
[Verizon Samsung Galaxy S III] brandonb0013:
Hangouts sent it just fine... So never mind I guess? I was using Google's new messaging app.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I've had issues with googles messenger app too. CyanogenMod's messaging app (the green one that looks like messenger) seems to work fine.
[Verizon Samsung Galaxy S III] brandonb0013:
I checked my app drawer, not there, checked the apps setting and its installed, not disabled, and I checked nova settings its not hidden. Also, when I go to change my default SMS it not available to choose from. Idk what happened but I'll just stick with hangouts haha.
[Verizon Samsung Galaxy S III] Master Cylinder:
It's not there. As far as I can tell, and I've researched this for hours, there is no way to actually know what your "secondary" bootloader is, sometimes called a bootchain. Every command at terminal or through adb give me only the "AP" bootloader which is like the primary bootloaer, which is VRALE6 on mine (that's what I flashed when I first rooted) which gives access to Download mode. Even the TWRP recovery log and the system info apps only give this on mine.

When people are talking about boot loader, they're talking about the secondary bootloader residing on partitioins SBL1, 2 and 3. These commands read what's on ABOOT partition for the AP Bootloader on mine.

Caveat: this is on mine which was rooted with flashing files through Odin, so I'm not sure if or why that would be different for someone who broke theirs a different way. However, if you look at the updater-script for the firmware file, you'll see exactly what file is flashed where.

I'd sure like to have someone prove me wrong because many devs and apps declare this command or that will tell you, but not on mine. You can try this on yours in a terminal: getprop ro.bootloader and see what you get? There is an adb command also.

However, if you're unsure, it won't hurt to flash the MF1 bootloader, as long as you then flash the NE1 modem after. I found myself unable to boot ROMs I flashed a couple of weeks ago and reflashing these fixed my issue.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Whoops, I led you astray... Apparently its the default android messaging app still, com.android.mms. Sorry about that!
[Verizon Samsung Galaxy S III] brandonb0013:
Haha. All good. Appreciate the effort!
[Verizon Samsung Galaxy S III] Master Cylinder:
You could post screenshots of your APN page then the APN type portion of your choice. Maybe others may have some input.
[Verizon Samsung Galaxy S III] yorkwar:
I'm using TWRP-2.8.6.

Thank you.
[Verizon Samsung Galaxy S III] Lrr_r:
The helpful and non-ambiguous way to identify a post is a link, not a "Nth on some list in some search". Assuming you're talking about this one, it doesn't seem to deal with the chosen volume level getting forgotten so I don't get the condescending attitude.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
After running that command, I get: I535VRALE6
[Verizon Samsung Galaxy S III] Master Cylinder:
Condescension not intended, but tends to leak out from time to time. Thanks for catching it. :o

Sorry that solution didn't work for you.
[Verizon Samsung Galaxy S III] hallstevenson:
Because....

Realize that some phones never get updates. Even some custom ROMs get updates once a month, once every 2-3 months, every 6 months. With "nightlies", it's probably silly and unnecessary to download/install on a daily basis. Just read the changelogs and you'll see that the updates are generally very low-level stuff that users almost never encounter.
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
Flashaholic Alert!! I. Must. Flash. :p :D :silly:
[Verizon Samsung Galaxy S III] Master Cylinder:
Possible Problems with recent builds

As [MENTION=2963287]mastamoon[/MENTION] alerted us yesterday, there may be issues with recent builds that include a serious rebooting problem that could be holding up builds. Here is a device maintainer's report for the SGS3 ATT model yesterday, which also includes reference to BT issues:

Reboots are still being looked into. The cause is known, coding around it is a bit difficult.

Bluetooth issues on CM 12.1 are not just on d2. Someone even made an app https://play.google.com/store/apps/details?id=co.loudbit.ao_shi

I'm getting the shakes, too, but it looks like we'll have to sit tight till the big brains get it worked out.:cyclops:

EDIT: link works now.
[Verizon Samsung Galaxy S III] bgorrell:
May be a slight leak there, but not taking it personally! If it's been an issue since February, I think it's worth another discussion. I followed mastamoon's thread thru most of it's life and did overlook that post. I adjusted the "voice earpiece" setting to 70% and still have the same issue. Besides being too loud, pressing volume up or down makes no change in the in-call volume. The point is if it's a bug it's not fixed. If it can be resolved so we don't have to edit a file every time we update (which didn't work) or adjust our volume every time we make a call (which also didn't work for me), it is worth addressing again. If the issue is specific to my device, that's different, but hasn't been determined yet. Just looking for some feedback/advice.
[Verizon Samsung Galaxy S III] mastamoon:
Try using the onscreen slider for incall Volume.. Maybe sliding that back and forth will work. Have you clean flashed lately?
[Verizon Samsung Galaxy S III] bgorrell:
I did experiment with both the on-screen slider and volume buttons extensively today. Neither makes a difference to the volume. I did a clean flash including going back to MF1 first about 4 weeks ago. But, I realize a lot can happen in that time. I'll try another clean flash later this weekend and report back.
[Verizon Samsung Galaxy S III] mastamoon:
If nobody else has come forward saying "me too" it's likely and issue with something with your setup. Kernel, mod, theme, app... You would be surprised what can cause odd, one off, issues.
[Verizon Samsung Galaxy S III] Master Cylinder:
I'd swear this issue is familiar from either masta's or amf66's thread... Oh yeah! I had the same thing as far as not being able to change volume in call at one point in 12.0 but later builds seemed to fix it. Maybe I had something going on that changed and didn't know it.

As to any little thing sometimes can make a difference, have you pulled the battery? (I'm sure you have by now for one reason or another.) And you flashed the NE1 modem after MF1. I guess you're on 5/18... Do you have a nandroid of some ROM that you think it works properly to make sure it ain't hardware related?
[Verizon Samsung Galaxy S III] hallstevenson:
Is anyone still making custom kernels for the S3? Speaking of volume mods, many allowed the ability to change levels but the sick CM doesn't appear to (the setting doesn't show up in Trickster Mod for me).
[Verizon Samsung Galaxy S III] toosurreal01:
Tried 8/16 and 8/17 and couldn't get data.

Flashed back to 6/15 and data is fine.

*EDIT: This fixed it for me
[Verizon Samsung Galaxy S III] ChuckFarley:
Curious, does everyone have issues with screen freezing on the YouTube app when watching 60fps vids? Is this a hardware limitation of the S3?
[Verizon Samsung Galaxy S III] Master Cylinder:
Stagefright Update

The latest Stagefright vulnerability patch update happened on the 8/14 build. Anyone using an older nightly might want to consider updating to 8/14 or later. All are good.

Will update the OP as well.

In depth (more than you ever want to know) XDA article on the Stagefright Exploit, though new required tweak for 8/14 not mentioned: http://www.xda-developers.com/stagefright-explained-the-exploit-that-changed-android/ That's mentioned here: http://www.xda-developers.com/a-demonstration-of-stagefright-like-mistakes/
[Verizon Samsung Galaxy S III] Shakes The AssClown:
I have the issue where the video freezes but the audio keeps playing
[Verizon Samsung Galaxy S III] brandonb0013:
I had that issue, just went back to an older version of the YouTube app and it seems to work just fine.
[Verizon Samsung Galaxy S III] phonetool:
Google Play Services has just been updated. Perhaps YouTube requires the latest?
[Verizon Samsung Galaxy S III] brandonb0013:
YouTube still works. The video will play about 5-20 seconds then the video will freeze but the sound will continue. Occasionally the video will come back for a half second or so. The older versions work just fine on my end.
[Verizon Samsung Galaxy S III] Master Cylinder:
Every video I play on Youtube works normally. However, I don't know how to find out what fps they are running at, so [MENTION=2690787]ChuckFarley[/MENTION]'s complaint I can't verify. My Youtube version is 10.31.55 and my Google Play Services is 5.8.8

PS - I'm on 8/20, bout to go up to 8/23.
[Verizon Samsung Galaxy S III] LLStarks:
Anything we can do to prep our phones for Android Pay?

Is NFC payment gone for good in our AOSP trees?
[Verizon Samsung Galaxy S III] :
I didn't think you were still using a d2. Unless someone comes up with some HCE code for pn544 I'm afraid that function will be missing.
[Verizon Samsung Galaxy S III] LLStarks:
Believe me, I'm trying to get off of this thing.

It just needs to hold out another month until the new Nexus 5.
[Verizon Samsung Galaxy S III] ChuckFarley:
I'm on the latest version, 10.31.55. The fps comes up now as an option for the quality level of the videos, 720p60fps. This quality option may not be available in the older version you're using? Not sure. As had been mentioned, the video will pay for a few seconds and then will freeze, but the audio continues. I'm just not sure if this is a CM issue, our a hardware issue. Anyone know if the issue exists on the TW roms as well? Thanks.
[Verizon Samsung Galaxy S III] Master Cylinder:
Our version numbers are the same! Came out 2 days ago. Mine shows the resolution only, no frame rate, even if I activate 'stats for nerds.' Nor can I find a way to activate that. Hmmm....

Maybe you can send me PM a video to look at that is 60fps?

EDIT - Restore one of your TW nandroids and tell us! :p Actually, I have a few around...
[Verizon Samsung Galaxy S III] ChuckFarley:
That's what I am thinking, try this vid: https://youtu.be/qrsATkVwu-8

I'll try out TW tonight, I'm on the run today.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well, this is interesting. I am presented with the frame rate after the resolution on this video. First time I've seen that. No other videos have offered the frame rate. Also, it freezes up in Youtube just like you said. But, in Tapatalk, if you tap on the image of the link then it pulls up it's own video player, apparently, unless there is one in CM12 that I can't find. And, it works normally there. Also, if you pull it up in Chrome, it works normally!

¯\_(o_O)_/¯
[Verizon Samsung Galaxy S III] phonetool:
Played in Dolfin browser just fine for me.
[Verizon Samsung Galaxy S III] ChuckFarley:
The 60fps on mobile YouTube is relatively (kinda) new, but it's a real pia when it doesn't work and the next best is 480p. I know that it doesn't come up at 60fps on chrome, looks like 480p to me. I'm not trying to complain, too much... I'm more just curious if the S3 doesn't have enough horsepower to push 60fps and would like to defer to your expertise, if you'll allow it.
[Verizon Samsung Galaxy S III] Master Cylinder:
I loaded up an Alliance TW nandroid and that video seems to work perfectly on there I'm sorry to say.

That would be a mistake. ;)
[Verizon Samsung Galaxy S III] ChuckFarley:
Thanks, Master Cylinder.

Dang! I was afraid of that. I do recall there being slightly better YouTube performance on tw. Hmmm... Decisions, decisions...

I was right to trust this question with you! So I'll try it again: in your educated opinion, what are the chances CM could/would be made to improve or match tw performance on the YouTube app?
[Verizon Samsung Galaxy S III] Master Cylinder:
That is a question for our device maintainer [MENTION=2044079]Nardholio[/MENTION]. (now that I've mentioned him maybe he'll come around and straighten us out.)

My own limited understanding/best guess is that a TW ROM does have drivers provided by the specific chip manufacturer for that particular chip and it's unique specifications for a specific function and alternative drivers sometimes can't match the performance. I've always felt that the mics don'lt work as well on AOSP, and some functions that TW provide and depend on the other sensors don't exist at all in AOSP for our phone because there are no 3rd party or open drivers for them, I suppose.

You see the same thing in Linux. Open source can't always mimic closed source code and there are too many possibilities. Sometimes stuff won't work right or at all.
[Verizon Samsung Galaxy S III] ChuckFarley:
That's a perfectly reasonable explanation that even a hack like me could understand. Thank you for your responses and for taking the time to entertaining my questions. I hope it didn't take up too much of your time.
[Verizon Samsung Galaxy S III] realicet:
Radio issues

Yeah I started with cm 12.1 on the 6-20 build and it seemed to work pretty good. The 4g and 3g data would go out and either say no sim or no service once every few days. Every now and then I would have to airplane mode reboot and the radio would function okay. Over the past couple weeks though this problem happens multiple times a day and I have tried since the 8-14 nightly to keep updating but it doesn't seem to help. This thread has gotten very long so maybe I missed a fix for this but any insight would be appreciated. I didn't know if reinstalling the 2 radio firmware zips could help or if I should wipe completely to a new nightly instead of "dirty updating" through the cm updater?
[Verizon Samsung Galaxy S III] :
Personally until proven otherwise I'm going to assume it's a YouTube issue as it's been reported that older apks work.

If you figure out otherwise please send me a patch.
[Verizon Samsung Galaxy S III] Master Cylinder:
I just tried back 4 versions with the same failed results. It could be others reporting success without realizing that a video that can run at 720p 60fps was coming up at 380p by default and had to be manually changed to the higher resolution and frame rate, like I had to do each time. I also tested other high resolution/frame rate videos with the same results.

I would try flashing just the MF1 firmware/modem combo first and see if that fixes your problem - that's what I've done to fix mine.

Got nuthin' but time at the moment...:eek:
[Verizon Samsung Galaxy S III] Stealth111:
Am I the only one that seems to be having data issues. I completely blew out my phone, and clean installed the latest nightly, and at random, I just lose data connectivity. Not just LTE, but data all together. I though it was from dirty flashing 6 months worth of roms. But somewhere alone the line around the 20th I can no longer keep data running...It was literally switching switching "MobileNetworks" to the off position. But since the clean install, it still loses data, but no longer switches off the "mobile Network" setting....Any ideas? I even tried switching back to MF1 firmware and modem for ****s and giggles..I am stuck with a 5 bar signal with an "!" next to it...I also have NOT turned on wireless at all or installed any programs since the wipe and flash..
[Verizon Samsung Galaxy S III] bryank29:
Had same issue...but it doesn't do it anymore. I Just ran an upate on various apps in the play store so maybe youtube was in that bunch.

---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------

I still have to manually flop the access points in Data because I get the "!" next to my LTE after a reboot. It's annoying but once it's enabled I am good to go.

SETTINGS > MOBILE NETWORKS > ACCESS POINT NAMES then click another radio button...wait a moment, and the original radio button should be re-selected, and your Mobile data should enable.
[Verizon Samsung Galaxy S III] Gibscreen:
8-26 nightly causes chrome to crash. Tried clearing cache, reinstalling chrome, nothing works. Someone over on a OnePlusOne forum had the same issue. Anyone experiencing this with 8-27 nightly? Just curious if they've already fixed it.