yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] escape75:
I've tried latest CM11 nightly, CM11 M12, latest nightly CM12 for the last week or so, same result.

Very sporadically I can get it connected after many reboots, I'd say 1% of the time.

Stock 4.4.2 samsung is 100%

It for sure has to do with a semi faulty hands free, but whatever samsung did they made it work.

Pretty sure it relates to this but I think the patch was dropped in newer builds and nobody cares:

http://forum.cyanogenmod.org/topic/77834-bluetooth-connection-drops-car-kit-bmw/

There's a lot of people complaining about this, it doesn't just affect BMW, it's Visteon build unit in my Mitsu.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Oh... I see... Luckily for me, SlimKat (CM11) and all of the CM12 ROMs I've tested have successfully paired with the hands-free in my Hyundai Genesis, Lexus ES, and with my Plantronics Voyager Legend earpiece.

I hope the patch mentioned the link you posted can be added to CM ROMs moving forward. Unfortunately, I am currently not skilled enough to do so personally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I have a problem with an older hands free device, but my earpiece (jawbone) works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
review.cyanogenmod.org/#/c/103111/

It's not that nobody cares. This is a huge project. Every time a new Android version comes out cm has to rebase the mod part. Stuff gets lost.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] escape75:
Ok I didn't mean that, but what I meant is that it affects a lot of people (according to my google searching)

and since bluetooth is very important part of a cell phone (android and others) it's very important to fix.

If a rom CM11, CM12, etc, is very stable but bluetooth doesn't work people have no choice but move back to stock :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Yes, BT is very important to me too which is why I am able to use some ROMs and not others. Fortunately, I haven't had any trouble using my Plantronics Voyager Legend earpiece with these CM 12.1 nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] escape75:
Just an idea, maybe a compatibility option could be integrated in the menu under blue tooth,

that would enable connections to "broken" headsets, maybe that would make it easier to code ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
So it doesn't matter if you're on NJ1 bootloader to go back to 4.x.x ?

I thought you had to be on NE4 bootloader for 4.x.x ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
No, you can go back to a 4.x.x. ROM. You just can't downgrade from NJ1 to NE4 firmware (without bricking).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] htc_softbank:
I found out an issue with the custom kernel!

I noticed it doesn't charge my anker 7200mA battery properly.

When I charged the phone or overnight it would show 100%, but immediately drop to 80% or 60% (unpredictable)

If I plugged the phone in to charge again it would properly charge to 100%.

Definitely a kernel issue since I reverted back to base kernel and all is well again. Just wanted to share in case anyone uses anker battery and thinking of going custom kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Matt_the_Geek:
Would it be a kernel issue or a ROM issue, that when I try to change the battery lights colors, hit 'ok' and 'settings' force closes, not saving the change and yet leaving the led stuck in the color I was choosing?

7/13 nightly and dkp latest (6/08)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Have there been any improvements on the YouTube playback front in the last two weeks of nightlies? If not, I will hold off on flashing an update as it's the only real issue I have with my current build.

Also, I'm beginning to feel like I'm the only one with this issue as I never see it mentioned by anyone else. :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
The YouTube freezes were eliminated a month ago. The only problem I've had recently was a reboot and super fast battery drain on the 7/14 build. I reverted back to 7/13.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
They started to add bells and whistles. When cyanogen adds bells and whistles, they have nailed down most of the bugs.

Still a work in progress, but its real smooth. I don't have any bugs to report.

7/13
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I get the freezes and stutter with any 60fps videos on YouTube. If that's not the case with the build you're on, maybe I'll flash that tonight and see how it goes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
07/13 and 0/7/14 - GPS slow lock. Answering call over bluetooth while navigating AND charging AND playing amazon music is almost an instant reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Matt_the_Geek:
updated to 7/14 and didnt flash dkp kernel, so on stock, and same thing. it was working at some point before 7/1 build, havent changed the lights in a while...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Just updated to the latest nightly and tested out 60fps video playback. It's better than my previous nightly from late June, but it still stutters here and there and occasionally freezes. Definitely a noticeable improvement from what I had before I updated, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I use my phone as you described a lot, at least playing music, navigating, and charging in the car. It was fairly regular that I would have a random reboot at these times. Never any other time. I'm sure you've noticed that the phone can get pretty hot in this use case.

One day, using Trickster MOD, I noticed that the CPUs Temperature Throttle was OFF. I was surprised to see the default configuration was OFF, but it was. Given the high temperature associated with the use case above, I enabled it and I have not had a random reboot since. It's been more than 2 months now.

Question, since you use the phone in the car, are you using a dock that supports audio? I am and have yet to get audio out through the dock. Setting are in the ROM to disable this, but it always seems to be disabled regardless of the setting. Have you had any luck with this?

The dock audio problem is really the only remaining "issue" I have with CM 12.1. Other than that, it is the smoothest, most stable, and nicest ROM I've run in the entire life of the S3. Pretty impressive (and fun) that a 3 year old handset can still be a very viable daily driver - a testament to the device and the progress that Android has made, and of course the developers that make CM 12.1 on the S3 possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Noticed this too when I updated from a late-June nightly to the latest. I reset the Display Calibration, but there was no noticeable change. Whereas I used to be able to clearly see the screen at like 40% on the brightness slider, it's now pretty dark even at 60% or so. It's especially apparent with whites on the screen, as they are very noticeably dimmed.

RGB are all set to 100% right now in my Display Calibration.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
Thanks!

Whoa, good point! I totally overlooked it as I thought cm12 builds for d2lte handled the temperature throttling. I've turned ON "Temperature Throttle" and will report back.

I am using bluetooth, and I don't use a dock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] escape75:
I've also notices it gets really hot in a car, vs. stock which stays cool.

Maybe we need to enable thermal management by default ??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
cm 12.1 profiles issue

ever since the first lollipop builds, and all the way until 7/13, I have noticed that cm profiles .. specifically lockscreen mode .. have been broken ...

I have a "home" profile which sets lockscreen mode to "don't ask for pin or password" on connect to My home wifi .. and the default profile is set to "leave unchanged"

sometimes it works, sometimes it doesn't .. and besides simply being annoying to have to enter My pin when I shouldn't, it also means that sometimes I am nowhere near home and discover that no pin is needed to unlock My phone

this worked perfectly on kitkat

anyone else having this issue?

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I also think that thermal management should be enabled by default. Not sure what the logic was that led to it being disabled. Maybe it was just an oversight.

I updated to the latest CM nightly yesterday. I double-checked the setting this morning and found that it was reset to OFF again. Apparently installing updates resets it. Beware!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoganerd:
What is the procedure for updating thermal management? I can't find that setting.

Thanks

.b
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
Install trickstermod from marked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
To report back:

Turned it ON, and drove around 50+ miles, navigating, streaming music (bluetooth) and charging - NO PROBLEM; phew!! ( I was so frustrated with the random crashes before, so I appreciate this immensely) :good:

I'd also like to request thermal management be enabled by default.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Glad to hear it worked out! And remember to check it after each update of the ROM. Updating the ROM seems to reset it.

---------- Post added at 05:42 PM ---------- Previous post was at 05:37 PM ----------

I use Trickster MOD from the Google Play Store. In Trickster MOD, you will find the setting on the last page titled "Specific". You will see it there called "Temperature Throttle". Turn it ON and profit!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I noticed today that my settings in trickstermod changed back today. Randomly. By themselves. Temp throttle off as well as zram (is that actually beneficial at all?)

Also my SD readahead 3072 was back to 512.

7/17 build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I have not experienced this. Are you using stock kernel? Have you set Trickster MOD to reapply the settings on each boot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Yes. I have it set to apply all settings at boot. It does. I have never had a problems with it.

It did this yesterday. I will try and make it happen again today. See exactly what happened.

It runs really smooth tho!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] escape75:
Not too familiar with the CM code review procedures,- what happens next with the patch?

-- I could test if there was a test build done that I could restore from twrp.

Also, could we make a change so thermal management is enabled by default in d2att builds?

-- Lots of people (incl. myself) noticing phones getting hot when the ambient temps are higher.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Is the app drawer supposed to look like this in power save mode?

The two "ghost apps" are what I see. They scroll left to right. (And right to left). It comes on and goes away with power save mode.

Nightly 07/17, but I have seen it before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
All bug reports without logs will be ignored. Having said that, here is a status update on development for d2:

I will likely bring back 1080p, the old problems with corrupted video recording seem to have been resolved.

Thermal management: it's not working correctly, you should not have to manually turn it on with Trickstermod. I'm going to see if I can get away with an entirely kernel based thermal solution and ditch the userspace daemon. This is something that is not usually allowed on official CM builds so it's going to sit on Gerrit for awhile. You can test by flashing this boot image https://github.com/nardholio/android_kernel_samsung_d2/releases/tag/12.1-thermal

Brightness problems: I recently tuned the brightness curve and replaced the color calibration backend. Unfortunately some people didn't take the upgrade well. I can offer no solution beyond the usual wipe cache and dalvik and format system before flashing and try again. The few of you with problems may have to do a data wipe if I can't figure out why.

Bluetooth/headset issues: works for me. You might want to try a non CM ROM, CM uses a lot of code from CAF and bluetooth code closer to AOSP will probably work better.

VOIP uses the wrong microphone: I'm looking into it. I need to figure out the optimal settings to make it work correctly.

Other one off issues with your phone, camera won't connect, phone call echo etc: works for me, if you submit logs I may be able to track it down but I work 12 hours a day at my job and d2 is a hobby for me in the evenings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So if I'm experiencing much lower brightness than before even at 50% or 60% on the slider, I'll have to wipe system/cache and flash again? Does that mean the new brightness being darker than before is an unintended effect?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I am gunna just toss this in real quick with some Mobil Odin... Thanks for this, gets a lil warmish from time to time ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
With automatic brightness on, the brightness slider will max out at about 50% in a typically lit bedroom or living room. In a setting with fluorescent lights it'll be brighter. It will reach true maximum outdoors in bright sunlight. With automatic brightness off, the slider will allow you to manually adjust the entire range. With automatic brightness on, the slider will do nothing in bright enough sunlight.

If you're not getting these results, try a wipe of cache, dalvik, and system and reflash. If it still doesn't work you'll have to bite the bullet and wipe completely.

I don't know why it's only affecting some people. Some possible causes:

Old kernels still using the old color calibration.

You had the color calibration set to 100% before and you were accustomed to the colors being brighter than they were supposed to be.

Alternatively you have color calibration set to 50% which was the old default but now really is 50%

Sunspots
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Just used GPS yo go about 30 miles. Then played a game. Both of these things used to make it really hot. Hot. Still gets hot but its seems to stay cooler and to cool off faster.

(Obviously I'm on that kernel posted up there a lil bit back)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] escape75:
If there's any way for me to test this, then I will: review.cyanogenmod.org/#/c/103111/

Should I be posting to CM forum to get this included in CM 12.1 codebase by default?

Surely it can't be that hard to test a simple change that will benefit lots of people :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
back in cm 11, certain apps and situations would lead to very hot device and auto reboot .. could basically know it was going to happen

on every lollipop rom, My device gets very hot with just about any extended or high performance cpu use .. it seems to be a lollipop thing

on cm 12.1 with dkp, I have experienced both the heat and auto reboot

however, on cm 12.1 with stock kernel .. I have NEVER experienced an auto reboot

I am running the 7/20 build and altho the heat is still there, this build "feels" smoother and seems to have better battery

cheers,

thanks for all of your tweaking

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I would like to add a bug to the list. Dock Audio doesn't work, and always seems to be a challenge when CM updates to a new release. I think CM 10 is the last time it ever worked. CYAN-40 talks about it. I've attached a fresh logcat of the phone being docked, then un-docked. It probably shows more than 1 cycle, but the last dock was at 6:17:47, and un-dock at 6:18:00.

As you can see from CYAN-40, it has been a real frustration for some of us that actually use the dock. It has also been frustrating that I cannot officially report it since we've not gotten an M build. I cannot even even report it in regression testing since there is no nightly where it has worked. I certainly appreciate all the work that has gone into keeping the S3 alive with the latest CM. Please, if at all possible, see what you can do about this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Snooze Alarm FIXED

Running 7/16, thanks for the snooze patch! Works as it should now, no problems at all.

GPS working great, no heat or reboot problems for me.

Thanks for all your hard work on the d2, makes my S3 a joy to have!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
You already post this question in the unofficial thread. You can try using other USB port on the PC or try in other computer to see if the PC recognize the phone..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
One question it's there any benefit in update busybox to version 1.23.2. The ROM came with an older version.

I use busybox app by Stericson to update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] escape75:
I tried Slim ROM 4.4.4 which I'm pretty sure is based on AOSP and had the same issues, weird.

Back to 4.4.2 stock for now ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mattaw2001:
What information would you like on the Thermal Managment boot.img?

I have been having the reboot after running GPS after about 30 minutes (faster if other services like BT music/audio are in use). I have just flashed the boot.img and it is currently running. What debugging information would you like?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I haven't seen the star (in status bar next to my alarm icon) in a while. I have supersu installed.

What is that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
The one in here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
The star means that you have priority interruptions only set. Accessed by tapping volume rocker.

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Derp, thanks man!

Also, I had lots of overheat issues, even still with the nodded kernel. Build 7/23 + kernel + trickstermod SOC set at 60.

Much MUCH improvement.

GPS, clash of clans, hard WiFi usage, all used to make super hot, not so anymore.

Serious improvement.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
You are using the modded kernel? And what do you mean by "SOC set at 60"? What option is that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
This is trickstermod app.

To be fair, I haven't really used it "stock". Just with the mod.

Default will be at 70

Where it says " tempreture limit".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Are you guys flashing the boot.img through ADB or Mobile Odin or what? I don't have adb installed on my pc so I'll have to do that later if that's what it takes.

---------- Post added at 08:33 AM ---------- Previous post was at 08:31 AM ----------

OK, because Trickster just gives me a toggle of on or off with the default kernel. Guess I'll flash the updated boot.img later. How did you flash it, through ADB, mobile Odin, or some other way?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
I got mobile Odin pro. You can probably use flashify also. Mobile Odin is free, you don't have to buy it. Just flash the boot IMG. You can also Google search for "adb naked drivers" and use (path): adb flash boot boot.img.

However, or you can use Odin for PC.

Mobile Odin is easy.

Download the boot.IMG

Open mobile Odin.

Click "kernel".

Go grab it from

/storage/emulated/0/download/boot.img

Then " flash firmware".

Setting in trickstermod will be different.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Ok. I got mobile odin to work (had read it didn't work on lollipop). I set mine to 65 and it seems fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I can make 65 the default
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
You also could have just used the latest version of TWRP that's the way i did it unless of of course someone still uses CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Has anyone else been getting frequent "Google Play Services has stopped" popups lately? I had been getting them for a few days in a row, so I just flashed the latest nightly complete with a /system format just to be extra thorough. Still getting them.

I am using the latest Banks Dynamic Gapps as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Banks gapps works fore also.

I'm almost certain I'm the only one who can't make twrp work. I use philztouch. Either way mobile Odin is much faster. Its faster than rebooting it, even.

I was having Google problems a while back. Had to wipe everything and do a super clean flash every time. This problem has went away.

Also, dkp has a new kernel out with some thermal adjustments. Looks like overheat is the new "camera" issue!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mattaw2001:
On a long journey with GPS and audio got rebooted

I had installed the new boot.img. Used Trickester Mod to set temp at 70.

I tried a long journey with GPS, BT audio and a call or two and got a reboot after 45 minutes. That was an improvement on previous 30mins. Note phone is clipped to vent of dashboard in cool air.

Dropping to 65. I'll keep you updated.

Is there a good way yet of discovering if it was a thermal problem that led to a reboot?

M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Sorry, no. I had posted something that didn't really make much sense. Excuse me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
The latest google play services has problems. Reverting to an older version fixed it for me. What also worked was using broken gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mattaw2001:
Answered and was irrelevant. Please ignore this post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Has anyone noticed if you first tap the screen to focus the camera then take the picture it works well but if you take a picture without first focusing it the led shines for about 3-5 seconds before taking the picture?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Yes, my camera behaves the same way, but only for about 2 seconds.

Running 7/16 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I'm glad I'm not the only one and I'm glad tapping the screen first is a simple workaround. However, I hope this bug can ultimately be fixed. I haven't experienced this behavior on most other CM based ROMs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Stagefright: new Android vulnerability

Does anyone know if a patch for this Stagefright vulnerability is being applied to CM builds?

http://www.theguardian.com/technolo...right-android-vulnerability-heartbleed-mobile

http://www.npr.org/sections/alltech...-phones-would-let-hackers-in-with-just-a-text
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
Stagefright issues

https://plus.google.com/+CyanogenMod/posts/7iuX21Tz7n8 says:

Recent Stagefright issues

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.

CM11 will see these updates hit as part of out of band fixes this weekend (these releases occur weekly).

CVE-2015-1538

CVE-2015-1539

CVE-2015-3824

CVE-2015-3826

CVE-2015-3827

CVE-2015-3828

CVE-2015-3829

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. ﻿

Another interesting read on this topic : https://news.ycombinator.com/item?id=9955431