yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Ok, question. [MENTION=2044079]Nardholio[/MENTION] are you maintaining these builds still? Or should we report problems elsewhere? I have an AT&T s3 but on Cricket. When I try to send a pic over text using the Google Messenger app it won't send unless I turn off Wi-Fi. I can get a log while trying to do it, also can try the CM texting app, but want to know who to talk to about the problems.

Also, I was on the 06/05 build but just updated to the 06/20and still having the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ominousnimbus:
It's pretty remarkable how persistent this bug has been on this device over the years. I'm still on CM11, but there were various builds of CM11 last year where I experienced the same thing. It would come and go in the nightlies, and was present in at least some of the M releases I believe. The cause must be very subtle and hard to pinpoint.

If I recall correctly, in some cases switching to the old (ICS era) AOSP Messaging app or Textra was a workaround. Hangouts and the new Messenger were more prone to this happening.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] micl9:
nevermind
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Edgehead123:
3rd party camera app problems

Hello, I'm on 6/19 and I tried installing CameraMX as an alternative to the stock camera (I really missed night mode, hdr and panorama). Every so often the apprehend on me. Now I get an error when I try to open the app saying the app isn't working and try to restart the phone. The app works upon a restart but I'm getting that error more frequently now. The CM 12.1 camera app has also been giving me this same error. Anybody else with this problems or/and some advice?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I tried the stock app. After it taking a while to load the conversations I sent a test picture. It works. I can receive while on Wi-Fi also.

---------- Post added at 08:26 PM ---------- Previous post was at 08:16 PM ----------

I have one odd thing still. Has anyone else tried to apply a theme? I applaud the "neat" theme. It's a dark theme that says it's for CM12.x+. But here is what I get in menus.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Never mind. I went back to stock theme and discovered that the theme's icon for vibration mode is a skull.

And now I see a weird icon in my status bar. Anybody ever seen this skull before?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HamZusGh:
I have problem with candy caméra and retrica

The phone restart when i take pic with stock caméra. candy camera and retrica but i don't want to use another app like open caméra

Ho have a solution for this problem and than'k

I have SGH-i747m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
My phone also often shuts down when I use most camera apps except for Camera Fx.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XaveT:
Maybe I'm just slow?

Good morning,

I'm having big issues with this build (cm-12.1-20150622-NIGHTLY-d2att).

I use TWRP 2.8.7.0. I go in, wipe everything.

use the MTP to copy over my ROM and NJ1 bootloader/modem.

I apply the updates in 1) ROM 2) bootloader order.

I reset cache/dalvik for good measure.

I restart. It finds and installs 82 apps.

Then nothing happens. The screen just goes black. I press menu a few times (varies, as low as 2, as high as 5) and I get a mostly blue background but nothing loads on it. What am I doing wrong?

If anyone has an idea, I'm up for it. I really want to get Lollipop on this, it's my test device :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
What model/carrier is it? Why are you flashing bootloader/modem? Are you flashing any gapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bklyndiaz:
TWRP?

SORRY IF OFF TOPIC. but is TWRP 2.8.7.0 available for SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I have 2.8.6.0 and don't get the option of installing a 7.0.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bklyndiaz:
i dont get the option either! was just wondering how XAVET IS USING 7.0

thanks for the clarification.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Master Cylinder:
Also best to md5sum those files after you get them over through adb shell. Also install bootloader/modem first (though now they're already installed) after addressing [MENTION=615005]wrenhal[/MENTION]'s question of course. EDIT: I guess the ROM doesn't care what's the modem, etc until it boots ...

Power down, pull battery, etc ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XaveT:
Hello. It's the Samsung SGH-i747, the US AT&T one. The procedure at the beginning of this thread said to, so that's what I was doing (first post). Should I be doing something else? I'm not doing any gapps yet.

---------- Post added at 06:20 PM ---------- Previous post was at 05:50 PM ----------

Hello. I repulled the ZIP from the nightly repository. The hash matched on my machine, and also on the device (shell on device). I tried the power down and pull battery methods. It still installs fine in TWRP, shows the android facey thing for a minute or so, does the finding and installing 82 new apps. Now it just shows the android facey thing with an expanding grey circle around it that fades away. (I left it like that for over 30 minutes) I've tried tapping on the face, holding on the face, swiping on the face, pressing home, and rebooting. It's different than earlier, so that's progress, but still not working. Any other ideas?

I can't imagine that it would matter for the OS, but there isn't a sim card in it, and I don't believe the front camera functions. Again, I can't imagine that those would make the OS fail, but hey, I've been wrong before.

---------- Post added at 06:24 PM ---------- Previous post was at 06:20 PM ----------

Hello all. I doubt I can post links, but it's available on the TWRP device download page.

protocol: https

site: dl.twrp.me

folder: d2att/

You can also find it on Google, search TWRP, and find the device in the list (d2att).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Can you try installing a version of just a kit Kat Rom? Wipe everything and install just the Rom and reboot. This way we can make sure it's not something wrong with the hardware or ram.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhack21:
Not available for install using the TWRP app just yet. I flashed the tar file in mobile odin just fine.

Sent from my SGSIII using the XDA premium app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I just flashed TWRP 2.8.7.0 successfully using the Flashify app. I can't seem to find a changelog though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
since 2.8.4 you can flash the .img directly from twrp itself, from the install menu
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Sounds like a simple apn issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Try wiping system and data and reflashing again if you flashed modem/bootloader after the ROM. Also if you're coming in from firmware that's very old (Older than MJB) I recommend flashing stock first to program your nvram.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
yeah,I just caught that. He should have done the modem/bootloader, then Rom. Or maybe booted with new Rom, then flash bootloader? Oh well.

Hey, my texting issue is fine when using the stock app, which I like better than messenger in somethings, but the font is a little smaller it seems. Any way you know to make the font in just messaging bigger?

And did you see my post about the theme issue? Do we post these things to you or to CM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nirogu325:
Contact the Neat theme developer regarding that cosmetic issue. Nardholio only brings support for the development of this ROM nightlies as the thread title indirectly suggests.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mringer:
Keyboard crashing with 6/23 nightly

Anyone else have keyboard problems with 6/23? Mine crashes every time with every app. It doesn't matter whether I use the AOSP keyboard or google keyboard. Just started happening after installing 6/23
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plastic_green_head:
No issues on my S3. Tried both AOSP and SwiftKey.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Well I've seen in some other thread where there are some issues with themes not working in menus properly and that it's on the CM side. I figured I'd let him know so he can tell me where to report it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
I just updated to 06/23 and I am getting weird screen flash when I receive a call while using an app (internet, fb, gmail, etc). I just ring, flash and cycle through a few notifications, it becomes very hard to take the call but once I answer it all is fine.

It also behaves correctly if it rings while the screen is off.

Anyone else getting this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aschreiner22:
Couple of issues still persisting

1) Call volume issue: I still am getting very loud volume when calling or receiving a call. I have to turn the volume all the way up still and then back down and it is ok.

2) My email (corporate email) widget on the desktop doesn't refresh properly and shows previously read emails. Only when I actually close out the app completely and wipe it from the recent list does it refresh.

I'm on the latest nightly (6/23) on ATT. Not sure what I should be providing for as far as logs or where to upload them to.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
My call volume issue would come and go on 06/05. It went at one point and hasn't been back since. I'm on 06/20 right now. Once you turn it all the way up and then down do you leave it at the lowest volume? Because I think what stopped my problem was going all the way up then all the way down and without lifting my finger from the screen I then went up to about half way. I can now use the buttons to control in call volumes and it's not loud when the call starts. Maybe if you start a log recording then make or receive a call and adjust the volumes and then stop the log and save it. I use an app called catlog that has a widget that starts and stops recording by pushing it. I thought of doing this but my problem was gone. I haven't tried speakerphone lately so I don't know if that problem persists and I don't want to for fear it'll bring my other issue back. Anyway, hope this helps and that maybe a good recording can be gotten.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mringer:
Well, not sure what my problem was but it's gone after updating to 6/24.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HamZusGh:
No one can help for the problem of camera
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Not sure what the problem is because camera has been rock solid since the unofficial versions. You will probably have to record some logs during the crashes and post them for [MENTION=2044079]Nardholio[/MENTION].
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Edgehead123:
total noob here, also having severe camera issues and random reboots. How do I record logs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
There's a thread on xda somewhere. I'll have to look it up later. Unless someone who knows posts it first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirkgbr:
I'm sure there are many other ways to get logs but this is where I learned.

Help Your Developers; Pull a Logcat when Issues Arise

and

[Tutorial] How To Logcat

and

[UNIVERSAL][LOGCAT]How to get & read a logcat/ Troubleshoot your own issues!

Please do not paste then entire log into this thread but instead use Pastebin or an attachment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
I have to disagree. Video recording remains hit or miss for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rnagam1:
I am on 6/24 nightly and whenever I dismiss an incoming call I get "Unfortunately the Dialer has stopped" message. Is anybody else experiencing the same issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outlogic:
6/20 nightly. The camera is not working. Get the error that can be translated "Can not connect to camera". The same error was reported from another user of my blog.

Open Camera freezes as well and doesn't work on 2 devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
It's best if you try the latest nightly first to see if issue has been resolved. If not, take a log of crash and post it.

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Hmm. I'm on 06/20, AT&T, modem is NJ1. Opencamera works fine. Can even get 1080p recording on back video. Tried stock camera and everything works except back camera is limited to 720p recording. If a clean wrote and fresh install doesn't work then they'll need logs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Alarm Snooze Went Crazy

Running 6/24 nightly. Alarm settings are set to silence after 25 minutes, snooze length 5 minutes.

This morning after one snooze alarmed as it should the second snooze somehow states it will snooze until 5:50 am on Saturday.

Saturday at 5:50 am is when the alarm is set to go off again for the next days work.

Very strange, never had this happen before!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outlogic:
It was a clean fresh install. And I was not the only one with this problem. Do you save GPS data to your photos?

Installed 06/25 and the stock camera works. Haven't tested it with GPS on yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gundal:
as someone else reported, i am confirming the nfc does not work with screen locked, so smart lock cannot be used to unlock the phone with nfc tag.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I never save GPS because I take too many pics of my kids and such.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Nightly builds are missing for the past 3 or 4 nights. Any idea what's happening?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I haven't seen any either. I wonder if the website for CM has any info?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
They are releasing the last CM 11 and 12 milestone releases. This seems to have blocked the server for last couple of days
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
So what does that mean for us? And where do we report issues on their site?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Once the milestones for 11 and 12 are out of the way, they'll be going back to 12.1 nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
CM 12.1 nightlies are back without the milestone release for our device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greglarson:
0629 is available now. Initial tests cm-12.1-20150629-NIGHTLY-d2att pass on my i747m.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Yes they are! Already downloaded and installed the latest.

Too bad we didn't get a milestone. Without it, there's no way to officially report bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Milestone was for 11 and 12. Not 12.1 from what I read.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Snooze Alarm 2nd Occurrence

Running 6/24 nightly, snooze alarm after second snooze states it is snoozing until 5:50 am the next day. That is when the next days alarm is set to go off.

I see 6/29 has added code for:

alarmmanager: Add sanity checking for elapsed_realtime alarms.

Maybe this will fix my snooze problem? Downloading 6/29 now to give it a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Let us know how 6/29 goes! !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
CM update works again 6/30 nightly... Yay!:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingHaye:
try the 06/29 wifi wouldn't connect so revert back to the 06/25 that was the first thing i notice didn't go any further.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
No milestone for d2, d2lte was a cluster on cm11, also I can't be asked to flash old builds to test them. We skipped cm12 because it took too damn long to fix the camera.

Also, I do read this thread, and I do fix things that I can do stuff about. Sometimes even non d2 specific stuff. I ignore posts without logs unless the answer is pretty obvious, like you have a setting wrong or you need help flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Snooze Alarm third occurrence after 6/29 install. Settings are silence after 20 minutes, snooze time 5 minutes.

After second snooze, alarm states it will snooze until the next days alarm time! After 5 minutes it does not alarm.

I see there are 3 lines of code for the alarm in 6/30, I will try that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
That is very weird behavior! Consider trying a third party app like Gentle Alarm. I switch to it a few years ago due to other issues with the native clock at that time and have not looked back!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
11 M12 for d2lte is still the newest build with a 99.99% functional camera (for me). I had to flash back over the weekend. I'm still reading this thread and I'm still excited to see how far this phone will go, but the camera problems still make 12/12.1 a deal-breaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
I did not have this problem with 5/31 or 6/13 nightly. It started with 6/24, wonder what could have changed?

Thanks for the Gentle Alarm tip.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
The latest Cyanide L ROM has a fully functional camera and is based on CM 12.1. It is quite impressive.

You're welcome. Gentle Alarm is a very flexible and powerful application. You'll love it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
So logs of the call volume and speakerphone problems if someone can get them would be helpful?

Also is there any way to increase the font in the stock messaging app? I can pm you screenshots side by side of a comparison to say Google Messenger.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Consider trying the Textra app for maximum configurability.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I know for a fact that the ui people for the app are working on adding font size as configurable, I was just wondering about right now rather than future. This app does everything else I need it to.

---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------

Also how would we go about this issue. When the phone screen turns off it doesn't respond to the hang up command from my headphones (long press of the call button). Samsung headset. The short press still mutes it though. Would a log even help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Reboot while applying a theme. Using 6/30 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dragoonmx:
can i use this rom in a i747m

can i use this rom in a i747m?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Logs and a better explanation of the problem or gtfo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Problems like yours are very hard to diagnose, especially since they tend to vary by headset and I'm not going to buy a headset just to fix yours. I need more details, such as what nightly you're on, which bootloader and modem, if you're using a custom kernel, the exact headset model, and yes logs.

There's a reason most real developers don't read xda. Maybe I should make you all wait for the milestone release to submit bug reports.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Know how I know you didn't read the OP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Looks like you have some corruption on external sd which fsck took care of. Also please disable xposed and try again (also try a different theme)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dragoonmx:
lol sorry read it after posting
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
I reported this in this thread on May 12th:

Although I didn't circle back, it WAS the stock kernel. I reported it again on June 9th:

The recent occurrance was on a more recent nightly with the stock kernel and the stock camera. If you think logs will help, I'll submit them when it happens again (and a video sample to you privately, if that will help, but I'd rather not post it publicly). But since the camera has never crashed, I'm not sure logs will help you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
[MENTION=6367928]niftium[/MENTION] What goes through your head that first you quote a post I made saying bug reports without logs will be ignored with a bug report without a log, and then when I reply where's the log you ask if I really want a log? Am I not speaking the same language as you?

Or what I'm really trying to say is that's not a problem other people are having and I need more information and also to eliminate the possibility something unique to you is causing it. And unlike the million and one other rom "devs" out there I'm the one who actually fixes the camera on this phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
wheee .. don'tcha hate when someone/thing pees in your corn flakes

go man go!

your turn to be amused ..

so I have a system for a client running 10 databases

about six months ago he asks Me to separate into two systems running 5 databases each

I explain that separating without also splitting into two separate servers will mean that My queryByexample classes and programs will no longer be able to see all 10 databases from individual systems .. he says ok

yesterday, he says he can't query across all ten databases

I said I told you that

he says to fix it

I said no, it isn't broken .. but maybe you are ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] htc_softbank:
Love the Rom and been using it as a daily driver since it was unofficial.

Back when matrixzone was developing the unofficial he mentioned not to flash a custom kernel to over clock (since the Rom would become unstable)

Just wanted to see if this is still the case. If oc'ing is now possible, are there any recommend kernels?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Dkp is the only third party kernel I would even hazard to recommend. Well and maybe quantum. I'm not sure there's many other ones out there for this phone anymore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
Quantum is a great kernel. I'm running it right now over the official 5/29 nightly with zero issues, but it doesn't have any overclock/underclock options.

Dkp has the overclocking options you're looking for.

Deathly is the only other custom kernel for this phone I know of that's been updated to 5.1. It is a good kernel with lots of governor options, but I don't remember if oc/uc were supported. I usually cap my max frequency to something a little under stock max to save some battery so that's just not something I pay much attention to.

We used to have Shift on lollipop too, but I haven't run on it since the very early builds of Cyanide. I'm not sure how up to date it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Level99:
I didn't change anything in the performance area for my tests, so I guess the bug is just basically squashed. As for per-app performance profiles, see here:

http://www.xda-developers.com/change-performance-profiles-on-a-per-app-basis-with-xposed/

tl;dr it can assign governor, min/max frequency, scheduler, and many other performance-related variables on a per-app basis. Disabling it means everything runs under what you have set as default for the device.