yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pwned101:
Guys.. I have my email accounts setup on the default email app. I have set it to check every 5mins and has turned on the notifications too (both sound and LED) from the email settings. But it never gives me any notification when a new email arrives. Is it the same for everyone else?

EDIT: switched on sync at its working. Wierd, I thought the email app worked without sync turned on..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smashcz:
http://www.android.com/about/jelly-bean/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Thanks for the hint... I am with Rogers in Ontario. I tried to follow your steps to switch "Set preferred network type:" from WCDMA preferred to "LTE/GSM auto (RPL)" and I got no data connectivity.

Rogers customer: please make sure your APN set to ltemobile.apn and your plan is LTE capable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
I feel like the release will be something big lol. Call bug fixed is what I'm betting.

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Hi there... maybe I have this problem but just not caught it... would you mind to elaborate what call bug you have experienced please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enzyne:
I've found several random issues with the dialer sometimes you can't hang up it will lock up in you. Other times it will freeze when dialing out or adding another call to do a three way. Other then that everything else is good for me :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Did you install CM10.2 stable using the Cyanogenmod installer? I think it packages a bootloader. Not sure which, and honestly not 100% if it does/did so don't quote me on that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
No, just used TWRP with the 10.2.0 zip. I've never been able to get the CM installer to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
But you tried? I don't know, it was an idea like that, that's the only thing I could see that would/could try to flash a bootloader...

except going back to stock, did you try that? If you flashed a 4.1.1 stock rom that could explain it, it has the DLK3 bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Good guesses... But my issue then was really that my laptop USB driver was broken so the CM updater couldn't even try. In fact, I didn't ever try on my phone. I crossed my memory and it was my dad's Sprint S2 that I tried that with.

I also haven't flashed back to stock in over a year, so haven't done that either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I'm all out of ideas why you could have been on DLK3 then. Guess it doesn't matter since it's solved. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
So, therefore you CAN odin a tar that has the current / MJB bootloader? The op was worded in such a way that it sounded like you couldn't odin any tar at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't believe there's an issue ODINing (ODIN'ing? ODININING? haha) a tar containing the MJB bootloader if you are already on the MJB bootloader, only with downgrading. Not too sure why you'd need/want to reflash the MJB bootloader over and over though.

EDIT: ALSO ALSO ALSO ALSO I can't help but notice you're a Canadian user (or at least says your flag?). If you have a i747m DO NOT flash the MJB bootloader. That's a sure brick.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ozark_8125:
Merci, mon ami. I'm in the states now, so am on a US network with the d2att. Thanks for the warning - unfortunately too many of our brothers from the Great White North did not heed the warnings as you pointed out and went off to the great hoser in the sky.

Oh, and I don't want to have to reflash stock over stock again - but, once in a while, I R E A L L Y screw up the phone, the file system borks, and I start over.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Alright. Not sure if one could unbrick their borked i747m by using a 16GB SD card like people trying to flash a previous bootloader are doing. Might be possible, might not. Curious, but not enough to intentionally brick my phone. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
back to 10.2.1?

I should have read my own post. The real deal killer for me on cm11 was the freezing camera/video camera.

Just took a quick picture, switched to video, short video, then back to camera. preview was scrambled. Snapped a shot, phone froze then rebooted.

last_kmsg attached.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Same here...couldn't even open Gallery to look at pictures...froze phone up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I don't believe an MJB Odinable file exists, thus the no flashing from Odin when running MJB bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
I just flashed my Rogers S3 to M3 2 hours ago and tested LTE tethering without having any issue. I don't think it matters but can you check your baseband?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
MK5. I'm on 2/11 nightly and my LTE tethering is okay. Maybe it was a fluke. I may flash the M3 again to test this and make a report but I'm just so tired of this phone not working when I need it to.

I made a bug report to chromium because chrome beta was acting up. Right now it seems that early adopters of S3 have a CPU bug that causes problems with neon code. Go to terminal emulator and type "cat /proc/cpuinfo" if your CPU revision is 0 you probably have this issue as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Do you have camera problems? Read my comment above...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Camera probs here too. Keeps force closing and I need to reboot. Really high.

Sent from my Samsung Galaxy S6 using your mother's preferred browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nico3d3:
Anyone else still having problems with Bluetooth on the Milestone 3 release? I installed it along with K747 kernel but Bluetooth support is crap. It fail to connect when I want to send file from my PC. It's no better than what I experienced with the Nighly build. I'm just wishing the final stable version will be released soon... Anyway... at least CM10.2.1 is rock solid for now and Bluetooth work perfectly with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Yup, rev 0 for mine.

---------- Post added at 08:49 AM ---------- Previous post was at 08:48 AM ----------

Yes!!! Same issue. Mine on M3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Anyone try 02/12? Did those camera fixes have any effect?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I did, and nope!

Here's my video camera screen capture.

Then, black camera when toggling.

Then camera froze.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Everything looks normal to me. hehehe
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
I can't even flash 02/12 some error a out my boot loader. I have never had a problem with that not even sure how to check/update the boot loader and I'm scared of bricking from what I've read! Going to try 02/11 to see how it goes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Boot in download mode and check your bootloader version there. Report back. We'll help you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
I did try to see what version I'm on but it didn't tell me...I can try again if you can show me what I'm supposed to look for :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I tried to attach new photo in trillian. Locked up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Ditto, no bootloader version shown in download mode. Instead I ran adb shell and then bugreport | grep 'bootloader'. My bootloader is: I747MVLDLK4

I am currently on CM 11 nightly 2014-01-21. Do I need to worry about updating my bootloader to flash the latest nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Yes, you will need to. It looks like you have a Canadian phone. Read back to polobunny's recent posts, or maybe he'll hop on soon to tell you what to update to. It's very easy.

Can't recall if I asked this a few days back: Is anyone having major battery drain on nightlies from the last few weeks? Specifically from Play Services, Android OS, and/or Android System? A lot of us on Vanir are having this problem and I'm trying to figure out if it's CM code, Vanir code, or Gapps related. I'm using Banks standard Gapps on 2/9 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I derped and totally got confused, you won't find the bootloader version in download mode, my bad.

That's a very good way of finding your bootloader loonieryan, although it depends on bugreport which might have been disabled, it works well enough for must.

You should update as VQ30DE mentioned, and your best bet would be to update to MF1. Not MK5 as this is the dreaded bootloader that will blow the efuse and stop you from going back. Unlike d2att users, we don't have a leaked bootloader so the one right before the latest is MF1. I'll get you a link when I can, currently trying to catch some sleep.

---------- Post added at 01:14 AM ---------- Previous post was at 01:12 AM ----------

Oh and other simpler way to find your bootloader

su
Getprop ro.bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Thanks for the info! Found MF1 in this thread so going to try that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Northerntouch:
Bootloader Error

I have searched all over the place but I can't find the bootloader for I747MVLUEMK5. I was able to flash the latest modem with this version but can't seem to find a link to just the bootloader. I am trying to flash this because of the get.prop error.

So far the only solution I can see is to flash the stock firmware which will upgrade the bootloader and then re-root and flash CM11. The weird thing is that I was able to flash the 2014-02-04 CM11 nightly but any version after that gives me the bootloader error. This seems weird that I would be able to flash an earlier version but non of the subsequent ones.

Update: Found the file
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Well there you go. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
MF1 isn't supported by the install script but you could add it manually and it should be fine. I went to MK5. I don't have a reason to downgrade my bootloader anymore, I already did my unlock when I was on LK4.

EDIT: Maybe it is, I can't check right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It is.

cm-11-20140213-NIGHTLY-d2att

assert(getprop("ro.bootloader") == "I747UCDMG2" ||
getprop("ro.bootloader") == "I747UCUEMJ2" ||
getprop("ro.bootloader") == "I747UCUEMJB" ||
getprop("ro.bootloader") == "I747MVLDMF1" ||
getprop("ro.bootloader") == "I747MVLUEMK5" ||
getprop("ro.bootloader") == "I747MUMUEMK3");

I should update my signature. Made me realize it's outdated ha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Thanks for the confirmation. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Just fyi the camera/gallery crash/force close in CM11 right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I tried searching but no luck. Anyone know if it's possible to install a nightly while using ART? When I install/upgrade a nightly, I get the optimizing apps (which is so slow) and then the cm boot screen sits there spinning. It feels like upgrading should be possible, or I'd expect to see more people report issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Its interesting. I don't see any of these camera gallary crashes ppl talking about. Usually my phone is the one with all the bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Deleted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kurrent:
flashed latest nightly - phone won't boot

i recently flashed the latest nightly, via OTA, and phone won't even boot, into dl or recov mode either.

never experienced this before, only way to get any response out of of phone is to pull battery and put it back in, but i only get samsung logo briefly and flash of blue text that says "recovery booting..." then just a black screen and phone is unresponsive. sometimes the cm logo will flash for split second but rarely does it get that far. releasing buttons or only releasing power button (upon seeing recovery booting text) has no difference in effect

any ideas on how to get phone back to life? canadian s3 phone btw and previous rom was cm nightly from 3-4 days ago
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Well that's strange...what nightly are you on, though?

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
FWIW...I had not been seeing the issues either - until yesterday. What happened yesterday - I did a factory reset, format, wipe, then clean install of my usual - latest CM 11 + latest Quantum Kernel. Now I have the camera issues. Kind of unfortunate. All the dirty flashes I had been doing were apparently letting something survive that made the camera work. :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] srnoth:
That's very interesting. Just realized that was the same thing that happened to me.

So I decided to flash (dirty) an older build (m2) from January. Camera then worked fine (no crashing). Then I flashed back (dirty) the latest nightly, and sure enough, no crashing!

Your hunch seems to be right that something left over from the old nightlies enables the camera to work on the newer night lies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justDave:
The camera is broken in 10.2.1 as well and dirty flashing from 10.2 to 10.2.1 didn't fix it. I'm back on 10.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I just took a picture using the camera app on my test setup of 10.2.1 yesterday. I think you're in need of a clean flash, or the issue lies elsewhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Stupid camera issues...I really thought I remembered the camera working in earlier CM11 nightlies...is that possible? I thought I had it working on a clean flash of one of them (early early Jan or Dec 2013)...not 100% sure, though.

Really hope they fix it soon...doesn't look like any fixes are in the works, though.:(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cristianpark:
CM gives me a good headache today. I had 2/06 build installed and yestarday my battery got drained, I put the cell to charge and it doesn't boot immediately, I supposed it was very discharged. Today I recieve a call and can't hear the ringtone, then I answered and listen anything, I tried to play a song and no luck either. Then I flashed last nightly and have the same behaviour.

I tried to install S3Rx and I get bootloop after data wipe, I dirty flashed S3Rx and get the phone working again with ear speaker and loud speaker working good. My major concern is that I have MJB bootloader and can't flash stock 4.1.2 stock AFAIK, nevertheless I love CM and when it gets a little more stable, I'll give it a shot again. Are you guys having similar issues with cm 11??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
I don't have any camera issues on 2/13 nightly.

But 1 issue that is bugging me is that every now and then the in call handset & speaker volume diminishes significantly and the only way to resolve it is to reboot the phone. Seems to happen after my phone is connected to my car via Bluetooth, then disconnected after taking some calls and playing some music via Bluetooth. Had the issue on an older nightly of CM11 and still happens on 2/13.

Anyone else encounter this?

Sent from on the toilet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanD911Phx:
I have had absolutely no problems automatically updating while using ART. And if the boot screen appears after optimizing apps, it is a crash and not part of the process. It normally occurs first then optimizing apps and then starting apps. If you're rooted check the tail end of /proc/last_kmsg for the reason.

BTW, how do you recover? And exactly which version of CM are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Do you notice that if you switch home screens fast, then try to open an app right away it doesn't let you?

I find that SOOOOOO annoying since I'm really fast with my phone...doesn't happen on 10.2 nightlies...

And DanD, you don't have any camera problems either?

Elliott

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanD911Phx:
No camera problems on my SGH-i747 :good:

I'm on snapshot CM11 M3 and after auto-installing that I re-flashed Gapps with the latest to date: pa-gapps-stock-4.4.2-20140207

That package uninstalls the stock browser, message handler, and the AOSP launcher, and puts in the Google Now Launcher as the default. But after booting I make Nova Launcher the main launcher.

As a side note, on my Nexus 7 2013 (flo) I have the exact same firmware/Gapps versions, but with the Photosphere camera added automatically because of it being a Nexus. The only problem I'm having is a few watchdog reboots :crying: on the N7 that I haven't tracked down yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Thanks. And do you have the lag that I mentioned above? You have to be very fast to notice it...if you switch home screens then try to open an app right away nothing happens...but if you switch, wait half a second, then open it, it works...

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanD911Phx:
No lag with GNL or Nova. Very snappy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Oh okay...it's not lag in general, just that specific spot.

I was using Launcher3, though...can't stand Google's Launcher.

EDIT: On GEL, it's not possible to change which home screen is the default, right? That's such a deal breaker...

EDIT2: Camera isn't crashing...but Gallery app does...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanD911Phx:
I previously answered YOUR SPECIFIC QUESTION - You asked if I had lag with a specific scenario. You chose to interpret my answer as applying to only general lag.

I HAVE NEITHER kind of lag (I tested your scenario, on both GNL and Nova) and my gallery app does not crash either ...

You have never said what Gapps you loaded. Suggest you try the ROM version and GAPPS version that I mentioned above. There is a variant called full modular that doesn't remove the AOSP launcher.

For the record, my Camera is com.android.camera2 version 2.0.002 (366c3600f3-30) and my Gallery is com.android.gallery3d version 1.1.40030

End of my discussion about this lag stuff. I originally replied to the OP who asked about CM11 updates with ART enabled. This has gone too afar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Thanks.

I can now confirm this only occurs in Trebuchet (Launcher3), which is a real shame.

I am using modular GAPPS from PA. Have same gallery as you...clean install and this is the 2nd nightly I've tried where it crashes...I am noticing now, though, that it only crashes when I access the "Camera" portion, where my actual pictures are kept...other folders like "Screenshots", and "Downloads" works fine. Guess a problem on my end.

And I don't think it has gone too far...I simply asked you a question, and was mistaken in thinking that you were too lazy to try what I was specifically talking about, and instead thought you were just mentioning general lag (which is what most people do); sorry. :highfive:

EDIT: Fixed gallery problem by removing all my pictures and only putting back some of them...seems to have fixed it for now! Sorry guys...thought it was a universal problem...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I am running the latest cm11 nightly, enable art and all is well. If I use cyandelta or just use the twrp recovery to install the next nightly it goes through the updating apps and then reboots and freezes at the boot screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skibler:
I cleanly installed todays nightly and gapps. Everything seems to work ok, but the phone never prompts me to unlock my SIM card. Has anyone else had this issue? Is there a way to prompt it to unlock the SIM? Trying to look at the "Mobile Plan" settings page just prompts me to insert a SIM. I have tried re-inserting it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CanuckinPA:
I'm currently having a bunch of frustrating issues with the LiquidSmooth 4.4.2 ROM and am ready to make a change. Am I correct assuming that CM 10.2 is not KitKat and I'll also need to flash a JB gapps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Goggles still not working on CM 11 nightly from 2014-02-13. Seeing this in my logcat:

I/goggles (32622): CaptureActivity: handleShutterButtonClickEvent
I/goggles (32622): CaptureActivity: Ignoring press on shutter button in state STATE_TAKING_PREVIEW

Also on the CM forum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Correct.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zmnypit:
sorry if I've missed it but which bootloader are you guys running or recommend with the newer versions of CM that seem to abort in installation? d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
MJ2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zmnypit:
You mean MJB? I've looked for a flashable zip and they all say mjb
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No I mean MJ2.

http://invisiblek.org/d2firmware.html
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skibler:
Just in case anyone else has this issue, it turned out to be an issue with the bootloader and modem.

I had updated the bootloader to I747UCUEMJB (for AT&T) as a requirement for the newer nightlies via this thread: http://xdaforums.com/showthread.php?t=2321310

This left the device in a state where it seemed unaware of my SIM card's presence.

After also updating the modem to I747UCUEMJB via http://xdaforums.com/showthread.php?t=1831898 everything worked as expected.

All of this seems to have also fixed an issue with having to manually connect to paired bluetooth devices as well :o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Why don't you try CM11 or Quantum? Latest Quantum is running so smoothly for me. Definitely do a clean flash and use PA Gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Looks like CM team have merged all d2 devices into one build. Now we have single build for d2 devices:

http://download.cyanogenmod.org/?device=d2lte
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Have you flashed this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Not yet....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I have. Works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CanuckinPA:
I used the CM installer and it flashed this version. Seems to be working fine so far
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
With the recent kernel merge it was a matter of time til the rom was merged. Makes more sense anyway. Building entire roms for a bit of changes doesn't seem very logical. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Yeah, hopefully this will lead to faster and more efficient response to S3 issues in general. I wonder what drawbacks there are to merging, if any.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't think there's any real drawback and I don't think it's gonna lead to faster/more efficient response to S3 issues in general.