yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] dillalade:
Found what was causing this odd behaviour.

It's a trebuchet setting, that when ticked will cause the behaviour I detailed above. When turned off the problem is rectified.

Simply turn 'OFF' System Settings > Launcher > Homescreen > "Fade Side Pages"

Nice & simple (perhaps nobody saw this issue, as the fade side pages is ticked off by default I believe.)

Hope this helps someone or the team in general to diagnose this quirk.

:thumbup:

The very few things I've noticed that require attention:

SMS black (selectable but doesn't action.)

Wifi-direct (settings in wifi page, selectable but the following screen is grey.)

MHL (worked in CM9 but without Audio)

A2DP (music over Bluetooth)

[This list, is not to taunt devs to press on and provide solutions, rather to notify those that maybe contemplating the switch over to CM10.1 as to what to expect.]

I honestly can't find anything other then these 4 nigly elements, but once targeted, this device will be beastyyyyyyyy !

As a user, personally the only features I'm really sacrificing is A2DP & then MHL.

Otherwise, a definite daily driver as far as stability goes. Then performance, well it's leaps & bounds beyond stock & cm9... project butter shines through with a hasty/snappy speed.

Big Thank you to the team involved in this effort, shocking progress!

(Running jaguarAudio build from infernix.)
[Samsung Galaxy S Relay 4G] TheDigitalBug:
so why are networks shown twice? see screenshot
[Samsung Galaxy S Relay 4G] gtmaster303:
If it works properly, does it matter?

Sent from my Captivate Glide
[Samsung Galaxy S Relay 4G] tany.jags:
People...thinking to switch

Which CWM version are you using with these builds...i have the one which only reads ext-sdcard and makes nandroid backups dated 1980!....if there is any better version please point me to its flashable zip....
[Samsung Galaxy S Relay 4G] misteropinion:
Problems with #87

FWIW, yesterday's build (#83, before the broken ones) would have Phone die three times (while still ringing) before you could answer. Today's build (#87, first after the broken ones) you can't be called (straight to VM) but you can call out just fine. I captured logs but ... I recognize no phone activity. Tried clearing Phone's cache and data and rebooting, same result. I'm going to try flashing back to one where I knew Phone worked. Otherwise, I'll try a wipe and a reflash to today's build. *sigh*

Catlog attached.
[Samsung Galaxy S Relay 4G] misteropinion:
The problem did not move to my old G2, so I went back to #83, where it was still broke, which points to hardware, but then the problem magically cleared, and I flashed directly from #83 to #88 and it's still clear. So, I dunno, I'm mostly blaming T-Mo, but I'll have to keep an eye on the hardware now.
[Samsung Galaxy S Relay 4G] TheDigitalBug:
Just because it's running properly doesn't mean there aren't any side effects such as elongated time to register or network or data not working when switching
[Samsung Galaxy S Relay 4G] b3orion:
Me Thinks I Brokened it...

Well, this is just my luck.

I am coming from the CM9 ROM, finally to JB. I did a backup and full wipe. I then flashed build #88 and the applicable Gapps.

Everything installed fine, downloaded all my apps again, then restarted my phone. Then the problems start.

Now, every time my phone turns on, it flashes the Samsung logo for about one second, then a blank screen.

No download mode, no recovery mode, no nothing!

All I did was install applications! :mad:

Has anyone else had this issue, or is my phone just unlucky?

I can't even restore it via Odin...

Any tips? Can't even get logs as the phone doesn't show up in adb...

What could have happened from installing applications from the market to do this?!

EDIT:

It seems as though the problem is not with the ROM, but with the DPI modification app I downloaded...LCD Density Modder Pro.

I suggest that anyone running Android 4.1+ not use this, as it corrupted the Relay, and G2 as well. Thankfully the G2 was still able to boot into Recovery mode so I didn't kill it completely.

Also, I was able to get the relay into recovery mode... finally. I had to leave it for about an hour, in it's blank screen mode. Then I pulled the battery and tried again. I was so happy to see the recovery screen!!
[Samsung Galaxy S Relay 4G] :
https://www.dropbox.com/s/iguotyzti6vi3k3/2013-04-16 14.51.50.png

It boots, that's about it. Doesn't even know how much battery life is left (which is why there's a big question mark). No I don't know when it will be done. Just thought I'd share.
[Samsung Galaxy S Relay 4G] dillalade:
New Kernel.

Niiiiiiiiiiiice :thumbup:

---------- Post added at 01:07 PM ---------- Previous post was at 01:04 PM ----------

[/COLOR]On a separate note, is anybody experiencing Partial WakeLocks - typically MediaScannerService (munching at around 80% battery.)

Using BetterBatteryStats and still diagnosing what the hell it's constantly scanning (on every boot it continues to re scan.)

It seems unnecessary.

Watchdog Lite also reports 'Android Media Process' to be hogging CPU a lot (perhaps it's something corrupt on my SD card, though wanted to share, as others may be having this problem too - however the problem is intangible - but it sure is munching my battery.)

EDIT:

So with some googling I've discovered a way of switching the MediaScanner Off & On at will (via Terminal commands.)

Disable Media Scanning:

su

pm disable com.android.providers.media/com.android.providers.media.MediaScannerReceiver

Enable media scanning:

su

pm enable com.android.providers.media/com.android.providers.media.MediaScannerReceiver

I saved these in Gscripts (app from market) - and created Homescreen shortcuts for each of these 2 scripts.

(So that I can Disable and re-Enable when I want - typically I guess you'd only like to re-Enable for when you've taken new photos and want them visible/usable in Gallery etc.)

I gather this is a temporary solution - and maybe a solution for something corrupt on my SDCARD rather then with the ROM itself - BUT for if it's not the case of corrupt media files on SD, and perhaps a general issue that others are receiving, then I hope this method provides for some success for other users & most importantly some insight provided to the developed here.)

I hope to receive some better battery results if anything.

[This all came for the desire to diagnose my Battery Stats, as I sensed something was munching my battery, I hope I have homed into something regarding MediaScanner at least for myself.]
[Samsung Galaxy S Relay 4G] misteropinion:
Has anyone experienced FCs of Phone while the device is in landscape? I'll get a logcat, it's pretty reproducable. I've also seen a situation where I'm listing to Pandora, screen is off, Pandora stops playing and the lockscreen is flickering. If I change the orientation it usually stops. This is harder to reproduce, but has happened several times. FWIW, that's Pandora with lock screen controls turned on (and it may have happened without Pandora as well, but I can't swear to it) and pattern unlock.

Battery life contiunues to be abysmal. Has anyone had any luck with the 4100/4200 mAh batteries with the hunchback?
[Samsung Galaxy S Relay 4G] killkillkill:
How many nandroid backups do you have?

The media scanner will go through ALL of your files and catalog them for MTP, even "non media" files.

Upstream CM has implemented a workaround, similar in practice to ".nomedia" files.

Find out which of your directories contain the largest number of files (and you don't need/want to access via MTP), go into that directory, and type "touch .noscanandnomtp". That directory and all its subdirectories will now be excluded from media scan until you erase the .noscanandnomtp file. For example; "cd /extSdCard/clockworkmod; touch .noscanandnomtp".

Just go over your sdcard and exclude all the directories you don't want to have scanned, then you'll find the media scan completes very quickly following bootup. You should also go over your internal fake-sdcard.
[Samsung Galaxy S Relay 4G] klokwyze:
These Nightlies sound pretty scary. Think I'll stay away... I guess I got lucky w/ my current build because I only have a few minor problems (echo on receivers end, minor flakiness w/ tethering/hotspot) Using the last 10.1 Stable. Any plans on another stable in the future w/ bug fixes or feature additions?
[Samsung Galaxy S Relay 4G] dillalade:
Oh Nice find :thumbup:

Just read up on this commit.

True, I do have a lottttt of CWM backup dirs all over the phone (not good housekeeping :p)

I may give this a go later today, as it stands, my (somewhat primitive) method with the Terminal commands seems to have literally doubled my battery life so far.

But what does this mean " touch .noscanandnomtp"???

Type that where?

Don't you mean to just create 'maker file' in that name (much the same as we used to do with .nomedia maker files)?

Just little confused with the " touch .noscanandnomtp " touch part you wrote?

Thanks

SGR-4G on CM10.1 {JB}

---------- Post added at 09:53 AM ---------- Previous post was at 09:45 AM ----------

It's really not that scary.

However may I suggest you use the 'Infernix-JaguarAudio' build I previously pointed out in this post http://xdaforums.com/showthread.php?p=40173101

It's utterly stable, smooth, reliable and fast!

(Whack in the above .nomediascanormtp trickery & your flying.)

(The only major features you will be lacking will be A2DP, MTP & wfi-direct.... anddddd Audio all around is so much better then that of the normal nightlies that you may be using.)

Give it a go, you may be pleasantly surprised

SGR-4G on CM10.1 {JB}
[Samsung Galaxy S Relay 4G] killkillkill:
Lesson 1: http://linux.die.net/man/1/touch

"Update the access and modification times of each FILE to the current time.

A FILE argument that does not exist is created empty, unless -c or -h is supplied."

In other words, if the file does not exist, create an empty file of that name, otherwise just update the timestamps.

As far as "where"... in the location where you want to create the file.
[Samsung Galaxy S Relay 4G] :
Be careful with that. I actually submitted the patch upstream for that. While it's good, it does have some disadvantages (changes you make to your sdcard won't properly show up in media players or over mtp) It's just a bandaid for a broken media scanner and you need to remember to remove it as necessary to rescan your card once in awhile
[Samsung Galaxy S Relay 4G] misteropinion:
Does that depend on where you create that file? I created mine in /mnt/extSdCard/clockworkmod , which is where the backups are. Does it just stop the scanner, or does it -prune like find?
[Samsung Galaxy S Relay 4G] killkillkill:
Why would you want to rescan that which you don't want to scan in the first place?
[Samsung Galaxy S Relay 4G] :
For clockworkmod backups completely skipping the scan is the desirable behavior (unless you're copying them to your computer over mtp). I was thinking of a different scenario where you use it to exclude scans of mp3s.
[Samsung Galaxy S Relay 4G] Jason78729:
I tried infernix's new jaguaraudio34 build. Phone booted fine, radio signal was strong but WiFi is broke, physical keyboard doesnt work and Battery stats aren't reading correctly. Looks like good start with the new kernel.
[Samsung Galaxy S Relay 4G] Jason78729:
LTE Build.prop Question

I've seen on other devices build.props that in order to enable voice + date you need to add ro.config.lte=true and ro.config.svlte1x=true to the build.prop. I noticed by default that we only have ro.config.svlte1x=true in our build.prop. I have added the additional line and can confirm that date and voice work with the added line ro.config.lte=true. Nardholio or Infernix what are your thoughts?
[Samsung Galaxy S Relay 4G] :
Lol when it's ready it should fix a2dp issues with the jaguar audio and wifi tethering. And probably run a bit faster as well. Stay tuned.
[Samsung Galaxy S Relay 4G] dabotsonline:
Sorry, is this an LTE hack?
[Samsung Galaxy S Relay 4G] misteropinion:
That's good news. I switched back to the regular nightlies because I need at least some a2dp.

Also, I believe the issue where Phone FCs when it rings in landscape has gone away, at least in the 20apr nightly.
[Samsung Galaxy S Relay 4G] infernix:
I have banged my head against the wall with A2DP on my 3.0 jaguaraudio builds, but I cannot track down the issue. I'm pretty sure something is going wrong with routing and it looks like it's a kernel issue but it could also be userspace.

Will have to focus efforts on 3.4 for now and hope that when that is feature complete, A2DP works again.

That and hoping for a JB source drop from Samsung.

Anyone on jaguaraudio 3.0 builds (e.g. don't need a2dp) should flash cm-10.1-20130420-EXPERIMENTAL-apexqtmo-jaguaraudio.zip (build 130). Extensive debugging code is removed and it has a fix for proper zcache.
[Samsung Galaxy S Relay 4G] Braccoz:
i don't think so... msm8260a has no lte support
[Samsung Galaxy S Relay 4G] gtmaster303:
Can anyone kindly tell me which release is the most stable overall right now? Sorry, haven't been keeping up with the thread....

The "stable" is from over a month ago, so I was hoping one of the nightlies is just as stable and a bit more up to date.
[Samsung Galaxy S Relay 4G] dillalade:
Highly reccomend infernix build (only major sacrifice is no A2DP)

Otherwise extremely stable dd usage.

http://ls.infernix.net/jenkins/job/apexq-infernix/130/

SGR-4G on CM10.1 {JB}
[Samsung Galaxy S Relay 4G] killkillkill:
If you understand how non-voLTE handsets work, those build.prop edits may begin to make sense to you. For a device such as ours, i.e. without lte, those edits are totally meaningless.

Voice and data will multiplex just fine under existing configuration.
[Samsung Galaxy S Relay 4G] CarpeNoctem:
Can this help for the development and drivers: http://www.androidpolice.com/2013/0...ing-today-available-exclusively-through-kies/
[Samsung Galaxy S Relay 4G] gtmaster303:
Oh hell yeah!

This should definitely help close the few gaps we currently have
[Samsung Galaxy S Relay 4G] :
Development has already started on the new drop. Camera colors are normal and audio is in progress.
[Samsung Galaxy S Relay 4G] Grank:
Can I upgrade without wipe?

Hey,

I've been running the 10.1-20130307 build as my daily driver pretty much since it came out, and I have almost no problems, it's fantastic. Perfectly stable, great battery life, almost no annoyances. So thrilled with this phone, thank you for all your hard work! :)

A couple quick things:

I notice that the current stable build linked from the first post is 201303

09

. With 0307, I have the issue described in this ticket, which drives me a little crazy. In the ticket, infernix says:

Does that include the 0309 stable build, or does that refer only to nightlies? (I note that the bug wasn't reported as fixed until April 5th, so I'm not sure at what point that got pulled in)

If so, can I upgrade from 0307 to 0309 without wiping any of my user data, or is that going to cause problems? (I have everything set up the way I like it and always hate doing so much of that stuff over again every new ROM...)

New voicemail notification doesn't work for me... It never reflects me actually having new voicemail (which is annoying but I've long since gotten used to, as that functionality wasn't working with any of the ROMS I had on my Desire Z either), but it always shows up immediately after a reboot as a new voicemail.

After rebooting, the only way to make that notification go away (stop being in my notification tray and an icon in the topbar and constantly flashing my LED) is to go into Settings, Apps, All, find the Phone app and hit Clear Data, which will make it go away and stay gone until the next time I reboot...

Anyone else run into that? If so, any chance it's fixed in nightlies?

The phone is working so astoundingly well I'm almost afraid to mess with it by going down the nightlies path, if the 0309 build would fix the keys issue, and plus I'd presume I'll have to wipe my data to go to nightlies...

(My carrier is Rogers in Canada, and it's entirely possible this is something that can be solved by some configuration magic, so if anyone is familiar with that, let me know.)

Oh yeah and, if I do go nightlies, and I don't need a2dp at the moment, am I better off pulling from the apexq-infernix job, or should I respect the "not for general use!" label and stick with the mainstream apexq CI?

Sorry for all the questions! :o
[Samsung Galaxy S Relay 4G] kilr00y:
got my relay yesterday. stock firmware didn't last 5 mins ;)

installed build 96 right away on a really blank device. i'm experiencing no issues whatsoever so far. didn't try a2dp yet though.

great work, guys. i really love the rom :)

have two questions nevertheless.. maybe somebody got lucky with resolving these...

usb mass storage is gone with jb. i get that. but is there any way to work around that? i used to have a linux boot image on my sd for emergeny uses. but without mass storage, of course, there's no booting from usb. an application that enables the external sd as mass storage (temporarily) would be perfect. is there something like that? google got me nothing.

while rooting, i flashed the cwm-recovery provided in the gingerbread thread. i'm kinda used to ext4 and the cwm offers quite little options. but neither 4ext nor rom manager provide me with another compatible recovery.. again, usb storage mounting would be nice and some batch options (like wiping system/cache/boot with one click). anybody found another recovery that's working?
[Samsung Galaxy S Relay 4G] croogrog:
I have been using twrp you can find it here

http://xdaforums.com/showthread.php?p=39116805
[Samsung Galaxy S Relay 4G] kilr00y:
thanx :) trying it now.
[Samsung Galaxy S Relay 4G] Jason78729:
Can somebody post the stock jellybean image once its released? I don't own a windows PC so I can't utilize kies.
[Samsung Galaxy S Relay 4G] orange808:
That already happened.
[Samsung Galaxy S Relay 4G] Jason78729:
Sorry, pulled a noob move and didnt check the general forum. Thanks
[Samsung Galaxy S Relay 4G] :
Sorry for the delay in release of a new build. We're working through extreme upstream breakage of anything but a 3.4 kernel (which we're also working on)
[Samsung Galaxy S Relay 4G] gtmaster303:
No problem. Thanks for the update.

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] :
So you may have noticed nightlies stopped getting built around Wednesday due to upstream asshattery. Fixed starting with build 107. You will most likely have to clear data on the phone app and re-pair bluetooth devices (again) after flashing. Phone will force close otherwise (I'm blaming upstream)

New features:

New jb blobs for our phone instead of borrowed from other devices. Camera and audio now normal. No more separate audio branches.

Samsung service mode and 2G toggle work with the new baseband https://www.dropbox.com/s/n4y9dvwrevo2eho/RelayMC5modem.zip

Activate service mode with *#*#4636#*#* and possibly other codes will work as well

(DO NOT CLICK UPDATE SMSC IN SERVICE MODE OR YOU WILL BREAK YOUR SIM CARD)

New vibration intensity setting in advanced settings. Doesn't work

Linux version 3.0.73

Still broken:

WPA2 tethering

You tell me
[Samsung Galaxy S Relay 4G] wedg11383:
Does this mean the video camera should work properly, because I am still seeing wrong colors and force closing?
[Samsung Galaxy S Relay 4G] gtmaster303:
You better be referring to a fresh flash...

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] wedg11383:
I am. Full system wipe. Factory reset and caches cleared. Also not able to get gps going. Tried flashing new modem again and wiped again. Same result.
[Samsung Galaxy S Relay 4G] :
Should have clarified that front video recording is still messed up. Some people reported color problems with the rear cam which is what is now fixed. GPS is a concern I will look into.
[Samsung Galaxy S Relay 4G] wedg11383:
For video, I have color issues with the rear camera and color issues and the screen divided into sixths with the front camera. Also swapping between cameras in video mode, force closes and causes reboots.

When you say the rear camera color issues are fixed, you mean just with picture taking, not video?

I'm just trying to clarify what the known issues still are. Also are these camera issues ones that can be solved or does the JB release still not give enough information? Is it just a matter of time?

Thank you again to everyone for their hard work.
[Samsung Galaxy S Relay 4G] misteropinion:
Did not do a full wipe. I can confirm the GPS sees no birds, even with a cold start. Phone works.
[Samsung Galaxy S Relay 4G] mmafighter121:
If I could get some help with the latest Stable Jaguaraudio build?

After having rooted on day 1 and been waiting for a solid full functionality rom, I made the jump to the jaguaraudio build #136 from:

http://ls.infernix.net/jenkins/job/apexq-infernix/136/

I backed up in Titanium and in CWM Recovery and installed through CWM recovery.

It boots up and runs and the camera even works perfectly, but theres no Play store, no Wifi calling, no GPS option, and I can't find anywhere to log into my google account to sync contacts or anything. I'm trying to get all of my information and applications back into the phone and I don't know if I'm missing something really really obvious but I can't find anything anywhere. I just have a bare bones phone now. I went to revert to my backup, but for some glorious reason it didn't save. SO I tried to make this one work and downloaded the newest play .APK and installed it, so maybe I could pull my information from Titanium but everytime I try to open the play store it just kind of flickers open then vanishes. I tried clearing the data in the application manager and whatnot, but it still just appears and vanishes. as a total fallback Im downloading the latest JB release .zip, but I'd really like to run with this build and see how it works.

Is there no Wifi-calling or GPS, in this build? Can I access my account to sync my contacts and calenders again? Can I get into the play store to get Titanium to restore my apps? Should I just revert to the JB build?
[Samsung Galaxy S Relay 4G] wedg11383:
This might be a lame suggestion but did you flash the JB gapps when you installed? Also as far as I know we have never had wifi calling working on any of our custom roms yet.
[Samsung Galaxy S Relay 4G] mmafighter121:
no I didn't flash it, just downloaded the apk and ran it. I'll flash it now just to see if it works. If theres no Wifi calling at all I have to revert anyway, I have 0 service in my house, its fine down the street but without Wifi calling, I can't use it.
[Samsung Galaxy S Relay 4G] Jason78729:
Its possible to port the WiFi calling from stock but from what I understand its very difficult. On my Defy they got it working but eventually stopped putting it in the builds because of upkeep I'd assume.
[Samsung Galaxy S Relay 4G] :
I am unable to get GPS working again even after flashing back to stock. For now I'd recommend against flashing to one of the newer builds.
[Samsung Galaxy S Relay 4G] wedg11383:
Thank you for the heads up. I'm grateful I always do a backup before flashing.
[Samsung Galaxy S Relay 4G] misteropinion:
It is... sort of the broke.

Since I upgraded my recovery to TWRP (which I like, don't get me wrong), I can't get to my old clockwork backups, and the backup I thought I had made [note to self, check that the backups are actually there...] I didn't before I flashed the first working build (Nightly 107), so unless I bother to flash back to an older CWM recovery I'm going to go boldly with the new stuff. GPS doesn't work with Nightly 109 either.

Reflashing the modem perhaps? Thoughts?