yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] _RaZziel_:
Thanks for your comment, and I don't want to be rude or anything, but I think that what you said does not apply to my scenario. I really think that we meant something totally different by the term "retro gaming". Since I'm mostly the rpg-kinda-guy, I want to play things like the early final fantasies and some GBA-titles which is more convenient whilst sitting on a sofa with a PS3-controller and watching my TV than otherwise. this should be fine at 30fps. And yes, I consider this retro already. I of course own the titles I want to play this way.

So my question still remains: Does the Relay support MHL on the current android 4.3 cm-roms? Are there any plans including it? Is it working on any 4.2-roms (my google-searches did not yield anything useful).

If this is of any help, I pulled a catlog which has been started shortly before the MHL-cable was plugged into the phone. You can find it here http://pastebin.com/KdA1ySyq. I also pulled a /proc/last_kmsg after the phone rebooted which might also be of help, that one you can find here http://pastebin.com/ah0dx4Sx.

If I can do anything else to help, please let me know. Unfortunately, I don't know enough to fix the problem myself or even to find the exact issue in the logs.
[Samsung Galaxy S Relay 4G] :
That was fixed like a month ago.

I haven't seen this, try clearing out your SMS database. delete /data/data/com.android.providers.telephony/databases/telephony.db and reboot

Fixed as of the 10/14 nightly (hm, maybe I should start a changelog)

MHL does not work for me. Yes, it is a planned fix, unfortunately at the moment we only have 2 active devs and lbcoder has flat out said he won't work on it because it doesn't affect him. I've started dev'ing for d2 and aegis2 as well, so my time is kind of split.

I'm going back to sea duty in May as well, we will be in shipyard, I will probably be working 12-16 hour days 6 days a week so I probably will not be very active except for critical bugfixes.
[Samsung Galaxy S Relay 4G] killkillkill:
It is hard to be interested in working on something that (a) you don't have the hardware for, and (b) would not ever use even if you did. I have an IFC6410 to plug into my TV.
[Samsung Galaxy S Relay 4G] robuser007:
SADLY THIS IS NOT COMPATIBLE WITH TWRP AND YOU WILL NOT GET WIFI.

=> will this be fixed (soon?) ? I'm thinking of buying this phone or the droid 4.
[Samsung Galaxy S Relay 4G] scaltro:
I still cannot move app 2 sd... I tried to reformat the SD to FAT but still I can't. Every third-party app2sd app fails as well. Am I the only one with this issue? Any idea how to fix it?
[Samsung Galaxy S Relay 4G] Renae27:
Is there a reason you can't use CWM? Perhaps you are misunderstanding the statement you quoted. TWRP and WiFi are not two seperate issues, WiFi is an issue if you use TWRP to flash CM10.2. If you use CWM to flash CM10.2, WiFi works fine.
[Samsung Galaxy S Relay 4G] Sidneyaks:
Had a few questions, but answered them through research. I'll leave them here for anyone who runs into the same thing. Very excited to get into 4.3 on my phone. :)
[Samsung Galaxy S Relay 4G] chris122380:
I am still getting random reboots. I'll try a clean install this weekend and grab a logcat if it does it again.
[Samsung Galaxy S Relay 4G] killkillkill:
There is no benefit to twrp recovery -- if you need recovery so much that you need a touchscreen interface, then you're doing something seriously wrong, and quite frankly, the entire purpose of recovery is to be AS SIMPLE AS POSSIBLE so as to avoid potential bugs that might impede its successful use in... RECOVERING your otherwise borked device.

So no, there are no plans whatsoever to improve twrp.

Use CWM. CWM is far more useful, more reliable, works correctly, and WE SUPPORT IT.

---------- Post added at 03:41 PM ---------- Previous post was at 03:36 PM ----------

Realistically, a logcat isn't very useful for reboot issues. Most of the time, reboot issues happen as a result of kernel problems, which will never be reported in logcat.

adb shell su -c 'cat /proc/kmsg' | tee > kmsg.log

^^ from a linux terminal. This will obtain a kernel log. Keep dumping it until you can reproduce the random reboot, check the log for a crash trace at the end. If there is no crash trace, try again (sometimes it will reboot before the trace gets printed).

If provided with a kernel log, the logcat can be helpful.

Also, what build are you running?
[Samsung Galaxy S Relay 4G] chris122380:
I'm on the latest build and I'll try grabbing the kernel log tonight if I can get it to crash.
[Samsung Galaxy S Relay 4G] misteropinion:
Does kernel.panic=_numnber_of_seconds_ work in this linux? It's a 3.4 kernel... That often helps getting error messages off of servers.
[Samsung Galaxy S Relay 4G] Renae27:
[MENTION=2044079]Nardholio[/MENTION]

Previously you had recommended the staging builds over the nightly's. Is that still the case? I ask because I noticed that your staging build was updated.
[Samsung Galaxy S Relay 4G] rudias:
I noticed on mobile network settings and network mode, there is options that the phone doesn't have and if changed, app crashes. On my previous phone, I had WCDMA only, GSM only option, and WCDMA preferred/GSM which seems suitable for this phone. Is this something that is known?
[Samsung Galaxy S Relay 4G] chris122380:
I received an error. Unable to write the log file.

shell@android:/ $ su

su

root@android:/ # cat /proc/kmsg | tee > kmsg.log

cat /proc/kmsg | tee > kmsg.log

cat /proc/kmsg | tee > kmsg.log

sh: can't create kmsg.log: Read-only file system

[1] + Stopped (signal) cat /proc/kmsg |

Done (1) tee >kmsg.log

sh: cat: <stdout>: Broken pipe

1|root@android:/ #
[Samsung Galaxy S Relay 4G] _RaZziel_:
This means it tries to write the log to / which is mounted read only (which is a good thing, I guess). So just put the log somewhere you can create it (like /storage/sdcard0 or /data or /data/data, if it's a big log the first would probably be a good idea).

Edit: I just saw that the originally suggested command was using adb and would have dumped the log to a folder on your computer, which might be the better option.

Btw.: I now set-up my raspberry pi using emulation station and is works quite well as a variety of emulators, so I got around that mhl-issue.
[Samsung Galaxy S Relay 4G] chris122380:
I tried creating the log file to multiple different locations on my computer and received the same error. Only concern about putting it on the sdcard0 is that it would quit writing the log file when the phone crashes. (I think it would any way). Is there a good way to get the kernel log file without connecting to my computer (I'm updating to Windows 8.1 this weekend)?
[Samsung Galaxy S Relay 4G] :
Try %userprofile%\Desktop\log.txt

If you still can't create a log on your desktop you're definitely doing something wrong.
[Samsung Galaxy S Relay 4G] chris122380:
The error I posted was a direct path to the desktop. The posts give me some ideas to try. I'll try this weekend after updating my computer.
[Samsung Galaxy S Relay 4G] :
https://github.com/xplodwild/android_packages_apps_Focal/issues/30

trololol
[Samsung Galaxy S Relay 4G] killkillkill:
1) You can't write to a readonly filesystem.

2) DON'T DO THAT ON YOUR PHONE. Even if the kernel spits out the log, it won't SAVE it, because the panic will reboot your phone without syncing your filesystem.

---------- Post added at 06:17 PM ---------- Previous post was at 06:14 PM ----------

First off, delete the virus.

Install actual operating system; http://fedoraproject.org/get-fedora

Install android-tools package (su, yum install android-tools)

Run the command I gave you.
[Samsung Galaxy S Relay 4G] chris122380:
It's not a read only file system. It creates the file with nothing in it. I'm running cmd as administrator.
[Samsung Galaxy S Relay 4G] killkillkill:
I promise you. "/" IS A READ-ONLY FILESYSTEM.
[Samsung Galaxy S Relay 4G] chris122380:
I'm not saving to "/" I'm trying to save to c:\ running as administrator on Windows 8. Hopefully this weekend Windows 8.1
[Samsung Galaxy S Relay 4G] gee one:
Yeah, I think those are the same thing. I'm not a windows expert, but / and c:\ are both root directories. And, if I'm not mistaken, windows is usually installed to the c: drive, cuz the a and b drives are reserved for floppy drives.

Try Nard's suggestion and save to your desktop.

sent while running with scissors
[Samsung Galaxy S Relay 4G] chris122380:
Shouldn't matter though I get the same error trying to save to the desktop. I posted the error message from trying to save to the desktop. I'll try a few tricks this weekend to see what happens. I am tech savvy that's why I tried the desktop when c drive didn't work. I may also update my SDK because this is the first time I've had this problem.
[Samsung Galaxy S Relay 4G] gee one:
The error you posted seems to be from on the phone. I think the suggestion was to run the command from your pc (via adb shell [command]) and not on the phone (via adb shell). One sends the command to the phone from your pc, the other you type the command into the phone via the shell. Not much difference, except for the output part. If run from the phone, it will spit out the file to 'pwd' which seems to be /.

sent while running with scissors
[Samsung Galaxy S Relay 4G] chris122380:
Ok that makes more sense. If I do it straight from the command line I get the error that tee command dose not exist.
[Samsung Galaxy S Relay 4G] Jason78729:
Use the "tee" command, not tree.
[Samsung Galaxy S Relay 4G] chuckiev79:
I just want to report a few things. First off let me just say awesome work by devs great rom. I was experiencing random reboots but not since nightly before last. Secondly there is still a bug that when you try to adjust sharpness when editing a picture force closes the app. Lastly as in terms of gaming i highly recommend the moga bluetooth contoller it works like a charm; especially with the universal driver app now in the playstore, not sure if this will suit your needs just tring to help. Ps i suck at punctuation. Lol
[Samsung Galaxy S Relay 4G] ruggie0:
How do I get Bluetooth tethering to work with my nexus 7 2013, also on CM 10.2?

EDIT: Scratch that. I got it working, but it's intermittent.
[Samsung Galaxy S Relay 4G] killkillkill:
Do you need me to quote you again?

YOU CANNOT SAVE DATA TO A READ-ONLY FILESYSTEM!!!!!

YOU CANNOT RUN TERM COMMANDS ON PIECE OF JUNK VIRUS, NOR ARE YOU ACTUALLY RUNNING ANYTHING ON SUCH VIRUS. WHETHER VIRUS IS VERSION 1, 2, 3, or 8 MAKES NO DIFFERENCE. DELETE THE VIRUS AND THEN PROCEED.

---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------

NO FRIKKIN KIDDING.

You're on your own. I'm absolutely through trying to help you.
[Samsung Galaxy S Relay 4G] :
lol I use adb on windows and it works just fine

Major updates are coming soon:

Magamo fixed the boot logo

New recovery soon with swipe controls and bootlogo (also Koush finally added us to rom manager, so cwm touch is also now available)

Some keys will be remapped to support vim/shell sessions. Shift 1 will be ESC, the microphone will be right alt, Email will be ctrl, and contacts/messaging will be search. I briefly considered changing the microphone to voice search like it should be, but that's long press menu and also configurable

major upstream kernel updates once they are tested stable.
[Samsung Galaxy S Relay 4G] chris122380:
I'll install I Linux vm and SDK. It might be a while till I get the log file. Not everyone can afford a Mac or be tech savvy enough to use Linux as a everyday computer. (This is not the place to have a anti Windows campaign).

DO I NEED TO REPEAT THAT I KNOW THAT ROOT IS READ ONLY.

---------- Post added at 12:02 PM ---------- Previous post was at 11:47 AM ----------

What exciting news good job everyone involved.
[Samsung Galaxy S Relay 4G] ruggie0:
Not a place to discuss your hatred of windows.
[Samsung Galaxy S Relay 4G] killkillkill:
Every place is a place to attack crimes, crap, viruses, and ignorance.

If you love that virus so much, why exactly are you using a LINUX PHONE?
[Samsung Galaxy S Relay 4G] scotte9999:
If it was my phone, I'd love the VI-capable keys, unfortunately that seems like the wrong thing for my wife. Are the keymap changes going to be the settings, or is this the start of selectable keymaps for the hard keyboard? (Seems like it should be possible to make it an option for the hardware keyboard, I just don't know where that lives in overlay land.).

On another topic, I noticed that at least with the October 2013-vintage nightlies, no cell signal results in what looks like a sign overflow in the "Status" part of "About Phone". Rather than "-200 dbm" or whatever, it reads "2147483647 dBm 255 asu". I suspect this isn't a radio issue, since we only have one JB radio for this phone, right?
[Samsung Galaxy S Relay 4G] ruggie0:
I never said that I LOVE Windows, and where I agree with you that "every place is a place to attack crimes, crap, viruses, & ignorance", I hardly see WinBlow$ being that. I actually have WinBlow$ 8.1 pro w/ WinBlow$ Media Center running as a DVR and I gotta say, it was VERY easy to setup & maintain.

Which is why I use a Linux-based phone & tablet (Nexus 7 2013 edition, *****es! :cool:). Easier to setup & customize, plus more affordable.

Does WinBlow$ have its pitfalls? Sure, but so does Linux. So does experimental & nightly builds of Android.

You don't have to use the SAME platform across all devices. Just because YOU do doesn't make it law.

And you don't have to come across as a superior snobbish arrogant trolling d!ck, either.

Now, let's get back to the thread topic - I dunno if this is an issue with my Relay or with my Nexus 7 (also rooted running a nightly build of CM 10.2), so I'm gonna post this in both forums and see what sticks:

When trying to setup a Wifi Direct connection, my N7 sees my Relay just fine, but not the other way around. I flashed the latest cwm touch recovery on the relay before flashing the ROM (had twrp on it before getting cwm). What would cause it?
[Samsung Galaxy S Relay 4G] Jason78729:
Linux is honestly easier to learn than the virus windows. I don't like off topic stuff but I agree with killkillkill that any forum is an appropriate place to positively promote open source and linux and to warn people of the crap known as windows. Its free to try, easy to dual boot with windows (which is only useful for gaming and linux is getting better), and is much more stable, speedy, amd secure. I've taught the firefighters at my department how to use it and they've all made the switch.
[Samsung Galaxy S Relay 4G] gtmaster303:
Without sounding out of line (all you devs are above my head), i would suggest Windows discussions (good and bad) be kept in a separate general thread, as it has nothing to do with CM roms. The last thing anyone wants is to get off topic. Thank you

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] Ziida:
Sorry if this is an obvious question for Relay owners, but is there a reason that there have been no "Stable" or "Release Candidates" for this phone?
[Samsung Galaxy S Relay 4G] :
[MENTION=4178888]Ziida[/MENTION]: We only became "official" with 10.2 and 10.2 is not release-worthy at this time. It's getting close though. We were on unofficial 10.1 before that, we stopped development on it though. The repos are still there, people are welcome to finish it up and make a 10.1 release.

[MENTION=848742]scotte9999[/MENTION]: The remapped keys will stay on our staging builds for now. (The builds we use for internal testing, although the server is not password protected and anyone can run them)
[Samsung Galaxy S Relay 4G] misteropinion:
I vote for the vi keys! Unless we can have emacs, of course.
[Samsung Galaxy S Relay 4G] orange808:
We get it. You don't like Windows.

Jeezus... Let it go.
[Samsung Galaxy S Relay 4G] croogrog:
Do you recommend any particular staging build or should I just use the most recent successful build?
[Samsung Galaxy S Relay 4G] janejunx:
Still happening after a clean install. Going to try stock messaging for a bit.
[Samsung Galaxy S Relay 4G] robuser007:
Can bthe wifi be used with another recovery?
[Samsung Galaxy S Relay 4G] :
The good news is magamo fixed the boot logo problem in the kernel. The bad news is some people are hating on our new logo.

http://i.imgur.com/L8pFR7g.png

Builds in the next few days will likely go out with the d2 logo, which is oversized for our screen and will look distorted.(Yes I know there hasn't been a nightly since the 16th, there's something odd going on with the servers)

Get your popcorn, the drama is at http://review.cyanogenmod.org/#/c/52024/ and http://review.cyanogenmod.org/#/c/52023/
[Samsung Galaxy S Relay 4G] gtmaster303:
Bite my shiny metal ass! That's definitely a scaled down, cuter, green version of Bender :)

Sent from my Galaxy S Relay
[Samsung Galaxy S Relay 4G] Sidneyaks:
running nightly 10/14/2013 and teathering EATS my battery like no other. If there is anything i can do to help diagnose, let me know. It's not a huge deal since when im teathering, i usually have a laptop i can plug into to charge.

Im running the most recent nightly, and aside from the above, i have no complaints.
[Samsung Galaxy S Relay 4G] Renae27:
App2SD

Is it possible to get App2SD support?
[Samsung Galaxy S Relay 4G] killkillkill:
The piece of crap is universally a piece of crap.
[Samsung Galaxy S Relay 4G] _RaZziel_:
Yeah, great. Why again can't we leave all that bashing where it belongs, i.e. not here?

Anyway. I would very much like to have the vi-keys since I use the terminal a lot but unfortunately, I could not find those staging builds. Can someone please tell me where to find them? I had a look at those .kl and .kcm files but I could not easily figure out how to add a second alt-key though adding special characters is easy.

Edit: The problem with "tee command not found" is that tee is a linux command line tool that's obviously not installed on windows. Leaving out the pipe and tee, i.e. "| tee" would hopefully result it the output being written to a file. The thing about tee is, that it writes to a file whatever it receives via stdin, but it also dumps it to an arbitrary number of user defines files. So the output would get dumped to a file and you could see whats dumped. Alternatively you could install one of the many tee-variants for windows.
[Samsung Galaxy S Relay 4G] gee one:
OK, so I've been out of the building loop for a while... is the CM camera issue fixed or should I use lbdroid's kernel repo for a working camera?
[Samsung Galaxy S Relay 4G] scaltro:
Yeah... It would be very nice.

Actually I was able to set the default location to sd thanks to this guide http://techgage.com/article/moving_your_non-movable_android_apps_to_an_sd_card/

But this worked for me only for new installed apps. I still cannot see the button to move the already installed apps to sd or via app2sd.

It would be nice to include this in the CM as described here http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/

Apparently CM should already include this feature.

I'm running the last ROM 21-Oct
[Samsung Galaxy S Relay 4G] chris122380:
I have done a clean install of the latest nightly (CM10.2-20131021-nightly). Still getting forced restarts randomly. Was able to trigger these restarts when Google now locked up and then did a restart of the phone.

adb shell su -c 'cat /proc/kmsg' > c:\kmsg.log

and

adb shell su -c 'cat /proc/kmsg' > c:\kmsg2.log
[Samsung Galaxy S Relay 4G] janejunx:
Camera works fine for me in newest nightly.
[Samsung Galaxy S Relay 4G] :
How did you trigger a kernel oops from the row scheduler? Lol
[Samsung Galaxy S Relay 4G] misterfamilyguy:
I am on nightly 10062013, trying to install anything past 10202013 and it won't boot on my relay. Just boot loops at Samsung logo. Are devs aware of this or am I missing something? I have been installing from the beginning and I usually wait a week or so of nightlies to install.
[Samsung Galaxy S Relay 4G] janejunx:
They're all working over here.
[Samsung Galaxy S Relay 4G] misterfamilyguy:
Shoot, okay i'll try a few more things.
[Samsung Galaxy S Relay 4G] chris122380:
I do not know. I haven't edited the kernel or the ROM. Is a clean install was just grabbing the log files for you when doing a voice search.
[Samsung Galaxy S Relay 4G] orange808:
If you want to move your huge apps to the external sd, use FolderMount. And, please search the forums and the Play Store for solutions before you post. FolderMount isn't a secret or brand new innovation...
[Samsung Galaxy S Relay 4G] CrunchBangPow:
"0" Directory

Whenever I flash a nightly update, even if its a clean install, i keep having everything installing in a directory named "0". Searching around the comments seem to indicate I have an outdated recovery but the latest I can find is CMW-Based v6.0.3.7. Anyone have a newer version of the recovery or a solution for the zero directorys?
[Samsung Galaxy S Relay 4G] ruggie0:
I use ROM Manager and it updated to 6.0.3.8. But yes, I have the same issue and it would be nice to get info on how to fix it.
[Samsung Galaxy S Relay 4G] C3POID:
Interessting.

I do the same redirection aka remounting for some folders in crypted containers over tasker.

A953 (MS2) Talk with a little Tapa
[Samsung Galaxy S Relay 4G] chris122380:
I am still getting random reboots with Google now and Dragon dictation (Swype keyboard). What is the status for the rebuilt new kernel that is coming? Not eta we don't get those but what fixes can we expect from it?
[Samsung Galaxy S Relay 4G] :
If you are having trouble booting the latest nightlies please dmesg | grep manufacture and pm me the results. This one should be relatively easy to fix. Unfortunately those of you with affected screens won't get to enjoy the logo. (You can also try booting straight into recovery from one of the boot loops and pulling a /proc/last_kmsg we may be able to get styple useful data from that)

Lockscreen/wake issues are apparently fixed. Yay.

Second post will be updated with Google Now reboots. Sorry my post about an injection of CAF love was interpreted as meaning new kernel.
[Samsung Galaxy S Relay 4G] tylik:
I am on 10-21, and I'm getting a few random reboots a day. Several of them have occurred in conjunction with doing something with the pull down menu showing message previews and such, or using hte plume client for twitter, but this may just be happenstance.
[Samsung Galaxy S Relay 4G] :
Please "dmesg | grep manufacture" from a nightly that does boot and pm or post the results. Also can you boot into recovery from one of the reboots and pull the /proc/last_kmsg?
[Samsung Galaxy S Relay 4G] scotte9999:
My wife is getting similar behavior. Have you pulled a last_kmsg yet?
[Samsung Galaxy S Relay 4G] misterfamilyguy:
I'll do it later on today.
[Samsung Galaxy S Relay 4G] btack:
[MENTION=2044079]Nardholio[/MENTION] here is a last_kmsg from the nightly on the 23rd which is one that will not boot

View attachment last_kmsg.txt
[Samsung Galaxy S Relay 4G] :
[MENTION=4538268]btack[/MENTION] try this build http://ls.infernix.net/jenkins/job/...-20131025-EXPERIMENTAL-nardholio-apexqtmo.zip

As always, I am not responsible if you brick your phone. (Standard CYA). If it bootloops please provide a log.
[Samsung Galaxy S Relay 4G] btack:
sweet new splash screen.....it boots up and appears to be working as well as any other of the nightlies
[Samsung Galaxy S Relay 4G] :
Sweet. It should be in tonight's nightly then.
[Samsung Galaxy S Relay 4G] misterfamilyguy:
Hey, ya this version boots right up for me. Thanks Nardholio
[Samsung Galaxy S Relay 4G] :
Blame Samsung. You have a slightly different screen on your phone.
[Samsung Galaxy S Relay 4G] chris122380:
I wonder if my random reboots are related to gapps. If I do a clean install with out it seems to work ok but then I install gapps and start downloading apps then phone freezes and reboots.

---------- Post added at 10:45 AM ---------- Previous post was at 10:04 AM ----------

Logcat - https://db.tt/I7wX9Is8
[Samsung Galaxy S Relay 4G] yohan4ws:
my contacts have disappeared after upgrading from sep 26 nightly to oct 21... going to oct 25 didnt bring them back, i searched and havent seen any1 else report a solution in this thread