yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
Does that theme change the no google/data services color also, or is it still grey on boot and turns purple when connected?

Also, due to my Signal Bar tweaks.. there may be times when you look like you have a better connection than you really do. It has to do with Signal Strength (dbm) vs Signal Quality (SNR).... Basically I change it to display Signal Strength and lower the 'bad/no signal' threshold to show bars more often. So, even though its really odd, you could have FULL signal strength but have a bad connection due to poor SNR.

But I would think you wouldnt show 'No Connection' it would just be slow/droppy..
[Verizon Samsung Galaxy S III] goldsmitht:
Yeh, it will grey out when signal strength goes down. And def not just "droopy" but down right non existent

:what:
[Verizon Samsung Galaxy S III] mastamoon:
Have you had this issue w/o that theme applied? I know long shot, but stuff like this does happen when a theme isnt kept up to date. Replaces files it shouldnt and causes breakage.
[Verizon Samsung Galaxy S III] goldsmitht:
Good idea, but no, this is second theme, and by different dev, so probably not the case.
[Verizon Samsung Galaxy S III] mastamoon:
Have you tried theme-less?
[Verizon Samsung Galaxy S III] WhammyDroid:
I am not looking for another app. DSPManager was working fine (outside of the issue I reported a long time ago, JIRA #1355). My guess is that one of the new cherrypicks is causing the issue.
[Verizon Samsung Galaxy S III] goldsmitht:
Will give a try next time I get same reading. Bit doesn't happen all the time, so not able to recreate it
[Verizon Samsung Galaxy S III] Chris123NT:
Actually it probably has nothing to do with the new cherry picks, there was a bunch of DSPmanager stuff merged in the past couple of days so one of those is likely causing the issue for you
[Verizon Samsung Galaxy S III] mastamoon:
The only thing I could possibly see being the issue is my dock cherrypicks... I doubt it but since its audio related its possible I suppose.

[MENTION=2682197]WhammyDroid[/MENTION] - try official and report back. Only way to know for sure.
[Verizon Samsung Galaxy S III] WhammyDroid:
Sure. I'll try to get to this sometime tonight.
[Verizon Samsung Galaxy S III] mastamoon:
9/13 build in the OP

-- no new cherry-picks

-- reverted some of the RIL back to just after 4.3 dropped to see if we still get the weird no data bug, had to add 2 cherrypicks to compile due to dependencies elsewhere in the ROM.

-- repo sync at 3PM EST

Happy Friday the 13th Everybody! :eek:
[Verizon Samsung Galaxy S III] mastamoon:
Ril Reverts didn't fix the dropout. Meh.
[Verizon Samsung Galaxy S III] zachf714:
Are you just reverting ril or all frameworks_opt_telephony commits ?
[Verizon Samsung Galaxy S III] mastamoon:
Everything back to July 31st I think it is. Must be in frameworks/base or something.
[Verizon Samsung Galaxy S III] Zacharybinx34:
9-12 build has my battery life back to being awful again.

Cleared data for Google service framework it whatever it's called too, no help.
[Verizon Samsung Galaxy S III] Chris123NT:
Got any wakelocks?
[Verizon Samsung Galaxy S III] dnsmo:
will this work on t-mobile network?
[Verizon Samsung Galaxy S III] Wh1t3Rose:
This the VZW thread. Go to the forum for your version of the S3
[Verizon Samsung Galaxy S III] Zacharybinx34:
Seems to be deep sleeping.
[Verizon Samsung Galaxy S III] khymbote:
Having very delayed wake up when I click the power button. Going back to the 10th build.
[Verizon Samsung Galaxy S III] zachf714:
Maybe, or the changes in 4.3 for frameworks_opt_telephony
[Verizon Samsung Galaxy S III] mastamoon:
Yeah that's very likely also, but rolling back to 4.2 causes other build issues from what I saw.

I also don't think the cm guys would want to hear it.
[Verizon Samsung Galaxy S III] zachf714:
Yup I will continue to look into it
[Verizon Samsung Galaxy S III] BrianAllred:
Off topic, but I'm bored this weekend and would like to try some different ROMs. Do I have to clean flash different AOSP ROMs, or is dirty okay?
[Verizon Samsung Galaxy S III] Restola:
I would clean flash them. Too many differences between aosp roms I think.

But make a backup and try it, what's the worst that could happen.
[Verizon Samsung Galaxy S III] iofthestorm:
Yeah, you might as well try it, worst case you need to factory reset after you reboot. Anecdotally I once accidentally flashed CM10 on top of AOKP ICS on my Galaxy Tab 10.1, that's two different ROMs based on two different versions of Android and I had no problems. Clean flashing is overrated :P
[Verizon Samsung Galaxy S III] riphamilton:
i'm on 9/12 - GPS issue was completely resolved by toggling GPS on/off.

now, my only issue is the wakelock caused by google services (see attachment).

i've noticed that when i wake my screen, about half of the time the GPS icon is on - i'm not sure what needs my location. i have wi-fi location on and am connected to a wi-fi network; if google now or another service needs my location i would think it would just geolocate via IP address. if anyone has any ideas i'll be happy to give anything a shot.
[Verizon Samsung Galaxy S III] goldsmitht:
Check Google settings all, locations, and make sure location reporting is off and location saving (think that's it, only two) is off as well. Can allow apps to use locational data, but turn other two off.
[Verizon Samsung Galaxy S III] mastamoon:
9/16 build in the OP

-- my power_profile.xml cherrypick got merged.. removed from CP list

-- the revert was needed for the build to uh.. build... id guess it will be fixed soon enough officially

-- repo sync 3:30PM EST
[Verizon Samsung Galaxy S III] senorbuck:
Had a couple YouTube freezes and subsequent reboots on the latest build. That to be expected?
[Verizon Samsung Galaxy S III] riphamilton:
negative. wakelock issue still exists; i still catch the phone trying to get GPS location when i power on the screen. to be honest, i'm kind of relieved location history isn't the issue because i actually use it (as creepy as it is!).
[Verizon Samsung Galaxy S III] dpaine88:
YouTube issues here too, videos won't play
[Verizon Samsung Galaxy S III] PerCompLLC:
Dirty flash of 09/16 Unofficial from 09/13. No wakelocks, YouTube videos play fine, GPS works flawlessly, everything running smooth! :D:D
[Verizon Samsung Galaxy S III] mastamoon:
Try this..

1. Watch a video in gallery you recorded.. it will most likely not play and reboot your phone. if not the first time you try, just keep trying till this happens.

2. On reboot, try to watch that video again.. It should play.

3. Now try YouTube.

This is caused by the kernel tweak needed to have instagram video work. Nard says he is going to try and fix IOMMU for us so maybe this issue will go away soon, but this workaround makes everybody almost happy :)
[Verizon Samsung Galaxy S III] mastamoon:
Did anybody notice data not failing on last nights build? I know not everybody bumps into the data issue (where you have signal, but have no LTE/3G/1X icon and the bars are grey). I usually have the issue on my way home from work but last night was fine for me.
[Verizon Samsung Galaxy S III] khymbote:
I had no issue yesterday. I started the download while in the building and watched it while I walked downstairs and even though it went from LTE to 3g it never skipped a beat.
[Verizon Samsung Galaxy S III] mastamoon:
Do you usually have an issue using the same route?
[Verizon Samsung Galaxy S III] khymbote:
I have had issues with data when in LTE and dropping to 3g and then back.
[Verizon Samsung Galaxy S III] goldsmitht:
Can also report that I installed 9/16 and no issues; videos played fine as well as YouTube

:D
[Verizon Samsung Galaxy S III] sivarticus85:
9/16 has been running solid for me since last night. My LTE to 3G and back has been toggling quickly, and I haven't noticed a loss in data.
[Verizon Samsung Galaxy S III] mastamoon:
9/17 build in the OP

-- new cherry-pick added for testing (requested by invisiblek) AIO: Don't plug the I/O queue in do_io_submit() - http://review.cyanogenmod.org/#/c/50536/

-- repo sync 3PM EST
[Verizon Samsung Galaxy S III] sbenson1226:
Did today's update kill WiFi for anyone else?
[Verizon Samsung Galaxy S III] mastamoon:
Not here, just switched to wifi to post this. What about wifi doesn't work for you?
[Verizon Samsung Galaxy S III] goldsmitht:
WiFi fine here
[Verizon Samsung Galaxy S III] necropuppy:
Anyone having random reboots on the latest build? Can't post lastkmsg ATM.busy at work.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Yes
[Verizon Samsung Galaxy S III] mastamoon:
Not yet. :confused:
[Verizon Samsung Galaxy S III] Chris123NT:
Nope, were you doing anything when it rebooted?
[Verizon Samsung Galaxy S III] Zacharybinx34:
Sometimes nothing
[Verizon Samsung Galaxy S III] damnyouwaffles:
Camera has a massive difference in quality than CM10.1. Could never get this quality with the old camera it seems.
[Verizon Samsung Galaxy S III] M Diddy:
Any word on the Android System battery drain? Mine's pretty bad. Down to 32% after 6 1/2 hours with minimal phone and screen time.

I've turned off the Wifi Always Scanning and it's still eating a ton of juice on my phone.

*Edit* Have had two reboots as well. The last one I was simply backing out of a text message and the phone bounced on me.
[Verizon Samsung Galaxy S III] lakingslayer:
I see that too. Finally I can use this camera. It's one of the reasons I kept going back to TW was the 10.1 camera. One question. Is there a way to save the images to my ext-SD card like in the 10.1 camera?

Thanks for the work on this ROM! :good:
[Verizon Samsung Galaxy S III] DiGi91:
17% battery after about 5 hours with light use; no idea what's going on. Clean flash restored apps with TiBu no data though. Turned off WiFi always scanning too.. Also BT was acting wonky in my car with the flexsmart. Androidsystem at about 44% which is insane! Phone is running very hot (In an UAG case I can feel the heat through it! Eek!)

Overall ROM is slick as hell no random reboots or anything like that but man that is terrible battery life.
[Verizon Samsung Galaxy S III] Chris123NT:
Guys with battery issues please install betterbattery stats and post a log after some usage. I want to see if you guys are getting any weird wakelocks or anything.

Also grap CPU Spy and see what times in various clock speeds are.
[Verizon Samsung Galaxy S III] damnyouwaffles:
To add onto battery, I went from 16% to zero and my phone died to a black screen without warning. Made me think it bricked itself somehow. Charging at zero now and its going pretty slow. It seems like it thinks its USB charging.
[Verizon Samsung Galaxy S III] DiGi91:
Charging mine from 4% and it's charging very very slow right now (Charging with OEM samsung cable & wall adapter)
[Verizon Samsung Galaxy S III] damnyouwaffles:
Well I just checked and its not on USB charge. Android System is at 41% usage for me. Charging speed seems to be picking up.
[Verizon Samsung Galaxy S III] DiGi91:
Currently at 18% battery with Android System at 37% Phone is still running really hot though.

EDIT: And Google Services at 29% trailing behind it.
[Verizon Samsung Galaxy S III] damnyouwaffles:
Try doing a fresh install. Format data too. I don't have overheating problems right now and Google services is at 2%. Formating data and fresh installs fixed my data problem, maybe it could fix yours.
[Verizon Samsung Galaxy S III] Mystikalrush:
Does root work on 8/02 build? I couldnt get my apps to access it.
[Verizon Samsung Galaxy S III] DiGi91:
I came from a complete format.. I could try another or just restore my Nandroid of M.O.A.R for now... Well once it's charged enough.
[Verizon Samsung Galaxy S III] damnyouwaffles:
Yes you have to go to developer settings and change root access to apps and adb.

---------- Post added at 05:18 PM ---------- Previous post was at 05:16 PM ----------

Yeah if the battery is still bad after a full charge, I'm going to revert to 10.1 because I need battery life for my job.
[Verizon Samsung Galaxy S III] DiGi91:
I hear you man I have tried a countless number of AOSP ROMs and I always seem to come back to TW sadly... were you running CM 10.1 stable or what? How was it?

I know it's a lot to ask for but pretty much looking for everything to more or less work (especially BT) Might just go back to TW =/
[Verizon Samsung Galaxy S III] damnyouwaffles:
I was running Masta's CM10.1 7/19 build. It is stable and I have no problems with it. Was my daily driver and might still be.

Edit: And yeah, I hate going to touchwiz. Its so slow and just doesnt feel as fluid as AOSP. But Mastas Cm10.1 7/19 works great and I think BT works fine.
[Verizon Samsung Galaxy S III] sbenson1226:
Wi-Fi is on but zero networks are coming up. Should have auto connected when I got home but didn't. Nexus 7 is connected just fine. I'll do a bit more digging to see if I can figure this out. Let me know if you guys have any suggestions. Thanks.
[Verizon Samsung Galaxy S III] khymbote:
WiFi is just fine.
[Verizon Samsung Galaxy S III] senorbuck:
Latest is running like a champ!
[Verizon Samsung Galaxy S III] jalewis:
For me too. Just turned it on and it autoconnected to my house wifi pretty quickly.
[Verizon Samsung Galaxy S III] soohyunk83:
signal strength vs official

Have any of you guys tried the official build to see if there's any difference in signal vs the unofficial build?
[Verizon Samsung Galaxy S III] Mixinitup4Christ:
Sounds like 9/16 is working really well, I'm on Chris' 9/7 build and ready to update. This is my daily driver, think I should flash 9/16 or 9/17?
[Verizon Samsung Galaxy S III] sivarticus85:
For me, it feels like 9/17 runs a bit snappier, but that could just be me. Everything I've tried has worked, including WiFi, data handoffs, and games.
[Verizon Samsung Galaxy S III] stang68x:
Is the new Google Wallet working for you guys? I don't see an option to use the NFC on my device to make a transaction.
[Verizon Samsung Galaxy S III] Div033:
So is 9/17 the new 7/19 in terms of stability? Would be fitting.
[Verizon Samsung Galaxy S III] iofthestorm:
I think the NFC part is still blocked for stupid political reasons. Since before people could use Wallet NFC payments using build.prop hacks, they must be actively disabling it on Verizon devices rather than simply testing for NFC.
[Verizon Samsung Galaxy S III] goldsmitht:
Menu >system settings >more and you can turn it on there. I don't use wallet, but think I've seen someone on here say its worked for them.
[Verizon Samsung Galaxy S III] stang68x:
Actually, this is different. People with Verizon phones have been able to use this new Google Wallet app. I think it's more of an issue with my actual NFC as I've had trouble transferring stuff via NFC, as well. Anyone using this ROM able to get the new Google Wallet to allow transfers?
[Verizon Samsung Galaxy S III] lakingslayer:
Deleted
[Verizon Samsung Galaxy S III] sbenson1226:
I got tap to pay to register by editing my build.prop to yakju and then setting up Google Wallet. Before doing this I did not have the option to make payments via NFC. In theory it should be working now, but I haven't had a chance to actually test it. Hopefully today...
[Verizon Samsung Galaxy S III] BrianAllred:
Can you send MMS? I edited my build.prop to d2spr to get tap to pay, but now I'm having some MMS issues.
[Verizon Samsung Galaxy S III] rmg88888888:
disregard
[Verizon Samsung Galaxy S III] sbenson1226:
Yes I can, but I reverted mine back to d2vzw. Did you confirm that tap to pay actually works? I'm hearing that even though it shows in the settings, once you actually try to use it at the store in hangs when trying to process the transaction. Sounds like the NFC is communicating correctly, but Wallet does some internal checks before actually transmitting the transaction. If your device doesn't pass the check, the transaction fails.

Keep an eye on this thread: http://xdaforums.com/showthread.php?t=1769083&page=328

They're busy attempting to modify the original apk to ignore these device checks.
[Verizon Samsung Galaxy S III] BrianAllred:
Unfortunately, not a lot of places to easily test where I'm at. I'll probably just revert to d2vzw and watch that thread for developments. Thanks.
[Verizon Samsung Galaxy S III] sbenson1226:
Same here. Cross your fingers.
[Verizon Samsung Galaxy S III] don_xvi:
No NFC for d2vzw

Just for confimation, here's the list of NFC-supported devices from Wallet support at https://support.google.com/wallet/a...email&utm_campaign=walletapp&utm_term=sep2013
[Verizon Samsung Galaxy S III] BrianAllred:
Just more reason to get a Nexus 5 or GS5GE when my contract's up next year. Hate this political bull**** VZW/AT&T/T-MOB are pulling.
[Verizon Samsung Galaxy S III] NedDasty:
New modded Google Wallet

There's apparently a new modded .apk for the Google Wallet that allows installation and setup on the VZW. You can see the post here: http://xdaforums.com/showpost.php?p=45699789&postcount=3244

We won't need to flash the NFC fix, since that's for TW-based ROMs, so all you really need is to push the following .apk to /system/app: http://xdaforums.com/attachment.php?attachmentid=2265777&d=1379501149

I haven't tested out any payments yet, but I have successfully set up this modded Google Wallet. I may run to CVS later to test it out and I'll report back to you all, since I heard rumors that payments don't work.
[Verizon Samsung Galaxy S III] BrianAllred:
I seem to be unable to get this installed correctly. I'm pushing it to /system/app, fixing permissions, and rebooting. Upon starting Wallet, it says my device or carrier isn't supported.
[Verizon Samsung Galaxy S III] khymbote:
Off topic but Kondik and Koushik did and ama on reddit about cyanogen getting funded and moving to a self installer among other things.
[Verizon Samsung Galaxy S III] WhammyDroid:
I am on Verizon and I downloaded my directly from the app store on my phone.
[Verizon Samsung Galaxy S III] mastamoon:
9/18 build in the OP

-- added cherrypick - d2 et al.: disable OABI compat - http://review.cyanogenmod.org/#/c/50398/

-- removed the AIO cherrypick - got merged

-- repo sync @ 3PM EST
[Verizon Samsung Galaxy S III] don_xvi:
What we're all trying to work around is that the one you can download directly doesn't support NFC payments on Verizon's GS3.
[Verizon Samsung Galaxy S III] rmg88888888:
You won't be able to pay for things in stores with your NFC chip, though.
[Verizon Samsung Galaxy S III] NedDasty:
Hi Brian--make sure you uninstall any previous versions of Google Wallet. If that's not working, then I'm not sure what the problem could be, since I'm assuming everyone in this thread is on Verizon. Are you absolutely sure you're pushing the .apk you just downloaded, and not an older version that you had in the same folder?
[Verizon Samsung Galaxy S III] zachf714:
Yepp Cyanogen Inc
[Verizon Samsung Galaxy S III] sbenson1226:
You don't have tap and pay correct? Anyone can install from the Play Store. The tap and pay is what everyone is trying to get to work.
[Verizon Samsung Galaxy S III] BrianAllred:
Yep, forgot to delete the Wallet.apk first, so I guess it was prioritizing that one over the modded one. Seems to work now; it's setting up tap and pay using the default d2vzw build.prop. I'll see if purchases go through later.
[Verizon Samsung Galaxy S III] sbenson1226:
This new modded file did work for me. When I loaded it up, everything set up correctly...except there was no tap and pay. I had to uninstall and wipe all traces of Wallet, then modify the build.prop to yakju, reboot and then reinstall the modded wallet file. I was able to go through the tap and pay setup this time. Once successful, I reverted my build.prop, rebooted and loaded up wallet and everything seems good. I'll test that it actually works when I leave work in a bit.

---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------

Seriously? You got it working with an unmodified build.prop?
[Verizon Samsung Galaxy S III] BrianAllred:
Yes, sir. Had to totally wipe Wallet data, then boot into recovery and delete the .apk out of /system/app/, then push the modded apk, fix permissions, and reboot. Good to go after that. Chose my Google account, put in my pin, and the first card it greeted me with was the set up tap and play card. Tapped it, agreed to everything, and it started working.
[Verizon Samsung Galaxy S III] sbenson1226:
Okay....breath....trying this again :)
[Verizon Samsung Galaxy S III] BrianAllred:
Good luck. My About page now says device is ready for tap and pay purchases. :D

And if you still have problems, we can move to PM and I can walk you through step by step what I did. I feel like I've cluttered Masta's thread enough, don't want to be a bother. :)
[Verizon Samsung Galaxy S III] sbenson1226:
You got it, thanks man. I'll hit you up if I can't get it this time.

EDIT: Well, got it working. Not entirely sure what I did different this time? Big thanks to [MENTION=5122301]BrianAllred[/MENTION], [MENTION=2916880]NedDasty[/MENTION], [MENTION=3313404]open1your1eyes0[/MENTION] and especially [MENTION=1016795]loserskater[/MENTION].
[Verizon Samsung Galaxy S III] billquinn1:
No link for download showing in the op. I'm on the mobile app. maybe that's the problem.
[Verizon Samsung Galaxy S III] mastamoon:
Odd, works for me using Tapatalk and browser.
[Verizon Samsung Galaxy S III] titanshadow:
Anyone else unable to get a data connection when on 2g (1x)?
[Verizon Samsung Galaxy S III] mastamoon:
Does it show 1x but bars are Grey? I've had that but eventually they turn blue.. I think it just takes a bit for the sign in to Google services to happen on 1x.
[Verizon Samsung Galaxy S III] senorbuck:
I noticed that too. Opened the thread in web view and went that route.
[Verizon Samsung Galaxy S III] billquinn1:
Yep. Figured that out too.
[Verizon Samsung Galaxy S III] sivarticus85:
How cool is it that CM is a legit company now? Bout time! :)
[Verizon Samsung Galaxy S III] titanshadow:
It showed 1x but was grey. I'm going to test your ROM soon because you can go into your mobile settings and tell it to go to 2G and not do LTE or 3G so I'll test it with that again. The areas where I get this problem I'm very seldom in.

... Edit... Checking the 2G box defaults to 3G every time. I don't know what happens if 3G isn't available.
[Verizon Samsung Galaxy S III] zachf714:
Yeah man .. Here is the while group for those who missed it
[Verizon Samsung Galaxy S III] WhammyDroid:
And I am ok with that as NFC is not a secure protocol.
[Verizon Samsung Galaxy S III] Reborn627:
I've actually been using it for the last week or so. I've used it at McDonalds to pay for breakfast and lunch a couple of times. I've also used it at circle k and my local grocery store without any trouble. You do need to either manually edit the build.prop or use the wallet installer.apk to allow for the wallet.apk installation. The reaction from the clerk at McDonalds was priceless! ;)

Peace,

Ray
[Verizon Samsung Galaxy S III] ace000724:
Has anyone ever lost there phone number, I look in settings and my number isn't there. It says 000-000-8626 and the last four digits aren't even my last 4.
[Verizon Samsung Galaxy S III] stang68x:
Yeah, I was hoping this new official release from yesterday would be different. Other stock, unrooted Verizon phones are able to use their NFC. I'm thinking my NFC is borked because of this ROM. Are you guys able to use your NFC for even simple things like Android Beam with this build?
[Verizon Samsung Galaxy S III] goldsmitht:
I've tried a few times, and no go. I think it was because I was on CM and they weren't. It worked on a TW ROM to TW ROM tho.
[Verizon Samsung Galaxy S III] sbenson1226:
Yes, my NFC has always worked on this ROM.
[Verizon Samsung Galaxy S III] BrianAllred:
I use NFC tags every day to toggle BT, wifi, things like that. No problems whatsoever.
[Verizon Samsung Galaxy S III] sivarticus85:
I just had to share this here. Thread hijack over.