yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] chris122380:
I am still getting random reboots. What's the best way to get a log file when not at a computer?
[Samsung Galaxy S Relay 4G] dillalade:
With these official nightly builds is it necessary to flash gapps when flashing nightly on top of nightly?
[Samsung Galaxy S Relay 4G] stephenclower:
You might try aLogcat from the Play Store. To help diagnose my own crashes, I've periodically pulled /proc/last_kmsg through ADB and sent it to the devs. Both procedures should have you covered.
[Samsung Galaxy S Relay 4G] :
[MENTION=5132711]stephenclower[/MENTION]: https://github.com/CyanogenMod/andr...mmit/83e26bfb29582815bc84aef745b5acb926e748b5

I just kicked off a new recovery build, I have a hunch this should fix it.

Reboots on the latest nightly might be avs related. There's another patch lbcoder wrote to fix it but it didn't make it to gerrit. I'll try to get it pushed through for tomorrow's nightly.
[Samsung Galaxy S Relay 4G] stephenclower:
Unfortunately my results are the same. I've put my last_log file up at https://dl.dropboxusercontent.com/u/5108743/last_log if it can be of any use.
[Samsung Galaxy S Relay 4G] John5788:
What's the current correct method for flashing recovery.img? I am trying to flash the latest nightly recovery.img with this command and output

localhost / # flash_image recovery /extSdCard/ROMs/recovery.img
failed with error: -1

Is flash_image not valid anymore? I am still on 10.1
[Samsung Galaxy S Relay 4G] dillalade:
The process com.android.phone has stopped.

Is what appears when trying to change the defaulted network mode from LTE (?) to GSM Only.

GSM/WCDMA also gives same error.

I would thought GSM would be the only network mode we'd require for our device. There is a long list to choose from.

Is there a bug here, or is there a specific network mode I should be attempting.

Thanks in advance
[Samsung Galaxy S Relay 4G] :
Due to the silly way d2-common is set up, we're basically telling Android our phone is capable of GSM/CDMA/WCDMA/LTE pretty much anything under the sun. We're also using d2 ril blobs from d2tmo which is LTE capable. Despite this, it somehow manages to work.

GSM is 2G networks and WCDMA is 3G and 4G (HSPA, HSUPA, AWS, and all the other weird acronyms). I normally keep mine on GSM/WCDMA preferred, although GSM/WCDMA auto also works. To activate GSM only, you can either use the Samsung hidden menus or tick the box that says Use only 2G networks. If you're getting FC's, try clearing data on dialer/phone
[Samsung Galaxy S Relay 4G] :
Unfortunately I know next to nothing about Heimdall. I saw your question on irc but nobody was around to answer.

On the general subject of recovery though, the 10.2 recovery is still very much a WIP and is still buggy as hell. The *only* recovery I recommend right now is this build http://cmw.cmfs.me/apexqtmo/apexq_recovery.img which is the same as our last 10.1 recovery build from our Jenkins. The first post will be updated with these links

If you started getting crashes from the 8/27 nightly, please try the 8/28 nightly, and please send me any logs from your crashes.
[Samsung Galaxy S Relay 4G] John5788:
I eventually just stuck the recovery.img inside a flashable zip and upgraded to the 322 recovery from unofficial. Seems to work fine here for the time being. I upgraded to 10.2 from 10.1 with clean install using it.

I started with the official nightlies from get.cm and my battery wasn't charging properly over USB. The USB connection would randomly drop out and cease charging. I switched to unofficial nightlies and my battery is charging again. I experienced this issue on 20130828 official nightly and was resolved in build #322 unofficial.
[Samsung Galaxy S Relay 4G] John5788:
I also want to mention that I am still seeing screen wake issues. I've been seeing this issue since the first CM10 unofficial release.

If the phone sleeps for about a minute, the next attempt to wake up the phone will result in the screen being blank, but I can still control the OS via touching the display (unlocking, playing music, etc.. based off memorization of icon locations).

I have to cycle through sleep/wake a few times via power button to get the screen to properly wake up.
[Samsung Galaxy S Relay 4G] chuckiev79:
I'm not experiencing any of these problems. I am on official nightly 8/28, but i'm still on the gapps listed on page one of this thread. I hope this helps.
[Samsung Galaxy S Relay 4G] John5788:
I'll have to give the next few nightlies and maybe even try CM9 again to see if I can reproduce this issue.

Else I might have to return back to stock, zero out the flash counter, and see if I can get a warranty replacement on the phone.
[Samsung Galaxy S Relay 4G] Jason78729:
CWM Recovery with External SD

Attached is a recovery with Nard's new recovery image that supports the external sd card. Please test at your own risk. I've had no issues so far (only did a nand backup to the extsdcard. Please give feedback. I simply copied this zip to my internal sdcard and install the zip from their. So far it seems to be working fine for me.
[Samsung Galaxy S Relay 4G] Jason78729:
If anybody needs any help with Heimdall send me a PM. I don't use windows so all flashing outside of recovery has to be done with Heimdall by me. I'm no expert but I've been able to figure out everything I've needed so far.
[Samsung Galaxy S Relay 4G] Jason78729:
Am I missing something or is the CM power widget removed in the newest nightly, 08/28/2013?
[Samsung Galaxy S Relay 4G] dillalade:
RE: Trebuchet Home Settings.

Is there any drawback in backing up & restoring Trebuchet data (with Titanium backup) - when installing from a full wipe.

(Tested and it did restore all but the widgets, which is better then nothing, but don't want to do this, if this type of data restore to a system app is detrimental.)

I'm trying to backup restore Trebuchet homescreen layouts is all.

Nard, if the above is not a good idea, could you perhaps pinpoint what system file could be storing the Trebuchet settings (particular Home screen setup) , so i can do a manual backup/restore of this file(s).

(Before it's said, Yes I have tried Nova, Apex etc - fully aware they have native backup/restore features. But I like to keep it stock CM without all those 3rd party Bells & Whistles. :cool:)

Thanks in advance.
[Samsung Galaxy S Relay 4G] dillalade:
Lastest nightly, full wipe

systemupdateservice seems to be preventing a deepsleep for me.

(something worth noting perhaps, google sync - on 'browser' was never ending it's sync - going on for a longer then usual length of time... so manually stopped browser sync.)
[Samsung Galaxy S Relay 4G] :
Yeah, upstream put some crap in to try to prevent Google phones (Nexus) from downloading otas (which obviously won't work with Cyanogenmod) and they broke deep sleep for everyone.
[Samsung Galaxy S Relay 4G] scaltro:
Hi, I'm on the 08/28/2013 build but I found this having the worst battery drain compared to the old one.

i also have issues recognizing my sdcard...a 64GB I can see it mounted, but I cannot see any folder from fileexpert anymore.

If I run file manager with root rights instead I can find all my files in the microsd.. very weird.

Any idea?
[Samsung Galaxy S Relay 4G] chris122380:
The 8/29/13 nightly would do random reboots when doing a Google Now search (I wasn't near my computer to get a log file sorry). So I did a clean install and Google Play crashed on me and the phone kept dropping connection with my SIM Card ( wish is brand new). The 8/26/13 nightly is the last nightly that worked for me (As a update. With last clean install problems unsure about doing a clean install till after the nightly updates to a snapshot or RC). Next time i'll try grabbing log files but difficult for me to do when not at my computer (Can't figure out how to add the log file to xda through the xda app). Also difficult when I have no idea when the phone will crash or else i'dd force it to when collecting a log file.
[Samsung Galaxy S Relay 4G] chuckiev79:
Whatever you guys did to tame Google services ram usage. Thank you!
[Samsung Galaxy S Relay 4G] chris122380:
Did a update from 8/26 to 8/30. No crashes so far with 8/30. It did do a soft restart right after it installed but nothing after that.
[Samsung Galaxy S Relay 4G] tylik:
Rebuilt the phone with 2013.9.1 yesterday afternoon, first on the new kernel. (Why does feeling vaguely grumpy mean "rebuild one of your devices" to me?)

So far, no unexpected problems. Still a tad flakey around charging, and a lot of bluetooth disconnects (though mostly while I've been on wifi). Generally smooth and sweet.
[Samsung Galaxy S Relay 4G] stephenclower:
FYI, it looks like my constant voice input-related reboots have been fixed since the 8/29 nightly build. I don't know whom to thank, but know that I appreciate the fix.
[Samsung Galaxy S Relay 4G] chris122380:
I started having the voice search reboots after the 8/29 nightly. I'll try getting a log file if I can reproduce it when connected to my computer since it is random. It does a hard reboot when the voice search freezes.

logcat file: https://www.dropbox.com/s/ypdrmofplcsobgl/logcat.txt
[Samsung Galaxy S Relay 4G] :
Everyone is invited to try build 325 of apexq-staging

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

The main difference from today's nightly is it contains an updated kernel that should stop some of the reboots/crashes that are video related. I'm still trying to figure out what's causing the Google Now reboots.
[Samsung Galaxy S Relay 4G] John5788:
Damn. I was hoping it would fix my black screen wake problem, but still exists for me on this kernel too.
[Samsung Galaxy S Relay 4G] chris122380:
I'm frequently getting "scanning for GPS" message. I'll collect a log file tonight.

Looks like no Google search crashes after updating to 9/5 nightly (so far).
[Samsung Galaxy S Relay 4G] misteropinion:
performance

I flashed the 20130904 nightly yesterday morning and it's a glory and a wonder. I had been experiencing severe memory starvation, and something about that one resolved most of those issues. Unless of course freezing Sundroid helped with that (something about the new Sundroid release is causing it to not be able to agree on a location and it was using huge amounts of CPU time, like 5-8 minutes a day, interfering with deep sleep and all the usuals).

If the 325 apexq-staging is equally stable, i'll unfreeze Sundroid (with the widgets deleted) and see if things are still good.

I wish I had that extra 1GB of RAM between the Relay and the GS3... Pocket computer!
[Samsung Galaxy S Relay 4G] chris122380:
Ok I spoke too soon Google now voice search is still crashing.
[Samsung Galaxy S Relay 4G] misteropinion:
Mine works with staging 325.
[Samsung Galaxy S Relay 4G] chris122380:
I'm using nightlies and Google now tends to crash and do a phone reboot right after charging, right after a reboot, background noise, or when Google Now freezes. Started with about 8/25.
[Samsung Galaxy S Relay 4G] tylik:
Flashed it first thing this morning, heavy use all day, so far so good.
[Samsung Galaxy S Relay 4G] ruggie0:
Stock Jelly Bean radio & bootloader....

so, here's a question (and if I missed it being asked & answered, my apologies....I usually try to find the answer first before posting),

Should I update radio & bootloader if the phone CAME with the jelly bean update already installed?
[Samsung Galaxy S Relay 4G] stephenclower:
If you're on stock Jellybean then there's no need to flash the new radio firmware. You already have it.
[Samsung Galaxy S Relay 4G] chris122380:
I did a clean install last night using 20130905 nightly. Received a no boot (Samsung logo and then black screen) after installing 20130906 nightly. Is anyone having problems with the latest nightly?

After the clean install my GPS problem went away. I did get two force restarts one after running my script calculator app for the first time. The second force restart happened after enabling "Personal recognition" and doing a Google voice search. I'm still unclear what logcat log file you need or how to create it (adb logcat -v > c:\logcat.txt what logcat command line arguments??? ).
[Samsung Galaxy S Relay 4G] :
apexq-staging 326 is out, with the addition of an open-source hotplug replacement. Please report any bugs in a separate thread.

Also [MENTION=681986]dilla[/MENTION]dale: blacklist should be fixed in the latest nightly (and in build 326). Problems with "normalized" phone number matching (your country code problem) and with the ringing not stopping have been patched. (I haven't tested, this data is just from the changelog)
[Samsung Galaxy S Relay 4G] dillalade:
This is happening to me too.

Was on 0902 flashed 0906 and got the black screen.

Flashed 0905 and boots fine.

Niiiice, I will be sure to test and report back :thumbup:
[Samsung Galaxy S Relay 4G] janejunx:
Black screen on 09/06 as well. First nightly with severe problems for me, though, which is pretty rad.
[Samsung Galaxy S Relay 4G] tylik:
Just a note on 325, before I install 326 -

Yesterday on a few occasions I noticed that the names of app, both on the mainscreen and the app drawer or whatever that's call, were messed up. Originally it look just as if part of the letters were all shifted slightly from the rest, but at times I wasn't even sure they were roman characters. (And then I rebooted and it was fine.)
[Samsung Galaxy S Relay 4G] chris122380:
Unable to boot 09/07 same problem as 09/06. I even tried a wipe first and still no boot.
[Samsung Galaxy S Relay 4G] dillalade:
FYI to all:

CM on facebook have stated not to flash 7thSept Nightlies!

Flashed 326, I suspect the Hotplug feature is indeed working, as my battery dropped only 1.5% per hour during my sleep. That's terrific.

As for this call blocking.

It didn't work.

If you blacklist a number with the country code the caller can still get through.

But when blacklisting the same number without the leading country code then caller is blocked, however sometimes the caller will hear half a tam ring.
[Samsung Galaxy S Relay 4G] chris122380:
It's also on Twitter now: Check out [MENTION=4193338]Cyanog...ter.com/CyanogenMod/status/376280220350676992

I'll start following cyanogenmod on Twitter.
[Samsung Galaxy S Relay 4G] C3POID:
back to black

Hi there,

I got my SGH-T699 and I'm definitely have to change the T-Mobile ICS4.0.4 to CM10.2! (Till now I have a Motorola Mileston2 (A953) with CM7.)

So first of all I brought it to root with [root]Samsung Galaxy S Relay 4G and played a little bit around and saved some files to the extsdcard.

After that I followed the install guide of cyanogenmod.org (see link above) and tried to install the latest nightly 20130907 (CWM v6.0.3.5) but I got the following error:

...
getprop("ro.bootloader") == "T699
...

And then I remembered that I have to upgrade the bootloader and the modem. But I didn't find any infos how to upgrade...

So I copied the zips to the extsdcard and installed first the bootloader and then the modem zip.

After that I did a reboot. At the start screen where I have to choose the language I powered off and started again in recovery mode.

This time the install of CM10.2 worked. But after the reboot I see the Samsung logo and then the screen is still black.

After 5 min I removed the battery, put it back and powered on again.

But again the Samsung logo is shown shortly and then it's all going black.

Any ideas or maybe did I something terrible wrong?

Thanks in advance

PS: Maybe I should try the 0905 first...
[Samsung Galaxy S Relay 4G] dillalade:
Read my post 3 messages back.

Have a read all the knowledge is here!

Flash 5th Sept nightly
[Samsung Galaxy S Relay 4G] croogrog:
If you read a few of the posts above you would know not to install the sept 7th nightly.
[Samsung Galaxy S Relay 4G] C3POID:
Big SORRY, I didn't refresh my browser view :silly:

But my install seems to be ok expect for installing the "wrong" version of CM?!

...ok, I did a wipe data/factory reset again and installed the 20130905.

It's booting right now and looks great!

thanks - and sorry for being a little bit stupid
[Samsung Galaxy S Relay 4G] chuckiev79:
In stock image editor, the sharpness setting crashes the apk.
[Samsung Galaxy S Relay 4G] dillalade:
Nard,

The HotPlug feature in 326 staging has that been added to the official CM builds?

I'm loving the battery on 326/HotPlug, and unwilling to upydate to 9thSept nightly if HotPlug is not available.

Cheers

I can confirm
[Samsung Galaxy S Relay 4G] chuckiev79:
And when I say stock I mean not a third party app. Not stock firmware. On today's nightly, but I think this issue is consistent on all builds.
[Samsung Galaxy S Relay 4G] :
I highly doubt open source mpdecision will make it into the official cyanogenmod. Don't hold your breath.

Staging build 327 is out, which should more or less match the 9/9 nightly. The kernel has received another injection of caf goodness and should stop the pesky memory leaks from kgsl. And I had to work closely with the d2 kernel maintainers to prevent a workaround for our buggy firmware from being overwritten.

I haven't heard anything about Google Now reboots recently? I've heard that a complete wipe of gapps can solve it.

Sharpness editing is most likely not an apexq specific bug and will be fixed upstream.
[Samsung Galaxy S Relay 4G] killkillkill:
Its not a hotplug feature. Its an MPDECISION feature. All hotplug is, is the routine that actually powers the second core up and down (and arranges for it to be done without crashing everything running on the second core...). MPDECISION is what decides WHEN to call hotplug.

Mpdecision also usually does some extra things, like responding to input events by slamming the cpu frequency up high, quickly, to make the UI fluid.

Now qualcomm offers two forms of mpdecision; the most common, being a userspace blob that sends commands to the kernel through the mpdecision interface. The second is a semi-open source option, but requires firmware be run on TRUSTZONE. Trustzone is, of course, EVIL.

The changes I've made involve replacing the mpdecision INTERFACE in the kernel, with a full blown in-kernel mpdecision. This in-kernel mpdecision is a lot more tunable than blob mpdecision (for example, it can disable second core altogether during sleep, which is default behavior). This mpdecision also includes a much more efficient form of TOUCH BOOST than the blobs offer.

Touch boost is part of the so-called "project butter", and is what causes the cpu frequency to bump way up on input events. The google implementation is limited by the userspace mpdecision blobs, so runs triggers from kernel, through surfaceflinger, power hal, mpdecision blob, and back to kernel. This is obviously quite insane. The in-kernel mpdecision takes the input events DIRECTLY. This is, obviously, much more efficient. It is set to boost the core minimum frequency up to 918 MHz. I've thought about bumping that up to 1200, but am on the fence about it. UI fluidity seems pretty decent, and the higher you go, the more power you burn, so hard to say.

If you feel like playing with it, there is a sysfs interface to it at /sys/kernel/msm_mpdecision/conf/boost_freqs, as well as a bunch of other tunables.

I really have no intention of pushing this up to CM. Nard may, if he feels like it, but even then, upstream is a wacky bunch, so whether it will be accepted or not is anyone's guess.

---------- Post added at 05:16 PM ---------- Previous post was at 05:14 PM ----------

Build 327 is borked. Missing the system/etc/firmware/wlan directory. Repo is fixed now, but can't build due to gerrit being borked. Next successful staging build should be good, or 327 if you don't mind broken wifi, or drag in the path from a different build.
[Samsung Galaxy S Relay 4G] chris122380:
How do you do a wipe of gapps? When I've not been installing the gapps zip. Any specific apps to clear under settings? I am still getting the Google Now reboots but very random some times it works and sometimes it doesn't.
[Samsung Galaxy S Relay 4G] :
This is the method I use, it's a bit extreme but you know I like to be thorough.

Deinstall all Google apps.. Gmail. Google +, Maps, Search, etc etc. This includes Play Store. This is important because updated apps get stored in another place as system apps, and you need to nuke both copies.

Format your system partition in recovery and then reinstall your ROM. This is to remove any remaining parts of Google in system.

Boot into Android. The settings from the removed apps will be automatically removed.

Go back into recovery and reflash gapps.
[Samsung Galaxy S Relay 4G] CarpeNoctem:
[MENTION=2044079]Nardholio[/MENTION] I just got the phone and installed straight this CM10.2, unfortunately no WIFI

I followed one of your post and flashed the lastest modem and bootloader, still not wifi

Wipe the phone, still no wifi... Anything I am missing here?

Thanks
[Samsung Galaxy S Relay 4G] :
Are you on official nightlies or my staging build? lol try the newer staging build 331.
[Samsung Galaxy S Relay 4G] CarpeNoctem:
I am on the official nightly
[Samsung Galaxy S Relay 4G] croogrog:
Are you using twrp? I think it will break wifi if you install cm 10.2
[Samsung Galaxy S Relay 4G] stephenclower:
Be sure you flash the CM-10.2 ROMs (staging or official nightly) with Clockworkmod Recovery. using TWRP will yield borked wifi for now.
[Samsung Galaxy S Relay 4G] chris122380:
What recovery are you using? TWRP recovery isn't currently supported in CM and will keep Wi-Fi from working. Also prevents the setup wizard from launching. I recommend the CWM recovery.
[Samsung Galaxy S Relay 4G] RodimusConvoy:
:eek: I thought CWM wasn't available for the Relay 4G
[Samsung Galaxy S Relay 4G] CarpeNoctem:
I am using CWM but reflash seems to have fixed the issue. Now I am facing excessive battery drain or the phone is not charging... I will revert to 10.1 for now.
[Samsung Galaxy S Relay 4G] chris122380:
I have had no battery problems so be sure to do a wipe before installing.
[Samsung Galaxy S Relay 4G] :
I was getting insane battery drain from Facebook, I had to remove it. Hopefully it gets updated soon.
[Samsung Galaxy S Relay 4G] dillalade:
Nard,

Im tempted to flash your latest nard build over my current 331 staging setup.

Advised?

Basically wanna trial the CMAccount feature.

Unwilling to flash the official nightly because im currently in love with the mpdecision that's baked into unofficial builds (including your personal builds i assume?)
[Samsung Galaxy S Relay 4G] :
I'm running that build right now and it seems stable enough
[Samsung Galaxy S Relay 4G] :
by the way, the Android Tuner app has a special mpdecision tab for tweaking the settings for this particular mpdecision mod
[Samsung Galaxy S Relay 4G] dillalade:
Now to actually research mpdecision to understand this apps mpdecision variables :D

As it stands, the default mpdecision mod drains 1.5% battery during long sleeps compared to ~3% battery drain without mpdecision :thumbup:
[Samsung Galaxy S Relay 4G] terminal addict:
Wait... what?

There are Official Nightlies, Staging, and "nard builds"? What are "nard builds"?
[Samsung Galaxy S Relay 4G] dillalade:
Yes.

Official CM builds = http://get.cm/?device=apexqtmo

Staging CM builds (cooperated by team ApexQ devs) = http://ls.infernix.net/jenkins/job/apexq-staging/

Nards test builds = http://ls.infernix.net/jenkins/job/apexq-nardholio/
[Samsung Galaxy S Relay 4G] CarpeNoctem:
I have some really weird issues here and I have no clue how to address them...

I reset completely my phone by going back to the official 4.12

After that I used heimdell to install the recovery available here: http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo

When i boot in recovery... BLACK screen...

I try to install this one too: http://xdaforums.com/showpost.php?p=44298607&postcount=4

Same result

Anything I missed??? I start to be very very confused.
[Samsung Galaxy S Relay 4G] terminal addict:
Ahhh.... Thanks! I think I have been to both pages before but didn't notice the -staging vs -nardholio. :o