yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] wedg11383:
Audio Stuttering.

For at least the last month I have been getting stuttering/glitchy playback of audio on my device. This was in test builds and official builds. When I finally started troubleshooting it, I observed that they stopped if I forced a minimum clock of 594Mhz. It seems like, even with the screen on and running audio players and navigation, etc, the phone kept trying to down clock all the way to 384Mhz and stay there.

I tried fresh builds and different audio players with the same results. I also have tried various governors and schedulers. Also I tried various SD cards in case it was a performance issue transferring data. It was more prevalent when using BT but still occurred even with corded headphones.

When I searched, it did seem some users on other phones had experienced similar issues, so I wondered if maybe it was an upstream issue.

Has anyone else experienced anything like this? I do mainly use FLAC files. Is there an issue with the FLAC decoder, maybe its not optimized and needs more processing power to run? Are there any logs that would be helpful?
[Samsung Galaxy S Relay 4G] Nocturin:
I haven't travelled quite as much since I got back, but going across SC/NC/GA statelines I've had less issues where previously I wouldn't have service till I restarted the phone.

Which google settings? PM Me, I'd be interested to try this. Tired of "Unknown" calls.

CM11 has worked better for me than CM10.2, but it's anecdotal and if you want to poll, follow GTs advice and put a thread up in general.

I've noticed this while running spotify too, and if I don't catch it soon enough the phone will lock-up and a hard reboot is needed. I disabled SetCPU and it didn't happen as frequently, and SetCPU seems to harm batt. life more than leaving the governer stock, but I'll modify the min. clock and see if it happens again.
[Samsung Galaxy S Relay 4G] DOMF:
I (mostly) fixed this in the latest hypnotoad build, but if you're using official CM you can try putting the line:

echo 95 > /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load

into the "msm8960" section of /system/etc/init.qcom.post_boot.sh section. In official, it's at 99, there's significantly less stutter using the value 95, and so far none that I can tell using 90 (although this may slightly consume more battery life)
[Samsung Galaxy S Relay 4G] Nocturin:
Glad I'm flashing the new build as we speak!
[Samsung Galaxy S Relay 4G] wedg11383:
Worked perfectly. Thank you very much.
[Samsung Galaxy S Relay 4G] DOMF:
Fantastic! Which value, OOC?
[Samsung Galaxy S Relay 4G] wedg11383:
The 90 value worked best. I tried the 95 but there were still some issues. I usually go back and forth between our custom builds and the CM officials but it doesn't seem like they've been updated in a while. (Not complaining).
[Samsung Galaxy S Relay 4G] dillalade:
Hi all,

Been away for a while.

Now I want to make the move to CM11.

My question being, do the Jenkins builds still gain from the mpdecision (better battery performance) compared with CM's official nightlies (in the same way they did with CM10.2)?

Thanks in advance
[Samsung Galaxy S Relay 4G] DOMF:
Yep!
[Samsung Galaxy S Relay 4G] wedg11383:
I'm unable to toggle usb tethering after installing build 599. Has anyone else installed this and experienced similar issues? WIFI tethering works fine.
[Samsung Galaxy S Relay 4G] :
nardholio build 599? Are you out of your mind?
[Samsung Galaxy S Relay 4G] wedg11383:
Yes?

I'm not sure I understand. Did I do something wrong.
[Samsung Galaxy S Relay 4G] thewebmaker:
Hi guys,

i owning the t699 for almost 4 months. it replaced my old defy which died the RIL Bug death. Now i interessting from stock to cm 11. But there some questions i have.

1.) Do you think or believe Samsung will publish a KitKat Stock ROM for the Relay ?

2.) If CM11 is unusable for me, how do i get the original stock f/w back to the phone (For the Defy i used SBF Files and a motorola software)

3.) I connected the Relay to my Exchange 2010. I now been able to sync my tasks and sms to and from the server without additional software. On the Defy i tested different CM 10.2 Roms which all haven't had theese features. Are they only available on stock rom ?

4.) At the moment, only the MHP Function isnt integrated. Will it be in the final stable release ?

Best regards from Germany

Flo
[Samsung Galaxy S Relay 4G] caitsith810:
I've been using this rom for a while and I've been getting word from other people that I speak to over the phone that they can't hear me all too well.
[Samsung Galaxy S Relay 4G] dillalade:
Nard,

I'm on the 602 Nard build.

Something I've noticed is that WiFi will *sometimes* not want to toggle off (using the 'Quick Settings Panel') - forced to reboot & then toggle it off.

Also when hold pressing WiFi toggle to get to WiFi system settings, the WiFi setting page is not shown as we'd expect - some glitch perhaps.

However i have just noticed your statement on Jenkins " Project apexq-nardholio

test builds for apexq by nardholio, not for general use!*

seriously. DO NOT FLASH THESE"

Just wanted to put my findings out there.

Other then this, I've come against no other problems :thumbup:

CM11 Jenkins 602 Build
[Samsung Galaxy S Relay 4G] :
I too had this problem. Solution was to clean the food/gunk/dirt out of the microphone pinhole at the bottom with a very thin piece of wire (or in my case the connector off a broken cable held with pliers). For maximum effect you can disassemble the phone and remove the piece altogether so when you push the crap out it comes out instead of just going further into the phone.
[Samsung Galaxy S Relay 4G] gtmaster303:
I've noticed that the earpiece volume during a call is low even when set to max. I would have to toggle the volume up and down once to get it back to max volume. And I have to do that every time I'm in a call. Anyone else having this issue?

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] stephenclower:
Hyperactive battery drain on 802.11N networks

Greetings,

Ever since staging build 172, I've started noticing my phone running very hot--even when charging at home over night. When I leave home and switch to mobile data, the device isn't able to find any net addresses. When I reboot the phone and use it at work over wifi, everything is fine--including the severe battery drain. Likewise, leaving work's wifi and switching to mobile data works. When I then return home, the phone starts running hot again, and the cycle completes.

The only significant difference between the two networks is that my home connection uses N on the 5GHZ band, while work uses G on the 2.4GHZ band. I've got Better Battery Stats running again and and am happy to send a dump of its logs out in addition to logcats, last_kmsg output, etc. Before I keep going down this path, I just wanted to see if anyone else was also observing similar behavior over N. Or am I barking up the wrong tree?

Thanks,

Steve
[Samsung Galaxy S Relay 4G] wedg11383:
I'm getting the same thing. I notice it really hot even with airplane mode is engaged. Even the last few official builds just don't seem to work very good. Phone hangs a lot. Bluetooth streaming is unusable. I'm just going to wait for the great developers here to sort it out.
[Samsung Galaxy S Relay 4G] Magamo:
I experienced this the other night. It appears to be the netmgr process spinning out of control. I've not noticed it as of yet in any more recent builds than 172.
[Samsung Galaxy S Relay 4G] janejunx:
I had it in the newest nightly. Phone was on its charger all night, but managed to die and not charge past 1%. Had to revert back a few nightlies.
[Samsung Galaxy S Relay 4G] wedg11383:
I tried build 177 and found the same thing. I kept clean wiping and flashing different builds today trying to find something that worked. What I ended up trying was turning off mp-decision after I saw a lot of errors related to it in logcat. I also disabled the temperature throttle. I know these are not great solutions but the phone is running perfectly right now. It's running much cooler than it was and is streaming over bluetooth while charging flawlessly. I'm running the latest official nightly right now since that was what I happened to be trying when I thought of turning off mp-decision, but since I had the same issues in build 177 and the nightly I wouldn't be surprised if this helped with that build as well.
[Samsung Galaxy S Relay 4G] yohan4ws:
How do we turn off mpdecision ?

Also, I had issues with audio stuttering when streaming over bluetooth to my soundbar the other day with wifi enabled, switched to 5ghz wifi and it smoothed out. This is on Jan 14 nightly. Have also experienced freeze ups but - no logs so take it for what it's worth.
[Samsung Galaxy S Relay 4G] wedg11383:
I used an app called trickster mod to make the changes but I'd advise caution. I don't fully grasp what the features do but I know they have a purpose. I'm waiting for a developer to tell me what an idiot I was for touching them in the first place. If you make the adjustments,monitor the phone closely is my recommendation.
[Samsung Galaxy S Relay 4G] :
FYI for those of you with rev 4 socs (aka rev 0 cpu): http://review.cyanogenmod.org/#/c/58169

This is not related to the overheating you may have been experiencing lately, this is from a bad wifi update and should be fixed in the newest builds
[Samsung Galaxy S Relay 4G] dillalade:
How are you guys managing to flash these staging 4.4 Roms with those NWT files instead of zip.

Please advise

CM11 Jenkins 602 Build
[Samsung Galaxy S Relay 4G] gtmaster303:
Rename to .zip file. Already mentioned. Should be added to op

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] dillalade:
Cheers.

I did a search on this thread for NWT but only found Magamo's response as to why they've used this file extension, nowhere did I find the resolve.

Thanks, much appreciated.

Is everyone now using the latest gapps as found on CM's site, namely ' gapps-kk-20140105-signed.zip '

:thumbup:

CM11 Jenkins-4.4-Staging 177 Build
[Samsung Galaxy S Relay 4G] Magamo:
I'm sorry, this will not be added to the OP. This thread is no longer for discussion of individual builds. It is for discussion of the source and the CM11 project. The experimental branch builds are the team's testbed. Beware the dragons.
[Samsung Galaxy S Relay 4G] Magamo:
What you were experiencing was a wifi bug caused by a bad 'prima' upgrade. We discovered this and reverted the upgrade on the 22nd. A build done today withe the listed reverts will not exhibit this behaviour.
[Samsung Galaxy S Relay 4G] janejunx:
I'm getting unusually high heat and battery usage on the 1/24 nightly still. Not quite as bad as before, for sure, but my phone just got fairly hot after sending 20 texts, which isn't particularly taxing behavior.

Screen is only 30% of my battery consumption, Google Play Services is 12%? Not sure why; the only things I've used today are Facebook, Facebook Messenger and Go SMS Pro.
[Samsung Galaxy S Relay 4G] robuser007:
I'm also having serious draining isues on 26/01 and can't turn off wifi (keeps draining): on 25/01, which build didn't have the wifi issues ?
[Samsung Galaxy S Relay 4G] :
Can those of you on the nightlies see if copying this file http://review.cyanogenmod.org/#/c/58339/2/firmware/WCNSS_qcom_cfg.ini to /etc/firmware/wlan/prima on your phone fixes it? (click the download icon on the right hand side of the comparison to grab the file, unzip, and then rename it WCNSS_qcom_cfg.ini)
[Samsung Galaxy S Relay 4G] falle21:
My mistake. Downloaded
[Samsung Galaxy S Relay 4G] falle21:
I still have The same problem
[Samsung Galaxy S Relay 4G] falle21:
Problem solved in last nightly (27)
[Samsung Galaxy S Relay 4G] gtmaster303:
How quickly and often do the tweaks and fixes seen here get incorporated into the official nightlies?

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] Magamo:
Some get incorporated at the next nightly. Some never. Keep in mind that this is our test bed for what goes into the nightlies. Some changes are held out due to requests from CyanogenMod.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
Hey [MENTION=4908192]Magamo[/MENTION] im going to be getting this device on saturday at around noon Pacific Standard Time and would love to start developing on this device...currently ive been doing alot of work on a similar device that has most of the same motherboard parts and know how to build from source code and have a fully set up linux machine....i would be glad to join the team and have hangouts if you'd like to chat on further developing for the phone. Thanks.
[Samsung Galaxy S Relay 4G] Magamo:
The team meets on IRC -- irc.freenode.net #apexqtmo, feel free to stop on by.
[Samsung Galaxy S Relay 4G] misteropinion:
I would call. ¡no bueno! on the 0202 nightly. I am not at home so I can't get a logcat via adb, but it looks like L3 freezes as soon as you try and do something, I had to restore.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
agreed...flashed last night and on cyanogen screen at startup if you try to select it freezes up immediately...reverted to earlier release...Also working on a few goodies and surprises for you guys
[Samsung Galaxy S Relay 4G] robuser007:
I'm running 02/02 without problems, didn't try 03/02 because of the bbqlog for the next nightly: revert jit.
[Samsung Galaxy S Relay 4G] misteropinion:
Where are you seeing that? I don't see anything about jit here http://www.cmxlog.com/11/apexqtmo/ or when I look in the changes on the Infernix Jenkins.
[Samsung Galaxy S Relay 4G] robuser007:
It's an android app (bbqlog)
[Samsung Galaxy S Relay 4G] :
Anybody here manage to get Google Wallet Tap and Pay to work with either the official nightlies or a TeamApex build?
[Samsung Galaxy S Relay 4G] mazak23:
USB host.

I know that MHL is not functioning in 11.

But anybody tried usb host ?

Cheers
[Samsung Galaxy S Relay 4G] wedg11383:
I was wondering if anyone was still having overheating issues. I clean install every official and unofficial nightly when they come out and still everyone gives me heating issues. Even with no wifi or bluetooth on, if I just browse the internet for a few minutes, the phone gets hot in my hand. At the same time, the battery life is pretty good and I can't identify any apps using excessive cpu or network. Also if I have music playing from any source and I lock the screen, I have issues. Opening and closing the keyboard while on the lockscreen consistently freezes the phone but things like music playing and tethering continue to work for a few minutes but the display is frozen, then it reboots. I can provide any logs needed. I appreciate any feedback.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
have you tried using an app like wakelock detector to see what may be causing it...i use that app to find them and disable service to disable them...both free in play store
[Samsung Galaxy S Relay 4G] wedg11383:
Yes I have used those and Greenify to track down everything going on with the phone. When I'm not using it, it definitely goes to deep sleep and I get 1-3% drain an hour and it is fairly cool. The second I touch it though it starts burning up but no tool shows any process running out of hand. The built in battery usage usually shows display as the main battery drainer but I have it on the lowest setting. The battery doesn't really drain badly from use either, its just the extreme heat that it starts producing. I also have tried swapping batteries. The battery itself remains fairly cool, it's the cpu that starts blazing. It behaves like this on a fresh install without even any gapps flashed.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
this definately sounds like a kernel issue to be honest...mine luckily hasnt been overheating at all on this rom or my beta build...will deffinately be reviewing code in the kernel to see what it might be...also some performance apps for example trickster mod or kernel tuner may cause these issues as well...has on a few of my previous devices
[Samsung Galaxy S Relay 4G] dillalade:
Given the Jenkins builds are for dev purposes only. Has anyone been successful in building a CM11 rom as per nighlies but with the necessary ApexQ delights - typically mpdecision/thermalD etc. for that leaps & bounds of better battery performance. Seems a shame, the official nightlies i find drain my battery fairly quickly.

I would do the do if I had a dedicated machine to push out builds.

Thanks for the efforts TeamApexQ
[Samsung Galaxy S Relay 4G] REV3NT3CH:
My beta build comes out awesome...will be giving updates shortly
[Samsung Galaxy S Relay 4G] dillalade:
Cool.. Will you be publishing the build for public consumption at all
[Samsung Galaxy S Relay 4G] REV3NT3CH:
Yes...besides this build I'm also building a kernel that should definitely fix battery drain...I should have some work uploaded next few days for everyone to enjoy
[Samsung Galaxy S Relay 4G] dillalade:
Be very interested to give that a try. Thanks in advance

Currently not enjoying CM11 official nighlites compared to TeamApexQ's unofficial CM10.2 builds with all the added potency they've managed to incorporate.

Even a ApexQ version of "CM10.2 STABLE" would be a wonderful interim ROM for those waiting for a fully functional (all the CM bells & whistles) CM11 ROM.
[Samsung Galaxy S Relay 4G] REV3NT3CH:
To put it lightly the build I'm releasing has a very nice set of bells and whistles that will be very enjoyed I'm sure. My only concern mainly now is kernel as by what I believe some makefile optimizations were not done properly or at all...be it official or not. Where it runs as I have it now is very stable...just working on very small kinks at this point
[Samsung Galaxy S Relay 4G] Magamo:
TeamApexQ is announcing our new release:

v4.4.2_0001

https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/HypnoToad-4.4.2_0001-apexqtmo.zip
[Samsung Galaxy S Relay 4G] dillalade:
Awesome. Downloading.

Any further information regarding this ROM? :sly:

Thank you for the release :thumbup:
[Samsung Galaxy S Relay 4G] Magamo:
All such information is in the OP.
[Samsung Galaxy S Relay 4G] Guiyoforward:
This looks great.two questions:

1- Any feedback on battery life?

2-can this be dirty flashed on top of cm 10.2.1?

Thanks!
[Samsung Galaxy S Relay 4G] misteropinion:
I flashed it on top of the 0207 nightly with a cache format and a dalvik cash flush. Launcher3 crash-looped when it booted, but I put the settings button in the quick bar, so I could get at it and clear launcher3 data, which fixed that problem. Otherwise, it boots, and it sees networks and such. Beyond that, I cannot say at this time.
[Samsung Galaxy S Relay 4G] robuser007:
with tweaks by TeamApexQ that are certified for the Relay: wich tweaks do they mean ?

Interface tweaks (different from the dialer) ?

My battery use is pretty decent in standby: around 10% for 10hours (using cyanogenmod ) 06/02/2014 (greenified, but not the play services).
[Samsung Galaxy S Relay 4G] Magamo:
Mostly in kernel mpdecision and full AVS -- The selection to stay with Launcher3 over Trebuchet. AOSP dialer. Those are the main tweaks.

This likely has to do with the fact that while CM is starting to ship a customised launcher (Trebuchet) internally, it's still calling itself 'Launcher3' which means as they change data structures, it becomes incompatible with the AOSP Launcher3. My recommendation? If flashing over a recent CyanogenMod 11 nightly, then install a third party launcher first so that you can clear the settings on Launcher3, then switch back to it. Other than this recommendation. We are not going to support dirty flashing this over CM-11 nightlies. We will only support dirty flashing this over other HypnoToad builds, or CM-10.2.X stable.

1) I'm getting about 50 hours per charge on average with moderate usage and no airplane mode

2) Yes. We specifically set it up to be able to dirty flash over top CM 10.2.X
[Samsung Galaxy S Relay 4G] HippoMan:
Does anyone know of a version of TWRP which works on the Galaxy S Relay 4G, in the first place? I haven't even been able to find a TWRP version which works on this device.

Thank you in advance.

.​
[Samsung Galaxy S Relay 4G] HippoMan:
Never mind. Something better than TWRP.

Never mind.

I found something for the Galaxy S Relay 4G which is even better than TWRP, IMHO: CWM Advanced Edition by PhilZ.

Go here to check it out.

.​
[Samsung Galaxy S Relay 4G] slartibartfast42:
I'm having trouble with this ROM. I am clean installing. The problem is the setup wizard. If the setup wizard runs, it crashes as soon as you pick a language. The phone won't let you do anything. If the wizard doesn't run, like because you installed the rom and gapps separately, the phone seems OK, except for no set up wizard. I'd have to set up everything manually. What's going on?
[Samsung Galaxy S Relay 4G] terinfire:
Depends on which version you're running -- you need to include that. Most certainly, it's probably something to do with the WiFi.

So, devs, as of the 2/10 M3 build, it is looking REALLY nice. Per the issues that I've had before (different things potentially killing the kernel), I've noticed now that most of them only occur now when WiFi is on. Will try to post a few last_kmsg's before EOD.

EDIT: Will post the actual message, but kernel panic because: not syncing: L1 nonrecoverable cache error detected

Will try lowering the CPU frequency to see if that helps (apparently some folks with mako had this issue?)
[Samsung Galaxy S Relay 4G] burritoboy9984:
I was just about to post the same thing. No matter what I do (tried 3 different gapps versions, the one in the first post is for 4.4.1, not 4.4.2), I get "Unfortunately, Setup Wizard has stopped." and I can't go any further. Does anyone have the rom linked on the first post working? Any advice?

Edit: Here is the link to the 4.4.2 gapps.
[Samsung Galaxy S Relay 4G] terinfire:
Here are some dumps:

https://dl.dropboxusercontent.com/u/20940511/m3.20140210.1300.txt

https://dl.dropboxusercontent.com/u/20940511/m3.20140210.1330.txt

https://dl.dropboxusercontent.com/u/20940511/m3.20140210.1415.txt

https://dl.dropboxusercontent.com/u/20940511/m3.20140210.1420.txt
[Samsung Galaxy S Relay 4G] Magamo:
We acknowledge this problem and are working toward a solution. I have posted a patch that will fix this problem temporarily. The root of this problem stems from the fact that we are using a CyanogenMod base, but do not build the CMAccount apk. The following is a CWM flashable copy of CMAccount.apk. Flash this after the HypnoToad Image and the setup wizard will work properly for now. After setting up the phone initially, feel free to remove the apk from /system/app.

https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/CMAccount-11.0-M3.zip

Though if you can get some logcats of when this crashes, we would appreciate it.
[Samsung Galaxy S Relay 4G] chuckiev79:
I just want to first say what a great job the devs have done on this rom, and the mpdecision is a huge advantage over the official cm builds. The difference, at least for me, has been day and night. One small question, which i presume is most likely a no, but feel inclined to ask anyway. Is there any chance for icon pack support on this rom? Im currently using the unicon xposed module for this but keep getting fc's on launcher 3. And i have cleared the data on it several times to try and prevent this.
[Samsung Galaxy S Relay 4G] robuser007:
How do you notice that ?
[Samsung Galaxy S Relay 4G] chuckiev79:
Just from how much battery life I had left at the end of the day. However I'm not using greenify ...yet
[Samsung Galaxy S Relay 4G] dillalade:
I'm on a full wipe install of Hypnotoads release.

Running well thus far.

Something i'd noticed on previous nighly or jenkins builds which persists on this rom also is:

Performance, Processor, Minimum Frequency.... whatever i set this too, usually 486mhz in my case - the system doesn't adhere my setting and always is stuck at Minimum Frequency 1134mhz.

Unsure if this is just a UI glitch that illustrates 1134mhz as minimum as a mistake or if the system is indeed sticking its Minimum freq at 1134mhz.