yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] buschbarber:
I was on the 06/14 nightly. I was experiencing terrible battery drain, lockups, and reboots. I cleared the caches and flashed 06/15. All is well now.
[Verizon Samsung Galaxy S III] merdely:
Does the Display & Lights setting crash for you?

If you set a Performance Profile (like Power Saving) and reboot, does it retain the setting?

Thanks.
[Verizon Samsung Galaxy S III] Darryl Henley:
Attached logcat for Display & Lights settings FC.

Looks like an "Invalid int" in the Backlight config.
[Verizon Samsung Galaxy S III] buschbarber:
Display and lights still crashes Settings. Not sure where Logcats are.
[Verizon Samsung Galaxy S III] mastamoon:
Ping [MENTION=2044079]Nardholio[/MENTION] [MENTION=2385005]invisiblek[/MENTION]
[Verizon Samsung Galaxy S III] dmginc:
Anyone else's calls sound muffled lately?
[Verizon Samsung Galaxy S III] chowner:
I just noticed this on M7
[Verizon Samsung Galaxy S III] buschbarber:
I experienced the sane thing with M7. Speaker phone volume was very low.
[Verizon Samsung Galaxy S III] MartyMacGyver:
I noticed that for Bluetooth calls.. ramping the volume down a bit and then back up got the volume back to normal.
[Verizon Samsung Galaxy S III] chowner:
No dice for me.

Trying to use speaker phone is what brought it on for me. Reboot was the only resolution.

I was fine for days using bluetooth mainly, but speakerphone did it in.
[Verizon Samsung Galaxy S III] Skyrocketing:
Lost service on 6/17 nightly. Tried a full wipe, still nothing. Any ideas?

Edit: Fixed after full wipe, install, and physicall resetting SIM card
[Verizon Samsung Galaxy S III] Gareee:
Latest update fixed the display settings crash for me
[Verizon Samsung Galaxy S III] buschbarber:
With 06/18, Display and Lights settings work properly, as well.
[Verizon Samsung Galaxy S III] merdely:
Same for me. However, the Performance Settings still don't "take". After the update, I did a test reboot. I set to "Powersave" and when it came back up, it was at Balanced again.
[Verizon Samsung Galaxy S III] buschbarber:
I just tried it and had the same issue with Performance setting not holding after reboot.

By the way, why did you switch to the MB1 modem?
[Verizon Samsung Galaxy S III] merdely:
I was having the problem of only being able to send one text. I read in another thread that it was the ML1 modem. So, I did an nvrestore, flashed the MB1 modem, and re-set up my phone. I haven't had a problem since. I heard is was the ML1 that was the cause.
[Verizon Samsung Galaxy S III] Gareee:
Is contact sync down for everyone? Just updated my wife's phone to cm11, and I can't get it to restore contacts.
[Verizon Samsung Galaxy S III] tv31284:
Is anyone else getting an error when trying to use wireless tethering?
[Verizon Samsung Galaxy S III] mastamoon:
my build from this morning shows it turning on correctly. Or is there an error when trying to actually use it?
[Verizon Samsung Galaxy S III] tv31284:
I get an error when I try turning it on, which kills WiFi and forces me to reboot.
[Verizon Samsung Galaxy S III] mastamoon:
Mine turns on fine. Have you tried to clear caches?
[Verizon Samsung Galaxy S III] tv31284:
I did, unfortunately that didn't help. I can only imagine its because I've dirty flashed. I haven't tried it with a clean flash. It's just such a pain to set everything up again. Bluetooth tethering works fine though and that'll suffice.
[Verizon Samsung Galaxy S III] mastamoon:
I havent clean flashed in ages.. since CM11 was released...

You may want to try formatting /system then reinstalling rom and gapps. Your data/layouts should be fine.. maybe there is a leftover in system that the install isnt catching.

Do you have any other framework type mods installed.. like xposed? Those could also cause some problems.
[Verizon Samsung Galaxy S III] tv31284:
I just tried that too to no avail. I don't have xposed installed. Stock Cm, stock kernel always.
[Verizon Samsung Galaxy S III] mastamoon:
Then I say nandroid backup and data wipe... See if it still happens. If it does restore backup.. If it doesn't then you can selectively restore apps and necessary data.
[Verizon Samsung Galaxy S III] razorloves:
if you want to try one last thing before doing the data wipe, as masta suggested, just try this simple fix. It usually takes care of odd wifi and tethering issues.

turn off wifi then delete these 2 folders and reboot. they will be automatically rebuilt when your phone boots up.

/data/misc/dhcp

/data/misc/wifi

Heads up: deleting those 2 folders will reset your wifi settings and delete stored wifi passwords.
[Verizon Samsung Galaxy S III] tv31284:
That worked perfectly. Thank you.
[Verizon Samsung Galaxy S III] bmeek:
Good info! Where were you two weeks ago? http://xdaforums.com/showthread.php?p=53113887 . :)
[Verizon Samsung Galaxy S III] funkymonk101:
Hey all. Anyone have a solution for Google Maps Navigation rebooting the phone during longer trips? WIthout fail, any navigation of 10+ minutes, the phone will reboot in the middle, although not necessarily after the same length of time. Very unsafe while driving.

This used to happen occasionally on CM10, for trips of 30+ minutes. On CM11 it happens in much less. I did dirty flash from 10, but have since done a full wipe, did not fix the issue. I've tried M7 and various nightlies, all seem to have the problem.

I've seen people discuss this problem, but no solutions. I loathe to go back to a TW ROM, but functional navigation for long drives is an essential feature of my phone. Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
No

Ive started rebooting my phone before a trip to work around this. And reboot again before the next trip. I never got reboots with waze though, and waze is basically google nav now so you might want to try it out if the reboot trick don't work.
[Verizon Samsung Galaxy S III] funkpod:
I have this problem right now while using Alliance Rom.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I have had this problem for the past few months on cm11. I too would love to find a solution or have the cm team work on this.
[Verizon Samsung Galaxy S III] Roger W:
Hour-long navigations haven't been a problem for me; is the GPS firmware part of the modem flash package? I'm on the ML modem and M7, which is a dirty flash over a clean nightly just after M6.
[Verizon Samsung Galaxy S III] buschbarber:
I wanted to copy a URL from Firefox to a Gmail message. I can highlite the URL, right click, and select Copy, but I cannot find the correct keyboard shortcut to Paste it into the email.
[Verizon Samsung Galaxy S III] NedDasty:
I've been getting constant reboots on the last five nightlies or so. Sometimes the phone will continue to reboot during the reboot process, and I have to pull the battery for a while. I've been trying to take note of when it happens, but it's incredibly random.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I'm having massive battery drain on the 4.4.3 nightlies. So far today my phone has been on battery for 4 hours and has not been in deep sleep at all even though I haven't touched the phone till now. Wakelock detecter says google play services has caused the most CPU wakelock while faceebook has caused the most wake-up triggers. Bam_dmux_wakelock has caused the most kernel wakelocks. Can anyone tell me what any of this means?
[Verizon Samsung Galaxy S III] funkpod:
http://download.cyanogenmod.org/?device=d2lte

Hey, so the 6/08 snapshot located here is the last pretty stable build from what I'm reading? Don't care if it's 4.4.2, just looking for pretty reliable.
[Verizon Samsung Galaxy S III] Gareee:
I'm having a few recent issues that are bugging the heck out of me. Cm11s auto updater is now replacing trip with a very basic cm recovery, and I have to reflash trip after updating now. Grrrrr!

I'm also now seeing issues when my tracks tries to share a run for Google drive. I don't know if that's a Rom issue, or a recent Google drive bug though.

I might roll back a few days to when Google drive was working, and see if it's the Rom, or Google drive acting up.
[Verizon Samsung Galaxy S III] Mtsprite:
Yes, there will be no more "stable" builds from them, instead there will be "M" builds which are basically snapshots.
[Verizon Samsung Galaxy S III] chowner:
???????????????
[Verizon Samsung Galaxy S III] bmeek:
I'm not clear on your recovery issue, but I noticed that My Tracks recently got an update that changed the export options substantially.
[Verizon Samsung Galaxy S III] funkymonk101:
How do I check that? My baseband version is I535VRBMF1, not sure about anything more specific than that.
[Verizon Samsung Galaxy S III] Roger W:
Take a look at this thread:

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

You don't want to take the full ML1 package because it will lock your bootloader, but someone made a hybrid package that has the old, unlocked bootloader coupled with the newer ML1 baseband. That's what I use. No idea if it's relate to your nav problem, though.
[Verizon Samsung Galaxy S III] funkymonk101:
Thanks. I've looked at that thread a bunch of times, but the "Latest Firmware" links to http://invisiblek.org/ no longer work.

I found these files later in the thread:

http://d-h.st/users/invisiblek/?fld_id=35606#files

I'm guessing d2vzw_ML1_modem.zip is what I want, but with all the Knox lockdown hysteria, I'm afraid to flash anything without clear instructions saying it won't lock my phone.

Besides the navigation issue, I've had reception issues since going to CM11, so I wouldn't mind trying a new modem if it isn't going to mess up my boot loader.
[Verizon Samsung Galaxy S III] Roger W:
That sounds like the right zip. The zip I used has a sha1 of

1dd53014108d61da3b8698e1f82efb01a6f81f42

edit - and the md5 of mine is the same as the one listed at the download page, so that's the file.
[Verizon Samsung Galaxy S III] funkymonk101:
Yup, it is the same file, thanks! Read some other threads too, seems this one is safe to flash over MF1.

d2vzw_ML1_modem.zip

MD5: 4894dabfb48e711d8c54d373c5707671

SHA1: 1dd53014108d61da3b8698e1f82efb01a6f81f42

I'll flash this modem, then post back here in a few days if it's made a difference with my navigation issues.
[Verizon Samsung Galaxy S III] buschbarber:
How do I download this file without downloading and installing mobogenie?
[Verizon Samsung Galaxy S III] Roger W:
I searched for the md5 and found an alt site

http://www.androidfilehost.com/?fid=23329332407592256
[Verizon Samsung Galaxy S III] buschbarber:
I just checked and I am running I535VRUCML1. Is that the same?
[Verizon Samsung Galaxy S III] funkymonk101:
I believe so. I was on MF1, and after flashing, my baseband in About Phone became ML1 like yours.

I downloaded the file from here: http://d-h.st/users/invisiblek/?fld_id=35606#files

But as long as the MD5 or SHA1 matches up, doesn't matter where you get it from.

I had no problems with flashing the modem through Clockwork Recovery. Didn't brick, still have LTE/GPS. Will have to see on my next drive if the Navigation reboot is still there (lately it happens within a few minutes of starting). Will also see if my general CDMA signal strength/reliability have improved.
[Verizon Samsung Galaxy S III] Gareee:
I wonder if that issue is with my tracks then? It's still having the same Google drive post problem to facebook 3 daily later.

BTW, I've been reading about art. Is there a thread or way to replace davlik with art on cm11?

---------- Post added at 07:58 PM ---------- Previous post was at 07:32 PM ----------

The latest twrp recovery is being over written by the nightlies with a built in cm recovery when you update from the system menu. I have to then flash twrp again over the top of it.
[Verizon Samsung Galaxy S III] Mystikalrush:
Im still on a 4.4.2 build. Which nightly are 4.4.4 and up?

Questions:

Is there a new gapps recommend for this as well?

Is there a recommend firmware? I'm only using ML1 baseband, not firmware.

Complete system wipe required?

Is 4.4.4 stable enough as a daily driver, or still to early?
[Verizon Samsung Galaxy S III] chowner:
A few questions.

I've had horrible reception on my phone recently. Although I've never returned to stock as some has suggested. I'm still running ML1.

Would like to hear some thoughts on if I should go to stock and then stick with ML1 or go to an older base.

Who's done what and what have been your results. Its at the point now where I may return to stock (eek!) to have a useable device.

Builds from a year ago where fabulous, but KitKat has been soso the whole time. (Not complaining, thank you for all the hard work!)

Thanks
[Verizon Samsung Galaxy S III] Gareee:
I'm rolling back to the snapshot build, and think I'm going to stick with them.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I was having similar issues for the last couple of months. I wasn't sure if it was due to using the ML1 modem or the latest cm builds. I flashed back to the MB1 modem and went back to the M7 build and it would seem as though reception is better....but I can't say scientifically if that's the case.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
The nightlies after the M7 are 4.4.3...I haven't flashed any since the release of 4.4.4 so I'm not sure if the newest nightlies are 4.4.4. I was having severe battery drain on the 4.4.3 nightlies so I went back to M7 and my drain has been fixed as far as I can tell.
[Verizon Samsung Galaxy S III] merdely:
http://www.cyanogenmod.org/blog/last-week-in-cm-jun-19-2014

No.

I didn't change my firmware. I'm still on MB1.

No. Generally the only time you have to do a wipe is when going from CM# to CM#+1 (like CM10 -> CM11).

I'm happy with it.

So there was a bug a few weeks ago that seems to prevent my phone from remembering that I'd chosen the PowerSaving Performance Profile. It always reboots into Balanced. Interestingly, I've noticed improved battery life since experiencing this bug. On Balanced, I see that my percentage at the end of the day is possibly 10 points higher than it had been. That could be usage or other factors, but I'm happy with my battery life on both 4.4.3 and 4.4.4 nightlies.
[Verizon Samsung Galaxy S III] tv31284:
I had a reboot while starting up Navigation and I've attached a logcat. Though, after that reboot, I used Navigation for over an hour (nonconsecutively, but at least 30 minutes at a time) and I didn't have any further reboots. I did notice the phone slow down horribly the longer I used it though.

This was on the 6/21 build, btw.
[Verizon Samsung Galaxy S III] BattsNotIncld:
I'm on SlimKat but I've noticed this same issue on every AOSP rom I've tried. The solution I found is to flash an alternate kernel. Right now I'm on the latest Leankernel but I've also had success with BMS.

The random reboots are now very rare, and the phone no longer bogs down to a crawl after 15 minutes of using Navigation.
[Verizon Samsung Galaxy S III] kidhudi:
Hey guys. Is there any way to get the Google search dialer to work on this?

Thanks
[Verizon Samsung Galaxy S III] funkymonk101:
There's a good chance the ML1 modem fixed/mitigated my Navigation reboots. I navigated for 30 minutes yesterday without a reboot (previously I couldn't go 10 minutes). Will keep using it and see if it holds up.

The ML1 modem also seems to have improved my signal reliability, if not strength. My apartment has terrible signal, and previously it would constantly move from single bar to no signal at all and back, even if left in one spot. Now it seems to do a much better job at holding onto that one bar, so I can make calls without them dropping on me.

This is all on the 6/18 build for me. Will probably flash the latest nightly soon.
[Verizon Samsung Galaxy S III] NedDasty:
The ML1 .zip file for me aborts because it's looking for a d2vzw, and I'm guessing the newer builds say d2lte. Did you have this issue? How'd you get around it, modifying your build.prop before flashing the ML1?

Edit: turns out this is a bootloader issue, and not only that, but I apparently already upgraded to the ML1 modem a while ago anyway. Cheers!
[Verizon Samsung Galaxy S III] Defragger51:
ART not working

After hearing all the good news about ART on the Google IO yesterday I decided to give ART a try again. Yes I have used it before but went back to Dalvik because my security cam app would not run. So after going into developer options and choosing use ART the phone reboots and its still on Dalvik, tried it several times same thing happens. I even uninstalled X-posed cause I remember reading it did not work in ART. Using the 06/24 nightly with out any issues . Anyone else having this problem , is it a problem with the nightly,any ideas or fixes
[Verizon Samsung Galaxy S III] chowner:
Been running ART for a while now no issues. Just updated this morning to latest nightly.
[Verizon Samsung Galaxy S III] eaglesfan398:
How stable is this rom? I am currently running liquid smooth. Also is it fast?
[Verizon Samsung Galaxy S III] bmeek:
I'm still seeing that my setting not to use the device button backlight gets reset with every reboot... Other than that, no issues with the 06/25 nightly.
[Verizon Samsung Galaxy S III] merdely:
I'm hopeful that this commit will fix it.
[Verizon Samsung Galaxy S III] Defragger51:
Update: Did a clean install of today's nightly, wiping dalvik,cache and system and was able to convert over to ART, everything is working smoothly, except my security cam app again.
[Verizon Samsung Galaxy S III] buschbarber:
Aside from KK launcher crashing a and poor battery life, I am having problems with text sizing in forum replies. The font size varies greatly from one reply to the next. One reply will have large text and the next reply will have very small text.
[Verizon Samsung Galaxy S III] MartyMacGyver:
Fingers crossed... it's evidently merged.

Based on your positive experience I updated from the 6/8 nightly (which loved to reboot at random moments, especially during navigation) and MF1 (which seemed to get rather poor signal) to 6/26 and ML1. So far, so much better! (I cleared cache before installing them.)
[Verizon Samsung Galaxy S III] bmeek:
I had great luck with the 06/08 nightly running the latest dkp kernel (no reboots), but wanted the latest v4.4.4 build (as long as it's proved to be solid).
[Verizon Samsung Galaxy S III] MartyMacGyver:
Haven't tried alternate kernels yet for this... will it work with these recent builds? I'm just glad the phone is more stable now.
[Verizon Samsung Galaxy S III] merdely:
This didn't fix forgetting the Performance Profile setting for me.
[Verizon Samsung Galaxy S III] savagebunny:
So been on 4.3 and well, I'm will be stuck with this phone for a while, was trying out CM11 builds back in February, and was having hot reboots, bluetooth wasn't working syncing to my car. How have the builds been lately? Also, ML1 is needed correct for this flash, went back from ML1 to MF1 due to issues on 4.3 with ML1 for me
[Verizon Samsung Galaxy S III] bmeek:
The various alternate kernels periodically sync with the cm11 native kernel sources, and although my favourite hasn't been updated since early June, it seems to run well with the current nightly (even though there have been numerous changelog entries for the d2 kernel over the past few weeks).

Unless you feel strongly about running a different CPU scheduler or manipulating clockspeeds and voltages, you're probably better off running the native kernel...

---------- Post added at 03:18 PM ---------- Previous post was at 03:11 PM ----------

Likewise the button backlight setting slippage persists with the 6/27 build.
[Verizon Samsung Galaxy S III] bmeek:
Here's a tangential question... How much value remains in maintaining separate discussion threads for cm11 on each of the d2lte carrier variants?

I imagine that the majority of issues being discussed are not carrier specific. Thoughts?
[Verizon Samsung Galaxy S III] tv31284:
I've never really believed that alternate kernels were significantly different or better than stock kernels but in this case, after switching to Lean Kernel, I'm at over 90 hours of up time (whereas before I'd get to around 40), navigation has been fine, the phone doesn't slow to a crawl, and battery life seems to be a little bit better.
[Verizon Samsung Galaxy S III] Roger W:
Despite my suggestion about ML1 last week, I myself had a navigation reboot today after a few half-hour usages. So I guess that's not athe real fix, if there even is one.

One difference is that I recently started putting it in the compass mode where the map swivels as you turn. I wonder if that's why I had the reboot for the first time.

Do you guys notice a relation between swivel mode and reboots?
[Verizon Samsung Galaxy S III] buschbarber:
I am using the Android Browser as my default web Browser. When I am viewing posts in this forum or others, the font size for the text in each reply can be vastly different. I never had this issue before. It is annoying because I have to change the Zoom level as I scroll from one reply to the next.
[Verizon Samsung Galaxy S III] tv31284:
Spoke too soon. Just had a reboot.
[Verizon Samsung Galaxy S III] bmeek:
Does anyone else see a new persistent notification for Google search? Tap the notification and you're taken to the Google search / Google Now settings...

Edit: Couldn't clear the notification or fathom its purpose, but it went away after a reboot. weird.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Does this rom along with other AOSP roms still have the SMS issue if you aren't on BMB1. Everytime I installed the ML1 modem it would only send one text then stop.
[Verizon Samsung Galaxy S III] Hybridnoob:
It did still have the problem a couple of months ago. I haven't tried newer firmware/modem since.

This bug affected very few people, but I guess we're the lucky ones.
[Verizon Samsung Galaxy S III] chowner:
I've never had this problem
[Verizon Samsung Galaxy S III] buschbarber:
I have never had this problem.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Well it has been a problem for others. Google it..others beside me have had the issue.
[Verizon Samsung Galaxy S III] buschbarber:
My biggest problems have been poor battery life, overheating while charging, and random net:err messages.

I am using ML1.
[Verizon Samsung Galaxy S III] chowner:
Yeah horrible battery life, with extremely slow charge times. Also reception is horrible, been in places where others with the S3 on stock rom have had 50%+ signal strength on LTE and I have nothing.

I've said it before and I really hate the thought, but I think I'll need to just bite the bullet and go to stock.
[Verizon Samsung Galaxy S III] esjames:
This affects a few of us including me, mostly on the east coast. Truth be told the MB1 modem/firmware works well with me as far as speed and connectivity.
[Verizon Samsung Galaxy S III] ChiefIlliniwek5:
I'm beginning to have the same thoughts. My battery life is atrocious. My phone has been off AC for 4 hours and 20 minutes. With only 35 minutes of screen on time, my battery is already at 32%. Google Play Services is largely to blame for this as it is the #1 culprit on WakeLock Detector and my phone has been "awake" for 80% of the time, but I don't know how to fix this or if it even can be fixed. Would a stock ROM make it better?
[Verizon Samsung Galaxy S III] chowner:
most likely returning to stock would
[Verizon Samsung Galaxy S III] Defragger51:
Yes IF you are in one of the east coast stats that had problem with the ML1 modem , the same problem exist with the new NE1 modem. I just found that out myself now to try and fix it by going back to stock cause re-flashing the MF1 modem did not fix it.
[Verizon Samsung Galaxy S III] Hybridnoob:
1. Backup current ROM (CM11 in my case)

2. In Terminal Emulator - su (enter) reboot nvrestore - if you previously completed nvbackup

3. Battery pull once process completes, as it will bootloop

4. Boot into recovery, restore nandroid and flash MB1 firmware. I immediately or upon reboot have had issues on all newer firmware versions.

5. Reboot system and profit. No SMS issues since.

Side note - I had to manually wipe system, cache and dalvik, then install ROM and Gapps to get the next nightly to boot (CMUpdater bootlooped). Successive nightlies have installed and booted as expected.

MF1 and newer brought back the SMS bug.