yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Anyone been having issues with Bluetooth lately? I updated from 01/18 nightly which worked fine to 01/29 and again tonight to 01/31 and I'm still having issues with my Pebble. It will pair and claim that it's connected but my Pebble apps such as Music Boss and Notification Centre don't load/give me notifications. I paired and unpaired them several times, and sometimes when pairing the pair code number it would show would be wrong, or it would show on the Pebble but not the phone. Toggling bluetooth on and off a couple times actually caused the phone to reboot. It might be ok now but I'll have to give it more time to know for sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
Yeah, bluetooth is screwed up. Works fine with my simple bluetooth headset. But in any of my cars it wont' auto connect. And it keeps trying to connect to my headset any time it tries to make any other connection. Usually I sit in my car for 5 minutes fussing with it before I go anywhere. I've been looking for a solution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Yeah, all the bluetooth issues are getting out of hands on this device. I think I'll be going back to TW 4.3 while this gets sorted out. Whenever i try to use my phone in the car it's a disaster and i have to pull over and connect/reconnect/reboot to get it to work....

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
No BT issues for me on the M2 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] new_convert:
The same here. I clean installed CM11 multiple times but each time reverted to CM10.2 because the bluetooth connection issues with my car.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
I'm going to fall back to 01/18 for now. 01/31 is just too unstable. I keep having random reboots, issues with the camera and gallery, apps just loading to a black screen, etc. 01/18 had very few issues for me. Pretty much just front camera lag and the front camera is also too vertical but it doesn't bother me too much since I rarely use it. No issues otherwise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
10.2.1 is coming..

http://www.cyanogenmod.org/blog/cm-10-2-1-maintenance-release
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nahrah:
I reverted back to 1/27 anything after my Bluetooth won't connect or Bluetooth freezes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
The only Bluetooth commit in the nightly after 27 is a BLE guard fix, but I can't see that causing the issues...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nahrah:
Yea I know but for some reason on 1/29 and 1/31 my Bluetooth would hang on connecting. Even when I unpair and try to pair, it would just sit there in pairing mode. Mind you I'm not using any different kernel. I even did a full wipe to install 1/29 and 1/31 still same result. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
I may jump up to 01/27 but I just finished fixing and issue with not being able to receive calls after going back to 01/18 (phone app would stop when receiving a call) and eventually needing to nandroid to my backup before the 01/29 install and restore app data with TiBu so don't want to break it again. :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nahrah:
That's exactly what happen to me too. Phone app would crash when I nandroid back to 1/27. It would work half of the day and just keeps crashing. People said they called me but never rang or showed I have a miss call. Eventually just did a full wipe and start over with 1/27 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Luckily my Pebble gets the call data so it vibrates and shows me who's calling, but actually I had to nandroid to fix it. :P I tried reflashing after wiping system and it didn't work. Tried 2 gapps too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nahrah:
I did the same flashed gapps, also reflashed modem just in case. Didn't fix it, full wiped worked for me. Going to stay on 1/27 for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
Anyone else have phone lockup after boot on 2-2 nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Yes phone lockup after first boot up... Don't flash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pigrew:
Re: lockup with 20140202 nightly

Yes, and I had the darndest time getting it back running again. TWRP was freezing, too, and I don't understand why it could be since I always flash an alternate kernel after CM, and doesn't the recovery have its own kernel (or not?)? Anyway, I ended up flashing CWM without touch (with Odin), used that to install a previous CM package, and then reinstalled TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] srnoth:
Phone lockup here too. No problems restoring to previous nightly with TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Jumped from 0110 NIGHTLY to 0131 NIGHTLY and still realized there is lag occasionally.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Looks like I picked a good day to switch back to TouchWiz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] new_convert:
I'm not really sure about that! I still find CM10.2 a very refined and stable one. But of course it is a personal choice when it comes to comparing it against TouchWiz.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
While i agree that 10.2 is probably the best CM for the d2att, it still has issues not found on TW. For example, camera exposure settings don't work in any CM on this device, making the camera rather lame.

But yeah ive been thinking about going back to TW myself... CM11 hasn't been up to my expectations, so far. It'll get better but right now it is not dailyable for me. /saddace

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
I switched back to my CM11 backup about an hour ago.

Personally, the only reason I like TW is for stability. I hate the UI, Camera interface, everything. I tried themeing it to be more AOSP like, but it didn't meet my expectations.

Did this with my Cappy, S2 Skyrocket, and now the S3. Old habits die hard.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] new_convert:
I should agree with you on Camera app. I chose to use a third party camera app instead with CM10.2. And generally speaking, camera app in recent iteration of android is really user-enemy. Yes it has a clean and has a simple user interface. But it has lost the delicacy and usefulness for anything other than just pressing the shutter! Again, just my personal opinion and taste.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
Even with third parties, exposure settings are useless tho. You can try it, open any camera app set exposure to -2 take a picture, set it to +2 take another one and notice that they are similar heh. Works on TW. Granted it's Samsung fault for not giving open source devs the required information, end result is it doesn't work :(

Envoyé de mon SAMSUNG-SGH-I747 en utilisant Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] new_convert:
Oh! I've never tried it. But you are right it doesn't work. It's funny though that HDR works fine. It required taking at least 2 different exposures and it saves the originals too. They look reasonably different and the HDR is just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
All I've gotta say is that my next device will be a Nexus. I don't like the fact that the drivers we need for our device are locked away somewhere in TouchWiz.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] new_convert:
I would love to get a Nexus5 but the mediocre camera put me off. After all, Camera is perhaps my 2nd most important use for the phone after checking emails. Obviously making phone calls comes last.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
On a more on topic note, is anyone else getting reverted back to WCDMA Preferred from LTE after they reboot their phone? For some reason, the fact that I want to use LTE doesn't seem to stick through reboots.

Sent from my Samsung Galaxy S6 using your mother's preferred browser

---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------

The only reason I held back on the Nexus 5 was because LG manufactured it again. That's a whole different can of worms, though...

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] new_convert:
It happened to me after fresh install of CM and disappeared after a few reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
The 2/2 nightly is completely broken. It locks up immediately after boot and then gets into a soft reboot loop. Wiping /system and caches and installing 2/1 fixes it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanD911Phx:
I was able to recover without wiping /system...just cache and dalvik.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
So, when is 10.2.1 coming out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] detdett:
It will be out in 2 weeks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
10.2.1 is already out for lots of devices, expect something this week!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Maybe I'll try it! :eek:!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
What is the current best stable CM11 Nightly build, according to your opinion? Yesterday, I installed 02/01 Nightly and it was almost perfect, my only problem was with Bluetooth, sometime it work perfectly and a few minutes later, I try again and it fail to connect to my PC. That's why I can't use it for now because I'm using Bluetooth to transfer music file from my PC to the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joemommasfat:
Bluetooth was working fine for me before Christmas. But I don't think they keep nightlies that old around.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Did they fix the bootloop in today's nightly?

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hopoholic:
I just loaded this one up, all is well so far. Yesterday's was a crap-out, for sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Thanks for being the gerbil!

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I flashed back to 10.2 from 11. Just couldn't take anymore and I'm pretty forgiving. Random reboots, Bluetooth "no media" and inability to pair, lag, extreme battery drains, and finally the hard freezing with camera killed it for me. Otherwise, I love the ui and features of cm11, but those features matter more to me on my tablets. Looking forward to a more usable 11 and flashing nightlies again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
You may be excited to know that 10.2.1 should be released soon, then.

Personally, I've experienced decent battery drain, and since I never use BT, it doesn't affect me that it doesn't always pair. I thought they fixed camera freezing with the latest nightly?

Edit: Nevermind. I just crashed my camera.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
I would say 01/18 (best one for me so far) or 01/27 was also reported ok. Seems to be lots of Bluetooth issues after that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fr3d0x:
downloading cm 10.2.1....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Already test driving it, out of sheer curiosity. :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I'm still getting random reboots on 10.2.1 :(

ticket created: https://jira.cyanogenmod.org/browse/CYAN-3357

log: https://db.tt/h2SgGzlU
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
What modem and bootloader are you on?

Edit: And you're using the stock kernel, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
i747ucdlk3

stock kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah! Is there any reason you're not on at least MG2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I'm d2att US, are you sure that's the correct one for me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Absolutely. You should look forward upgrading bootloader and modem.

Bootloader:

http://xdaforums.com/showthread.php?t=2321310

Modem:

http://xdaforums.com/showthread.php?t=1831898

I suggest MG2 because you cannot go back from MJB bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I've updated to I747UCDMG2 bootloader and modem and will report back.

Thanks a bunch for this information!

Edit: my Jira bug report someone replied and said i needed to be running the latest firmware: http://invisiblek.org/d2firmware.html

I guess they are saying they won't work on it unless i'm running the one later than MG2. Thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I would test with MG2 first. Once you go to MJB bootloader, you can't go back to an older one.

Personally I can run CM10.2 without these type of issues with the Canadian bootloader prior to the last one, so out of pure guessing I would say chances are you'll be fine with MG2.

If you look at the dates, they're released at similar time intervals. :)

Edit: Also, the MJ2 bootloader is the leaked one, not an official AFAIK. invisiblek is awesome but I don't think he updated this page.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I tend to agree, thanks for all your help!

I'll report back, sometimes it would happen more than once a day others it could go days between. I have high hopes for this new setup :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crakerjac:
I'm still running i747ucdlk3 on CM 10.2.0 with no problems (occasional reboot, but that may be apps and not the ROM). What does the MG2 bootloader/modem give me? I'm even debating moving to CM 10.2.1 since all I want is something stable... I was running another ROM and I had nothing but problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
it won't give you anything because it's a firmware update. I have the random reboot pretty frequently which is what i'm hoping the firmware will fix. the reboot was my only issue with the stable. I like running stables myself but i would go to 10.2.1 since it's a maintenance release that should fix issues reported for 10.2.0 plus the new firmware may fix your reboot as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Get logs of your reboots if you want and someone can look at them. I'd rather treat both cases separately, cause if it's not broken why fix it? ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crakerjac:
I'm not terribly worried about the reboots. They are much more infrequnt than I had previously. Typically when it re-boots I'm doing something with an app.... so I'm not blaming the ROM. But I'm in the boat where, I'm not noticing anything wrong... so why fix what isn't broke. I didn't see anything in CM 10.2.1 that really jumped out at me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Anybody else get insane battery drain caused by the camera running in the background in the latest nightly?

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Great info... both of my bootloader and modem were way dated (LK4 I think)... and I saw your post and did an upgrade mine. Just a little note to those plan to upgrade theirs... if you do Bootloader and probably you want to do modem upgrade after it. I did Bootloader without modem and I got no signal, blank IMEI. I had to upgrade modem too to get it back to normal.

My 2 cents.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes that's exact and it's a "common" issue. Should have mentioned it. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Actually he has updated the page. MJ2 bootloader with MJB modem is the currently recommended configuration, per his page. MJ2 is identical to MJB except it doesn't blow your qfuse or add the knox counter :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Interesting piece of information, thanks a lot for the addition and the correction!

So upgrading to MJ2 you can revert back, if wanted, to an older bootloader I imagine?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Have not personally tried, but there are quite a few posts saying yes http://xdaforums.com/showpost.php?p=48888987&postcount=15
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thanks. MJ2 was indeed the leaked bootloader though and it was dropped, who knows if it could cause issues down the road. Probably not, haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nahrah:
Just installed latest cm11 nightly and Bluetooth connects fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Am getting Bluesleep wakelock according to BBS when Bluetooth is activated but not connected. It won't go into Deep Sleep at all until I turn Bluetooth off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
What are the ROMs that are not compatible with the latest bootloaders (i.e., MJB for AT&T)? Is it the stock and TW ROMs mostly, or what? Are TW custom ROMs updating their asserts to allow the newest bootloaders, or is there a technical reason they can't?

I probably won't ever go back to TW but I'd like to know a little more before I upgrade. Will go with MG2 for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Custom roms don't really matter because you can always modify the checks for bootloaders or any other piece of information nearly effortlessly. Most if not all of current roms will have newest bootloaders included as well as some of the older ones IF they do have a check for it. To take note TW 4.3 roms will necessitate a modem upgrade to have data but should not necessitate a bootloader upgrade by any means.

Rant part:

The "real" issue stems mostly from being unable to go back to absolute stock TW older than the 4.3 release like it used to be possible. If for whatever reason you'd like to restore your system to a prior than 4.3 state, you'll hit a brick wall. There doesn't seem to be any valid reasoning behind the lack of possibility to go back, so I'd be inclined to think it's simply a bold and dirty move by Sammy to thwart attempts of people to mess with their system by enforcing KNOX and SE outside of the corporate world which is really the only use of KNOX and SE...

Unless you have a tendency to blackout completely at times and never know whether your phone has been tempered with during your beauty sleep and feel paranoid about someone who might have saw your snapchat contacts. :p

Sammy goes as far as "void" a "warranty" if you try to mess with KNOX and trip the counter (in their own words, Knox Warranty Void) and although I haven't read anyone getting denied device warranty because of this yet, who knows if/when Samsung decides to take another stance about this in the future.

One thing is sure though, they can know now whether or not your device has been tampered with in the past, no matter the precautions you take or the state of the device when you return it if the need arises.

To me, and I think to quite a few other people, it looks like Samsung being even more closed to the open-source community as times goes by. On the other end of the scale, you have Oppo brand releasing a phone with Cyanogenmod preloaded and opening up their devices completely...

You can read more about KNOX, SE and TZ update directly from Samsung here:

https://www.samsungknox.com/en/overview/technical-details

It's easy to get excited about better security on your device, and it's even easier for Samsung to rally up Americans and look like the good guys by playing on their patriotism and using some buzzwords such as KNOX (in reference to Fort Knox) or US Department of Defense (Whoa!). No insult intended, I just think it's both clever and low-level marketing by Samsung.

So yeah, it boils down to the classic issue of buying a device that ends up not being yours completely without scraping the included warranty and service, just like car dealerships will try to convince you that your car is not eligible for covered repairs because you made an oil change somewhere else than where you bought it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Thanks for all the info, polo. As much as I like Samsung, that just reinforces my plan to get a pure Android device when I'm done with my S3. Maybe a Nexus or Moto X or its successor. I'm a big fan of T-Mobile as a company and the service is fine (LTE blazes but their rural coverage is weaker), so no more contracts ever for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gtluke:
Is it a device that can display song information? Mine always worked fine in my headset, but never any of my 3 car head units
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nahrah:
My car never displayed any info. I was having problems after 1/27 nightly connecting to any Bluetooth. But on 2/05 nightly everything is working fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Are you going into deep sleep if you leave bluetooth switched on? My phone has bluesleep and msm_serial_hs_dma kernel wakelocks according to BBS. This looks like it was an issue a while ago and was fixed, but I wonder if the new bluetooth fixes broke this again.

Wakelocks go off if I turn off bluetooth - but as I have a home dect phone/bluetooth thing - it defeats the purpose.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
No custom ROM should EVER include a bootloader or modem update.

Samsung KNOX and the KNOX flag/efuse are an effective security measure. While it is annoying for custom ROMs, root, etc., it actually serves a purpose and hardware warranty will still be honored.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Sometime between 1/25 and now cm11 builds broke the ability to use chrome beta on my phone. Clean flashed cm11 M2 and chrome beta doesnt have problems but latest nightlies do. A separate phone running 1/25 also shows no problems running. The problem occurs when doing a Google search from the address bar. I get SSL error pages. I have no problems using chrome but chrome beta fixes the black screen issue when you return to chrome from a different app. Also if you go to chrome beta setting and select your Google account it shows problems syncing. Can anyone confirm I'm running cm11 on i747m
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Is your time set correctly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
yes it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Date too I would imagine? Sometimes the silliest thing is having your date and time wrong and then obviously the SSL certificates error out.

Edit: Also what's the full error?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
My date and time are set to automatic and the date and time are right.

I get two errors, mostly the SSL error

the SSL error says:

Unable to make secure connection to the server. This may be a problem with the server, or it may be requirng a client authentication cirtificate that you dont have.

Error Code: ERR_SSL_PROTOCOL_ERROR
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Does that happen both on wifi and data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Yes. It doesn't happen on my nexus 7 though. So it seems specific to our phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Do you have any proxy set up in the phone? Adblocking? Software firewall? Thinking of possibilities here.