yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] o0BlacknesS0o:
Just for future reference to everyone

Reinstall of both was not necessary... After you first download and install Gravity box... You have to go into Modules and check the box next to gravity box then reboot then you can set it up... I believe this is listed in the directions for gravity box in its thread... After installing you can't go straight into its settings... Have to check it then reboot then you can access it's settings... Just for future reference

I have a bug with the profiles... I have Profile A set to use Insecure lock screen and profile B to use system default

System default is set to pattern lock screen

Whenever profile a is set it only uses the pattern lockage instead of using the insecure... Any thoughts?

Found another bug... Long pressing profiles quick setting causes a settings force close
[Verizon Samsung Galaxy S III] goldsmitht:
OK, I'm feeling like a noob again; how do I take a screenshot on 4.4.1 and how do I add that function to power menu? Sorry, on phone and can't find it
[Verizon Samsung Galaxy S III] ojpd:
Press on Power + Volume down button for like 1.5 to 2 seconds
[Verizon Samsung Galaxy S III] rhamorsky:
look under settings>buttons>powermenu
[Verizon Samsung Galaxy S III] goldsmitht:
Damn, thanks, I dirty flashed 10.2 so much I forgot where to look.

Muchos gracias

:banghead:
[Verizon Samsung Galaxy S III] Defragger51:
I am still running 12/9 nightly, just unplugged my phone at 9 am with a 100% charge an hour later at 10 am of all screen off idle time I have 88% battery, with phone idle using 31% of my battery . How is this possible? Until I changed from the unofficial builds to the official builds yesterday I had very very good battery life, would only go down 5% in and hour of screen off idle time. Does anyone else have this problem? Yes I did a complete clean data ,cache and dalvik wipe before install of the the 12/9 official cm_11
[Verizon Samsung Galaxy S III] jehelmer:
I just couldn't leave well enough alone... I did a clean install of cm11 which was running great this morning. And then for some reason I decided I should do the *228 programming (I thought it might help with poor service I was having in areas)...now I have 3g and don't have any 4G... Anyone know what I can do to get 4g back?
[Verizon Samsung Galaxy S III] ChuckFarley:
Darn, I was hoping that was the magic trick. Best of luck to you.

---------- Post added at 06:42 PM ---------- Previous post was at 06:13 PM ----------

One last ditch effort and I'll leave you alone. Have you tried fixing permissions from recovery?
[Verizon Samsung Galaxy S III] Hybridnoob:
A clean install (including full Odin) didn't fix it. One of the Devs said it's a QCRIL issue (not a problem on AOKP because it wasn't merged). I'm not really sure why it only affects some people, but I personally know one other person with the same issue. That person hadn't changed anything on their phone for at least a week when they started getting the SMS bug. Incidentally, I experienced SMS problems that same day. I believed (and still do to some extent) it was a Verizon problem.
[Verizon Samsung Galaxy S III] jager420:
I took the plunge and installed latest nightly with gapps posted in OP. I was a a little reluctant because of post claiming text didn't work. I'm running TWRP 2.7.0.0 and I chose advance wipe and wiped everything but micro SD. So far I do not have any issues with text messages (have received and sent pics as well) and the ROM run smooth. I like the phone dialer acting as my yellow pages. I really hope cell signal is good while working this week(in my experience I usually have to be on TW for good cell signal).
[Verizon Samsung Galaxy S III] MorphiousGX:
I installed the 4/6 nightly. Clean install since I had TW on before.

Funny thing is.... It charges fine using wireless charger, but not plugged. And I only see this with CM. I will have to try anther CM based ROM to see if I still have the issue.

I flashed back JB ROMs (cm and tw) and issue's gone.

Any thoughts are appreciated

---------- Post added at 02:03 AM ---------- Previous post was at 02:00 AM ----------

I bet I know your issue. Are you using default SMS app or hangouts?
[Verizon Samsung Galaxy S III] Hybridnoob:
Since something is clearly wrong and it's not a hardware problem, I would try to Odin back to stock then restore your CM backup (from external SD card) to see if that fixes your issue.

No, I disabled the stock SMS app and use a 3rd party app. I'm curious what you think my problem is though.
[Verizon Samsung Galaxy S III] Casper34:
Try re-enabling the stock SMS app. Then try. I think some 3rd party text apps still send through the stock app.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] wierdo124:
Have we/are we getting an M5 release?
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks, but that didn't work. I didn't expect it to, but tried it anyways just for curiosities sake. I'm able to send one (sometimes two) messages before receiving a failed to send message. If I toggle airplane mode or reboot, I can send one another message (or the failed one will then send). Again, no worries, I'm sure it will be fixed in due time. Voice+ is a good workaround for now.
[Verizon Samsung Galaxy S III] Casper34:
By chance, you don't have anything frozen do you?

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] Hybridnoob:
No, see below. The rest of the post is interesting as well, but to save space, I've included a link to it.

"D2lte and Jflte

Normally, we wouldn’t comment on specific device families in release posts – under the basic pretense that if the devices aren’t ready, they simply shouldn’t go out. D2 and JF present an interesting issue for us. As we unified GSM and CDMA variants into ‘one build to rule them all’ we’ve been making necessary modifications over the past 2 months or so to address all the feedback we’ve received. However, now that all the variants are served by one build, it would lead to confusion to release a build under the ‘M’ banner that worked great on 90% of the supported variants, but not the remaining 10%. Users of the CDMA nightlies for these devices would likely agree that there are still some niggling issues. It is our plan to address these items prior to green-lighting an M build for these families.

Understand that this decision stings. Our device maintainers have done an amazing job with planning, executing and handling all the complexity the unification process involves – and now we’ve held these devices from 2 M releases in a row. However we stand by the fact that release decisions should be based on the actual quality of the release; even if it means making an unpopular decision. If you are in desperate need of a D2/JF ‘flash’, then the nightly channel builds are available for that purpose. Else, trust that we make these decisions based on the responsibilities you place on this team. /tangent"

http://www.cyanogenmod.org/blog/cyanogenmod-11-0-m5-release
[Verizon Samsung Galaxy S III] mastamoon:
Could you get us a logcat from boot all the way through to sending an sms till failure?

You'll have to do this from a pc and have the logcat capture running from reboot.. I usually have 2 command prompts open, one with adb reboot ready and the other with adb logcat > logcat.txt Ill issue the reboot command once the initial boot splash happens, hit enter on the logcat prompt.

Grabbing a logcat after the fact wont work, needs to be captured during boot.
[Verizon Samsung Galaxy S III] skytbest:
I've ben getting very high Android OS and System battery usage. Anyone experiencing the same thing? This is while on 4G. Here is a screen shot of my battery stats:

http://imgur.com/MQUDGso.png

http://imgur.com/ek0vmKv.png

I'm on the 3/28 nightly, using ART, KT747 kernel - undervolted, and governed to max 1.3Ghz. Any recomendations on how to fix this issue?
[Verizon Samsung Galaxy S III] chowner:
Stock kernel, Dalvik, and no governor
[Verizon Samsung Galaxy S III] skytbest:
For real? Has this been the general stance so far? Where can I find the stock kernel sepeartely?
[Verizon Samsung Galaxy S III] stiltzkin:
I am getting completely abysmal battery life (~3-4 hours total, with maybe 30 minutes of actual screen on time) on recent builds. Also, my phone takes about 8 hours to charge, whether on the nice OEM 1A wall charger or over USB, it doesn't matter. This basically renders my phone unusable. However this did not start with 4/2, which I am running now, but has been going on since my last flash of 2/13. So I don't really know if this is a software issue or a problem with my battery; I may reflash stock rooted to find out. I also tried dkp with fast charging support to see if it made any difference with the charging time; it didn't.

I'm not sure what is causing this and so I normally wouldn't post about it, but others have been mentioning poor battery life so I thought it might be worthwhile to mention.

The issue persists with the above setup.
[Verizon Samsung Galaxy S III] rhcreed:
Ever since the change to cm11 (from 10.2) I started having the same thing, bad bad battery, unstable, just really unhappy phone. A few weeks ago I sacked up and did a full wipe of everything (with /system format) and a re-install. Solved all of my problems. Very glad I did it. I've been sticking to the 3/24 nightly cause it's stable and I'm good. I never had the mms issue so many people are talking about.

I'm running art (don't really see a difference, sorry). and now I'm backing up daily with TiBu.

Maybe it's time for a full wipe? Hope this helps someone.
[Verizon Samsung Galaxy S III] chowner:
I've experienced the slow charge, but if I reboot and clear caches it's been fine after that everytime.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks, Masta! I wasn't looking for direct support, just letting a user know there's some issues for some people. Since you're willing to help, I'll try to get a log soon. I'll try to get it this weekend when I have some free time. Do you want me to send it to you direct?
[Verizon Samsung Galaxy S III] mastamoon:
You can email it to me if you like, myxdausername [MENTION=5499064]gmail.com[/MENTION] :D
[Verizon Samsung Galaxy S III] SDQB17:
Running 4/5 and I was getting some of the best battery life ( 65% left after 8-9 hrs at work), that is until today when my battery discharged in 3-4 hrs. I looked at battery stats and somethings are a bit off I would say. My AV app (Lookout) which never uses a lot had used 25%, so did Google play music and I had not even used it in about 3 weeks. Also something called Media, used over 25% and I couldn't even force stop or access that one. And Twitter..which I wasn't using either. Weird that all 4 show 25 or more percent and these are app that don't ever show up as using a lot of battery normally. My phone went down to 3% before 10AM, Left for work at 8. Stock everything , just CM .

Something else...my sd card isn't being recognized either. For a few days my notification bar was saying preparing sd card every time I woke my phone up.
[Verizon Samsung Galaxy S III] darkknight1812:
For those having high battery drain, try Greenify from the app store. I use it on all of my devices. Also, see if your phone is going into deep sleep. Sometimes an app or two might prevent the phone from going into deep sleep. You can use cpu spy to check or wakelock detector to see how many apps are causing the whole to wakeup. I would try this before a full wipe because if you install the same programs, then they will just continue to wake your phone after a full wipe.
[Verizon Samsung Galaxy S III] nrock2256:
So I've noticed a few things on 4/6: Terrible charging (8 hours to full charge), super low call volume, no speaker phone, and netflix causes a crash every time. I'm going to do the CM OTA to 4/7 and manually clear cache and come back with the results and an overall review of the rom thus far.
[Verizon Samsung Galaxy S III] SDQB17:
I am on 4/7 now and got a full charge from 3% in 2.5 hrs ( but it had discharged in less than 4) just the opposite...lol
[Verizon Samsung Galaxy S III] MorphiousGX:
Well, If you have Hangout installed, uninstall it. I had a similar issue that was due to the way Hangouts was installed (either integrated or via GApps). If that's the case, you can install it after you determine the issue.

As for MY issue with the battery. I've spent most of the weekend trying to figure it out. I ODIN, and flashed the 4/6 nightly again. I ODIN again and tried another CM based rom that used the latest nightlies. Same issue.

However, I found something rather interesting. If I kept the cable plugged, and I removed the battery, then inserted it back in... it will charge while the phone is off as it should.

But the moment I reboot, or unplug then plug back in, it exhibits the same issue. I do stress however, this ONLY happens with CM. I tried TW and I tried JB release of CM and also MIUI, but didn't see the issue. Only when I try KK CM. Any ideas? OH and reminder....if I charge using Wireless (QI), the problem is not there.

---------- Post added at 11:21 PM ---------- Previous post was at 11:18 PM ----------

I can tell that Greenify and Tasker combined with KTweaker/KT Kernel, I had my phone sipping battery when screen is off like 0.3% - 1% hour at the max.That's with Wifi/Data/Sync enabled
[Verizon Samsung Galaxy S III] Hybridnoob:
Done. Check your email [emoji106]
[Verizon Samsung Galaxy S III] :
And this is what I hate as a developer. Incomplete bug reports. You did not mention at first your problem was with power off charging mode. What happens exactly when you plug it in when it's off? And what is the exact sequence? Do you plug it in and turn it off, do you turn it off and then plug it in? What happens next?

And yes I'm the guy who would be fixing it. If you'll remember from a few pages back when I got in that spat with that guy when I mentioned this is the development section. So I'll repeat it. This is a development thread. Bug reports are appreciated. General chatter like "stuff didn't work" without logs and full details are not. General support should be in Q&A.
[Verizon Samsung Galaxy S III] MorphiousGX:
I appreciate your help and feedback. And just to give you an insight, I did file a formal Bug Report with all the details. So it is very possible that I "thought" I included it here.

Going back, I did verify that I did mention this only happens while Plugged In, Regardless of ON or OFF. And that I only am able to charge if using Wireless charger.

But since I am a Software Engineer myself and hate incomplete bug reports, I will give you the exact details in hope it helps with troubleshooting the issue.

1. Problem is inability to charge the device while plugged via USB or AC. Regardless of phone state (On/Off). This is only exhibited with CM KK releases.

2. Phone will charge without any issues using QI Wireless Charging, regardless of phone state (On/Off)

3. While phone is on and Plugged, Phone remains at the same % and shows its charging, however it is not. When unplugged, it takes it 20 seconds to recognize the device is unplugged and reports back the same % it had prior to plugging it.

4. While phone is OFF and Plugged, the phone will exhibit an endless loop and vibrate. It will not charge, nor does it show the expected behavior (Battery with % Charge and animated charging, then off screen). It does not matter if I plug and turn off, or have it turned off then plug in. Results are the same.

5. While phone is OFF and Plugged, the phone WILL Charge if I pull the battery and reinsert it. And will behave as expected. HOWEVER, it will go back to the issue in #4 if I unplug it or reboot it.

Steps to troubleshoot and concluding the issue:

1. I ODIN and started with Fresh Install each time I did the following (including wiping my internal storage clean)

a. Tried it with TouchWiz. No Issues as above

b. Tried it with MIUI (JB). No issues as above

c. Tried it with CM (JB). No issues as above

d. Tried it with CM (KK). Issues occurred

e. Tried it with CM Based ROMS (JB). No Issues as above

f. Tried it with CM Based ROMS (KK). Issues occurred.

To Clarify, I tried Carbon ROM which is based off CM for my tests on e and f.

The phone is on the ML1 Radio and Its not Bootloader is unlocked. Also, I am using the ROMs AS/IS for the tests. Strictly the ROM
[Verizon Samsung Galaxy S III] :
Please link to your bug report on the tracker.

---------- Post added at 05:14 AM ---------- Previous post was at 04:43 AM ----------

Please link to your bug report. Also which version of cm 10 did you test? Exact build and kernel version please.
[Verizon Samsung Galaxy S III] skytbest:
In order for this to help you actually have to have apps you want to greenify...
[Verizon Samsung Galaxy S III] skytbest:
Care to share your secrets? Any tips are appreciated. What are your Tasker scripts doing? Also how do set up KTweaker?
[Verizon Samsung Galaxy S III] Argent36:
Anyone having trouble downloading the newest nightly via the phone?

also it appears that the hangouts/mms issues are back - in the recently nightlies - - anyone have an old version where that worked?
[Verizon Samsung Galaxy S III] chowner:
seems the site is down at the moment
[Verizon Samsung Galaxy S III] zwolf4444:
Is anyone else still having GPS issues? My phone still has a hard time locking onto GPS, and frequently it lags or loses lock altogether. I'm on the 4/6 nightly, but I've had the issue continously since at least mid-March nightlies.
[Verizon Samsung Galaxy S III] MorphiousGX:
OK not sure how I can get that bug report #. Maybe you can help? I submitted it via the "Report a Bug" button from within the ROM. It gathered and sent the report.
[Verizon Samsung Galaxy S III] SDQB17:
Anyone have any clue why this is happening? What the heck is Media and why is it using all my battery...this is just the last 2 days with 4/5 and now 4/7. After 6 hrs at work it was down to 18% and the only thing using it was this..I actually didn't use the phone all day.

BTW..I am posting this here because the Q&A thread will not allow me to attach the picture file
[Verizon Samsung Galaxy S III] :
That actually does nothing. It composes an email in your email client after a long pause of collecting data. You'd still have to send it to someone. Please file a bug at jira.cyanogenmod.org
[Verizon Samsung Galaxy S III] mastamoon:
Can you verify if your sdcard is ok? Seems almost like the media scan service is having a hard time scanning the card or a file.

You should grab a logcat and see if you see anything related, or post it here for others to look at.
[Verizon Samsung Galaxy S III] SDQB17:
I'll do this...is it best to use something like Catlog ( having never done this yet) , also is there a certain amount of time I should let it run? ( another stupid question) again never done this...sounds easy just want to do it correct. I'll go check the tutorial.

Also as a side note...this must be why the last week or so whenever I wake my phone I see in the notification area it says " preparing sdcard "

Edit...I'll try a new sd card the phone isn't recognizing it. I suppose it could also be the phone itself?
[Verizon Samsung Galaxy S III] esjames:
I have a question for this community, yes i should post this in the Q&A section but I want answers from those using CM11 on the D2LTE builds only. Does the SMS features work on the latest nightlies using either the MF1 -or- ML1 firmware? My testing show the latest firmware works on the non unified builds and i really don't want to whip out odin again to verify this.

Thanks!!!
[Verizon Samsung Galaxy S III] mastamoon:
You can do it whatever way works for you really. Are you saying the phone doesnt see the new card or the old? If new, you might have to format it to work in your phone. If old, then its probably why your phone is freaking out. If both, well going back to stock and seeing if its recognized would be the test to see if its your phone or the cards.

It does work on either firmware... but some are bumping into an issue where SMS stops working... its happening on both ML1 and MF1.
[Verizon Samsung Galaxy S III] SDQB17:
The phone is no longer recognizing the old card. I have yet to run out and get a new one..will do that today. While at work all day though, I had the card removed ( only had music etc.. on it) and I am at 9.5 hrs and have 68% left :) So thank you for pointing out it is the sdcard. Don't know why I didn't figure that one out haha. Now to find out if it is the phone or the card or the software ( although I seriously doubt it). Update: New card is recognized and working fine. First time I have had an sdcard fail...now I know what to look for. Hopefully it stays this way...thanks Masta for the heads up on what to check
[Verizon Samsung Galaxy S III] skytbest:
I'm running the 4/8 nightly, using Dalvik, on the KT747 kernel and my battery is consistently dying when is still notifies 15% remaining. Is anyone else having this issue? Any ideas how to fix it?

When it dies I plug in and it will say 0% again when I turn it back on.
[Verizon Samsung Galaxy S III] bdr9:
That happened to me a few months ago. It happened for a few weeks and then it stopped. Try completely draining the battery, then plugging the phone in and letting it charge all the way to 100%.
[Verizon Samsung Galaxy S III] skytbest:
This is effectively what I did last night when it happened. Still died today at 15% :(
[Verizon Samsung Galaxy S III] darkknight1812:
The first thing you should do is to determine if it is the modified kernel that is causing the issue. Running a different kernel than the one provided in the rom is beyond the scope of this thread.

You should try wiping the caches and/or reflash the nighty. It sounds like a bad battery but further tests have to been done.
[Verizon Samsung Galaxy S III] bdr9:
For what it's worth, I wasn't using a modified kernel when it happened to me a few months ago.
[Verizon Samsung Galaxy S III] Casper34:
[MENTION=3090069]skytbest[/MENTION], I have that same issue!! I am also running ktk. Wonder if it is with his kernel. I have never had an issue before related to his kernel though. I will reflash my nightly without his kernel and let you know tomorrow.

Sent from my ghost white SGS3!
[Verizon Samsung Galaxy S III] nickhex89:
On the current nightly as well as the past one it's been saying update check failed... I was connected via WiFi tried by just data connection as well and did the same. I can direct download from cm webpage, but just informing.
[Verizon Samsung Galaxy S III] merdely:
SMS Issues - Bandaid

I'm one of the people that can basically only send one text and then it stops working. Sorry... I don't have a log for anyone.

Before, I thought my only recourse was to reboot after each text I send. That was annoying.

A few posts ago, someone mentioned that Airplane Mode also "resets" texting to be able to send another message. And that's been working for me too, but that also disconnect Bluetooth and Wifi.

Today, I added LTE to the Quick Settings tiles. Toggling that off/on also allows me to send additional texts.

Hope that helps you guys!
[Verizon Samsung Galaxy S III] iwearthebelt:
I'm having the same issue, when trying to use the CM updater I get "update check failed, please make sure you have an internet connection" I updated directly from the CM direct download page. Still have the same issue when I checked for update after installing the 4/10 nightly.
[Verizon Samsung Galaxy S III] mastamoon:
What mode is your phone on? Try setting it like below.
[Verizon Samsung Galaxy S III] merdely:
Mine is set that way.
[Verizon Samsung Galaxy S III] iwearthebelt:
Sorry, answered to wrong topic.

Same settings as well.
[Verizon Samsung Galaxy S III] mastamoon:
Ok :-\
[Verizon Samsung Galaxy S III] Casper34:
Mine is set for the top one. If I change it to anything other than that one, I lose all function, no phone, no text, no internet. I have to reflash the ROM to gain service back.

Could this be why I don't have an issue with texting? What are the other members settings who don't have issues?

Sent from my ghost white SGS3!