yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dorf18:
random reboot on latest nightly when messaging
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manfromgta:
This post will likely be ignored without a log attached.

Sent from my SAMSUNG-SGH-I747 using Xparent Cyan Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Unfortunately these random reboots, if like mine, leave no last_kmsg behind and I'm not sure logs would show anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcaseiro:
Running 0906 since yesterday and so far no random reboots. It feels pretty stable and snappy. Cross fingers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Did you get yours while messaging? That's the only time I get random black screens and have to hold the power button to restart.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
If mine goes black it's usually when I have open camera running. But I would actually get random reboots, no pushing of the power button needed.

---------- Post added at 11:21 AM ---------- Previous post was at 11:17 AM ----------

I realized that I couldn't find my nandroid of 08/20. I was running the 08/08 for the last few days. Smooth. This morning naked that up and installed. 09/07. We'll see how this works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
naked = nandroid (autocorrect?) :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Ha ha.. Meant backed.... I had to switch back to my 8/8nandroid because I needed the phone for some serious stuff that I couldn't use it for testing.

Later in the week I will be able to go back to a current nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
dialler goes hiding on incoming calls on lockscreen

locked screen, someone calls me - rings and vibrates but the screen stays blank, no buttons appear to answer/reject the call - the caller finally gets sent to voicemail, however the phone kept on ringing and vibrating for about 7 minutes - until i pulled the battery out. (0902 build) - I've seen this asinine behavior a bunch of times by now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
This may be related to screen on delay, which is a known problem in cm 12.1 right now, and is being worked on. Good news! The 9/9 nightly will include a hack to ramp up the CPU when the screen turns on, I will probably leave it even after the current set of delays is fixed!

Also, no 1080p for you. Videos taken at 1080p will not save. Sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] melvinaury:
One question that I don't find with search. How I change from Dalvik to ART. Where is the menu for the option. I don't see it in the developers options.:confused::rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
I believe Lollipop uses ART by default. Someone, please correct me if I'm wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Surj138:
Correct. The option to change runtimes was found in KitKat, when ART was still experimental
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
fixing gps issues for good (hardware, some soldering..)

(I've been meaning to write this for a while, I think it might be worthwhile for others with similar signal issues on their GPS! Not entirely OT as, before I always mercilessly blamed CM build quality for my GPS issues.. /sorry..!/ )

I've broken and replaced the front glass 3 times, and likely from those, the gps antenna was somehow messed up. Slight overheat, the GPS would go nuts.

navigation became so frustratingly flaky that pushed me to do something crazy. I soldered a copper wire onto the antenna a month ago. Leave it long enough inside the cover as in the bottom picture. (Actually, this "wire" is just a portion of de-soldering braid that came in my soldering iron kit.) The theory is, the GPS antenna is now "big" enough to make contact with satellites, and there's no "contact" problem with thermal variations.

Anyway, ever since this brutal fix, my GPS has been AWESOME!

Here's what I did: (credit note: the first image has been lifted from another xda thread, I took the bottom image..)

[IMG="d2lte-sgh-i747-gps-antenna-fix.png"]http://evuraan.info/screenshots/images/d2lte-sgh-i747-gps-antenna-fix.png[/IMG]

If you are pushed by gps issues to go this way, here's another post you should consult (to familiarize yourself with the gps antenna connector) before getting the soldering iron out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HMkX2:
Running the second-latest nightly (9/9/2015) and LTE is still nonfunctional. The best I can get is HSPA+.

(I am not sure a log would help since it is a persistent issue.)

Also, I am unable to select "Network Carrier" in the mobile networks menu, it simply loops infinitely when searching.

Does anyone else have this problem on AT&T?

(Using NJ1 baseband/radio on Knox-tripped bootloader)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
The last 2 nightly builds are significantly larger than all previous. We had been sitting at about 238MB and the last 2 are at 286MB. Is this expected or indicative of a problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcaseiro:
Running latest 0911 build and so far so good...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
So has the lag been addressed that often prevented the screen from waking up in time to answer an incoming call?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcaseiro:
I've received several calls today from my boss and it seems fine. :thumbup:

Give it a go yourself and post your feedback here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rnagam1:
Running the latest 9/11 build. The screen does not wake up immediately. It takes a couple of rings before the screen wakes up but is now way better when compared to prior to 9/11 builds
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
In the commits, there's a change to boost all cores when screen on: http://review.cyanogenmod.org/#/c/108635/

That helps with the problem for now. It was dialed down in the next build though: http://review.cyanogenmod.org/#/c/108943/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
I'm giving the 9/11 build a try. It does seem improved, if not perfect. However, in my impatient testing, the phone may not have had a chance to enter some deep sleep.

As for the change to "dial down" the boost at screen on, judging from the change log, that was included in the 9/11 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tdotdot:
Your phone isn't going to sleep? I found that with pac (based on cm), mine didn't either. I attributed that to a gapps error though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
My phone has been sleeping just fine. Haven't had the 9/11 build on long enough to judge it is that department.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
The change to dial it down is for the Galaxy Tab 2, which only runs at 1.2 GHZ. That change does not affect d2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Since our system partition is HUUGE, I added dex preopt for the system apps, which adds a bit to the size. This should lead to slightly faster boot times after flashing a new build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Cool! Faster boot is always welcome.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] datit.haui:
hi, when i connect the headset to my phone, it sounds inactive? please help?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hi. Please provide the following information

Brand and model of headset

Type of headset, Bluetooth, wired, etc

What you're trying to do, listen to music, make phone call

Current bootloader and modem (note these can be different)

Logcat

And standard disclaimer, if I can't reproduce it with the headsets I own, it probably won't get fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobamoba:
I'm still having bad lag with most recent version (9/12). Anything I can do to help track down why?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] datit.haui:
hi, i'm using headset wired, while I connect the headset with the phone, the sound system is lost. At a time such, I restart the device to retrieve sound system, please fix it. tks u. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobamoba:
For others having lag, just passing along my solution. If you use Xposed, check the your logcat because my lag turned out to be an Xposed module that had been working perfectly fine up until a few weeks ago. Although I'm using the most recent Xposed Official for 5.1, I'm thinking a change in the CM12.1 nightlies a few weeks ago somehow broke part of Xposed or broke some previously working modules or something like that.

Bottom line, when I disabled the previously-working-now-broken modules, the lag went away and that might solve your problem as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sjamie:
Thank you! Which xposed modules did you find are now broken?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobamoba:
It was a little hard to trace but I think it was Lucky Patcher's Xposed module. I disabled the Xposed portion of Greenify for good measure as well because it wasn't super apparent (to me at least) which module was causing the problem. However, I could tell it was a module that ran all the time - like Greenify or Amplify - rather than a module that was app-specific.

The thing that was causing the lag, as far as I could tell, was that the module or modules were looking for something on the SD Card and not finding it and were basically thrashing the drive and not stopping and all of that constant SD access was interfering with everything else that wanted to access the SD Card, like every time I did anything on my phone it would trigger the Xposed module to hog the entire SD access and force everything else to fight for miniscule slivers of SD access, which is what made the whole thing laggy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dunkin11:
Android Pay

Anyone get Android Pay working with this ROM? I manually downloaded the Android Pay APK and the latest version of GPS. Whenever I open Android Pay, it tells me "Android Pay is not available." I also tried disabling SuperSU because I found reports of that working for some users.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
You have Xposed working on 5.1.1? Can you point me in the right direction to do that myself? I'm really missing my Xposed modules I had on kitkat.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Everything you need is at [OFFICIAL] Xposed for Lollipop [Android 5.0/5.1, v74, 2015/09/10].
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
got trolled by the camera, and this time it got personal

That is fine, 720p is ok. However, I just got trolled by the camera, and this time it got personal:

Today, I recorded a video of my son's first words - the screen showed the red time counter to assure the video indeed was being recorded. I stopped after 90 seconds, but later, could not find the media file! It saved the photos I took, but not the video. retried, a number of times, no videos saved. photos, yes, it saved those.

rebooted, it started behaving normal. well, if that's normal... :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
What camera software.? I use open camera or "a better camera". Although I've had problems with lock ups with all cameras on earlier builds, I haven't worked it hard since installing the 9/13 build.

Oh, and sorry to hear about the file problem. Being a dad I know how frustrating missing that stuff can be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
just the stock camera app.

(I tried using opencamera on a recent nightly a few weeks ago, somehow it messed up my access from lockscreen - it started to prompt me for password for lockscreen camera access. Worse, after deleting opencamera, stock app also started to ask for password for access from lockscreen. And that's when I did a clean flash to the [then] latest nightly)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
Fine, I will ask: snapshot

(admittedly, I don't know much about the release curve/checkpoints..)

why not declare 09/20 (or 09/24..) as d2att/d2lte cm12 snapshot?

//too soon?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Just wanted to hop in and let everyone know that YouTube 60fps videos still freeze on the latest nightlies. Just flashed the latest build and tried a few videos. About five seconds in they all froze while the audio kept playing. Same as it has been for the last 2-3 months.

This means that if a video was recorded at 60fps you will not be able watch it in HD at all because 720p60 becomes the only option.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
I can't get WiFi working on the latest nightly (9/27). Anyone else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jswclw:
Working here on the 9/27 build. It does seen slightly slower to pickup the SSIDs when it is toggled from off to on. But it does work.

I should add that I an running dkp kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] greglarson:
Seems to be working fine for me on 9/27 (without any special customizations).

As a test, I turned wifi off, then did a reboot, then turned wifi on.

It connected quickly to my preferred (5Ghz) wifi.

In the Wi-Fi->Advanced menu, I have 'Scanning always available' set to On (in case that makes any difference).

- Greg
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Ended up doing a dirty flash of 9/27 over 9/27 and it took about half an hour but WiFi finally started working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
So I'm on a pretty old nightly (8/20), but I've experienced the camera crashing a few times. The only way to fix is to reboot. Here are logs though right after the camera crashed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
While some of that might be useful, I would think that upgrading to a newer build would be recommended.

Also, [MENTION=2044079]Nardholio[/MENTION], I just wanted to say that I'm on the 9/25 build. Getting decent Bluetooth with both my lg stereo set, and my jawbone. The phone wakes the screen pretty quick and other than a reboot on the first day I've had no lockups or reboots. Heat hasn't seemed to be an issue do fast. But I am still noticing some lag. I'll do a reboot later today and then get some logs of just normal activity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
I would, but I just hate having to wipe and go through that long process of restoring all my apps and settings and also losing all my wifi passwords, and thus having to ask my friends again for them at their houses. Dirty flashing, from what I know, is usually just kind of a no-no, and you'll never even know if the ROM is performing its best unless you do.

So I'll probably hang out on 8/20 for a bit longer :P It has hardly any bugs that I notice. I use it as a wifi only device though.

Should we expect to ever see a cm12.1 milestone or will we only continue to get nightlies? The nightlies work really well so that would be cool with me. I'm just curious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Going from nightly to nightly isn't dirty flashing, it's considered an upgrade. Besides titanium backup saves Wi-Fi passwords and texts and such. Also, there are separate programs that save those kinds of details.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
Hm, would going from nightly 8/20 to 9/28 still not be considered dirty flashing? If not then I'll do so, but that is in fact quite a bit of time in between.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Wi fi password backup

Google play ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Worries about "dirty" flashing between major version releases i.e. 11 -> 12, or even 12 -> 12.1. Also you don't usually flash one Rom over a different Rom. Even a month jump should be fine, just make a nandroid backup before flashing just in case.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
In our private CM forum, they announced two upcoming stable releases for CM 12.1, a security upgrade to the first CM 12.1 release and a new stable in about a month and a half. I will not be approving the first based on the fact it doesn't even boot on d2 but we will see about the second one.

As always, if you're already on the latest nightly when a stable comes out flashing the stable is dumb and not supported, unless your nightly is like 3 months old.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
That sounds fantastic. We all really appreciate the effort being put into this!

However, can you elaborate on "As always, if you're already on the latest nightly when a stable comes out flashing the stable is dumb and not supported, unless your nightly is like 3 months old."? I don't understand what you mean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Nightlies are like running a beta version. A beta version that is months ahead of the release version and stays there. Flashing a release version over it is like going back to a nightly from several months ago. Likely won't with very well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] plastic_green_head:
Does the Google search bar keep showing up for anyone else, regardless that it is turned off in the options? If I re-enable it, then disable it again it goes away temporarily... but it randomly pops back up. Well, at least half of it does as shown in the attached screenshots. Also, if I completely completely turn off the Google app under the Apps setting to get rid of the bar once and for all - it results in a never-ending "Trebuchet has stopped working" message and am unable to do anything at all until I factory reset. I have tried removing the clock widget but it didn't change anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
to flash a newer/lastest nightly over a previous release of the same rom major version (ie cm12.1) all you have to do is:

Settings-> About phone-> CyanogenMod updates-> tap the refresh icon (top-right)-> tap the latest nightly and let it download

when the download is complete, do Not install it ... reboot into recovery, preferably twrp

the following are based on twrp menus

BACKUP

.. Mine takes approx 20mins for 4.4GB boot+system+(internal)data+cache

go back to

home

twrp menu

install .. flash the new nightly .. it should be in /sdcard/cmupdater/ .. should take approx 2-3mins

tap wipe cache+dalvik button that should be there after the install

tap reboot

after a couple mins of boot animation, you should see the white android is upgrading/optimizing box

the system is rebuilding the ART cache .. depending on how many apps you have, this WILL take awhile

the boot will finish and you are upgraded :good:

you should have all settings, passwords, etc intact since you did not wipe any data nor factory reset and do not even have to re-install/flash gapps cuz

cheers

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
According to the changelog for the 10/01 nightly, there is a fix for the search bar not staying hidden.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnnyrichter:
Went from CM11 to cm-12.1-20151001-NIGHTLY-d2att. Took a while due to having to perform the MJB>NE4>NJ1 bootloader upgrade path but everything went without a hitch. Now that I'm running it I have found some bugs.

-When I view a new text message in my notification pull-down and choose "Read" it removes the notification but doesn't open up the text.

-Sometimes when I tap in a text input field it opens a blank white window where the keyboard should be, and if I tap in that window the keyboard appears plus whatever key I tapped. So it's like the keyboard is there and fully functional, but needs touch input to display itself.

Otherwise I'm extremely happy with it so far in the hour or so I've been playing with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I don't usually go to texting from those notifications, I'll try today. What keyboard are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WHib96:
Back on kitkat there was an option in the browser to save Web pages for offline reading. I just realized that that option is now gone on lollipop. However, if you go into the tabs menu in the browser (where you can add new tabs or swipe ones away) and click the little options button (the three dots), there is a "saved pages" button, which only takes you to the history. Seems like either the saved pages option isn't supposed to be there of the save pages option just isn't implemented yet.

Is this a feature that was just removed in lollipop or is it specific to our device? I actually really appreciated that option as one who uses the s3 as a wifi only device. Can the feature be implemented?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Frozen

I just had a problem with my phone. I was on a call. Had the phone on speakerphone. (by the way, haven't had to do this in a while and noticed the lowest volume position is actually pretty loud). When the call was over I lifted the phone to hang it up and the screen was black and wouldn't come on. pressing the home button or power button did nothing. Even the lights on the soft buttons would not come on. I waited a few moments to see if there would be a delayed response, but nothing, so I held the power button to reboot. Below is the Last_kmsg file. I actually had one after this reboot.

EDIT:

Also, this is on the 09/25 Nightly, NJ1 baseband
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] whodisname:
Yeah but that boot time. Updates Facebook for like 30 min. Am I right! Lol.

Great work. I'm not on this right now, is anyone having random freezes/reboots with GPS and/or headphones? Last time I used this that was still an issue on the latest builds?

Also, does it run smooth with xposed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnnyrichter:
I'm using whatever keyboard is default in this rom.

It's almost like that "Read" button is acting like a "mark as read" option. I can recreate that bug on demand, but the one where the keyboard pops up as blank has only happened 3-4 times.

I'm also noticing that there is no longer a performance menu. Was that stripped out for CM12.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Thevenine:
System-wide audio loss on headphone insertion

I noticed this about a week ago after i moved from cm11 to cm12.1 nightlies. Whenever i insert the headset, my phone loses all audio functions; from speaker, to mic to earpiece. :eek:

I have to reboot before everything starts working again. The funny thing though is it doesn't occur everytime. It happens when I least expect it. I've gone through all the pages in the thread and no one else has mentioned it. Now I'm not sure if it's the rom or the hardware itself. :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
I've seen someone mention it before, was that you on the q&a thread? I don't have time to look. My Samsung headset works fine. Used it the other day a couple of times while I was waiting for my lg+ stereo Bluetooth to come in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] user8932679:
My phone lags so much when I get an incoming phone call. So much I cannot answer the damn phone. This just started happening recently.

Going to update cyanogenmod and see if that helps (on a July 1 build right now)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Thevenine:
Any advice?? I also use a Samsung headset and it can get really frustrating sometimes what with the frequent reboots.

---------- Post added at 08:37 PM ---------- Previous post was at 08:33 PM ----------

July build?? You really do need to update
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] user8932679:
Yes I didn't want to do an update as that build had everything working that I needed. Didn't want to break anything :P

I just did the update, phone seems faster. But this is usually the case after a new install (this time wasn't a fresh install, just an update). Time will tell whether it will slow down a bit. Also I will see if the phone call lag occurs again...