yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] antiseen:
I'll try a different gapps.

Yesterday, after a reboot maybe(not sure), it was working fine for a while. Then it started freezing again.

I have like 7 email accounts in the Gmail app. 2 Gmail accounts and 5 imap accounts. Maybe that could be a contributing factor. I'll do another clean flash of the latest nightly and report back later.

UPDATE: it in fact appears to be a rom problem. Occurs on tkapps as well.

Things to note: wasn't happening with just my Google account in there. After adding all my emails to the Gmail app it worked fine for one email then freezes on the next.

This occurs after you enter an email to read and when you press back to go back to your inbox. Freezes at that point then the force close notification pops up 20-30 seconds later.

I've got a lot of emails in my inboxes that it pulls, so this could also be a contributing factor. Well, I mean as opposed to someone with just one Gmail account or even someone with 7 email accounts(like me) but keeps them all empty. Not sure.
[Verizon Samsung Galaxy S III] Master Cylinder:
In Call Quirkiness

[MENTION=3317925]herbby[/MENTION], I have been able to duplicate your problem. After selecting speaker during a call, the output can go back and forth between the handset ear speaker and the back speaker. I expect the microphones are flipping around, too, however they do it. I'm on 10/17. This can be a problem as one frequently needs to access other info on their phone whilst talking. Anyway, it makes it more cumbersome.

I've included a logcat from during the call if [MENTION=2044079]Nardholio[/MENTION] is interested in checking it out. I had to use Catlog because if I hooked up to the PC I couldn't duplicate the problem!
[Verizon Samsung Galaxy S III] herbby:
Thx Master Cylinder. It's awesome how much all you care to respond and try to figure things out in a quick fashion.
[Verizon Samsung Galaxy S III] Deliquified:
TK gapps should be the first ones recommended imo. Frankly, i have no idea why more people aren't using them as they are updated often, quite stable, and rarely give issues.

Edit: Perhaps they aren't used often because they are sorta buried in the thread? Here's a quick link for the nano gapps updated at the beginning of the month.

https://basketbuild.com/devs/TKruzze/5.1.x GApps Packages/MODULAR - Nano GApps
[Verizon Samsung Galaxy S III] Master Cylinder:
Why don't you give the stock email client a try... Or maybe another email client might work better?
[Verizon Samsung Galaxy S III] antiseen:
I will if it comes to that. It just sucks because I really like the Gmail app.
[Verizon Samsung Galaxy S III] Master Cylinder:
Did you manually wipe your /system partition before installing the ROM and GApps?

From the TK GApps thread:

"In order to switch to TK GApps from another GApps provider or remove an Addon Module you're no longer using, you will need to (from Recovery - In the order listed):

Manually wipe (format) your System partition

Flash your ROM

Flash GApps package

Flash any Addon Modules (optional)

Wipe the Dalvik & cache

Reboot"
[Verizon Samsung Galaxy S III] antiseen:
I'm not sure if I wiped dalvik at the end.

I'm using cwm. I usually do wipe data/factory reset, then wipe cache, then wipe dalvik. Do that a couple times then I format /system, wipe cache and dalvik. Then I flash rom and gapps. Then reboot.

The next nightly I'll try wiping dalvik before rebooting at the end.
[Verizon Samsung Galaxy S III] AyUaxe:
Should probably switch to twrp recovery. Not sure that cwm can properly wipe caches etc as configured in 5.1.x.
[Verizon Samsung Galaxy S III] antiseen:
I'll try twrp again. I guess I'm just old school. I really like cwm.
[Verizon Samsung Galaxy S III] AyUaxe:
Same for me until a few months ago. Can't stay with something as essential as recovery, after support stops, esp considering how significant changes were from 4.x-5.x. I think you'll like it once you use it a little.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I was partial to CWM for the longest time too. But there's a LOT of nice features in TWRP. And at this point I *think* people had issues on either CWM or old versions of TWRP, and I'm pretty sure I HAD to make the switch for some reason.
[Verizon Samsung Galaxy S III] antiseen:
Yeah, I stopped flashing when I bought the moto x 2013 in... 2013. I'm using this phone as a stopgap until I get a nexus 5x. Done with Verizon locked and bloated phones.

Anyway, twrp seems to have fixed it. I like cwm but I didn't know its support ended(I just started using this phone again a couple days ago). It doesn't matter that much to me to not use cwm. I was working off of mid 2013 flashing knowledge and even back then twrp was the favorite recovery.

So yeah, clean flashed 10/17 and tk gapps. No longer freezes so far.
[Verizon Samsung Galaxy S III] Master Cylinder:
Can't argue with this . TK is the GApps Master!
[Verizon Samsung Galaxy S III] Jaws4God:
ive noticed this too.. didn't know if it was a glitch or something i wasnt doing correctly..

Sent from my SCH-I535

---------- Post added at 03:45 AM ---------- Previous post was at 03:44 AM ----------

I use BlueMail. free and very powerful. havent seen any issues with any nightly updates.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] pogeymanz:
WiFi dropping during sleep?

Am I the only one here who has had this issue of WiFi turning off after sleeping? To be more specific, I have the policy set to keep WiFi on "Always" when the phone goes to sleep. Yet WiFi is disabled after going to sleep. Sometimes it's immediate and sometimes it takes a little while (I know because if I wake up my phone after a couple of minutes there is a ~10% chance that it's still connected to WiFi). I've been using the app "CatLog" to read my logs and I don't see anything interesting except for this error:

E/WifiStateMachine(1561): WifiStateMachine L2Connected CMD_START_SCAN source -2 3833, 3834->obsolete

Is it saying that the WiFi driver somehow is reporting being in an invalid state?

I have tried pretty much every 12.1 nightly for months and always have the issue. My experience is very similar to this bug report: https://jira.cyanogenmod.org/browse/CYAN-6953

Except that our phones don't have the same config files in /etc/wifi as report there.

Just for good measure, I compared the files in /etc/wifi between version 12.1 and a CM 11 version and they were the same. My WiFi worked fine in CM 11.
[Verizon Samsung Galaxy S III] Master Cylinder:
When you say you compared those cm11 files with the current ones, do you mean there are the same number of files with the same names? Or did you compare the contents of all of the files. If not, you could, as an experiment, create a backup folder in the /etc/wifi location and copy all of the current files into it and push the cm11 ones in there to see what happens. You could also compare those files contents since all but the 1st 4 seem to be plain text files. With the right software you could compare them all at once.

EDIT: ...making sure the files you put in /etc/wifi have the appropriate permissions.

EDIT: You could also do a flash where you wipe /system to make sure you're getting the up-to-date files. (Might need to reinstall GApps?)

EDIT: :eek:[MENTION=5292677]pogeymanz[/MENTION], might be time to do a fresh flash which will include GApps of course, and wiping /system.
[Verizon Samsung Galaxy S III] Jaws4God:
I just went to the 10/21 version.. my battery seems to be

dying SUPER fast

.. and now says it will take 15 hrs to charge.. anyone else experiencing this?
[Verizon Samsung Galaxy S III] Jaws4God:
*** UPDATE *** I just dirty flashed (and wiped cache / dalvik) back to 10/20 version and now it already went from 38% to 40%... says it will only take 5 hrs to be full. so i think it may be related to the 10/21 release.
[Verizon Samsung Galaxy S III] Master Cylinder:
Hey pogeymanz,

You might go snooping around over on the cm12 d2att thread (SCH-i747 I think?) because our device maintainer, aka the guy who could address this, is the OP and he uses a d2att and also others might have had this problem. and it might be the same hardware/drivers ...
[Verizon Samsung Galaxy S III] Jaws4God:
does anyone else have a delay when someone calls for the screen to wake up? I turned off the heads up in case that was causing it to lag but it still seems to do it. Thanks.
[Verizon Samsung Galaxy S III] AyUaxe:
That has been an ongoing issue, but one I thought was resolved. I don't see it on 10/14, where I'm holding for a bit. Are you using a different kernel and what CPU speed, voltage, and governor are you using?
[Verizon Samsung Galaxy S III] mav3rick478:
So I've noticed twice now that I've been having issues with mobile data (10/17), seems to be show up when the phone wakes up from overnight and I leave my house and Wi-Fi. There seems to be an exclamation mark by the signal instead of the LTE letters. Mobile data days it's on but when I open an app like Instagram it won't regret or hangouts won't send a message. This morning when it happened I had to restart my phone a couple times and data started working again. Last time before this I had no mobile data for a couple hours even with restarting my phone multiple times and giggling airplane mode. Anyone else had this happen?
[Verizon Samsung Galaxy S III] XdrummerXboy:
This has been an ongoing issue for me, and I think many others, for months. Sometimes I have success with toggling airplane mode, sometimes I have to reboot. Sometimes it takes a couple reboots.

That's the only real issue I have with this ROM.
[Verizon Samsung Galaxy S III] AyUaxe:
Most convenient fix for mobile data has been go into mobile network settings (long press on pulldown menu icon), access point names, select any other apn, go back to what you were doing and it'll reconnect to lte. No reboot or airplane mode needed. Airplane mode helps with a recurrent similar WiFi issue. YMMV. Happy d2 farfehrgenugen.
[Verizon Samsung Galaxy S III] Master Cylinder:
Yep, except for downgrading the modem, which seems to be the most reliable fix at the moment.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Which version are you on MasterCylinder? I think/thought I was on MF1, but I still have issues. Are you saying that its working almost 100% with a downgraded modem?
[Verizon Samsung Galaxy S III] iikaronte:
Hi, I am obviously new to posting here but have been using this rom for a long time. I currently live in the UK (using giffgaff) and everything was working fine until the beginning of September. I am not sure what I did but I have tried every combination of flashing/wiping with TWRP/CWM but still have this problem:

Everything works great, 3G, GPRS and all, but I cannot make or receive phone calls. When I try to call it says "mobile network not available".

I have been flashing most of the updates manually together with d2gsm_rilblobs.zip. It does not look like this is happening to anyone else, but maybe there are not many of you living outside the US, so I decided to take the initiative and post myself. Let me know if anyone can help me diagnose this. Thanks.
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks for posting. I've been meaning to try a giffgaff sim when visiting UK, but haven't had the chance yet-just used vzw international calling and data. Please check mobile network settings to see if "global" is selected. It defaults to LTE for me, which I think is CDMA. If setting to global or a gsm option, if you have it, doesn't fix it, might also check [MENTION=2044079]Nardholio[/MENTION]'s thread for d2att, as that's the USA gsm version of our phone. Please let us know how it works out.
[Verizon Samsung Galaxy S III] iikaronte:
Thanks for the quick response! Mine is set to Global, so that can´t be the problem. I checked out the d2att thread but couldn't find any reference to anyone living outside of the US or suffering from the same problem.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well, I'm on NE1 at the moment as it seemed to work for awhile there. But, not anymore. When I was on MF1 I never saw it for a good month or more, but does seem like it popped up once. I'm gonna flash ML1 after I post this and see what happens. Have used it and seemed to remember it working. This problem can be a bit unpredictable.
[Verizon Samsung Galaxy S III] XdrummerXboy:
LTE is a separate technology from CDMA, they work independently of each other. VZW uses LTE for data, and CDMA (I think it's also called 2G or something like that) for voice and texts. They go together for Verizon, but are not the same.

You might be onto something in regards to checking for a GSM option though.
[Verizon Samsung Galaxy S III] AyUaxe:
Yeah, technically I think LTE is a form of GSM, but in our d2vzw settings, vzw's CDMA architecture seems conflated with LTE. Global setting allows gsm comms--I'm pretty sure that's how vzw provided me service on the UK GSM vodaphone or o2 system. I had voice, txt, and barely enough data (the main reason I want to try giffgaff next time I go). Hope our Brit mate can get it sorted and clue us all in.

---------- Post added at 05:02 PM ---------- Previous post was at 04:55 PM ----------

I'm pretty sure this voice call dys function has come up before, but I can't recall the context. One other place to check would be the CyanogenMod forum--there's a guy, ChrisNY over there who's very knowledgeable. Otherwise, hang in a bit here and maybe someone else, even [MENTION=2044079]Nardholio[/MENTION] (pbuh), may have better Intel for you.
[Verizon Samsung Galaxy S III] Master Cylinder:
FYI

I've put zips in the "d2vzw ROM Extras" link of MF1 firmware only and MF1 modem only. ML1 and NE1 modems are there as well.
[Verizon Samsung Galaxy S III] AyUaxe:
Flashed 10/28 this morning, wiped caches. Getting double Google play services crashes at every wake up and some app launches. Maps is completely unusable. Jeez, hate the frigging play integration. It's been nothing but a pain. Stand alone apps were fine, except for Google's control fetish. But then maybe it's just me.
[Verizon Samsung Galaxy S III] jburk68:
Had same issue with play services after flashing 10/28 as well. But a reboot right after fixed it; haven't had any issues since.
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks! Tried reboot, immediately 2 Google play services crashes. Tried full shutdown, wait a bit then power up. Same thing. I generated a bug report, but can't recall how to send it to anyone via this forum. Probably just nuke it and restore my 10/14 backup until I have time to mess with the mess that is gapps again. Thanks to all for any suggestions, tips in the meantime.
[Verizon Samsung Galaxy S III] Master Cylinder:
I had the same thing happen after restoring 10/16 yesterday coming from another ROM. Reboot fixed it. On 10/28 now with no problems.

As far as reporting a bug, you can get a logcat and post it here and try to bring it to the attention of Nardholio. You can post here https://jira.cyanogenmod.org/browse/CYAN which seems to be the official bug reporting pathway. You can look on there to see if this bug is reported. You could look on the d2att thread to see if anyone else is experiencing this EDIT: where Nardholio is the OP.

However, it doesn't look like a bug at the moment since no one else is reporting it, but rather something cranky with your install.

EDIT: [MENTION=3056030]AyUaxe[/MENTION], you could try restoring older versions of Play Services and/or Play and/or Framework to see if that helps. That got me through a similar situation in the past.

[MENTION=4652020]XdrummerXboy[/MENTION], I've been running ML1 and it works normally including with data, at least for the last few days.
[Verizon Samsung Galaxy S III] skyss07:
I have that same problem but mine is that I go to the settings>apps>google play service> and I modify the permission which I allowed and cheked all of it and reboot
[Verizon Samsung Galaxy S III] XdrummerXboy:
I'll give that a shot, thanks!
[Verizon Samsung Galaxy S III] Master Cylinder:
BBC News App Videos

Does anybody use the BBC News app? I can't get video's to play on it with this ROM since they upgraded their app, starting in July. I can watch videos normally in any other app or situation. Also, I can watch BBC News app videos on another AOSP ROM - AICP which borrows a lot from CM12 but I don't know how much.

I wonder what the difference could be?

If I run a July version of the app it works, but the new app is way cooler and has a lot more features.
[Verizon Samsung Galaxy S III] endleesss:
My install was OK. But i lost root access. TWRP is still there. Which root do you recommend? I last rooted this phone years ago when it first came out, and never took any OTAs. Thanks
[Verizon Samsung Galaxy S III] XdrummerXboy:
Root should be built in, you just need to enable it in developer settings.

Or at least I think that's the case.

Edit: unless you're talking about a different ROM
[Verizon Samsung Galaxy S III] skyss07:
Root can be acquire again by enabling the root access in developers options in settings if you want a native root in aosp or if you want to use SuperSU in Google Play you can either flash it and its automatically rooted afterwards. Search flash SuperSU in google and download the zip file and flash it in recovery.
[Verizon Samsung Galaxy S III] phonetool:
Enable Developer Settings:

System Settings / About Phone / tap multiple times on Build Date.

Then get root. Easy peasy.
[Verizon Samsung Galaxy S III] Droidriven:
It's Build number isn't it?
[Verizon Samsung Galaxy S III] phonetool:
Honestly, by the time I get to About Phone I'm slapping and punching everything. LOL
[Verizon Samsung Galaxy S III] XdrummerXboy:
Yes, its Build Number
[Verizon Samsung Galaxy S III] Droidriven:
Yes, that was a little sarcasm for humor's sake, its hard to convey that through text though.

It was also to correct the statement for anyone that may have seen it and been mislead. Thanks.
[Verizon Samsung Galaxy S III] Jaws4God:
does anyone know if CM13 has been released in beta stage yet? coming to the S3 ? Thank you.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I think someone said AICP had CM13 but its not even close to working with network type stuff yet. But that was a week or two ago.

We still have an active device maintainer so I would think CM13 is coming to the GS3, its just a matter of waiting.
[Verizon Samsung Galaxy S III] Master Cylinder:
However, we got unofficial builds out there now!

http://xdaforums.com/showpost.php?p=63729768&postcount=312
[Verizon Samsung Galaxy S III] AyUaxe:
Would the d2att M build work on d2vzw, if we flash vzw apns? Would we need to flash a CDMA radio, too?
[Verizon Samsung Galaxy S III] Master Cylinder:
Ride 'em Cowboy!!:cowboy: You should be a bronco buster!

My initial thoughts are:

1. [MENTION=2044079]Nardholio[/MENTION] would be the one to comment on that. Don't know if he would, though.

2. What differences in the kernels could there be? I guess you'd have to take into consideration what chips might be different on that device compared to ours, which would necessitate, perhaps, having different drivers for them, though there might be drivers built in to handle it. Build.prop on that device would be something worth looking at and comparing to ours. You could get a stock 12.1 kernel and compare them in some way, size, MD5, even see what you can see unpacking them, or get the source and see if you can suss out what differences there might be.

3. Need to carefully compare the partition tables. Various partition table references for our phone are in the "d2vzw ROM Extras" link, one even showing the start and end "cylinders" which would be useful for comparing partition sizes for the relevant few partitions involved in the ROM. May or may not need to if they copy is done "by name" which is usually the case. (?) Also, do they have the same names and mmcblk id's? Wanna have a good look at the updater-script to see what differences there are, if any, compared to ours.

4. A ROM flash doesn't touch the bootloaders or modem in their own separate partitions. (Those partition tables I referenced before are a great tool in understanding how this stuff works, as are updater-scripts.CM12 does use different flashing methodology compared to 11 or other kinds of flashes.)

I wonder what's different about TWRP for their phone and for ours?

Are you a sky diver? Just curious. :silly:

EDIT: But, the bootloaders do have to know where they're pointing to next. And as for updater-script, I think there's a different script with 12.1 that's in charge. I don't have time to go lookin at it.

An interesting exercise, but I'm not smart enough to say anything definite.
[Verizon Samsung Galaxy S III] AyUaxe:
Thanks, [MENTION=6629594]mastercylinder[/MENTION]. Good thoughts. Maybe a weekend project, since this is still my DD. Got backups, so what me worry?

Seems I've seen d2att folks on [MENTION=4932679]decimalman[/MENTION]'s dkp kernel thread and since [MENTION=2044079]Nardholio[/MENTION] is maintainer for both d2 flavors, hoping for his and our sakes they're not too different. I'll post results of simplest test, unless [MENTION=2044079]Nardholio[/MENTION] (PBUH) says it's no go.

Meantime, 11/11 with dkp seems great. Little snappier than 10/14. Only on it for a day, so can't say much more. BTW, cured Google play service crashes by DLing pico tkgapps, wiping system, flashing 10/14, gapps, etc, then reverting Google play service to original-now showing as ver 8.1.15(2250156-230).

I have no intention of ever jumping out of a perfectly good airplane.
[Verizon Samsung Galaxy S III] Master Cylinder:
So, aside from having good sense about perfectly good airplanes, you're saying that you used GApps that were about a month old? Did you have these stashed? Where did you get 'em because I can only find 10/04 in the mini's and 9/20 in the Pico.

EDIT: I misread your post - missed that comma, But the following still may apply. What GApps were you using before?

The reason I'm asking is that someone over on AICP has been having the same trouble you're having after flashing more recent GApps packages from Open GApps. Check this out which may apply to your situation?

https://plus.google.com/+AlexCruz/posts/bNABBK5VANV
[Verizon Samsung Galaxy S III] AyUaxe:
I think the last time I dealt with gapps was in June. Wound up doing full wipes and restoring a good backup. I think the last ones were G Play services 7.5.71 (1955121-436), store 5.6.8, GSF=5.1.1-1914015 from banks 6/6 or 6/11 gapps. Now GPS is 8.1.15 (2250156-230), store is 5.10.30 from tk.
[Verizon Samsung Galaxy S III] Jaws4God:
is anyone having issues with screen blackout? i noticed most when browsing web with stock browser.. couldn't wake screen.. had to hold power button to restart..

noticed on 10/27 build and 11/7 but im on 11/12 right now testing it.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] choadtron11:
Working ok for me so far. Some flaky BT where it drops/stutters for a second, but I was warned. I am using a circa 2010 sony head unit.

Made the jump from 4.1 modified samsung OTA push (bone stock 3.4?) to the 11/12/15 Cm nightly. Used TWRP 2.8.7 and did a full factory reset, then wiped: system, delvic, cache, data. Installed rom then TK gapps.

Try that process and see if it works any better for you.

Still trying to get my head around notifications and controlling what I want notifying me and how. (just want to know I have email for instance, not read half of it in the pull down)

forgot to add running NE1 base band.
[Verizon Samsung Galaxy S III] Stealth111:
I can tell you this. I am currently testing an Unofficial CM13 build on my S3 right now, and so far it is flawless. No network problems at all. Daily driver material for sure. I am still going through all things to see if I can find non-working bits. So far the only thing that doesn't work correctly is the cLock widget. It doesn't want to show the weather. Doing more testing on that. This was a wipe and clean install, not dirty flash over 12.1, though I may nandroid back and try that! Also I am going to wipe and install with gapps pico, as this install was with no gapps. I love my S3 sooooo much! I am beyond stoked to have Marshmallow running on it! It is silky smooth and fast! Once I get the all clear, I will post the rom.

Sent using Tapatalk