yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnnyrichter:
Any way to get rid of the carrier logo up in the top left/nav bar area on the lock screen? I hate that the big ATT seems to have replaced where my little notification icons used to be when viewing the lock screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I haven't noticed any call lag lately and I'm on 09/25. Gonna update tomorrow morning to the latest.

---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------

No suggestions. As I said, mine works.

---------- Post added at 07:21 PM ---------- Previous post was at 07:19 PM ----------

Ok, I'm using Swype and it is show coming up sometimes, but no white squares. As for the "Read" button. That does mark it as read where as if you tap just above that on the message or the name of the person you'll get the messaging app to come up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Anyone have any difficulty adjusting the in-call volume when using the speakerphone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I haven't tested on the latest (10/04) that I installed yesterday, but on 09/25 I could adjust the volume some but even on the lowest setting it was pretty loud.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
WHAT? I COULDNT HEAR WHAT YOU SAID CUZ SPEAKERPHONE IS REALLY LOUD!

couldn't resist :laugh: :cool: :angel:

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Thank you! I'm really glad I'm not the only one experiencing this annoying behavior. :cyclops:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
That issue has been around forever for our device. I doubt it'll ever get fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nirogu325:
Had that issue on 10/04 nightly. I have to use the speaker a lot so I had to go back to TouchWiz due to this issue. The volume slider does not work when using the speakerphone. Oh well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Yes, Touchwhiz ROMs don't have this problem and neither does SlimKat which is CM 11 based.

Also, other D2 variants don't have this problem. It seems to be unique to D2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nirogu325:
...and d2tmo builds like the one I used on my T999.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Some promising commits going into tonight's build for those of us that have been waiting for dock audio!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Had to try it ASAP this morning. Still no dock audio. :(

And it looked so promising. Maybe it is getting some attention finally and there will be more adjustments in the coming days...I hope!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Try the 10/10 nightly. Also make sure dock audio isn't disabled in developer options and also try soundabout app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I saw that additional commit today. Anxiously awaiting the build, but I'll have to wait until Sunday to try it. Too much going in tomorrow.

In the past, when it was working in cm10, sound about was not required. But I will give it a try if it still isn't working on Sunday.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
[MENTION=2044079]Nardholio[/MENTION] I have found a bug.

The other day I put three apps in my download que and set one to update. I then turned off the screen. When I turned it back on several minutes later, the first app I set to download was JUST finishing installing and the second began downloading. I again turn the screen off. Like 10 minutes later, I turn the screen back on to find that the second app is still installing, and finishes shortly after the screen was turned on. The update then begins downloading and I turn the screen off. Several minutes later it is still installing and finishes shortly after turning on the screen. It seems that when the screen is off, the phone simply doesn't do any tasks, which I don't recall ever experiencing on Kitkat. Also related to this is the fact that wifi doesn't seem to connect unless I turn the screen on. For example, a few minutes ago I went into my bathroom where I get no wifi signal to brush my teeth. I then came back to my room and sat for about 20 minutes. When I turned the phone screen back on, the wifi connected shortly after. Why didn't it connect when the screen was off? I also experience this a lot at school, like when I walk from one building to another. Again, I don't recall this ever happening on Kitkat. It's kinda just a nuisance.

For whatever dumb reason though, I did not take logs immediately after this. The wifi thing has been happening all day and I tried to recreate the thing with the downloading apps again. It happened again with downloading one app. These logs were taken immediately after doing that.

I hope you'll look into it.

Also, do you think the speakerphone volume issue is fixable? I'm just curious if that problem will be around forever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
Have you looked at advanced WiFi settings. Make sure "keep WiFi on during sleep" is set to "always" and perhaps uncheck "avoid poor connections" to see of it corrects your issue. [emoji4]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
It is set to on even during sleep. I do have the other one off (the don't use bad connections one) which I suppose I can turn on and test how it affects it on Monday. However, I don't think that will help much considering I usually am within range of good signal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spiderkr:
Got some strange wifi behavior. Can`t connect to my wifi (i can choose it, enter pass, but it not connecting just saved)until i choose my region in wifi settings. After reboot i need to choose region again.

How can i fix it?

P.S. on stock rom wifi connects perfectly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] youssefkr:
When am updating or downloading an app, and the screen turns off, after I turn it back on I always find that the app is installing, it's like the phone won't install app when screen is off. It's really annoying, I can't put my apps to update when I go to sleep because when I wake up I'll find that the first app on the list is installing ... Strange really...

Can anyone recommend me a good gapps package, because am getting google keyboard force close from time to time and when I toggle gps on, google play service force close also...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Set your country code with a persist prop. persist.sys.country should do i. See here https://github.com/CyanogenMod/andr...mmit/95ca098d2b64b2923ef1876cd0492949911363a5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I thought I had the wifi turns off during sleep bug fixed, I'll look into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So I've had a problem for months now with Gfycat GIFs/videos locking up my phone regularly when viewed via a preview mechanism like the thumbnails in Relay for Reddit or the built-in image handler for IRCCloud. Viewing gyfcat links in Chrome tends to work okay, but when viewed inside of other apps via an internal image viewer it more often than not locks up my phone. When it happens I have to do a hard restart.

I just saved a syslog, but I'll have to wait until I'm back home to attach it to this post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
DDOS attack warning

This popped up while trying to view the TV Guide website for my local sports broadcasts.

Had to go into settings, APPS, Chrome, Force Stop, clear cache and data to get rid of it.

Searched Google, only a few references about it.

Anyone else seen this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Looks like a scam or phishing.. run a malware scanner on your phone just to be sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
BTW, I forgot to mention I was running 10/10 nightly.

I did run a virus/malware scan, results showed clean.

Updated to 10/12 nightly after scan.

I think it may have been a Drive By pop up?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
If you're clean then yeah, that's probably it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
Where is the option to change the lock screen wallpaper? If I recall correctly, it used to be under the lock screen options. It isn't there now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jason2678:
You have to do some fiddling in system to change it on CM12, or there's a Play store app to make it easier. Instructions and the app are both linked to this thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Would you like some logs from when I've tried to update a bunch of programs, because I have a bunch that are waiting to update right now. I have the same issue and honestly thought it was something wrong with Google play.... and is this a problem with the Rom or the kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Took a while longer than I expected to try this, but I finally go to it. Dock audio is still broken, even after the latest lot of commits that seems so promising. Docking the phone seems to have no effect on the audio output. Use of SoundAbout made a difference, but still didn't work. SoundAbout did report that it was routing sound to the dock, the audio would stop coming out of the phone, but still didn't make it to the dock.

Without a stable build, I still cannot report this through official channels. Is a logcat of docking any use here?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
And the game begins:

http://www.cmxlog.com/13/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miatawnt2b:
Pretty exciting. I am really hoping that there are enough devs around still to help build a stable CM13 based ROM. I don't want to give up my S3 anytime soon. Just too expensive to upgrade when the phone works as well as it does.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Yes, I love my aged yet capable S3! :cool:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rutilant:
Xposed (newest version) doesn't work on the latest nightly 10/15... It gets stuck on booting forever. Hope it gets fixed, I miss it already.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Yes, it does. You must use v75 from the main Xposed thread. It was just released a few days ago. I am running it successfully.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Both your reports here and any bug report you submit if there is a stable will be read by me and the response will be the same: I don't own any dock hardware. Also I can't do anything without logs :) and even with the log, it well be tough without hardware to test on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
You won't get official M until after Christmas at the earliest. I'm not switching nightlies over until CM13 has a feature set on par with CM 12.1. Unofficial builds are probably about 2 weeks away for d2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcaseiro:
Awesome news
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I'm just thrilled there is even talk about bringing M to d2! :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Android m. As in "monumental wait for the camera to once again be fixed!" Lol!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Same here. I really didn't think we'd get it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rutilant:
Weird I tried v 72 and v75 and they both get stuck at booting forever. Not sure what's wrong. I reflashed without xposed and it boots fine.

EDIT: tried it again (4th times the charm?).

It rebooted by itself like 5 times during boot and then it finally went through. Thanks for the heads up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Every time a new version of Android comes out, CM has a soul-searching moment about which old device hacks they will continue to support and which they will drop. For some devices this is the end of the road, although they may live on in homegrown builds if a developer chooses to continue development.

For now, at least, it looks like CM will continue to support everything we need. Although we are pretty far away from anything actually functional (Nexus devices and some newer devices are already booting but d2 needs some special love that isn't ported yet)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Well darn, that's some killer news, cap'n!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Yeah, I'm grateful for the continued support by both CM and the d2 device maintainers. While CM12 was noticeably less stable than any other version of CM before it on the ol' d2att, I was still grateful to have it. Things like calls coming in at max volume every time, 60fps videos not working, gfycat previews in apps crashing the phone... etc. were never fixed in any build of CM12.1 for our device. I'm crossing my fingers in hopes that those problems somehow go away with the switch to CM13.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
It's largely because the s3 has hardly been surpassed by new hardware. With 2 gb of ram and a dual core cpu, it is powerful enough to handle most anything. The camera isn't the best, but it sure isn't bad! In my mind the only thing that could really prevent the phone from continuing is, like you said, a lack of developers since the amount of users is decreasing. I'm hoping that we'll get a nice stable cm12.1 build soon that has worked out all the little bugs we have now (we're progressing :) ) or cm13 builds that don't have the issues, which would really let this phone shine as a great phone even against the s6 and it's equivalents.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Wow! My phone booted on the first try with no issues. I'm glad you got it working though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Anybody would be nice enough to look into their stuff for the 6th of October nightly and upload it somewhere for me? Bluetooth has been terrible for a few days and I believe this happened after the plethora of commits on the 9th. I can't workout at the gym with my Bluetooth headphones anymore as it constantly cuts out. I've tried another pair of Bluetooth headphones and the same thing happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
This post prompted me to look into the skipping issue, which started for me a lot longer ago (yes your dev uses the d2 as his daily and actually by choice, I also own an LG G3 and am eyeing the upcoming BlackBerry Priv)

I need everyone to pm me the contents of their /data/.cid.info file.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I am so happy to hear I am not the only one who experiences Bluetooth skipping. This is a problem that seems to appear over time. Upon clean flashing a new nightly, Bluetooth works perfectly with no skipping. After about one week, the skipping starts for me. Unfortunately, the only fix I've found is to clean flash another nightly or some other ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
I do not currently use Bluetooth for anything. Would it still be beneficial to have the file? I will submit it if so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
After extreme daily use of my Bluetooth speakers and Bluetooth earpiece for my cell phone, I can no longer imagine a world without Bluetooth. LoL
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Saw a bunch of kernel commits in the recent nightlies. If only I had the knowledge needed to decipher them. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rnagam1:
5/13 build holds LTE settings after reboot. The folder icon changed. Before a folder was rounded with a nice open/close animation. Now it is squared and opens up to the entire screen. I personally would prefer the rounded icon. That had a materialized look.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
After downloading, I had the 5/13 update install overnight. When I woke up, my phone was on LTE. I assume that 5/13 preserved the LTE setting during the update since previous builds always reverted to 3G, requiring user intervention to regain LTE connectivity. Nice job! I will check BT w/my headset today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
Downloading right now, will report back later today.

thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
One thing that I noticed right away about BT with Plantronics Discover 975 headset is that the headset no longer hangs up a call. I can still answer the call by pressing the headset button, and I can also redial using the headset button, but cannot terminate a call with the button. That function worked fine in CM 11. I need a longer call to see if CM 12.1 still locks up and auto-restarts during a long BT call with the 5/13 nightly.

Oops. While I was typing this and the phone was simply sitting on the homescreen, it rebooted on its own. I am attaching the log. I'm not sure if it also captured the BT issue, but the events were only a few minutes apart.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
Tried 05/13 build this morning with two different BT accessories (headset and car). Call quality, media streaming etc, is all flawless, but the autoconnect function still doesn't work.

I did a clean flash, and tried it with clean new pairings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phaze13:
Can CWM recovery be used instead of TWRP?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
I've only ever used CWM. It's never caused me any problems. I'm on 6.0.5.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I personally prefer it over TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
I don't believe that CWM is being supported anymore. TWRP, OTOH, is still being updated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Level99:
I think 5/7 was the one that was pretty good about not having random reboots. 5/12 so far has been relatively solid, but I've been trying to unbrick my D415 and it hasn't had a lot of uptime to guarantee anything. One thing I did notice is that for 5/12 I didn't dirty-flash. Maybe something was propagating from the code into data and a clean install either fixes it or helps. Will have a better baseline later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ashokjp:
3 things, i would appreciate if someone could confirm and also happy if i could get an official fix if its a bug

1. Whatsapp profile pictures are not getting synced OR even displayed in contacts. When i open a contact, i can see them linked to whatsapp, when i edit, i also see a image holder with section named Whatsapp, but its empty

2.Facebook app is installed, but it is not registered under Accounts, also cant find an option to sync. When I had samsung firmware, upon logging into facebook, it used to ask and sync fb pictures to contacts.

3.Using bluetooth in car. When dialing a call, the car gets the phone sounds ONLY after the call gets connected. Meaning, if i was playing a music, if i dial a phone number, the music should stop immediately, show dialing in car, and also hear the ringing / engaged tones, and also the conversation. Here car doesnt change status, until the call is connected. I wouldn knw if call is going thru or is busy, or failed. am having a ford fiesta and this works fine with every other phone original firmware, be it a simple nokia phone or a samsung s3 stock.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
DELETED
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ashokjp:
Is this for me, also once i switch to this kernel,

1. can i revert back to original if bug is not fixed

2.if it gets fixed, do i have to replace kernel after every nightly update ?

my issues with bluetooth is not reconnect. pls confirm

anything on the profile photo sync thing ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yes

No

No

No
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ashokjp:
Yes for?

---------- Post added at 03:21 AM ---------- Previous post was at 03:20 AM ----------

I just have 1 more bug on the 13/05/2015 (latest) nightly. Camera sometimes shows - Cannot connect to camera. fixes on reboot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Sorry I mean

No, not specifically for you

Yes, you can go back to official nightlies.

No I'm not going to force you to flash this same file over and over if it fixes the bugs, why the hell wouldn't I put it in the nightlies?

No I won't confirm.

No I won't fix photo sync. That's not a d2 specific problem. I don't fix stuff that's wrong with CM in general.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ashokjp:
I used TWRP, Flashed that IMG to boot partition and am stuck on boot now.

---------- Post added at 03:32 AM ---------- Previous post was at 03:30 AM ----------

Please help me with the file to restore the original nightly kernel. This thing is not booting up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I promise you it boots. To flash back, look in /sdcard/cmupdater
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ashokjp:
Its been 10 mins+ now, still stuck at boot. u sure abt this ?

Also how i did is, i went to TWRP, clicked install, chose img, then flashed. it said successfull n i rebooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
*bows down*

I cannot provide you this file at the moment but I cannot begin to thank you for all the work you've done on the d2att platform so far. Thanks as usual Dave, I'll try to get you this ASAP!

Edit: I lied, sent you the content. "semcosh". On my way to the gym now, wired headphones and all. :X
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
By the way, if you use an f2fs formatted /data partition, as I do, twrp may fail to boot for you due to recent kernel improvements. I have repacked the latest twrp (2.8.7.0) with a compatible kernel.

EDIT: forum limits file uploads to 8 MB so I had to split it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
It's great that I can disable Heads Up notifications, but how do I re-enable ticker notifications? There doesn't appear to be any way within the ROM. The xposed module "Enable/Restore Notification Ticker on Lollipop" doesn't seem to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I was on Phils but I'm gladly going back to TWRP. Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Get the app "Heads Off" from the Play Store. I have the paid version and it works perfectly!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
We are getting closer to M

http://review.cyanogenmod.org/#/c/113198/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Nice! Here's hoping that the eventual M build miraculously fixes the 60fps YouTube problem. That's the biggest nuisance with CM12.1 on this device by far for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I'm running 2.8.7.0 already, is there any way to see the format before updating to a newer nightly¿ Was going to grab the latest tonight as I'm still on 10/06. And I'll upload more last_kmsg files from freezing and a log taken while trying to let apps update while idling. It only made it through 5 apps in about an hour.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
[MENTION=2044079]Nardholio[/MENTION], the biggest issue I have with Bluetooth is after I use apps like Timeriffic or Tasker to automatically disable Bluetooth at night to ensure my morning alarm actually rings through the phone's speaker and NOT through my Bluetooth earpiece, sometimes a reboot is required to re-enable Bluetooth. This problem first appeared months ago and although it has gotten better, it is still problematic. Besides this and the BT skipping issue, everything else works virtually flawlessly. Thank you for your time, effort and energy supporting this device!