yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] rutger1413:
something odd i noticed with the processor settings.

When changing the min CPU frequency, it always resets to 918 when you back out of the screen. The Current freq. will drop down to the lower frequency you select though.

Is this just me or is anyone else seeing this. Not really a big deal, but figured I would post it here.
[Verizon Samsung Galaxy S III] Chris123NT:
Pretty sure that has to do with the in kernel mpdecision cherrypick.
[Verizon Samsung Galaxy S III] Crewski:
I had the grey bar/no signal issue on the 9/18 build. I work in a steel mill and my office is in the basement.....which leads to barely getting a 1x signal. I went outside for a bit and I had the grey bars with nothing next to it. Once I toggled data off/on, I had LTE and was connected to google.
[Verizon Samsung Galaxy S III] mastamoon:
How long did you let your phone sit at the grey bars/no icon state before cycling data?
[Verizon Samsung Galaxy S III] Crewski:
It was probably around 7 or 8 minutes that I should have had signal before I looked at my phone....then another 4 before I cycled data.
[Verizon Samsung Galaxy S III] BrianAllred:
So I flashed a nightly and lost my wallet app, then did exactly what I did to get tap and pay and it doesn't work anymore. Man, this thing is finicky.
[Verizon Samsung Galaxy S III] mastamoon:
:mad:

Thanks for the report. I wonder how many or for how long a phone tries to reconnect before it gives up for an extended period of time. Doubt thats the case though.
[Verizon Samsung Galaxy S III] Div033:
Does anyone else get scrolling lag in the Play store? It was smooth in 4.2 but has been laggy in 4.3... I noticed similar issues in other apps as well... Is this a bug or a "feature"?

Edit: try doing a search and then scroll through the results... It's like the days of eclair
[Verizon Samsung Galaxy S III] goldsmitht:
No lag here, except for images catching up. But I'm just attributing that to the signal issue
[Verizon Samsung Galaxy S III] Div033:
Whaaat seriously? What could possibly be different? Are you using a custom kernel?

Edit: okay. Super weird. Some searches it flows smoothly, but on others it's laggy... Try searching "cosmopolitan theme" and you'll see what I mean. Not a huge issue by any means, but an odd one for sure.
[Verizon Samsung Galaxy S III] goldsmitht:
Totally stock CM - mastamoon's unofficial - and in was doing a search on purple themes. Issue could be related to signal strength

:confused:
[Verizon Samsung Galaxy S III] Div033:
Yeah searching purple themes is laggy for me. Other search terms, like "wow" is smoother. Idfk. Lol. I'm probably just bad at androiding.
[Verizon Samsung Galaxy S III] mastamoon:
Google Play store seems fine for me.. only 'lag' I get is from either scrolling to fast and hitting the end of the list for a second and/or waiting for thumbnails to populate. I search purple themes and cosmopolitan themes w/o issue. On Wifi :)
[Verizon Samsung Galaxy S III] Stealth111:
Same thing here, I drove for 10+ minutes in a great signal area with nothing. Airplane mode brought it right back to normal...

Sent using Tapatalk
[Verizon Samsung Galaxy S III] mastamoon:
9/19 build in the OP

-- repo sync at 3:10PM EST

---- Note, I re-enabled LPA aka Low Power Audio. I found that the only real issue is with playing Google Play Music. And I found that close GPM, kill it via the multitask list then open it again, it seems to clear itself up. Trying to erk out some more battery life here.
[Verizon Samsung Galaxy S III] defTwitch:
greatly appreciate your erking
[Verizon Samsung Galaxy S III] Chris123NT:
FYI the LPA things seems to affect Apollo as well, at least it did for me before I disabled it.
[Verizon Samsung Galaxy S III] mikejr83:
Same here. I made sure to clear my account from the app before flashing. I wonder if we screwed up our secure element.

EDIT:

So I dirty flashed and had this problem. I fixed it by doing this: clear data on the Wallet app, remove Wallet app, reboot, add Wallet app, fix permissions, reboot, now you should get the tap to pay setup.
[Verizon Samsung Galaxy S III] BrianAllred:
I got it back with these steps:

Clear wallet app data.

In Recovery, remove apk from /system/app/

Fix permissions.

Reboot into system.

Reboot into recovery (again).

Put modded .apk into /system/app/ (on this step, I renamed it "Wallet.apk" since that was the original name. Hopefully this helps it survive more dirty flashes.)

Fix permissions.

Reboot into system.

Haven't tested to see if it survives dirty flashes yet, but I got tap and pay back, build.prop still unmodified.

Edit: Wow, good timing. Haha.
[Verizon Samsung Galaxy S III] goldsmitht:
Not sure if this is hardware or software, but my battery seems to take a very loooong time to charge. Sometimes it seems that if I am charging and non the phone at the same time, it is still losing power.

Hardware, software, or new battery?

:confused:
[Verizon Samsung Galaxy S III] Stealth111:
Flashed your new nightly, still having same data issues. I literally flashed, let it get up and running, and as soon as I drove down the driveway and left my Network Extender, it went right to full bars, no LTE indicator, and no data. Says LTE under settings, but says disconnected for data. Have plenty of screenshots showing it as well. Would no go back to connected until I airplaned it. :(

Chris123NT, are you still having this issue as well?

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Chris123NT:
I actually didn't have the issue on masta's 9/17 build, didn't try his 9/18. I just ran a build for myself, wondering if this one will have the problem or not.
[Verizon Samsung Galaxy S III] senorbuck:
I've noticed that too. Not sure if it's all in my head or what. I've tried different USB cables and adapters and still the same thing. Figured I'd let it charge/die a few times before throwing it out the window :cyclops:
[Verizon Samsung Galaxy S III] goldsmitht:
I have 2, so I'm gonna have to test them. Seems that when I let it get down below 30%, it takes hours, and sometimes 6-7 to completely recharge. May be time to get new ones

:confused:
[Verizon Samsung Galaxy S III] mastamoon:
Ive never had a problem charging accept on USB connected to my PC which is a non-issue issue. Only other time charging sucks is with screen on and using GPS in my car. Even with a 2.1 amp charger, it barely charges at all, but with a weaker charger it actually looses charge while charging.
[Verizon Samsung Galaxy S III] Chris123NT:
Data issue is back on my build from last night, not sure what's up with that unless the fact I had no issues yesterday was a total fluke
[Verizon Samsung Galaxy S III] airmaxx23:
Focal is being removed from CM.

Focal Camera App Removed From CyanogenMod As Its Developer Xplodwild Leaves The Team - First Fallout From Incorporating
[Verizon Samsung Galaxy S III] SymbioticGenius:
This question might sound silly, but I cannot remember the last time I clean flashed anything, and my recent voyages back and forth between cleanrom (considering giving my phone to mom and getting Droid MAXX) has left my phone kinda buggy (Random Resets, Bluetooth wont cut off, I fixed GPS though!)

My question is: What is safe to restore after a full wipe? I'll probably be clean flashing Masta's 9-20 around 3:30 when he posts it.
[Verizon Samsung Galaxy S III] Reborn627:
I've run into an issue with data lock if the phone sits unused for a period of time. I'm guessing this may be a battery save feature, whoohoo, however it doesn't always immediately reconnect. I've noticed it with the 9/18 and 9/19 builds. I am currently running a stock mastamoon build. Just my observation.

Peace,

Ray
[Verizon Samsung Galaxy S III] BrianAllred:
Focal dev speaks. Wow... Talk about a clusterf...
[Verizon Samsung Galaxy S III] mastamoon:
From a stock based rom? App Data "might" be ok, and I would limit that to apps that are a PITA to reconfigure.. if its just to save you from having to type your username/password, I wouldn't bother restoring that. Don't restore any system data.
[Verizon Samsung Galaxy S III] SymbioticGenius:
I wasn't clear at all, my apologies. I have a few Nandroids of CleanRom and Your builds, within the past week or so. Ive been restoring back and forth between the two. Im currently on a restore of your build. I was having random resets, and still have the bluetooth wont turn off issue, which never went away. I then flashed "Dirty" your 9-19 build over it, and I didn't get any reboots yesterday afterwards, but I have had a few today. Probably due to me Nandroiding back and forth. Im on your build, and want to clean flash your next build to see what the hype is about and if it actually might fix something. The last time I clean flashed anything was my Droid X2 on CM7 (nowCM10!). Heck, I even restored some apps and Data to this phone from the X2. Please confirm my best course of action.
[Verizon Samsung Galaxy S III] mastamoon:
Nandroiding shouldn't leave any remnants going back and forth I wouldn't think. To get the best experience I would make sure I have CWM recovery installed then do a factory reset (cache/dalvik/system/data wipe) then install fresh. If you are having reboot issues, I wouldn't restore a thing until you see if they have followed onto the the new install. Restoring stuff then complaining about reboots and other issues is bad juju. You wont get much help.
[Verizon Samsung Galaxy S III] SymbioticGenius:
Nope, I try not to complain, only ask for advice, and on the few occasions where I qualify, I'll even offer advice. My friends have been saying this would catch up with me eventually, Even when going from CM9-10 I dirty flashed, never had a problem. Now I can't get my phone to stay on for more than 20 minutes. If the Nandroid didn't do it, could it be a rogue app causing it and how would I find out?
[Verizon Samsung Galaxy S III] mastamoon:
Fresh install with no restore would be what I would do. Download the 'must have' apps and configure them manually and run for a bit. If you still get reboots its either one of your must have apps or maybe a hardware issue?
[Verizon Samsung Galaxy S III] khymbote:
I see some bad JUJU coming for us. They want to sell cm to an oem. They said the base ROM should stay open but I'm not sure how if they want to sell it for use.
[Verizon Samsung Galaxy S III] zachf714:
I just had this problem ... Did you fix it?
[Verizon Samsung Galaxy S III] mastamoon:
Ive seen that once.. a reboot fixed it.
[Verizon Samsung Galaxy S III] sivarticus85:
Man... This reminds me of the fallout with that "kernel".

Anyway, I've also seen the phone number issue. As masta pointed out, reboot fixed it for me as well.
[Verizon Samsung Galaxy S III] zachf714:
I rebooted a bunch and that didnt fix it. I just pm'ed the guy that made the stickies thread so he can get me into the extended roaming fix thread
[Verizon Samsung Galaxy S III] Restola:
It's amusing to realize that a CyanogenMod phone will need (the free) CM flashed on it, since there are restrictions to get google certified that require removing features many people may find useful.

This (partial) comment kind of wraps up my feelings on the whole subject:

I dont know anything about open source, but I wonder if there is anything stopping someone from legally opening "DarkblueogenMod Inc" and selling the same source code to different vendors.
[Verizon Samsung Galaxy S III] wolficus:
yup i have actually had that problem. granted i did it to myself on accident.

go into settings > more > mobile network settings > cdma subscription.

check that you are using ruim/sim and not nv.
[Verizon Samsung Galaxy S III] zachf714:
I even went back to a touchwiz based rom and still have the problem :(
[Verizon Samsung Galaxy S III] Rixanu:
I have a quick question about switching roms. I was gonna try out a few other roms today in light of the recent shenanigans with CM, but I noticed a bullet point in the OP about how TWRP isn't wiping data properly. Is that an issue for just this one rom? Also, how should I go about switching roms now? Should I just flash CWM and backup/wipe/flash new rom from there? Thanks.
[Verizon Samsung Galaxy S III] wolficus:
Ouch... And you are set to ruin/sim right?

If so... I wonder if something happened to your sim card...
[Verizon Samsung Galaxy S III] zachf714:
I might try to do an nvrestore
[Verizon Samsung Galaxy S III] BrianAllred:
I had no problem clean wiping and installing CarbonRom with TWRP.
[Verizon Samsung Galaxy S III] mastamoon:
There have been a few cases of a twrp data wipe causing a corrupted data partition needing a full odin to fix. Best bet is to not risk it, flash the latest CWM recovery, do what you need to do, then put TWRP back on when you are ready.
[Verizon Samsung Galaxy S III] minnysota:
+1 for me. Anyone know why this is happening? :eek:
[Verizon Samsung Galaxy S III] mastamoon:
Mine is almost instantaneous. :confused:

Is it like this from a reboot or after its been on for a bit?
[Verizon Samsung Galaxy S III] minnysota:
Just clean installed yesterday. Stock kernel.

Definitely seems faster after a reboot, but I rebooted earlier today, and it was super slow to wake up until I just rebooted now.

Hrmmm...
[Verizon Samsung Galaxy S III] zcmack:
i'm also on 9/10 and just started seeing this two days ago. it is not incredibly slow but it is definitely noticeable. even after a reboot. i'm trying to think of the apps i've installed/updated since then. do you have the new google wallet installed?
[Verizon Samsung Galaxy S III] minnysota:
No I don't have the new GWallet. I find it hard to believe it would be an app issue.

Correct me if I'm wrong?
[Verizon Samsung Galaxy S III] ace000724:
Thank you so much, I wasn't able to call for a couple days:)
[Verizon Samsung Galaxy S III] mastamoon:
9/20 build in the op

-- 4 new cherry picks --- last 4 in the list in the OP

-- repo sync at 2PM EST
[Verizon Samsung Galaxy S III] wolficus:
Hehe actually I just subscribed to this thread today :p

So that fixed the issue for you?
[Verizon Samsung Galaxy S III] ace000724:
It did, not sure why it was set to NV but switching it and rebooted fixed it.
[Verizon Samsung Galaxy S III] WhammyDroid:
I really hope the audioflinger fixes address the overamplification issue I reported. Will report back tonight.
[Verizon Samsung Galaxy S III] wolficus:
Sweet :)

Glad my derpy push this and see what happens knowledge came in handy :)
[Verizon Samsung Galaxy S III] zachf714:
Im so happy I backed up my IMEI to NV because apparently it was my IMEI showing but it was really F*CKED UP !!! so I did an nvrestore and was all good.. I guess I am going to stay away from aosp for a while lol
[Verizon Samsung Galaxy S III] Rixanu:
Alright, I'll probably do that once I figure out why I can't seem to flash CWM. :/ Thanks.
[Verizon Samsung Galaxy S III] mikejr83:
Sucks about your situation but it's good to hear that nvrestore works as advertised. I'm on my second SGS3 and I've always had that thought in the back of my mind about the IMEI getting screwed up. Thanks for reporting that the nvbackup/nvresotre works correctly. First time I've seen a first hand account of that.
[Verizon Samsung Galaxy S III] zachf714:
I was seriously like "HOLY FK" then nvrestore fixed it then i was like "thank god"
[Verizon Samsung Galaxy S III] WhammyDroid:
On a sad note, it did not :(
[Verizon Samsung Galaxy S III] jalewis:
I jumped from 9-9 to 9-17, 18 and then 19. I use slacker radio daily and on each of those three builds slacker would only work intermittently. Sometimes it worked correctly, but most of the time it would load one song, play it, and then not load or play the next. In all cases I had a couple bars of LTE, they were blue, but no arrows, like it wasn't being called for. When trying to skip, or pause and then play again slacker became unresponsive and I ended up rebooting pretty much every time hoping it would resolve the issue, but in most cases it wouldn't. I tried killing the app and restarting it, opening the browser to force data to start, toggling airplane mode, all without success. I flashed back to 9-9 this morning and haven't had a problem since.

Has anyone else seen any weird issues like that?
[Verizon Samsung Galaxy S III] mastamoon:
Sounds like the LPA bug. I was able to use Pandora, Google music and sirius without much issue. I did have to kill google music once to get it to work but the other apps worked fine.

To fix, edit your build.prop.. Change lpa.decode=true to lpa.decode=false and reboot. This will stick till you flash again.
[Verizon Samsung Galaxy S III] Stealth111:
Masta, I just installed your last build, hoping those couple cherrypicks might help with the no data issue. I have NOT left the house to check yet, but I can report this: I have absolutely NO data now when sitting at home right next to my network extender. I have full 5 bars, perfect db/asu, shows "Connected" on data side, but it will not get an IP address now. Under IP Address it says "Unavailable". I airplaned, rebooted, no luck, just not getting an IP address. I will check when I leave tomorrow, and get out of extender range to see what happens...
[Verizon Samsung Galaxy S III] mastamoon:
Jeez :mad:

Have you rebooted the extender?
[Verizon Samsung Galaxy S III] BrianAllred:
Update for the people that care about tap and pay with Wallet: if you renamed it Wallet.apk in /system/app/ when you installed it, it should survive dirty flashes. Mine retained tap and pay and everything.
[Verizon Samsung Galaxy S III] goldsmitht:
Wasn't there something about extenders working only on 2.5 or 5 GHz (Mhz ?) settings and not auto? Or am i confusing with something else?

:confused:
[Verizon Samsung Galaxy S III] Stealth111:
I think you are thinking wireless. :)

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Stealth111:
Meh. Woke up this morning and I had an IP. Just took a while I guess...

Sent using Tapatalk
[Verizon Samsung Galaxy S III] mastamoon:
Well that's good u suppose. How about when you left the house. That's usually the problem right?
[Verizon Samsung Galaxy S III] mikejr83:
Anyone having problems turning wifi on after you've toggled it off? Mine doesn't come back on. Also, Bluetooth won't turn off after turning it on.

I'm on 9/19. Been dirty flashing since 10.2 unofficials started. Maybe I need a clean start...
[Verizon Samsung Galaxy S III] MG386:
On masta 9/20 and no problems with WiFi/BT/signal so far. I've used all of the above, toggled off and on, and left WiFi/BT area and returned and everything reconnects works as it should for me.
[Verizon Samsung Galaxy S III] senorbuck:
Lost data just a bit ago. Had to toggle data. Had colored/grey bars, just no data icon. No big deal though :)

I'm in a decent coverage area...
[Verizon Samsung Galaxy S III] sivarticus85:
I'm getting a gallery fc when I try to use the "sharpness" feature in image enhancement.
[Verizon Samsung Galaxy S III] posaune76:
Try disabling Android Device Manager. Got rid of my wakelock issues on another ROM.
[Verizon Samsung Galaxy S III] goldsmitht:
try clearing data gallery and rebooting; will sometimes clear up issues. I'm having no issues using the image enhancement, and really like that feature
[Verizon Samsung Galaxy S III] mastamoon:
Weird.

I was just off roading in the middle of nowhere.. Had little to no service most of the time, signal with no data type.. The second I got to the road.. Signal came right up, connected just fine.. 1x/3g/lte all over the place.
[Verizon Samsung Galaxy S III] khymbote:
Had a moment there the data handoff from phone to wireless. Had to toggle wireless on and off to get back on the wireless in the house.
[Verizon Samsung Galaxy S III] mikejr83:
Having this same issue. Have not tried the suggestion on clearing data and rebooting though.

EDIT

Tried force stopping, clearing data, and rebooting. Issue remains :(
[Verizon Samsung Galaxy S III] sivarticus85:
All other enhancements have worked fine, it's just sharpness that fails. Clearing data didn't help... It's not a big deal. I was mainly posting here to get it attention.
[Verizon Samsung Galaxy S III] Restola:
That setting fc's for me too (on the official here).
[Verizon Samsung Galaxy S III] goldsmitht:
OK, damn, does it to me too... Thought I had it working, sorry

:banghead:
[Verizon Samsung Galaxy S III] sbenson1226:
Did you rename it after you installed it?
[Verizon Samsung Galaxy S III] BrianAllred:
No, it was before.
[Verizon Samsung Galaxy S III] dmeadows013:
Masta have you thought about adding the Active Display feature found in ChameleonOS? It's open source: http://rootzwiki.com/topic/102761-featurerom43-active-display/
[Verizon Samsung Galaxy S III] Stealth111:
That is a sweet feature. Loks like what is on my Droid Ultra. Would love to see it over here on my S3!!
[Verizon Samsung Galaxy S III] BrianAllred:
Carbon ROM has this, and I'm a little disappointed with it, honestly. It keeps the proximity sensor on indefinitely, even if the feature is turned off. Pretty noticeable battery drain. :/
[Verizon Samsung Galaxy S III] billquinn1:
I have a question about the CPU speed. I am using the latest dkp kernel and latest nightly and I like to run at 1620 or 1674. The setting does not stick. It lasts until the phones wakes from sleep. Not reboot but just sleep. Is this a feature or just a quirk?

Not a huge issue obviously but some apps scroll way smoother with just a touch of extra clock.

Thanks
[Verizon Samsung Galaxy S III] Chris123NT:
I'm seeing the same, IP unknown when in range of the network extender.
[Verizon Samsung Galaxy S III] Chris123NT:
Was flashing some builds back and forth to fix the extender data, tried some telephony reverts and that didn't fix it so I flashed back to the original build and now extender data is working, *shrug*

I'll see how the handoff to LTE fares in the morning.
[Verizon Samsung Galaxy S III] wolficus:
Has anyone else had issues with wireless data speeds? I think a few updates ago... Mine went down the tubes.

I am hoping there is a setting somewhere that I am just missing.

My speeds are 1.2mb down .. And 2.5 up.

I use this to help back up my SD card to my home server... So I dont have to hook it up to a computer via a USB cable.
[Verizon Samsung Galaxy S III] goldsmitht:
On 9/20, and had serious data drops yesterday. Was in a bar that I normally don't have good service. And, since it was crowded with football fans, a lot were on their phones. Would a saturation of the net cause data drops as well? Too many trying to access limited bandwidth. Good part, when I'd go into a different part of the bar, my service would return.

And, with the constant data drops, battery got killed as well.

Otherwise, its running great, and can't even convince myself to try a TW ROM!

:D
[Verizon Samsung Galaxy S III] Chris123NT:
Drove to work this morning and had data when I got to work, so masta's cherrypicks to address the issue definitely seem to be working.
[Verizon Samsung Galaxy S III] wolficus:
Fixed the issue.. Was a pain to figure out but I now have 1.5MB transfer to my server instead of 127k. Also I have full 30mb service from my internet....

Had to turn off wireless optimization and reboot the router :/
[Verizon Samsung Galaxy S III] mastamoon:
9/23 build in the OP

-- the OABI commit got merged.. removed cherrypick

-- repo sync at 3PM EST
[Verizon Samsung Galaxy S III] goldsmitht:
you still using stock kernel, or something 3rd party? Been sticking with stock, but have seen a little downward trend in the battery life.

still think signal issues over weekend was due to over-saturation of the net usage, as well as an area that really has bad signal strength anyway. have had fairly good service all day, and never have a problem re-gaining signal when i ride the subway. no service in the tubes, but service when i reach each of the station stops.

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Stock kernel. Good to hear about your signal stuff though. Ive had moments of 'wtf' also, but try to let it just do its thing so I can see if it comes back and it always does. There were some reconnect dead connection merges done over the weekend.. maybe that plus my fix will make things even better. Probably not but we can hope...

:)