yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
Yeah any of my builds are flashable :D :p

But no, there isn't a flashable zip just for the fix without flashing the whole rom. You may be able to pull over telephony-common.jar from one of the builds but I cannot guarantee that it will work and or not cause any other issues.
[Verizon Samsung Galaxy S III] minnysota:
Sounds good. Thanks for the reply! I would love to rock one of your builds, but I've gotten too used to the navbar :eek:
[Verizon Samsung Galaxy S III] sivarticus85:
I've noticed I get battery drain when Google Maps location reporting is on. I always turn it off and I haven't had a problem since, even on the latest maps update.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah, I just noticed that I got the new maps (auto updated while I was on wifi i guess). I just cleared data on maps and made sure location reporting was off, so we'll see how the battery is now.
[Verizon Samsung Galaxy S III] julesism:
I also had a couple reboots on Masta's 7/19 build Friday night and yesterday. My phone was sitting (sleeping) on its dock/charger both times. I flashed imoseyon's latest kernel late last night and no reboots (yet). I'm going to try some of the suggestions above to see if I can improve battery life. I do not have leaked Play Store but I do have new Maps.
[Verizon Samsung Galaxy S III] RED ZMAN:
MastaMoon, have you begun to use this yet? The BT freezing bug is all I have left and it drives me insane.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] Chris123NT:
What I've noticed using that cherry pick, it will still hang on turning bluetooth off every once in a while, but it seems to only hang for 20 secs or so and then it does turn off, whereas before it would hang until you manually killed bluetooth share AFAIK.

So it's not a complete fix, but it seems to be an improvement.
[Verizon Samsung Galaxy S III] RED ZMAN:
Yeah, I saw your description, that's why I'm so excited. better than what we have now.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] zcmack:
I had two random freezes in the last 24 hours. I'm on the 7-19 build. Once was while browsing facebook, the other was while my alarm was going off (gentle alarm app) with the phone on the charger. What is strange is that both of these freezes required a battery pull. My previous freezes (from the last weeks worth of builds) would reboot themselves.

Flashing 7-19 fixed my broken still camera issue but I am still unable to record a video in snapchat.

I'm going to try imoseyon's kernel as well. Will report back on the reboots.
[Verizon Samsung Galaxy S III] goldsmitht:
reboots

i had a couple of reboots last night while playing jewelquest 2 and charging at the same time.

Might have something to do with my charger, as it seems to hang in sending SMS while charging as well. Hadn't heard that was a problem with anyone else, so was chalking it up to my USB extension cord. BUT, since everyone else seemed to have reboots on 7/19 thought i would report as well. unfortunately, today i can't recreate the reboot, and seems to have worked its self out.

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
The only random reboots I tend to get is when charging also. Usually when the phone is just sitting on my desk dock charging. Cant reproduce for a log, last_kmesg says the radio crashed.
[Verizon Samsung Galaxy S III] mastamoon:
7/22 build in the OP

-- 0/99 bug commit has been merged - removed cherrypick

-- added a bluetooth commit that might help with bluetooth hanging when trying to shut it off.

-- repo sync @ 3pm EST

** Romdashboard has updated their system to now always notify of the latest build instead of the next version increment. So now if you don't upgrade everyday but every once in a while want the latest, you will be able to download it right from the romDB app instead of having to come to this thread.
[Verizon Samsung Galaxy S III] shadrach47:
Did "babel" also get put in? When I restarted I had a new app, Voice+. Allows sms through gvoice.
[Verizon Samsung Galaxy S III] goldsmitht:
Don't see it on mine
[Verizon Samsung Galaxy S III] mastamoon:
Babel was renamed to VoicePlus (Voice+)

I had it on my install and immediately froze it as Ill never use it :)
[Verizon Samsung Galaxy S III] Chris123NT:
Interesting, I have the APK in /system/app but it's not showing up in the app drawer lol
[Verizon Samsung Galaxy S III] mastamoon:
Weird, mine ended up right next to my Google Voice icon.. Same icon also.
[Verizon Samsung Galaxy S III] Chris123NT:
Well that would be why, I don't have gvoice installed, voice+ must only appear when google voice is installed.
[Verizon Samsung Galaxy S III] mastamoon:
Makes sense I guess. I had a hunch about that. Lol
[Verizon Samsung Galaxy S III] Chris123NT:
Yup just confirmed it, installed google voice and Voice+ showed up in the app drawer
[Verizon Samsung Galaxy S III] RED ZMAN:
So I got updated last night, and upon my first toggle ON of bluetooth, which was this morning, it promptly did the same thing it has been doing for months, looks like it is on, but doesn't connect to anything. I let it sit, and it stayed like that for a half hour. I stopped Bluetooth Share and it instantly connected. When I got to work I shut it off, and no issues, but it usually only presents when I'm trying to connect.

I did the usual Cache/Dalvik. Should I wipe System and try again if I'm still having problems?
[Verizon Samsung Galaxy S III] mastamoon:
My bluetooth didnt auto connect this morning in my car which I never had a problem with before. I also tested turning it off before I turned my car off as this is what usually caused my hang and it still hung as expected. So I think that cherrypick dont do much.
[Verizon Samsung Galaxy S III] PerCompLLC:
My device won't even pair with my head unit anymore (Alpine UTE-42bt). I don't know if it's a kernel issue, a ROM issue, or just user idiocy... But it truly sucks.
[Verizon Samsung Galaxy S III] mastamoon:
Weird, I went to lunch today and it worked as expected for me. SMH
[Verizon Samsung Galaxy S III] PerCompLLC:
My issue is more than likely a user issue...
[Verizon Samsung Galaxy S III] mastamoon:
I guess I should have more closely checked this cherrypick

http://review.cyanogenmod.org/#/c/45090/

its a mod to the BatteryStatsService.. I dont think it actually effects bluetooth in any way, shape or form. All it looks like it does is remember to tell the BatteryStatsService that bluetooth got turned off. Hmm.
[Verizon Samsung Galaxy S III] RED ZMAN:
Did some looking around, the issue is on JIRA.

https://jira.cyanogenmod.org/browse/CYAN-504
[Verizon Samsung Galaxy S III] Chris123NT:
So basically it's another google issue, just like the 0/99 bug on LTE.
[Verizon Samsung Galaxy S III] mastamoon:
7/23 build in the OP

-- added "Show advanced reboot if using an insecure lock screen - http://review.cyanogenmod.org/#/c/45936/" - LOVE IT

-- Repo Sync @ 3:30 PM EST
[Verizon Samsung Galaxy S III] mastamoon:
Yeah thats an issue, but dont think the cherrypick is supposed to be the cure. Thats the way I interpret it anyway. Looks like its a fix for wonky battery reporting of Bluetooth, like showing its still on and using battery if its really been turned off/disconnected. IMHO anyway, could be wrong. It certainly doesnt fix the problem in that JIRA.
[Verizon Samsung Galaxy S III] goldsmitht:
Signal Strength Increase?

Is anyone having problems with signal strength on latest build (7/23)? Doesn't seem to be as good as 7/19, and thinking about going back to see if it is me or if there is a difference.

Just wondered if anyone else was seeing it.

:confused:
[Verizon Samsung Galaxy S III] Chris123NT:
Is this bars or actual DBm? Nothing has changed in the last few days that should be causing a weaker signal.
[Verizon Samsung Galaxy S III] goldsmitht:
No, more of an inability to send texts; was just more curious if anyone else was seeing it, or if it was just my phone again

:(
[Verizon Samsung Galaxy S III] Chris123NT:
Haven't had any issues sending texts, MMS, or even making calls tonight.
[Verizon Samsung Galaxy S III] ups2525:
Yep I can't text as well as no data connection & I'm not at home so I can't try Wifi. I have 3 nandroids of 7/22 each w/a different theme & I flashed all em' to 7/23 with the same outcome. Flashed back to 7/22 & all is well. I don't have time to try & work it out so I'll stay with 7/22 for now. No complaints at all just chiming in and while I'm here I'd like to say thanks a 'mill' for all that you do mastamoon!
[Verizon Samsung Galaxy S III] Chris123NT:
Wow that's weird, I just checked and I don't seem to be having any issues, sent and received SMS right after I flashed. Been building my own builds the last few days but today I used the same cherry picks as masta so it should be exactly the same.

Just checked mobile data and that's working too, I'll check LTE in the morning when I go to work.
[Verizon Samsung Galaxy S III] funnyperson1:
BT4.0 for stuff like the Fitbit should work on stock, Samsung used a different bluetooth stack than Google's AOSP one.
[Verizon Samsung Galaxy S III] devo1929:
I'm not sure that's completely true. I thought it was a difference between Android 4.1 and 4.2.

Sent from my GS3
[Verizon Samsung Galaxy S III] RED ZMAN:
So since the new BT cherrypick went in, I had to force close Bluetooth share once yesterday. When I hooked up this morning on my way to work, it didn't connect and I waited, and next time I looked, it was connected. Usually once I have to force close BT Share, I have to do it every time after that until I reboot.

That cotton picking cherry pick may be doing something.

How many folks with the BT bug are using NFC? USB tether?
[Verizon Samsung Galaxy S III] cesium:
He's correct. Android does NOT natively support bluetooth low energy, but should starting with 4.3. Companies like HTC and Samsung have, in the mean time, developed their own proprietary BLE stack for compatibility.
[Verizon Samsung Galaxy S III] goldsmitht:
Maps Batter Drain

Is everyone still seeing the battery drain caused by Maps update? I keep getting notice that i have an update ready for maps, but if its causing battery drain like everyone was saying, then i'll just keep ignoring it

:confused:
[Verizon Samsung Galaxy S III] mastamoon:
I turned off location reporting and it seems to have fixed the battery drain.
[Verizon Samsung Galaxy S III] goldsmitht:
but won't that affect apps that use maps for updating locations? I use a few, to include WeatherBug that rely on locational data. Or am i getting it confused with system locational data?
[Verizon Samsung Galaxy S III] mastamoon:
No that still works.. its Maps itself tracking where you go.. you turn it off in Maps itself.
[Verizon Samsung Galaxy S III] Neverender326:
Whatever GMS.NLP is that's what is causing drain. I have over 3k wakeups from that alarm in Google Services since last night. I only started seeing it after the new maps. I have location reporting disabled. Research on this alarm didn't turn up much.
[Verizon Samsung Galaxy S III] mastamoon:
Google Maps Service, Network Location Protocol would be my guess. Freeze/disable google now also.. I think it follows you around too.
[Verizon Samsung Galaxy S III] mastamoon:
7/24 build in the OP

-- bluetooth cherrypick got merged

-- added M2: msm: grow MM heap size for the iommu use case - http://review.cyanogenmod.org/#/c/45984/ - this partially fixes recording video in instagram.. partially!

-- repo sync @ 3:30 PM EST

Hopefully one of our last CM10.1 builds as CM10.2 will soon be upon us! :good: :victory: :highfive:
[Verizon Samsung Galaxy S III] Chris123NT:
New thread soon haha
[Verizon Samsung Galaxy S III] AdMire:
Just a quick question: I flashed the 07-23 build and Weatherbug kept putting my location as Pennsylvania (I live in Illinois). Just curious if anyone had anything similar. I'm going to flash the 07/24, just seeing if anyone noticed that. It looks like there are Google Map issues, not sure if they are related or not.
[Verizon Samsung Galaxy S III] senorbuck:
So by partially it looks like it records the video okay now but the processing of the filter and viewing of that is still dorked up? Close!
[Verizon Samsung Galaxy S III] mastamoon:
Yeah, we are still trying to track that down, hoping that commit atleast gets Cyanogen's attention maybe.. but with 4.3 dropping.. back burner and/or might be fixed automagically in CM10.2! :P
[Verizon Samsung Galaxy S III] funnyperson1:
Location issues may be related to this

http://review.cyanogenmod.org/#/c/45566/
[Verizon Samsung Galaxy S III] mastamoon:
That change should only come into play if our board define calls for it, which it doesn't.
[Verizon Samsung Galaxy S III] goatman101:
I too am having problems sending texts from the 7/23 and 7/24 build. I have to re-flash an older build and the issue resolves itself.
[Verizon Samsung Galaxy S III] NegativeOne:
Lots of people are experiencing this. I've been enjoying a nice trip to San Francisco personally :P. 7/24 is messed up too.

Hmm. Disappoint. Do you have any idea what it actually could be then Masta?
[Verizon Samsung Galaxy S III] Chris123NT:
Still having issues with in call audio being FUBAR on INCOMING calls only. Toggling speaker fixes it.
[Verizon Samsung Galaxy S III] mastamoon:
I tested while I was out and about today and had no problems with gps finding me anywhere I was, on wifi or not.

Have you guys tried refreshing your agps? Use an app like gps test. Or have you tried wiping system when you update to a new build? Just have to reflash gapps if you do.
[Verizon Samsung Galaxy S III] mastamoon:
I just tested by calling my cellphone with my house phone. Absolutely no problem, could hear and speak each way on each device. Didn't toggle speakerphone either.
[Verizon Samsung Galaxy S III] NegativeOne:
I used GPS Status to clear AGPS and to download it fresh (also tried just clearing). No good. I suspect it is not a device state issue because I can revert back to an old build and it gets fixed. I think it has to do with how code in the new nightlies is interpreting info from AGPS (network location)
[Verizon Samsung Galaxy S III] AdMire:
Yeah, I restored back to 07/21 build and everything worked fine. I haven't flashed 07/24 yet now that I see there are still issues. Although I may just to test it myself. I usually just wipe cache/dalvik on these nightly. I don't like wiping everything but external, I get lazy to set everything back up! haha!
[Verizon Samsung Galaxy S III] mastamoon:
Wiping system won't cause anything to change. Just be sure to flash gapps along with the rom.

I just went through all the commits going back to the 11th and didn't see anything that even remotely looks like it could have broke gps. 21st works though huh...
[Verizon Samsung Galaxy S III] mastamoon:
I'll try and revert http://review.cyanogenmod.org/#/c/45565/ tomorrow, but my gps works fine so I can see that it would break yours but you never know.
[Verizon Samsung Galaxy S III] AdMire:
I'm sorry, that's what I meant. I wipe those 3. System/cache/dalvik. With the new update to TWRP, it's kind of confusing because you have to go into "Advance" to chose those 3.

Actually, has anyone tried the default wipe that says "Wipes Data, Cache, and Dalvik"? Isn't "Data" different than "system"? I always go to advance and choose Dalvik/system/Cache.

---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------

I'll flash 07/24 and see what happens.

---------- Post added at 07:09 PM ---------- Previous post was at 07:01 PM ----------

Well after flashing 07/24, clearing System/Cache/Dalvik and flashing Gapps, looks like Weatherbug has found my correct location.
[Verizon Samsung Galaxy S III] mastamoon:
Woot
[Verizon Samsung Galaxy S III] Div033:
It took them a few weeks to get us 4.2 so I'd think it'll be the same for 4.3. We'll probably have some weeks of 10.1 nightlies ahead of us.
[Verizon Samsung Galaxy S III] glman1:
Steve Kondik posted on his G+ that there would be a zeroday release.
[Verizon Samsung Galaxy S III] Div033:
Whaaaaat

Edit: Wow you're right... That is crazy. Did not think it was possible!
[Verizon Samsung Galaxy S III] funnyperson1:
You're right, it's not possible.

Cyanogen was just stating that there was a zero day release of the source code for AOSP. Usually Google waits a while before releasing the source after a new release of Android. I would be shocked if it doesn't at least take a couple days for cm to work on nexus Devices and then a week or two for us to get some love.
[Verizon Samsung Galaxy S III] Div033:
Oh... Well then I guess I'd better take down the streamers and pop the balloons. Thanks for the corrections.
[Verizon Samsung Galaxy S III] sivarticus85:
Exactly. However, if they wait too long they'll violate the GPL, so it's good that it's out quick. Just a matter of time!
[Verizon Samsung Galaxy S III] NegativeOne:
I tried wiping everything but system and no-go. Would like to avoid that pain again. It would be odd if that were it anyway. I might also add that I had mine working temporarily, but it went back to the broken state, so please post back tomorrow and let us know if it continues to work.
[Verizon Samsung Galaxy S III] Chris123NT:
So quick update on the incoming call audio issue, it happens if the ringer is on vibe or silent. Thanks to mastamoon pointing me to the right commit to revert the issue is resolved and the revert is officially merged.

http://review.cyanogenmod.org/#/c/46006/
[Verizon Samsung Galaxy S III] ups2525:
Damn masta...you a BOSS!!!! :cool:
[Verizon Samsung Galaxy S III] dpaine88:
Am I the only one who's GPS thinks they are in California after the 7.0 Google Maps update?
[Verizon Samsung Galaxy S III] ElementR:
Try fixing permissions, that always fixes my gps issues.
[Verizon Samsung Galaxy S III] dpaine88:
Fixing permissions sadly did not help so I flashed a 6-28 build I had laying around and GPS is back to normal. Seems like I've had the issue since Monday
[Verizon Samsung Galaxy S III] NegativeOne:
No. I suggest reading the last page or two to find out more.
[Verizon Samsung Galaxy S III] mastamoon:
Somebody with this issue needs to help with some research. Download and flash the past week of official nightlies and help us track down where things went wrong. :) Mine is fine so I cant really help with tracking this down and there isnt much in the change logs that point to this problem.
[Verizon Samsung Galaxy S III] NegativeOne:
I've seen people say that the 17th-19th seem to be OK (which supports your hypothesis about commit 45565 which landed quite recently). I've got a busy day ahead of me at work, so I won't be able to do a lot of flashing.

Are you still going to try to revert the following today? If so I'll definitely give at least that one a shot.

http://review.cyanogenmod.org/#/c/45565/
[Verizon Samsung Galaxy S III] Hans5849:
I had the same problem. I was out near Schaumburg, IL and it thought I was in Pittsburgh, PA. I rebooted the phone and it cleared up.
[Verizon Samsung Galaxy S III] mastamoon:
Are you guys that are having GPS issues turning on Privacy Guard for any apps? Specifically apps that are not showing your correct location?!

If so, please turn it off or learn to deal with it not knowing where you are. Thats what PRIVACY GUARD DOES! Feeds bogus info to apps to keep them happy while not handing out the actual data its requesting.
[Verizon Samsung Galaxy S III] Chris123NT:
LMFAO, would explain why I've never had this issue
[Verizon Samsung Galaxy S III] NegativeOne:
I did set privacy guard for an application as a test, but I have since then removed that application. And for me, on the newer builds, neither Maps, nor Google Now (neither of which I've touched) show correct location. and if i install the app again, it's disabled. so it's not like it's saved somewhere.
[Verizon Samsung Galaxy S III] Hybridnoob:
I use Privacy Guard for several apps. Don't have any issues with the other apps (Maps, etc.) that I don't use PG on. For those having issues, it would be worth checking Settings/Security/Privacy Guard to see if it's enabled on the apps you're having issues with. There is an option to have PG enabled for all newly installed apps (off by default), so that may be the issue if you ever enabled it.
[Verizon Samsung Galaxy S III] mastamoon:
Welp my build just broke and I cant figure out why so probably not going to be a build today.. might be related to a bunch of the 10.2 stuff thats being done.. might not. Trying it figure it out.
[Verizon Samsung Galaxy S III] NegativeOne:
I don't have it enabled for anything. If you were to put out yesterday's build with a certain rollback, I wouldn't fault you ;)
[Verizon Samsung Galaxy S III] Chris123NT:
It's the voiceplus commit, I reverted it and it build.

For anyone who wants, here's a build for today.

Same cherry picks as masta's build minus tunnel audio (which he was removing in his as well since it's causing issues). Repo Sync 3:15 EST

http://chris123nt.com/CM/cm-10.1-20130725-UNOFFICIAL-d2vzw.zip
[Verizon Samsung Galaxy S III] NegativeOne:
No agps revert?
[Verizon Samsung Galaxy S III] cynikalJ:
I have a question and this may have already been explored but would the gs4 Google edition not help us with the ril? Mine works but it's still spotty
[Verizon Samsung Galaxy S III] khymbote:
That's what I found out and how I fixed my GPS issue. That and clearing data for maps, GPS tools and Google framework. Went outside let my GPS find me and I was fine after that.
[Verizon Samsung Galaxy S III] NegativeOne:
It's not really GPS that's a problem, it's the network location. At least that's the problem most of us are talking about. Clearing stuff doesn't fix that.
[Verizon Samsung Galaxy S III] khymbote:
I am currently running the 7/23 build as the 7/24 build broke netflix and any other video app for me. That was the only thing the 7/24 app broke. I had no issues on gps or location. I wouldn't know where to start on why location isn't working.

I do know however that there are a lot of bad GS3 phones out there with Verizon. I'm currently on my 5th due to hardware issues.
[Verizon Samsung Galaxy S III] Hans5849:
I got a logcat of the gps problem if you're interested.
[Verizon Samsung Galaxy S III] Chris123NT:
No, I didn't revert it since I wasn't having any problems with GPS and mastamoon's privacy guard explanation makes a lot of sense.
[Verizon Samsung Galaxy S III] khymbote:
I noticed when it when I finally used it. I turned it off on the apps that used location and or GPS. My apps worked again.
[Verizon Samsung Galaxy S III] NegativeOne:
Except my privacy guard is off and I'm having the problem. Also I'm not having the problem on an older privacy guard build.
[Verizon Samsung Galaxy S III] Chris123NT:
I actually just ran into this issue, thought i was in san jose. Fixed it by clearing data on Google services, maps and GPS status, rebooting and running GPS status and letting it acquire satellites. Now its fine.

Edit just had the issue again, something is definitely wrong here, I've never used privacy guard either, seems to trigger when GPS is off and your location is calculated by mobile. GPS is screwy as well when this happens

It's one of these two commits doing it, gotta be. Can someone else test? I'm away from home for the next few days so I won't be able to build to test.

http://review.cyanogenmod.org/45566

http://review.cyanogenmod.org/45565
[Verizon Samsung Galaxy S III] NegativeOne:
Mastamoon said that the first one doesn't apply to d2vzw.

By the way - shun the unbeliever! Shunnnnn! Shun! ;)
[Verizon Samsung Galaxy S III] mastamoon:
Ill do a build with both reverted. 45566 really shouldnt matter as its ifdef'd, but 45565 is doing some other stuff that I think could cause some stuff. Pure speculation on my part but we will see.

Hopefully it will be a good last 10.1 build before 10.2 gets going. Im not going to sync till I know its atleast useable for the most part. I dont have enough room on my SSD to have both projects going.
[Verizon Samsung Galaxy S III] khymbote:
I might be one of the few people in here with out that problem. It doesn't hit me spot on unless Im outside but its with in a couple hundred feet so its good enough. At least it knows what town I'm in.