yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Darren Moffatt:
Sure! I'll give Real Racing 3 a shot for 15 minutes and see what happens! I'll update my post once I'm done :)

EDIT: 18 minutes in and the game is still running smooth. Minus the fact I'm out of those racer coins and all :P

In terms of what games I play for long periods of time: Raiden Legacies, Kairosoft Games, Kemco RPGs, Final Fantasy Dimensions, Zen Pinball, Kingdom Rush, Quell...I'm kinda all over the place ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thanks a lot for your time, it's appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Saltatrix:
Bluetooth Issues

Im having bluetooth issues with a Kenwood Car Stereo. Ive had no issues going all the way back to CM9. For the past few months up until a few days ago i had been on Liquidsmooth. BT had been working there until the 2.5 release on 5/27. Liquidsmooth is partly pulled from CM10.1 but also from other roms. In an attempt to get BT working i clean flashed to CM10.1 RC5 over the weekend. That did not fix the issue. The phone sees the stereo and says its connected but its not. The stereo does not show the connection at all and the BT functions dont work. I saw mentions of a fix for BT that appear to be tied to the 6/8 nightly. I just now dirty flashed the 6/10 nightly but that did not fix the issue. The release of Liquidsmooth that broke BT was the 2.5 release which was released on 5/27. I was thinking about grabbing a CM10.1 nightly from prior to the 27th and pulling the bluetooth sharing apk out but after reading about the recent BT fix being kernel based im thinking that would not work... Does anyone have any thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nothing wrong trying an older release. I'm presently on 5/20 because I have issues with some of the new nightlies. I don't use bluetooth so I can't comment, but it's been good to me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
I have this same problem with the only game I play. Dh Texas hold-em. It will freeze the game and lock up the phone for 60+ seconds. Before about 6/05 build I never had this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Try the 10.1 M2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I lost playback controls with Bluetooth on Ford edge. Also. I still have the stuttering for the first two minutes of playing music. Feels like an hour each time!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tarmacx:
Call volume at maximum

RC5 here, wiped clean everything. KT kernel

The call volume stays at maximum (maybe even higher ?...) if I use the volume buttons while in call (same with speaker) the bar goes down and up but the volume stays at maximum. Tried with the touch controls as well but it wont work either.

I seem to be the only one with this problem ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
no one here will help you if you're not using the stock kernel. just saying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tarmacx:
Thank you, I'm gonna switch right away. I only installed it because most people seemed to be using it here.

You think it could be part of the problem ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thanks for quoting that, I disabled HW overlay and finally my games don't glitch. I have a Tasker script setup at boot using Secure Settings to disable it everytime I start my phone (otherwise it's disabled at each reboot).

Sucks having to do that, but at least I can play and keep up with the new nightlies and the improvements that come with it.

Tarmacx, not necessarily, but if you're going to report a bug to JIRA it's obligatory you run CM10.1 stock, and a RC rather than a nightly, plus add a logcat.

I don't get too many calls as of late, but I'll try to think about it if/when I get one and report.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I don't play games on my phone, however i encounter the same issue while using Waze (GPS app) for an extended period of time.

I'm sure this is the same issue, i havent tried with overlay disabled. I will as it sounds like it is the same issue.

I tried running Epic Citadel for an hour and i didnt encounter the issue... maybe that particular app/game doesn't use overlay and it is why its working well...

I'll do some more testing with Waze tho... at first i tougth it was happening because of KT747's kernel but i've found that CM stock kernel does it also (just takes longer, for some unknown (to me) reason).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
And once it starts doing it, it will do it every 30 seconds I've found out. Takes 15 minutes to glitch at first, but successive times it's almost instantly, until you reboot. Try disabling HW overlay in developer settings, it fixed it for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Yes. The symptoms you describe are exactly what im seeing too! I will def try disabling overlay.

Thanks for the additionnal info.

Hi from Qc City, by the way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Still not normal that we have to do that, but at least there's a workaround.

Salut. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
What's the deal with the low recording volume? It's been an issue for pretty much ever on this device.

Here's the Jira report: https://jira.cyanogenmod.org/browse/CYAN-126. We need to upvote this thing and get it fixed, as I'd imagine it impacts _nearly_ everyone who uses cm10 on their phones. Recording volume is low even for non-video app recording. I record all my lectures, and it's lame to have to turn up the volume to max on playback, just to hear stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thanks for bringing this to our notice. I have liked and commented on the jira report. This will increase the importance of this issue and then cm will fix this on priority
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VegUnited:
I'm having hell sending MMS with the stock app after the 6/22 update. Can send with other apps fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Some things are hard or impossible to address because the source isn't released and open source drivers have to be used in their place to talk to hardware or blobs. I think this is one of those things. It isn't that it isn't important or that people are ignoring it.

You can use use a kernel that supports the faux sound add-on and boost your Mic volume to help with this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
are you from the future?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
He must mean 5/22...Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Quick question. Does anyone's url bar in the stock browser not hide after scrolling on the latest nightlies? I'm on 6/12.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
Running 6.11 nightly and I can't find the pie controls. Did it get taken out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Hi guys.

I'm still running an older nightly (5/19), but for some reason my phone doesn't constantly vibrate when I get a call (on vibrate mode). It will vibrate once and then just stop. Does anyone know if there is a setting to change this, or if this is a bug that is fixed?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Pie is only available on devices that do not have physical buttons. By default on S3 it was always not available. Unless of course if you deactivate physical buttons with a hack or buildprop edit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
This has been asked about a million times in this forum, always with the same answer. I don't mean to be blunt and/or mean, but please try searching around a little bit before posting. I just search the thread for 'pie controls' and got 24 posts, so it's definitely there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
I haven't been able to send MMS since the June 9 release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
I'm on 6/9 release and can send SMS and MMS without any problems, at least I think. People have replied to my pic msgs with pic msgs so I'm assuming it's working both ways. Also works fine in group msging.

ANYWAY, since upgrading to 6/9 I can't seem to turn my wifi on. I can keep pressing the button over and over and it will toggle between on and off. However, when I toggle it from OFF to ON it hangs on 'turning wi-fi on' and never actually connects. I can't even edit my saved APs either. Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
I've sent 2 mms messages successfully with the stock app today. I'm running the latest nightly. I haven't had any issues going back either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] luciobarreto:
Tethering lte

Hi everyone,

I remember reading about it in the past but can't find an answer... is there something I need to do in order to make the portable hotspot work using my lte connection? Clients connect but get no Internet...

I remember that there was a script... can someone please help me out?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Nothing you need to do but configure it

Setting /more /tethering and hot spots
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
What carrier is your phone used with? I think for Canadian carriers (me with Rogers), WiFi tethering is still broken. I care less because I have iptables script runs on start up and solve the problem temporarily.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evoshifter2107:
I had that problem until I flashed a kernal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bruce Lee:
I had to use handcent sms to send mms messages. I am on rc5 with no battery issue also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Saltatrix:
Bluetooth Problems

Original Question:

Im having bluetooth issues with a Kenwood Car Stereo. Ive had no issues going all the way back to CM9. For the past few months up until a few days ago i had been on Liquidsmooth. BT had been working there until the 2.5 release on 5/27. Liquidsmooth is partly pulled from CM10.1 but also from other roms. In an attempt to get BT working i clean flashed to CM10.1 RC5 over the weekend. That did not fix the issue. The phone sees the stereo and says its connected but its not. The stereo does not show the connection at all and the BT functions dont work. I saw mentions of a fix for BT that appear to be tied to the 6/8 nightly. I just now dirty flashed the 6/10 nightly but that did not fix the issue. The release of Liquidsmooth that broke BT was the 2.5 release which was released on 5/27. I was thinking about grabbing a CM10.1 nightly from prior to the 27th and pulling the bluetooth sharing apk out but after reading about the recent BT fix being kernel based im thinking that would not work... Does anyone have any thoughts?

Since posting this question ive gotten a few replys about flashing back to older versions. As i mention in the original question the problem started when i went from LiquidSmooth 2.4 to 2.5... Since i asked the question i have flashed back to 2.4. I have clean flashed to the M2 release of 10.1 and other versions of 10.1 that date well before 2.4 came out... I understand this is not the forum for Liquidsmooth but something else occured to me which was the case for both Liquidsmooth and CM10.1. Before i was able to flash to 2.5 i had to update via an odin flash to a new baseband version of DLK3. Its possilbe that the issue is with my stereo not with the phone at all and im working on determining that but im also wondering if flashing the new required baseband version had any affect on the BT radio and could be the cause of my issue... if that is the case are there other baseband versions that satisfy the requirements of the newest versions of CM10.1 and work for ATT in the US? Any help is greatly appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
The update requiring Odin/ Heimdall was a bootloader flash. Typically they have the same release version naming as the modems (baseband, radio, whatever). To see if that was the issue, since you flashed back to what worked for you, does BT work the way it did before you updated to the newer release(s)? If so, then the bootloader flash is not the culprit.

Edit: meant bootloader, not firmware
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Saltatrix:
If im understanding you correctly the Odin Firmware flash does not have an impact on the BT functionality.... Is that correct? To answer your question i have clean flashed an easy half dozen different versions/roms including the 2.4 version of LiquidSmooth that had been working, the M2 release from March of 10.1 and a number of additional 10.1 versions from the last few months. None of them resolved the issue. However, i have not done an Odin flash back to the previous firmware to see if that fixes the issue. At this point im leaning toward an issue with my car stereo but unfortunately the next step there is to do a factory reset which will erase all of my speaker balancing etc which takes a while to set back up so im trying to exhaust all other possibilities first.

Thanks a ton for your help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Looking good, few questions.

I've read about 10 pages back so I'm not being ignorant, I have a few questions about build cm-10.1.0-RC5.

1. Is LTE currently working?

2. Is the issue where the device struggles to hang onto a weak signal when a strong 3G signal present still an issue?

3. Does the native wifi tethering work properly on LTE and 3G?

4. Any serious issues or reasons to avoid RC5?

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
1. Uh yes?

2. Yes, always been, seems it will always be. But that's a bug affecting ALL CM10.1 for GS3 and AOSP roms AFAIK.

3. Can't say, don't use it. I'd imagine yes though.

4. No.

Extra

5. Disable HW overlay in Developer settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Why disable them? Is Static screen back
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Some are still experiencing game freezes, even when doing a clean install.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Thanks for your reply and thanks for the tip. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
The #5 is the only issue for me so far, and not everyone encounters it, but if your games freeze or you get static on the screen, disable HW overlay and it fixes it. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
At the cost of the battery
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Disabling hw overlays takes cycles off the CPU so theoretically it could improve battery, I know there's some downside like slower app launches or something I forget it's been a while since I needed it :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Unfortunately it seems I am unable to encrypt my external SD card on CM 10.1 RC5. Does anyone know of a solution or some way to encrypt my external SD? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I wish I could answer you but not many people encrypt their data here I believe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yeah it was part of the stock Samsung ROM i'm kind of surprised it's not included. At least the full device encryption is a part of the base android system. I really wish I could encrypt my ExtSD though...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
It's probably best not to. You're just screwing yourself over by encrypting it especially if you use your external for backing up roms or apps. It defeats the purpose of backups because if you brick your phone, you won't be able to use anything on a new phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Umm I backup my SD card to my 4TB internal on my desktop every day. I deal with sensitive information I HAVE to use some form of approved encryption. Thanks for the tip though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Just out of curiosity isn't it a Paradox (pun intended) to encrypt your card because of sensitive information and at the same time run rooted ROM that is not very secure per say?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
CyanogenMod is open source and considering its popularity and endorsements by manufacturers, should be pretty trustworthy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Nothing to do with Cyanogenmod itself, but with the rooting part. If you're rooted, I can do whatever I want with your phone. Nearly. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Apps will only run with root permissions if the user grants them root permissions. Rooting isn't a security issue unless you let it be one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't think you quite understand what we describe as a security risk though. You only think about installed apps.

If you have a custom recovery, are rooted and I have physical access to your phone, I'll get your data. I can bypass your lockscreen if you have one. It's a breeze and under 5 minutes I'll be in.

That's what gravedigger76 was saying. It's ironic to encrypt your data if it can get decrypted so easily.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Right, and how are you going to get the data off an encrypted partition? I don't think you understand quite how full device encryption works. You can't simply just copy the data, not to mention ADB is disabled. I keep my phone off when it's not in use, and good luck getting it off me when it's turned on. Unless you're telling me that somehow you're going to use clockworkmod-recovery to magically give yourself the keyfile to my encrypted partition. Being rooted really is not a security risk, every linux distro would be considered being "rooted" and since one has root access. You are the weakest link when it comes to having root access.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You're using it well, and that's perfect, but you're 1 user out of millions most likely.

Either way, there's ways not to be discussed here for obvious reason to break into a phone, "full device encrypted". Which in Android, doesn't contain the SD by default.

As for root being a security risk, it is when you have an alternate environment to boot into, such as a custom recovery/unsecure boot image (like the majority of users sporting a custom rom). :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dani01c:
I keep on getting a failed message when trying to install the latest nightly. My buddies i747 is currently on 4/14 nightly. Is there something wrong? Twrp v2.5 is installed and everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Failed assert about the bootloader? You'll need to update... your bootloader! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
A custom recovery could be installed by a thief if your phone was running on the stock ROM without wiping it. It's also impossible to un-encrypt the encrypted data unless you have the key or there is a backdoor or flaw or through brute force.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Most Android 4.0+ are relatively secure, except for a few notable exploits on certain phones/certain brands (ICS debugFS for example) and will usually end up in a wipe for a custom recovery. But honestly, that's more or less related to full device encryption.

Point being, full device protection on Android is not the ultimate security no matter what people believe even more so if the phone is currently running. Physical access to a phone with a good set of tools and OTF encryption only resists those using conventional methods. I don't think this is a good place to discuss these things, I'm pretty sure we'd get into hot water for being on the verge of legality. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dani01c:
How any links? I looked in goo for open recovery and its the same version...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I posted some really detailed instructions recently. I can't find them on my phone, but if you search back a couple of weeks for me, you'll see them. Links and everything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dani01c:
You mean this? (The whole thing quoted on that post)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yes that. Good job :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Snapchat video crashes the phone and restarts it if I take a video longer than half way of the snapchat bar. I have tested this 5 times and can reproduce it. As soon as you let off the button I think when the video is being compressed is when it crashes. Also random device reboots, had these in CM 10 as well every once in a while. It's a clean install.

**Common issue it seems, found a fix for verizon users, anyone have the updated firmware for AT&T? https://plus.google.com/104277415207525128383/posts/iAVpVPYqMtM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
Wow that could explain and fix a lot, hopefully we could find an update tz modem rpm for d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ily112:
On the latest 6/14 Nightly, anyone else having really bad battery drain? Unplug my phone for an hour and it loses 50% battery life. Battery says it's the Phone which is taking it up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
Anyone figured out the new WiFi profile feature? I can't even find where to configure this setting.

---------- Post added at 10:08 AM ---------- Previous post was at 09:55 AM ----------

Never mind found it. Its under settings / profiles.

It allows you to change profiles based on connect / disconnect from an AP. Nifty.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
did you get an answer for this?

I'm also seeing the same thing... most (if not all) third party apps that have their own way to access the front camera make the phone to reboot as soon as a picture is taken.

I'm seeing this in the latest CM nightly... and also on every other roms based on CM/AOKP that I've tried.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
no answers or other mentions yet. you're the first to even reply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
See my post above it has a link describing the issue and a fix for verizon users only unfortunately. :eek:

http://xdaforums.com/showpost.php?p=42595164&postcount=14255
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Your post is talking about random reboot... Ours is about reboot when taking a picture with the front camera with third party apps.

---------- Post added at 04:57 PM ---------- Previous post was at 04:50 PM ----------

I hope someone will work on this... I would do it if I knew how to to do some coding. :)

By the way, I've checked last_kmsg and I did not find anything unusual.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
That's right. It's very specifically when some 3rd party apps tries to use FRONT camera. The same apps can use back camera without issue.

Zaigre, what apps does this happen for you? I'm seeing this happen on Cerberus and Photochron.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
The two apps that I just tried are androidlost and Pro HDR... But I remember having the same problem with other apps too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elijahblake:
Video playback after recording issue..

My volume is very low when playing back videos that I record. Video's that I play off of youtube or else where seem fine I believe, so is there an issue with the microphone when recording video?

I know there was talk about it a long time ago, but I can't seem to find if it was ever fixed...

Any help is much appreciated.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
I just flashed 06/15. My phone on vibrate doesn't actually vibrate during calls. Is there a way to fix this in settings? I can't find any vibration settings other than sound.