yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Master Cylinder:
I was over here from the Verizon thread trolling for bluetooth posts and saw this conversation about CMUpdate. Pretty much all builds/devices are having the same problem - a known bug. I went around to a bunch of devices when I noticed it wasn't working on mine. It just don't work that's all. On Philz, you get a different error:

E:unknown volume for path [@/cache/recovery/block.map]

E: can't mount [@/cache/recovery/block.map]

I've manually checked the build using adb md5sum in recovery and there's nothing ever wrong with it.

However, using TWRP, it works normally if you just go ahead and install after it errors. At least it's good for notifying and dloading builds ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
Hello boys and girls,

I skipped some of the latest nightlies, is the Bluetooth autoconnect issue solved ?

I know some changes were made around the 15th but were canceled afterwards.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I'm on 05/25 and I've been busy all weekend. I'll test this evening unless someone else already has.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
yep ... I believe the problem is in the aosp recovery commands sent by cmupdater
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
I'm getting Google play services has stopped messages every 5 minutes or so now. Just started today on 5/23 nightly. I tried reinstalling a newer Gapps package and it removed all the play stuff instead of installing. Anyone have any ideas on how to fix this?

Sent from my Lollipopped Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
What usually fixes it is installing the latest banks gapps. I think there us a link a few posts up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
Tried that with the latest version available and it removed play store, services, and Google app instead of installing anything. Had to revert to my 5/22 backup to have those apps and I'm still getting the error

Sent from my Lollipopped Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
I had the same problem with the latest update and the latest Banks Gapps removed Play Store and Play Services from my phone too. Do you have Privacy Guard for Google Play Services Wake up, Keep Awake and Auto Start turned off? I turned them back on and the message stopped popping up for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outlogic:
5/23 nightly. No more reboots. Don't use Bluetooth, but the rest seems to work like a charm. Great work!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Bluetooth and Play Store

I'm on 5/23 nightly, Bluetooth autoconnect is much better although a bit slower to connect than in the past. It seems that it does not want to release a previously connected device.

When I go from my home bluetooth speaker to my vehicle I have to turn off and restart bluetooth in order for it to connect in vehicle.

I have not had any of the problems mentioned in other posts with Play Store.

AT&T Galaxy S3 SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
Thanks for the update, I might try it again this weekend. I also see some changes regarding Bluedroid in today's nightly. Should help with bluetooth issues!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rnagam1:
I am on 5/26 nightly and I am having one issue with Bluetooth. if I turn on Bluetooth after starting my car, the Bluetooth toggle wont turn on. It tries to turn on but goes back to off. Are any of you seeing this issue.?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Yes, these Bluetooth issues are a PITA!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
They actually are the only thing that made me downgrade to Kitkat...otherwise, the ROM is fairly stable and efficient.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I agree! SlimKat is my daily driver while I keep searching for a stable LP rom. SlimLP by [MENTION=3639717]Perseus[/MENTION] is very, very close!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
05/27 nightly. Bluetooth is getting closer. Still some popping, but connect/disconnect is actually happening albeit slow like another poster said. I don't use this to much for music on Bluetooth anyway with car Bluetooth so this is my daily driver. I'll keep doing a nandroid each time before updating to have fallback though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoganerd:
Bluetooth still stinks on 5/27

I tried the 5/27 build with my Pebble watch and the connection doesn't last long after boot. Bluetooth dies and I have to reboot or use the A0-shi app to kill and revive bluetooth, then reconnect from the app. Total PITA. Most recent build with usable bluetooth was 4/22.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slickdexic:
Having to toggle bluetooth is a bit of a pain, but overall, I am very happy with the current state of Lollipop on this device. It's my daily driver. I dirty-flash nightlies, and full-flash every couple of weeks. My battery life is so much better than it was with any KitKat ROM.

When bluetooth is working 100%, I will have nothing to complain about.

I am still satisfied with my S3 almost 3 years later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Exactly! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lullcat:
This helped me as well (I am on 5/26).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AriaOfSorrow:
Yeah, my modem and bootloader versions currently match (LK3). Am I set to go with the instructions in http://xdaforums.com/showthread.php?t=2789917 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] solarwinggx:
Do you guys know any way to increase battery life?

after i installed cm12, the battery life is significantly worse than the original S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Poor battery life is almost certainty due to something keeping your processor awake. Better Battery Stats is your friend for discovering the culprit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Yeah, I get around 18 hours or better with moderate use. I can put my phone down at night and not turn off sync and only have 1-2% loss at night.

Touchwiz sucked juice even at night.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StandingCow:
Just wanted to say thank you for this ROM, I came from a kitkat ROM (RRROM), just finished upgrading my bootloader/modem and finally CM12! Was getting a lot of application stop messages but a factory reset fixed that.

Appreciate all the hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Master Cylinder:
I also use Greenify, which helps a lot! I had some apps that used a lot of juice all day even when I wasn't using them. Some apps may start up slower, but it's worth it to save battery life. I use the hold-return-button to kill apps, too, especially one's that I know are problematic, though I suppose Greenify can take care of some of this now.

Plus, you can use Privacy Guard>Advanced to disable some things from starting automatically (tread lightly!) and adjust keep awake.

I get some of the best battery performance ever on this ROM now!:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Reboot on 5/28 build while using Facebook messenger. I must disclose that I'm using dkp kernel and Xposed Framework modules.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I had a reboot as well, but I believe it subplot overheated. I was navigating, playing music, with the screen on, and on the charger for about an hour. The phone was blazing hot when it crashed.

That said, I can do the save stuff and not get so hot when on TW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Yes, I've also noticed some LP ROMs can get much hotter than TW.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
I notice in latest nightly that Bluetooth is working much better, It now auto connect and can end calls with my Bluetooth. And pause and play
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
I tried flashing the latest nightly. When I flashed it from TWRP, it never installed and remained on the 4/06 unofficial. I thought it would be the baseband so I updated it. I flashed MJ1, to NE4. Then I flashed NJ1 without rebooting. After it finished, I rebooted and it boots to the Samsung screen (without the CyanogenMod Alien) and then to the AT&T screen and then stops.

When I try to boot into recovery, it boots up to the Android with a open stomach and a triangle above it. When I try to flash CM12 from that screen, it says successful and reboots back to the Samsung screen and the AT&T screen and hangs.

Help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StandingCow:
Take what I say with a grain of salt as I am sorta new to this... but shouldn't you be on NJ1 for CM12... not NE4?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] InsaneDDay69:
You "should" but I used to have it working on mjb before I updated to nj1

Sent from my Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
Yeah, I got it mixed up. I flashed from MJB > NE4 > NJ1 (file name is UCUENE4_Restore)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
it sounds like you are in stock samsung recovery, which is normal after flashing baseband/stock

you just have to use odin to flash twrp recovery again
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
Geez, I haven't used Odin in years.

All I need to do is flash CM12 from there and I should be fine, right?

Edit: downloaded Odin 3.07 and flashed the latest TWRP using the PDA button. Fixed it, but everything got deleted :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
well, you flashed stock baseband .. of course it wiped everything .. back to stock

didn't you make a nandroid backup in twrp before flashing stock?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I've updated modern/bootloader before and lost nothing. He may have used the wrong set of files, or it was going from one to the other without rebooting in between.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
I did but it disappeared

---------- Post added at 07:54 AM ---------- Previous post was at 07:46 AM ----------

Bingo, if I rebooted it would say I didn't have an OS and would come up with the little android triangle thing so I didn't
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
You got this fixed?

You did something all fuggered up! If its still messed up what you do is flash philztouch. Twrp never once worked on my s3. It opens but doesn't mount anything. System, cache, data, nothing.

Try that.

Then reboot recovery and see if everything is back. (Should be)

Then wipe and flash ROM as usual. Or restore nandroid that is back again ;)

Hope this helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Isn't funny how temperamental some S3s can be? My phone loves TWRP yet hated KT Kernel. Go figure!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nirogu325:
My phone hates any CWM-based recovery such as Philz. It once corrupted my S3's inner clock, said it was 12:00 year 1979 or so and also it twice corrupted my S1's internal memory. I no longer trust CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
WoW! That's crazy. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoganerd:
Bluetooth in 5.29 seems to be working properly with my Pebble for the first time since 4.22. Thank you developers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
That's excellent news!!! :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Dec 31, 1969.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
Then I shall update, thanks for the info
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geearf:
Yup first bluetooth autoconnect working with yesterday's build.

Not much not working anymore!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I'm on 05/30. Haven't done any Bluetooth testing , but will tomorrow. For now though, this is doing great for me. I'm at just over 12 hours of use with 50% battery left and about to go to sleep. Last night I lost only about 3% battery overnight. Stable, great battery. Loving this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geearf:
battery has never been very good for me :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StandingCow:
The battery in CM12 is much better than the kitkat ROM I was using for a while. I also had a bluetooth issue (I reported it) this morning where bluetooth would crash, a phone restart fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mringer:
bluetooth better
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoganerd:
Yeah, there's nothing about Bluetooth on http://www.cmxlog.com/12.1/d2att/ but after dirty flashing 5.29 my Pebble has stayed connected for 2 days whereas previously it wouldn't last more than 2 minutes, even if I was in range.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Lots of stuff gets merged behind the scenes [emoji12]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rdoac:
I can confirm too that my pebble is staying connected too. I have not noticed any Bluetooth issues in nearly 18 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
Is Xposed working on this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Yep. I'm using Gravity Box, Greenify, and YouTube Background Playback without a hitch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xDark_:
Thanks

Did you use this version?

http://xdaforums.com/xposed/super-alpha-posted-permission-xposed-t3072979
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
please excuse the off-topic question ...

I have seen many people running gravity box xposed module on CM roms

doesn't it say in gravity box descript that it should Not be used with CM or custom roms ?

aren't those features already in CM ?

aren't there conflicts with CM-based features ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
Yes.

There are only conflicts if you enable both the CM and Xposed versions of the same features.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Google Search Bar

Does anyone know a way to get rid of that annoying google search bar from the screen other than using a different launcher?

I have been looking through the settings and can't seem to find a way to hide it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Nope! That's one of the main reasons I use Nova Launcher.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
Long press on screen, drag up on the three dots, turn off Google search bar
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bgon04:
bluetooth status

I am on the nightly 6/1 build released last night. The auto connect works much better for speakers (after ~6 disconnect/reconnects, the reconnect fails and then have to restart phone). My bluetooth band seems to connect quickly. The bluetooth audio still lags and stutters with music. Still a great job!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I've used nova or apex for as long as I can remember.

---------- Post added at 09:32 AM ---------- Previous post was at 09:17 AM ----------

I'm on 05/30. [MENTION=2044079]Nardholio[/MENTION] are you still maintaining this? Are you taking logs and bug reports? I may have missed what to do with these things. Anyway. Bluetooth is better for me except these things: I have static in playback of media and I still have a device that everyone I want to use it I have to re-pair it. I have no lag that I can tell and connect/disconnect with my earpiece is fine.

Also, does anyone here know how to decrease the minimum brightness settings? At low this rom's screen brightness is still too bright.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirkgbr:
:good: confirmed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
Any chance it's adaptive brightness messing with you? Personally I haven't noticed an uncommonly bright min.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I don't remember what kitkat Rom it was, but I could set it real low on minimum for late night reading or in dark situations like a theater. I turned off adaptive and set it as low as it could go and it was still too bright. There should be a way to tweak it. Not to completely dark but close like was built into that Rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Delete the google search app. Search bar gone.

---------- Post added at 08:58 PM ---------- Previous post was at 08:58 PM ----------

I think its just called google
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Master Cylinder:
It's called "Live Display" in Display and Lights, though it doesn't have that cool feature where you could set the brightness levels at all ambient levels. Without that, the 'Adaptive brightness' can fluctuate wildly at times when nothing's changing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Thanks, I'll give it a try. I had heard to turn it off because of battery issues so I haven't messed with figuring out what it does.

Edit: That's not it. That just changed the "warmth" of the display. I'm talking about actually dimming it further than what the Rom is showing. The Rom that had it before allowed you to set it to near 0 do your display backlight was almost completely off. I'll keep digging, maybe something in an exposed module or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Invalid1021:
Not exactly what you're looking for probably, but...

In LiveDisplay settings under Display, if you go to color calibration and turn everything down to 0%, it does make the screen a little darker, but appears to kill the effect of LiveDisplay
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StandingCow:
If I switch from ATT to TMO can I continue to use this ROM or would I instead use the d2tmo nightly builds? Why are they divided by carrier?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirkgbr:
Reason described here:

http://www.cyanogenmod.org/blog/all-about-l-part-1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
Quick update: I stopped using CM12.1 at the end of april because of the bluetooth Issues. Flashed 05/31 yesterday and most issues regarding BT seems to be resolved.

Those who, like me, were waiting to update beacuse of that, now looks like a good time!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
That does not work on my GS III.

Long press does nothing! Search bar is not movable by long press!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jondroid2:
Don't long press on the search bar, long press on a blank spot on the screen or just hit the menu key. The next screen that pops up will have a grey box with 3 dots at the top. Drag up on the dots. That opens up a settings screen. Turn off search bar from there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] StandingCow:
Appreciate it! So as far as me switching from ATT to TMOBILE... since my phone was purchased through ATT I would keep using the attd2 rom even if/when I change to TMO?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LambdaStrider:
Long press on your wallpaper(the background) and drag the panel up.

On an unrelated note does anybody else's screen become uncharacteristically bright after enabling power save mode?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
I'm using d2tmo. I can use the d2att and d2tmo rom's interchangeably.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I wouldn't recommend using a Rom built for different hardware. As for T-Mobile, you'll be missing some if their bands. There is a thread somewhere about enabling the 1700 aws band here on xda.

---------- Post added at 09:47 AM ---------- Previous post was at 09:37 AM ----------

I have found another piece to the brightness issue. Can someone else try this and tell me what they find?

If I use the brightness slider in the drop down settings panel. I move it slowly right to left and have noticed that with about a third of the slider still remaining on the left, my backlight stops dimming. In other words there is still another third of the slider left where it doesn't affect the brightness at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] niftium:
I can brighten/dim across the full length of the bar.

...which is not what you wanted to hear. Sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LambdaStrider:
I seem to have the same issue. Could you read my previous post and tell me whether you're experiencing the same issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
My device is T999V d2can ... which is almost identical to T999 d2tmo ... on AWS bands

I use d2att and d2tmo roms without any issues with phone, data, etc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingHaye:
battery life is still terrible..was hoping it would get better but can't have everything good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Battery life is about 2/3 of srx3 for me, I gots a big ole brick hanging out the battery hole tho!

Anyone know to get call recording to work? I use exposed but it only saves a 32 kb file with nothing in it (red mike call record)

(Black mike) Recenable for cm didn't work either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I agree about the battery life.

Back in Quantum 10.2, it was 4-5hrs of screen on time with no greenify or crazy undervolting.

Then, with CM11, battery life was halved to 2-3hrs of screen on time.

Now, with CM12, battery life is terrible - down to 1-1.5hrs of screen on time, with a new Anker battery, stock CM or Quantum or DKP kernel, no wakelocks of note in BBS. It's disappointing, to say the least.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I haven't really tried power save mode. I'm on balanced.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KingHaye:
got a random restart while typing in whatsapp...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SpiderNhan:
6/3 build eighty-sixed my SIM card detection.

Edit: Reflashing fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LambdaStrider:
Opening Google under Accounts crashes Settings. :/

Running June 2nd nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LambdaStrider:
Never mind, disabling the theme that I was using fixed the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doomrt:
On my side I have no problem going through a full day of office use without charging, and I couldn't do it with CM11.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] $avage$3:
Any difference in flashing a Tmo Rom on d2att?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Same experience here with all of these CM12.1 builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markgwiley:
Thanks a million, I didn't know that screen existed!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kirkgbr:
Not sure where to report this but...

i747 build 0603 nightly - I am using contact widgets on home screen. When one is chosen, I get "Unfortunately,Trebuchet has stopped".

If there is a better place to report this, please let me know.

Thanks and otherwise enjoying this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rnagam1:
I am also having the same issue. I also noticed another issue with bluetooth in my car. If I click the skip button in my car, it used to go to the next track in the playlist. Now it does nothing
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gizmoed:
I had the same SIM card issue but a reboot (after booting from recovery) fixed it instead of having to reflash.