yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] crayz9000:
Front-facing camera colors are still blue-tinted in video mode only with nightly build 132.

Also, I can repeatably crash Gallery when switching from video to still while on the front-facing camera. Toggling video to still on the main camera does not produce the crash.

Steps to reproduce:

1. Start the Camera

2. Toggle from main to front-facing camera

3. Switch from still to video.

4. Switch back to still

The Camera will close, and the following error will appear: "Unfortunately, Gallery has stopped."
[Samsung Galaxy S Relay 4G] Desertman123:
So I'm flashing CM onto my friends Relay and I got CWM and SU no problem but when I flash the CM zip and reboot it, it doesn't boot into CM, the screen stays black. This is my first time working with a non HTC phone so is there anything I'm missing specifically regarding Samsung devices? I restored the backup and the phone runs fine but its just CM not working. Anyone got ideas?

Sent from the glorious One XL on CM 10.1
[Samsung Galaxy S Relay 4G] :
Try 133.

Bug list:

FFC still force closes. Temporary workaround: switch to front camera before returning to still image mode.

Compass still sucks. We turned the orientation on it around again. This means calibrating it will be necessary before use. The way we had it was great uncalibrated but as soon as some kind of calibration took place it was actually off.

You tell me.
[Samsung Galaxy S Relay 4G] :
Did you remember to wipe after flashing?
[Samsung Galaxy S Relay 4G] Desertman123:
I factory reset before flashing then wiped cache and dalvik after

Sent from the glorious One XL on CM 10.1
[Samsung Galaxy S Relay 4G] kilr00y:
see if your downloaded files are fine (md5)..

did you format system before and/or install google apps afterwards? cm backs up previously installed google apps and restores them afterwards..

maybe you're stuck with an old piece of code there...

EDIT: nah.. wait.. it doesn't... it only does when you had cm installed before already.. you said that it's your first flash... boy.. night was too short...

either way.. formatting system before flashing might be something to try out either way.
[Samsung Galaxy S Relay 4G] Desertman123:
I'll try re downloading everything and doing a fresh wipe.
[Samsung Galaxy S Relay 4G] kilr00y:
hint: you'll have to "adb push" push files or put them on the sd directly as usb storage doesn't work in recovery... at least in none i've tried..
[Samsung Galaxy S Relay 4G] Desertman123:
Yeah I noticed USB storage didn't work when I first tried flashing it..

Formatting /system worked, thanks for your help!
[Samsung Galaxy S Relay 4G] janejunx:
I'm still getting no screen when waking with the home button sometimes (the back/menu buttons do light up when this happens). It requires turning "off" the already off screen with a power button press and then hitting power again for the screen to come up.
[Samsung Galaxy S Relay 4G] Jason78729:
Also have this randomly occurring.
[Samsung Galaxy S Relay 4G] icnocop:
Hi.

Thank you for cm-10.1-20130511-NIGHTLY-apexqtmo.zip.

For some reason, the mic is very low for the other party to hear during a call.

Any ideas on how i can increase the mic volume in calls?

I installed Smart Voice Recorder and disabled the device's auto gain control (AGC) and set the gain factor to 226x and the mic level tests work great but only in that app.

I installed HD2 Mic Control but it says "Your device is missing /proc/mic_level which is required to adjust mic levels..."

Can /proc/mic_level be incorporated in this rom?

Should I create an issue on github's TeamApexQ/apexq/issues?

Thank you.
[Samsung Galaxy S Relay 4G] :
That's a kernel hack for the HD2

http://dl.xda-developers.com/attach...c920d9/51908bec/7/0/3/6/2/2/diff_mic_gain.txt

In theory it could be adapted for our phone but perhaps we could just adjust the mic up a notch or two.
[Samsung Galaxy S Relay 4G] icnocop:
Thank you Nardholio,

infernix actually just created issue #29: "Mic levels too low".
[Samsung Galaxy S Relay 4G] :
Infernix turned mic bias in calls up a notch. Enjoy. We have not adjusted it for other use cases.
[Samsung Galaxy S Relay 4G] MTMTE:
Just flashed build #137 and its working great. THANKS!

Real quick, the app "Light Flow" that I know a bunch of people use to control the LED crashes on load.

I found the solution.

Before opening the app for the first time go into Settings>Accessibility> and under Services select light flow and switch it to "On". I had to do it twice before it took.

Next open the app. It should load up. If it asks for root permission be sure and give it.

If you open it before enabling it in Accessibility you'll have to reinstall and do it.

Typically upon the first load it will instruct you do do what I mentioned above. However it locks up before that.

After that it works great with build #137
[Samsung Galaxy S Relay 4G] stephenclower:
Would there be any way to revert this change? People I call using the regular earpiece now complain that I'm very loud, while other apps which take mic input aren't loud enough.
[Samsung Galaxy S Relay 4G] gtmaster303:
Lol, I think he is serious. You'd be surprised the kind of users a device can have. The old Captivate Glide had a blind community of about 10 or so users. All kept badgering dev to crack talkback bugs on the latest CM until it was finally solved after much effort. Not worth the time and effort to cater to the minority, but that's just my opinion
[Samsung Galaxy S Relay 4G] gee one:
Well, that's the beauty of open source- you can change what you don't like.
[Samsung Galaxy S Relay 4G] :
What other apps are you having trouble with?
[Samsung Galaxy S Relay 4G] icnocop:
Maybe we can compare dB levels; please see a picture of my comparison in Issue #29 on the github repository.
[Samsung Galaxy S Relay 4G] stephenclower:
I'm glad to see biggotry is alive and well here. Seriously, I know it can be frustrating especially when you deal with folks who do nothing but gripe all the time (I put up with such types all day long at my job), but at the same time the hackability of Android is what won me and a lot of other visually impaired users over to the platform. If projects like CM weren't around, I'd have abandoned ship long ago.

And, correct me if I'm wrong, but the Talkback problem was Google's own fault and had nothing to do with CM.

Steve
[Samsung Galaxy S Relay 4G] :
Steve, what other apps are you having trouble with that the mic is too quiet? And when you say normal voice calls are too loud, you mean when you hold the phone normally to your face, is that correct?

Also, thus far we've had one report it was too low, and we now have a report its too high. More opinions are needed. So chime in. And if we figure out a way to make it easily adjustable we can. The file in question is a simple text file, we could even tweak the use cases for special use cases (pardon the pun) and provide a flashable zip for those folks.

I do wish this phone had more visibility, those are the kinds of mods independent devs would be making themselves on a phone with a larger community.
[Samsung Galaxy S Relay 4G] stephenclower:
Nard,

That's right; I was holding the device up to my head. I rarely, if ever, use the speaker phone. Which file needs adjusting? I'm happy to tweak my local copy to see what values work best. I assume, also, that the device stores different gain levels for phone audio versus everything else?

Thanks,

Steve

---------- Post added at 11:30 AM ---------- Previous post was at 11:24 AM ----------

The Audioboo Two beta (available on the playstore) doesn't appear to capture mic audio when using the CM-10.1 builds, but it can on stock. If it's an app issue, I can hand it off to them for investigation.

Steve
[Samsung Galaxy S Relay 4G] crayz9000:
Black screen lockup on #137

So, I flashed build 137 and all has been well so far... until today, when after the other end of a phone call hung up, I pulled the phone away from my ear and the buttons lit up, but the phone's screen did not turn back on. The backlit buttons timed out, and pressing the Home button again lit them up, but the screen remained off. So I'm wondering if it's related to the black screen of death that plagued earlier builds.

Is there any more information I can provide to help track this one down?
[Samsung Galaxy S Relay 4G] janejunx:
I'm having the same problem, when waking up my phone via the home button. I don't think it ever went away for me.
[Samsung Galaxy S Relay 4G] gee one:
It happened once for me and I did a battery pull. I wasn't near enough to a computer to see if anything was actually running or even if the phone would respond via adb.

sent while running with scissors
[Samsung Galaxy S Relay 4G] janejunx:
Mine was fine by pressing the power button to go back into "sleep" and then pressing the power button again to have the screen come on. I've never not been able to do this/haven't had a full-on system freeze.
[Samsung Galaxy S Relay 4G] stephenclower:
No MTP

Greetings,

After the nightlies from 5/10, I'm finding that if I boot the phone, I can connect it to the PC, it shows up as an MTP device, and all is beautiful. If I then place it on my USB wall charger over night and then try reconnecting to a computer in the morning, it begins charging but never registers as MTP on the PC. I've tried four different USB cables, two machines, and all the ports on each with identical results. Are there any useful logs I can send you guys to help troubleshoot this one?

Steve
[Samsung Galaxy S Relay 4G] crayz9000:
I can't replicate the problem on my phone with build 137 (5/13). Going to update to 142 and see.

What USB wall charger are you using? I used the original Samsung one.
[Samsung Galaxy S Relay 4G] gtmaster303:
To elaborate, one user (claimed group of 5-10) single-handedly slowed down development of the device for his talkback issues that no one else cared for. I commend the devs for helping the guy out, really I do. But there were essentials as bugs such as bluetooth, video camera, etc. that I believe should have a higher priority, considering how many more people use them. It's an opinion, so please don't take it personally. But I digress...
[Samsung Galaxy S Relay 4G] stephenclower:
No worries; I don't expect (or desire) any special treatment, just so long as devs don't go out of their way to purposefully put access roadblocks in the way of folks who need adaptive technologies. Besides, you all do this on your own time, so making demands (disability or no) is unacceptable. Imho, I agree that bluetooth and video issues should take higher priority as well.

On a related note, where's the best place to donate so all the devs can get something for their work?

Steve

---------- Post added at 10:18 AM ---------- Previous post was at 10:14 AM ----------

I'm using that one in addition to the charger which came with my retired G2. I'll flash up to the current nightly and see if it yields any better results. Would sure love a changelog for some of these builds.

Steve
[Samsung Galaxy S Relay 4G] crayz9000:
Well, build 142 also works for me. Switching the USB cable back and forth from the charger and the computer and Windows 7 x64 recognizes the phone every time. I use Ubuntu at home, will have to try there as well.

What OS are you running?
[Samsung Galaxy S Relay 4G] gtmaster303:
I am wondering the same as well

Nard, what's the deal?
[Samsung Galaxy S Relay 4G] stephenclower:
Win 7 X64 as well. All of my non-Windows boxes are virtual. I'll flash today's build, let the phone charge over night, and see what happens when I come into work tomorrow.
[Samsung Galaxy S Relay 4G] infernix:
The problem with the mic volume seems to be a mic bias problem. The mic gets a certain voltage applied in order to pick up a certain sensitivity.

It could very well be a different board revisions. Can everyone (and especially with mic level issues) do a:

grep Revision /proc/cpuinfo

And post here?

Thanks.
[Samsung Galaxy S Relay 4G] Jason78729:
Revision : 0007
[Samsung Galaxy S Relay 4G] gee one:
+1 for 0007

Although I don't have any issues that I know of, but then again, I don't talk on my phone that much.
[Samsung Galaxy S Relay 4G] wedg11383:
Revision : 0007 as well.
[Samsung Galaxy S Relay 4G] croogrog:
0007 here too
[Samsung Galaxy S Relay 4G] icnocop:
Revision: 0007

I am the user having the low mic volume issue (issue #29).

I hope the revision has been identified as the problem because that's one step closer to solving it! ;)

Thank you very much!
[Samsung Galaxy S Relay 4G] dillalade:
+1 0007 here too on build #142

(No mic issues, I mean nobody on receiving end has complained about low levels yet.)
[Samsung Galaxy S Relay 4G] crayz9000:
Revision 0007 here as well.

Since the updated mic gain levels were applied to the nightly builds, other callers haven't had any trouble hearing me, but they are now complaining of high-pitched background noises coming in too loud.
[Samsung Galaxy S Relay 4G] stephenclower:
Nuts. Same results. If I pull the battery and restart the phone, MTP returns again.

---------- Post added at 11:58 AM ---------- Previous post was at 11:55 AM ----------

I'm also getting 0007.
[Samsung Galaxy S Relay 4G] aawillma:
Revision 0007 here. I haven't been told of low level issues, then again I tend to talk pretty loud. I do get reports of an echo every 5th call or so. Not enough to bother me or the other caller, I don't use my phone much for talking either :D
[Samsung Galaxy S Relay 4G] gtmaster303:
Yep, same as everyone else 0007

But the only time I've had trouble with the caller hearing me, was when the caller had me on their car bluetooth system and me on the other end with the Relay.

Otherwise, all other calls have been ok
[Samsung Galaxy S Relay 4G] misteropinion:
I flashed from 139 to 145 this morning and I get a bootloop (dont get to the cm spinner, just black screen and occasional SAMSUNG, so fairly low level). I'll try and get logs. I tried a battery pull, formatting /system and reflashing, same dealio. I recovered back to 139 and it's all good.
[Samsung Galaxy S Relay 4G] gtmaster303:
Running nightly from 5/16 and everything runs really well. Only issue to report is the DSP manager distorts music if you set the virtual room type to anything except studio. Music crackles with any bass and sounds really distorted

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] misteropinion:
I agree about the DSP, but I figured I wouldn't bring that up until the 3.4 kernel was out.
[Samsung Galaxy S Relay 4G] gtmaster303:
Yea it's not a deal breaker by any means. But I listen to music on my phone regularly. Therefore I thought I would bring it up... I actually like the dsp manager out of all the equalizer apps I've tried. Very simple, but effective

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] dillalade:
Anyone Upgraded Talk to Hangouts?

Tested video call on Hangouts (Nightly 16th May build) and recipient is not hearing me. Tried 2 video calls to different contacts and same issue. But I can hear them fine.

Maybe it's another audio Mic issue in our CM rom (considering I was receiving audio from the galaxy s2 video caller) or even an issue with Hangouts.apk.

Anyone else noticing this?
[Samsung Galaxy S Relay 4G] gtmaster303:
I know our video camera isn't the greatest, but I just tried taking a video of a graduation ceremony and this is what I saw...

Video recording is abysmal

Yea, it's the highest setting, no there's no crap on the camera lens

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] mikeybot:
Just had a weird thing happen.

I'm on the build from back on March 9 and had my phone slowly decrease performance to the point it wouldn't wake. Battery pull brought up the Samsung logo, then nothing. Cleared cache in recovery, same result. Tried to restore, froze on md5 check. Finally just reflashed CM and the phone is back on.

I'd love to post a log if possible, but I'm not sure if/where it'd exist.

The only recent system changes I made were to freeze one of the calendars (I have 2 google ones for some reason, I froze the older) and I froze twitter since I don't use it, but that doesn't keep it from starting up constantly

Sent in the booze cask around the neck of a St. Bernard
[Samsung Galaxy S Relay 4G] orange808:
I could be wrong, but I'm sensing some short tempers. This rom is experimental and in development. :)
[Samsung Galaxy S Relay 4G] gtmaster303:
:) Yes you're wrong. I'm just trying to be objective and to the point. Rom overall is great and quite stable, as I've said before

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] misteropinion:
Updates update: Nightly 146 does not boot loop where 145 did.
[Samsung Galaxy S Relay 4G] osnapitsjoey:
any hope for photosphere? btw i love you guys for making this all possible, and do you have any fix for the insufficient storage message i keep getting when i sure as hell have enough space to download more apps?
[Samsung Galaxy S Relay 4G] :
The file in question is /etc/sound_soc_msm_2x. Word of warning, it's 6000 lines long. The call input is on line 3158.
[Samsung Galaxy S Relay 4G] :
I am not accepting donations at this time and I don't know if any of the other devs are.
[Samsung Galaxy S Relay 4G] dillalade:
Anybody else able to replicate this, or is it that I'm in need of a full wipe reinstall.

On further test, I can hear myself on my device as a delay, but the recipient cannot at all.

FYI - Skype works well, as I use that daily (both video and voice calling.)

Perhaps it is then Hangouts app not playing nicely on our device.

:thumbup:
[Samsung Galaxy S Relay 4G] crayz9000:
So I have somewhat of an update on my Bluetooth phone audio issues.

Whenever my car's bluetooth connects to my phone, the first time it connects (since the last reboot) the audio works correctly. If it disconnects and then reconnects (like what happens when I leave my car for a few minutes and return) the phone audio stops working, and all attempts to make a call over BT audio simply result in a loud "pop" as the audio switches to BT (except it doesn't switch), followed by another loud "pop" when I switch the call audio back to the phone.

Rebooting the phone allows calls to immediately work the instant that Bluetooth is reconnected. The same symptoms repeat instantly the next time that my phone unpairs from the car, or is toggled off/on at the phone.

These symptoms have stayed consistent since the first nightly build I tried, which I believe was 20130405-experimental. I'm now on 142.

Should I go ahead and open a bug for this on the GitHub tracker?
[Samsung Galaxy S Relay 4G] killkillkill:
You do realize that the preview video is at a much lower resolution than the actual captured video, don't you? The preview video is far lower resolution than even the screen is capable of. Don't use the preview to gauge the video quality.

Also... what do you expect from a phone camera?

---------- Post added at 01:52 PM ---------- Previous post was at 01:48 PM ----------

Photosphere works fine, but remains binary only. Can be installed from here: http://xdaforums.com/showthread.php?t=1966426

... however, it will break video recording.

Once you play with it for a bit, you will notice that it is just a gimmick. Not practical for anything at all.
[Samsung Galaxy S Relay 4G] gtmaster303:
So the actual video is supposed to come out fine? Because I played the video back on the phone, and it looked exactly like the recording. Do you mean I have to play it back on another device to view actual quality?

Honestly I don't expect much from a camera phone...

If the preview is a lower resolution, why do still pictures (both preview and actual picture) come out so much more clearly?

With such a blurry preview, I could barely see what I was recording

Is it just me with these problems, or can anyone else confirm? If so, I'll wipe and reflash
[Samsung Galaxy S Relay 4G] crayz9000:
I can confirm that I'm seeing the same blurry previews. However, I've tried to record several videos, and it's apparently not saving the videos -- they don't appear in the Gallery and they don't show up when I hook up to my computer.

Secondly, I know for a fact that the stock firmware showed video previews at screen resolution, which I think is the point that gtmaster303 is trying to make.
[Samsung Galaxy S Relay 4G] killkillkill:
Did you set it for 1280x720? Or are you using 640x480?
[Samsung Galaxy S Relay 4G] gtmaster303:
No as I said before, my camera is at the highest settings and the lens is clean. 5mp for stills and 720p for video.

Trust me, I'm not the kind of person to waste someone's time if I didn't think there was a genuine issue.

I've attached some screenshots of what the phone looks like in either mode. Video is clearly much more blurry than camera stills

I've also noticed that video recording doesn't really work at all. The app crashes or freezes when I try to stop/start recording. Whatever video that did manage to record is saved, but is not playable on the phone. Haven't tested whether the file is playable on the computer

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] kilr00y:
uhm.. what build are you on? i'm on 147 and i just tested it. works fine. preview as well as the actual video..

camera preview though hangs after changing resolution in the settings and crashes if i attempt to record (video).

but changing settings -> leaving app -> restaring app -> record works fine.

no issues with still camera.
[Samsung Galaxy S Relay 4G] misteropinion:
Recovery updates?

Are the recoveries with the nightlies tracking the TWRP tip or is that static?
[Samsung Galaxy S Relay 4G] janejunx:
Just tried across all camera apps on my phone, and I can't recreate the issue. Nightly 147, updated to the newest modem firmware, running TWRP.
[Samsung Galaxy S Relay 4G] gtmaster303:
Running nightly 142. I'll try flashing to a later build then

Thanks for the input guys

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] stephenclower:
That's a shame. In either event, you've got my support. I'll try fiddling with the mic levels over the weekend while I'm on vacation and see if I can find an optimal setting.
[Samsung Galaxy S Relay 4G] crayz9000:
Confirmed video preview / not saving is a build 142 issue. Build 148 has correct video preview and MP4s are saved in DCIM\Camera folder.
[Samsung Galaxy S Relay 4G] gtmaster303:
At least I know I'm not hallucinating now lol

Thanks for the confirm

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] HippoMan:
Agreed. A re-up is definitely needed.

I've now managed to successfully download this on 2 different machines.

In both cases, the MD5 sum of the downloaded file matched the MD5 sum

listed on the goo.im site. However, the zipfile is corrupt.

MD5sum listed on goo.im site: 5a1cd5585540a820b3883da4f8cce864

[COLOR="Blue"]% md5sum cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip [/COLOR]
[COLOR="DarkRed"]5a1cd5585540a820b3883da4f8cce864[/COLOR] cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip
[COLOR="Blue"]% unzip -l cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip[/COLOR]
Archive: cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip or
cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip.zip, and cannot find cm-10.1-20130307-UNOFFICIAL-apexqtmo.zip.ZIP, period.
[Samsung Galaxy S Relay 4G] gee one:
Re: [CM-10.1] Galaxy S Relay 4G

Agreed... I get the same md5sum as you and unzip -tv yields some errors.

Edit: better yet, time to build from source

sent while running with scissors