yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] hardy81:
I'm running the nightly from Feb 26, since yesterday. It's somewhat more stable than snapshot M3, which had constant repeated random reboots or device freezing. This nightly also reboots randomly but more rarely. Generally it's very nice.

Some problems:

Random reboots, twice so far after Feb 26 versions installation. Like with the snapshot removing the usb cable seems to be a trigger for a reboot.

After setting wlan off the mobile data connection does not come back up, requires a reboot each time.

The Browser does not sync with desktop Chrome. Even the option to enable sync is missing (from device settings; it also previously could be activated from the Browser's settings but this option is no longer there either)
[Samsung Galaxy S Relay 4G] robuser007:
I never had those issues on cm11, there are apps that are causing this (just greenify them all). btw this is a cm10.2 topic.
[Samsung Galaxy S Relay 4G] hardy81:
Yes. But there is no thread for 11.

---------- Post added at 12:53 AM ---------- Previous post was at 12:50 AM ----------

Apps causing the mobile data not coming back up after wlan is shut down, or the missing sync functionality of the Browser?
[Samsung Galaxy S Relay 4G] Magamo:
Try deleting /data/tombstones/ and then rebooting. That should clear up your wifi woes.
[Samsung Galaxy S Relay 4G] hardy81:
Thanks. Didn't help though: still after disabling wifi mobile data does not come back up. Only a reboot restarts it.
[Samsung Galaxy S Relay 4G] Magamo:
This may have to do with the RIL updates that were rolled in for the d2. We're looking further into this, though this has not affected me in my OmniToad test builds. Perhaps [MENTION=2044079]Nardholio[/MENTION] will speak further on this. Logs are always appreciated though. The more logs available to us, the better.
[Samsung Galaxy S Relay 4G] yohan4ws:
The Browser does not sync with desktop Chrome. Even the option to enable sync is missing (from device settings; it also previously could be activated from the Browser's settings but this option is no longer there either)

x2.

supposed to be an option to sync under accounts for bookmarks, it's supposed to work with stock browser but I don't remember seeing it since JB releases.
[Samsung Galaxy S Relay 4G] :
WARNING: DO NOT FLASH THE CM 11 M4 on top of a nightly from after 303. (March 3). You will brick.

Also I will laugh at you since the M releases are actually older than the nightlies.
[Samsung Galaxy S Relay 4G] dayofthedaleks:
Shew, lucky me yesterday I flashed M4 over a late Feb Nightly with no problems.

1) How hard of a bricking are we talking? I'm assuming one can still boot into recovery and wipe for a full install. Any idea what the mechanism for causing the brickings might be?

2) Also how far behind the Nightlies do the Milestones tend to run? I had assumed the Milestones were slightly more stable, representing a road-tested freeze where the Nightlies could be a little more chaotic.
[Samsung Galaxy S Relay 4G] hardy81:
For me M4 caused a boot loop. Or Android boots but immediately something crashes (the dialog "... com.something.acore... has crashed..." flashes -> reboot). I can get to recovery, but at least wiping the caches does not help.

I came from a nightly which was about 1 week ago.

Factory wipe? Oh shoot.
[Samsung Galaxy S Relay 4G] :
Just reflash a newer nightly and it'll boot properly again. The M releases are about 2 weeks before the nightlies in terms of code and there was a major change recently preventing this downgrade.
[Samsung Galaxy S Relay 4G] yohan4ws:
found a fix for browser sync.. install the apk from here:

http://xdaforums.com/showthread.php?t=2624412

it puts back browser sync option under google account.
[Samsung Galaxy S Relay 4G] hardy81:
It works. Beautiful. The mobile Chrome sucks.

Now I'm wondering why is the apk needed since this is supposed to be in Android itself.
[Samsung Galaxy S Relay 4G] Magamo:
It is a Google Proprietary application, it is not part of AOSP. Why it was omitted from the Gapps package, that would be something to ask whomever packaged that. However, do keep in mind, having it separate promotes choice. There are people out there who do not use the stock AOSP/CM browser, and don't want the added google bits necessary to keep it in sync with Chrome/Chromium

You seem to be confusing Google's edition of Android that they typically ship with Nexus devices, which is the AOSP base plus their Google Applications suite (And Google Experience suite) with AOSP which is the pure Open Source base that community Images are built upon.
[Samsung Galaxy S Relay 4G] hardy81:
Is the any info when to expect the Release Candidate? And what is the last nightly which can be updated with it?
[Samsung Galaxy S Relay 4G] Magamo:
If there's no news on the CyanogenMod blog, then probably there's no info yet. Device maintainers don't always get insider knowledge of what's going on upstream.
[Samsung Galaxy S Relay 4G] hardy81:
With M5, this is fixed. Great.
[Samsung Galaxy S Relay 4G] RodimusConvoy:
There's an official CM-11 nightlies thread? Cause I can't seem to find it. And I don't mean its offshoots FatToad or OmniToad I mean officially CM-11. Or would this thread now be it despite the title?
[Samsung Galaxy S Relay 4G] :
Try the last nard test build. Gerrit is the holding area for new code. Not in the nightlies yet

Sent from my Relay running CM 10.2
[Samsung Galaxy S Relay 4G] killkillkill:
Heh heh, gotta love it when the guy who is responsible for certain glitches doesn't know how to explain them for public consumption.

Nard made changes to the battery charging code based on jf kernel source (that's galaxy s4 for the layman). Basically, for lithium ion batteries, a "full charge" is defined as hovering somewhere under-but-close-to 100%. Not right on 100%. So basically, the charger gives up at 98% and calls it good. It then leaves all alone until the power level drops down to something like 97% when it turns the charger back on and runs it back up to 98%.

So it looks weird, but is totally normal behavior. At least normal based on how its programmed at this point.

Now realistically, there is a safety margin built into the battery scale, so this start/stop threshold can safely be bumped up by 2% to make everyone happy that it actually says "100%".

Now about the wifi/bluetooth glitch. One of the big reasons for the introduction of 5 GHz wifi, is actually the issue of interference with BT. Now with wifi, the AP and the device will negotiate a range of spectrum to communicate on, with a bandwidth of 20 or 40 MHz (depending on the particulars of the link). Those devices will stay on that particular band for the duration of the connection. Wifi is smart enough to multiplex multiple devices in that same spectrum if necessary, while simply reducing the traffic rate of each individual device.

Bluetooth, on the other hand, is a *****. It takes the whole 2.4 GHz spectrum and bounces around all over the place. The idea here is to maximize the portion of packets that are able to reach the target. This, of course, is very unfriendly towards wifi, because it will jump right into the spectrum that the wifi negotiated. Now your wifi receivers on both the device and the AP are choked full of bluetooth junk that they don't want and have a difficult time recognizing the actual wifi traffic that they need. The more bluetooth is dumped out, the less wifi is received.

So now we get into something called "bluetooth coexistence". Bluetooth coexistence offers several techniques that are supposed to allow the wifi and bluetooth signals to work at the same time. One of the simplest techniques, is to simply tell the BT devices not to use the spectrum negotiated by the wifi. A much stupider technique is to limit (by time) the BT's use of spectrum, this allows the wifi to sneak in a few packets around the BT. Unfortunately, the more advanced coexistence techniques don't seem to be working for this device. We're not sure why. The stupid solution is working somewhat, but causes the BT to cut out rather significantly.

This is the reason why Nard suggested the use of a 5 GHz wifi AP. Because having wifi in the 5 GHz spectrum means that the BT can freely use the 2.4 GHz without interference.

Now this by itself, is probably a silly reason to upgrade your wifi AP to a nice new 5 GHz unit, but for anyone in the market for a new unit, I would highly recommend a TP-Link TL-WDR4300. These cost about $90, and are pretty high spec units with 5 GHz wifi, and are very very well supported by OpenWRT.
[Samsung Galaxy S Relay 4G] chuckiev79:
Latest build broke poweramp
[Samsung Galaxy S Relay 4G] dillalade:
Fresh install of latest nightly and I can confirm that Skype audio call both ways fails after like 1 second of either party having accepted the call.

Phone froze while testing a Skype call and rebooted after a minute.

Also native call blocking doesn't work the way it did when I tested the first official nightly of the 14th.
[Samsung Galaxy S Relay 4G] chuckiev79:
Rebooted and today poweramp works again. Go figure.
[Samsung Galaxy S Relay 4G] stephenclower:
I'm still seeing regular crashes on today's nightly. If it's helpful, here is the tail end of my last_kmsg file: https://dl.dropboxusercontent.com/u/5108743/last_kmsg
[Samsung Galaxy S Relay 4G] :
The 822 nightly will have a fix for Skype/Hangouts and will hopefully stop the Google Now crashes.

A fix for iso modes in Focal came from a completely unexpected source, another phone with the same cameras who was able to copy our success and may be on CyanogenMod soon (the express). Front camera is still busted in Focal.

OTG is still stuck on gerrit.

Sent from my Relay running CM 10.2
[Samsung Galaxy S Relay 4G] dillalade:
Great news RE: Skype (I use it every night.)

As for OTG, I did try your Nard build you'd suggested but the phone didn't recognize anything (from what I could tell anyway.)

Can't wait to test this out when available ;)

As for my tests RE: native CM10.2 'call blacklisting' (call blocking.)

I can confirm it has indeed been working (for numbers saved without international codes only!) since the first official nightly.

What I've noticed however in my tests, which made me believe it's broken at times during nightly flashes to date is that: when you add to the 'blacklist' a number (either from your phonebook or off the cuff numbers) which has the country code (+44 in my case for UK) then the blacklist doesn't work and the call comes through regardless.

Blacklist works well when you edit the number in the blacklist by replacing the international code (+44) for a '0'.

Perhaps some further logic can equip the blacklist feature to appropriately blacklist a number regardless of entering a number with or without the international code.

:thumbup:
[Samsung Galaxy S Relay 4G] Kueber:
Did a clean, fresh install (build 819).

Issues over the past days:

- SD-card keeps getting 'unexpectedly removed'. Pretty annoying when listening to music.

- Sometimes the SD-card won't be recognized until reboot (there's just nothing there)

- Battery life is horrific, yesterday something tanked my battery that hard it went from 70% to 0% in 3h while 'idling'. While listening to music power drainage was also way to high,

- Device freezes sometimes when trying to reboot.
[Samsung Galaxy S Relay 4G] dillalade:
Since using 21stAug nightly, the above is no longer true :thumbup:

Tested Nards unofficial, and OTG was working and almost ready for public consumption after they fine tweak the feature. Great progress on that front :D

Nard, I did as you said.

Placed a fully charged battery from dock into phone, booted, got 97%. Put the charger in phone and left it in over night.

Low & behold the battery did reach 100% by the time I woke up :cool:

Those trebuchet quirks RE: disappearing homescreen folders has been resolved since a few nightlies back (just giving out all info on what I notice, so other followers can tell what's what.)

Will report back RE: Skype/Hangouts fix when a new build pushes through.
[Samsung Galaxy S Relay 4G] TheDigitalBug:
I am not sure if anyone else is getting this, but my USB connectivity outside of charging doesn't work anymore since flashing these CM10.2 nightlys. Not sure if it's the rom or if I did something terribly wrong. (Maybe I need to update my recovery).
[Samsung Galaxy S Relay 4G] stephenclower:
I've had this happen a lot in the past but not nearly as often lately. Try disconnecting your phone from USB and pull the battery for 10 seconds. Restart, and your PC should see it again.
[Samsung Galaxy S Relay 4G] TheDigitalBug:
That seemed to have worked. Thanks! :good:
[Samsung Galaxy S Relay 4G] dillalade:
Installed nightly 23rd

Skype now works :thumbup:

Camera app now allows to save pics to sd card :thumbup:

Focal Picsphere now allows to take the PicSpehere :thumbup:

But it fails on rendering/blending stage (88% Blending pictures) - nice progres on PicSphere for sure.
[Samsung Galaxy S Relay 4G] chris122380:
Titanium backup fails to work. When trying to do a backup the app restarts it's self. Any idea how to backup app settings for this ROM so I don't have to reconfigure them when I do a wipe?
[Samsung Galaxy S Relay 4G] :
Make sure your version of Titanium is updated. Also, su is currently broken in cm-10.2 Try this: Install supersu, then go into the program, and update su when it asks you. then reboot, and go into supersu options, and install supersu into /system, and make sure respect cm root settings is checked, and then install supersu backup script so it automatically gets reinstalled when you flash another rom. I didn't realize supersu played nice with cyanogenmod until I had to do this the other day because titanium wasn't working for me either :)
[Samsung Galaxy S Relay 4G] chris122380:
I was able to get helium backup to work.

---------- Post added at 09:27 AM ---------- Previous post was at 09:21 AM ----------

I've also noticed that fix permissions is also missing.
[Samsung Galaxy S Relay 4G] croogrog:
I got su working by toggling the su options in developer settings.

Did install from extSDcard ever get back in the recovery.img?
[Samsung Galaxy S Relay 4G] stephenclower:
Sadly, Google Now is still making my phone reboot on the 8/24 nightly. I assume that no one else is observing reboots with Google's voice recognition?
[Samsung Galaxy S Relay 4G] chuckiev79:
Nope
[Samsung Galaxy S Relay 4G] Magamo:
I never said that there was an official CM-11 nightlies thread. I said that there were three (Now several more) threads discussing images based on Android 4.4.2, and that there also existed CM-11 nightlies. Most discussion of the CM-11 nightlies is happening either on the CM 10.2 nightlies thread or the FatToad thread.
[Samsung Galaxy S Relay 4G] RodimusConvoy:
Alright so I'm in the right place/thread.
[Samsung Galaxy S Relay 4G] sev:
I may be a little late to the party but Im running the stable 10.2.1 release and its draining my battery siginificantly, whats the fix for this?

Is CM11 stable enough for me to switch to?
[Samsung Galaxy S Relay 4G] John5788:
I've been running OmniROM for about a week now and I have experienced 0 crashes so far. It definitely feels better than the CM10.2 releases
[Samsung Galaxy S Relay 4G] Magamo:
Very likely ANY of the 4.4.2 based images now available will be better on battery than CM 10.2 However, some things to check, no matter what image you're on -- Location services. Google Play Services LOVES to constantly poll your location if you let it. This eats battery.
[Samsung Galaxy S Relay 4G] hardy81:
I'm on the M5 snapshot and everything is running very smooth and fast, very stable now. I have CM on several devices and it's the best ROM by far.

I've also decided to ditch nightlies now and go with the stable releases only.
[Samsung Galaxy S Relay 4G] hardy81:
My other CM devices have received a snapshot M6 but not this, I'm wondering why this is?
[Samsung Galaxy S Relay 4G] hardy81:
Has this ROM been abandoned by developers?

EDIT: "old thread"?
[Samsung Galaxy S Relay 4G] cucumbers:
Nightlies are coming out regularly. I would guess it's only a matter of time before the M6 snapshot comes out...
[Samsung Galaxy S Relay 4G] hardy81:
Since no dev is replying and no development discussion ongoing, perhaps we can conclude that this team has abandoned Cyanogenmod?

"Old thread"?
[Samsung Galaxy S Relay 4G] reaper000:
As [MENTION=5601853]cucumbers[/MENTION] has just indicated, the team continues to release CyanogenMod 11 nightlies. Look at the original post and click the nightlies link.

No offense to you, but just because they aren't replying and not discussing things, how can anyone conclude the team has abandoned CM if they're still actually developing and releasing CM ROMs..?
[Samsung Galaxy S Relay 4G] hardy81:
Apollo crashes immediately each time it's opened, on the snapshot M5. I wonder why there still isn't an M6, even though it was available for other devices weeks ago?
[Samsung Galaxy S Relay 4G] robuser007:
I am on the latest cm11 4.4.3 build and have the following problem: charging from usb (laptop) doesn't work after a while (sometimes after an hour), how to fix this ?
[Samsung Galaxy S Relay 4G] robuser007:
charging stops sometimes after a few minutes. Anyone an idea (charging usb with different cable and different pc) what's causing this or has anyone the same problem ?
[Samsung Galaxy S Relay 4G] croogrog:
Try using a wall charger most computer usbs don't provide sufficient voltage to effectively charge the phone.
[Samsung Galaxy S Relay 4G] orange808:
I suggest trying an earlier release instead of a nightly.
[Samsung Galaxy S Relay 4G] :
Can you try to grab a log?
[Samsung Galaxy S Relay 4G] subzerobob:
hi, i'm new here. what kernel version should i use with CM10.2.1 rom? i'm attaching a screen shot of my current set-up, and my battery drains in 2 and half hours on consistent use and 10 hours on standby. I would like at least 4 hours on non-stop use and 20 hours on standby. please help. p.s. i dont want to change the rom, it works good for me, but i want to go be able to go back to its kernel if the new one doesnt work for me, in which case do i just reflash the rom?
[Samsung Galaxy S Relay 4G] Artanis02:
Is error correction working properly on latest 10.2 nightly ?
[Samsung Galaxy S Relay 4G] taiber2000:
if i would like to downgrade to the stable cm10.2.1 from a lolipop rom, do i need to format system/chach/dal-vik/data only? or there is some else i need to format or do as well?
[Samsung Galaxy S Relay 4G] falle21:
Have to work doing a clean flash as you said
[Samsung Galaxy S Relay 4G] Artanis02:
hey guys, has the keyboard issues (error correction) been fixed?

greets
[Samsung Galaxy S Relay 4G] Artanis02:
Anyone else having problems video-calling with skype ?
[Samsung Galaxy S Relay 4G] :
MMS should be back down to sane levels in the next nightly.

Also recovery now does sd cards, you can download the new recovery here

http://ls.infernix.net/jenkins/job/apexq-staging/
[Samsung Galaxy S Relay 4G] Kueber:
Flashed latest nightly (826).. caught that annoying sd-card vanishing thing on catlog, in line 1887 things start to get messy, I assume. Basically it tries to play the next song and everything just stops and the sd-card is gone until I reboot (and the phone freezes while trying that most of the time).

Update:

Uploaded another log.. the sd-card was 'unexpectedly removed' two times in this logging session while moving files onto the sd-card. This only happens on CM10.2 for me.

Well, who would have thought.. gone back to cm10.1 and the sd-card still gets 'thrown out'. Don't have a clue what could have started this.. but it first happened after I did a clean cm10.2 install.
[Samsung Galaxy S Relay 4G] misteropinion:
When I reinstalled SuperSu Pro (which I was using on my G2 but had stopped) inplace of stock su my phone became dramatically more stable, but it took a couple of reboots before it smoothed out. SuperSu Pro and TiBu Pro are both worth the dinero, IMO.

Right now my only issue is that under certain circumstances the PK and VK both stop responding, even though screen scrolling still works. This most often happens while in Chrome.

I'm running Nard's 18 aug build (to get whatever feature he mentioned, I don't even remember at this point, probably going to flash up to a new nightly tomorrow after I look at the ChangeLog).
[Samsung Galaxy S Relay 4G] :
A lot of code I never thought would see the light of day has just been merged (aka noobnl did a gerrit sweep) so please report any unusual breakages.

Significant changes include:

OTG, however it broke somewhere between patch sets and currently works only for joysticks and possibly mice. USB storage will be fixed whenever we figure out where we broke it in the patch sets.

AVS. Should be fixed for everyone but let us know :p

Standalone power collapse: aka really really deep sleep (you want this). Somehow managed to sneak in in a different patch set.

Relevant upstream changes:

Soft key light timeout is now supported. The interface is a tad bit broken for keyboard phones, which you will see if you try to access the key timeout menu with the keyboard out. However, we will be the only keyboard phone on the 8/27 nightly with a functioning backlight ;) (Droid 4 and Photon Q are the only other 2 keyboard phones on cm 10.2 I can think of)

[MENTION=1509069]lbcoder[/MENTION] did a bang up job on most of this code. We should start an xda petition to get him unbanned.

He thinks he can even lap Google, Samsung, and Qualcomm and fix wifi/bt concurrency, which even the Nexus 4 (which we share a chip with) has problems with.
[Samsung Galaxy S Relay 4G] :
Next 4 things on the radar:

Fix OTG again

Fix haptic feedback

MHL

bt/wifi concurrency
[Samsung Galaxy S Relay 4G] :
Oh yeah, and since I am apparently the head developer for d2 now (I kid but seriously, I got 10.2 booting before they did) I also went ahead and fixed mass storage mode.

Use this app for easy switching

http://xdaforums.com/showthread.php?t=1711009
[Samsung Galaxy S Relay 4G] dillalade:
WoW

Good job :thumbup::D
[Samsung Galaxy S Relay 4G] stephenclower:
FYI, using ROM Manager to perform a backup, I received the following:

ROM Manager Version 5.5.3.0

August 27, 2013

I:using /data/media for /sdcard.

E:unknown volume for path [/external_sd/clockworkmod/backup/2013-08-27-10.37.42]

Can't mount backup path.

result was NULL, message is: assert failed: backup_rom("/external_sd/clockworkmo

d/backup/2013-08-27-10.37.42")

I:using /data/media for /sdcard.

/ tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
[Samsung Galaxy S Relay 4G] :
[MENTION=5132711]stephenclower[/MENTION]: I assume you flashed the latest nightly? external_sd was added as an additional alias for the sd card. You probably need to either wipe data on rom manager or update your recovery to one that was built last night. There should be one one the cm server or there's one on our jenkins.

FWIW I just installed Rom Manager and attempted a backup with an old recovery and it used sdcard1 instead of external_sd.
[Samsung Galaxy S Relay 4G] chris122380:
I have had 3 or 4 reboots in an hour and a half on this nightly. Unsure why, so I have deleted the cache and the Dalvic. If the problem continues I'll try getting a log file.
[Samsung Galaxy S Relay 4G] dillalade:
OTG works for my usb mouse and a small 4gb flash drive but not my larger flash drives (64 & 128gb.)
[Samsung Galaxy S Relay 4G] stephenclower:
Yup. I flashed the 8/27 nightly and am using the most recent recovery from the apexq-staging server. Since I'm apparently the only person in existence with voice recognition issues, I plan on wiping everything and installing fresh (once I can backup the ROM that is).

I wiped everything and installed CM and gapps yesterday, but for whatever reason my device refused to see the Sim card. I restored an old Cm-10.1 backup I had made with TWRP and updated it to the current nightly until I can figure out what was going wrong with the card. But before I do, I'd like to stick to a single recovery instead of jumping between TWRP (which can backup/restore from external storage and supports the openrecoveryscript format) and CWM (which currently does neither but lets Wifi live).

Thanks,

Steve