yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Relay 4G] CarpeNoctem:
ok, so finally wiped completely the device, successfully installed CWM and flash CM10.2

a Few things I noticed

My phone does not wake up 100% using the power button, sometimes the screen just stays black

The back and the menu buttons are not working... they light up but... nothing when I press them

the battery seem to drain faster than before while it is not running anything, perception or reality

the rest so far look stable and functional so far

Thanks !
[Samsung Galaxy S Relay 4G] John5788:
I had the same problems. I ended up just buying a new Relay 4G and all the mentioned problems went away. I notice immediately that this one has a newer ARMv7 rev 4 SOC and my original one had an ARMv7 rev 0. Also the menu colors look different on the new phone vs the old phone.

I'm going to send my original phone back to Samsung for warranty and hopefully they just do a PCB replacement for me and get me up and running with the latest hardware.

Probably not what you wanted to hear, but there are only a couple of us that see these problems.
[Samsung Galaxy S Relay 4G] CarpeNoctem:
Thank but I would prefer not to have to buy a new phone...

It would be nice to have more feedback about those issue and the hardware revision and address them.

EDIT: I just installed the latest 10.1 and the menu and back buttons are working.
[Samsung Galaxy S Relay 4G] scotte9999:
Can somebody elaborate on what this specific issue is? I don't see anything in-thread, so I can't tell if this bug is "when both are transmitting at the same time, performance suffers" or more like "BT driver crashes if WiFi is enabled".

Is this a performance or a functional issue?
[Samsung Galaxy S Relay 4G] misteropinion:
It's a functional issue. I believe that it was explained toward the end of the 10.1 3.4 thread. BT doesn't play nice with 802.11[bg] wireless on the 2.4 band, and getting the radio/driver to follow the standard so that BT doesn't use wifi's space is problematic.

Or so I recall reading.
[Samsung Galaxy S Relay 4G] :
Wtf there are krait v0's out there? That explains a lot.

Ok genius? Where do you think this feedback is coming from? I CANT FIX A PROBLEM I DON'T KNOW ABOUT! "It would be nice" if before posting you actually had a clue whether it applies to you. Do a "cat /proc/cpuinfo" and post the results.
[Samsung Galaxy S Relay 4G] CarpeNoctem:
Man, you should take a deep breath and chill, because obviously you are over tense and over react to something completely innocent. So genius, take a break and calm down.

I was trying here to explain what I am experiencing and if you would simply say what you need in order to resolve the issue, that would be a lot more constructive that this kind of comments.

Anyway, back to the topic, if you are interested (?) like i said I moved to CM10.1 for the time being as I need to use my phone outside the country for a few weeks, if when I am back I move to CM10.2 I paste the log.
[Samsung Galaxy S Relay 4G] scotte9999:
I saw the discussion of spectrum use, but that's what made me think that this was just a performance issue (e.g., BT not being configured to avoid the 802.11 channel in use, or 802.11 not being configured with BT coexistence). It's still not clear to me from your response either, but I appreciate the response!

If one has WiFi and BT enabled in the system settings, can WiFi be used (on 2.4GHz bands)? If yes, then does that prevent BT from connecting while WiFi is associated to an AP?
[Samsung Galaxy S Relay 4G] :
802.11 is set up to use tdma to avoid bt and bt should avoid the wifi channel in use. They're not talking to each other. As far as I know, no AOSP rom with this wifi chip has this working very well on Bluedroid. If they did, I'd already have kanged the **** out of them.

It's not just a performance issue, they will completely cut each other out and whichever one ends up losing gets disconnected.
[Samsung Galaxy S Relay 4G] aawillma:
I have the same symptoms as these guys and didn't ***** about them because I didn't hear anyone else saying much about it (also, I was so happy with JB I happily dealt with them). Anyways I checked my CPU info in Android settings and saw the same thing. Didn't realize it was a rarity. I ran that log and got:

Processor	: ARMv7 Processor rev 0 (v71)

processor	: 0

BogoMIPS	: 13.50

processor	: 1

BogoMIPS	: 13.50

Features	: swp half thumb fastmult vfp edsp neon vfpv3 tls fvpv4 idiva idivt

CPU implementer	: 0x51

CPU architecture	: 7

CPU variant	: 0x1

CPU part	: 0x04d

CPU revision	: 0

Hardware	: SAMSUNG APEXQ

Revision	: 0007

Serial	: 0000XXXXX00000XXX

Hope that helps. Sorry for the manual transposition. I’m pastebin retarded.
[Samsung Galaxy S Relay 4G] wedg11383:
I can confirm I have identical information as aawillma and am having the same issues being described regarding power and home button not completely waking. I never said anything because I assumed they were just glitches related to the newness of the rom and would be sorted out eventually.
[Samsung Galaxy S Relay 4G] killkillkill:
What is going to be a very big problem in solving this latest glitch, is that none of us developers have access to a phone that exhibits these symptoms. To be frank, my phone works *flawlessly*. I get uptimes that span weeks, and battery life that spans days, and everything is fast and fluid.

What this means, is that we are left with the following three scenarios;

1) That this gets fixed by one of you who has one of these phones,

2) That somebody donates/loans one of these phones to nard or myself,

3) That this problem will not ever be solved.
[Samsung Galaxy S Relay 4G] gee one:
I have a rev 0 phone and a slow phone to boot (sec_pvs=0xfafa). Talk about drowning in the shallow end of the gene pool...

however, the phone has been pretty stable and battery life is great. I sometimes get those weekly reminders from t-mobile to reboot my phone (I installed the my account app from t-mo). I did notice some of the freezes mentioned above, but it's not frequent enough to warrant going back to stock.

I'm on a cm-10.2 build from august 18th. I've been too busy lately to flash the recent builds. I'll try to find some time this weekend to flash a more recent build to see if the problem is worse.
[Samsung Galaxy S Relay 4G] stephenclower:
I also have a rev 0 phone but sec_pvs=0 (I bought my phone last September). Battery life isn't great, but it may just be that the battery's a year old and can't hold much of a charge anymore. Ironically enough I don't know if the screen wakes up properly or not when pressing Power as my eyesight is shot, and the device otherwise works when using something like Talkback for access. If this combination is useful, I'm happy to run debug code on it. Shipping it away currently isn't an option.

Steve
[Samsung Galaxy S Relay 4G] killkillkill:
The specific reason I didn't say anything about cpurev0, is that there are plenty of cpurev0 devices that are working just fine, including at least one in the hands of one of us developers (not me though). Which means that it may have nothing to do with the CPU at all.

---------- Post added at 01:15 PM ---------- Previous post was at 01:13 PM ----------

Appreciate it, but let me make this perfectly clear; we can't accomplish anything by running remote debug code. Need to have phone in hands for an unknown amount of time to test at.

What do you mean by "battery life isn't great"? How long does a FULL charge (down to near shutdown) last?
[Samsung Galaxy S Relay 4G] stephenclower:
I'd say between 18 and 20 hours. I program for a living so understand perfectly well the need for having a problematic device in-house to truly get to the root of an issue. My device usage is likely unique as the speaker remains open at a much more frequent rate than most, and I'm sure that's causing more significant battery drain than the rest of you. I'm not too concerned at this point but thought I would toss this info out there in case it could be of any use.

Steve
[Samsung Galaxy S Relay 4G] :
I need the following information from pretty much everyone who cares about this rom. send it to my name [MENTION=652814]gmail[/MENTION]

The results of cat /proc/cpuinfo and cat/proc/cmdline

reboot the phone and dmesg | grep PVS and dmesg | grep socinfo

what symptoms (reboots, slow wake, etc) you are having

whether the performance seems to have varied between cm 10.1 and cm 10.2 or even specific timeframes/build numbers

and whether you are willing to part with your phone for testing. We have devs in Canada and the USA, these are the preferred places to get one from to save on shipping and what not.

This is the only way we are going to fix this problem with apparently defective cpus.
[Samsung Galaxy S Relay 4G] killkillkill:
Your battery life is *not terrible*, probably reasonable given your type of use. Better, in fact, than any HTC phone I've ever owned. Sounds like yours is not exhibiting any weird behavior at all.
[Samsung Galaxy S Relay 4G] stephenclower:
OK; just thought I would mention it since you earlier said you can get days' worth of use out of your phone. Oddly enough, I get better battery life on my G2 running an admittedly not-as-efficient build of Android 4.2.2 from www.flinny.org. I've sent my device info to Nard just in case.
[Samsung Galaxy S Relay 4G] orange808:
Ok. Good for you.

On the Relay, you can set your governour to the lowest setting: "Power Save".

This will lock the CPU at the minimum clock.

The phone can carry on as well as my old Sidekick 4G did normally and the battery life is fantastic.
[Samsung Galaxy S Relay 4G] killkillkill:
- Changes made in the CM performance interface only seem to affect the first core, so do not universally apply.

- The CM power interface has a minor glitch regarding the "low frequency", since in-kernel mpdecision affects the minimum cpu frequency to provide "boost".

- Setting power save governor can and does impact the process of waking up from sleep, since the first core will be stuck at a low frequency. Effectively, it will be a total turd until mpdecision comes back online and wakes up the second core.

I don't recommend the powersave governor.
[Samsung Galaxy S Relay 4G] Braccoz:
well, unless they changed it (which i don't think they did, after i reported the bug months ago and it got flagged as invalid because a random dickhead @ cm did not understand what i was talking about) the performance settings of CM only affects the 1st core...

so no matter what you set, the 2nd (and above) core will always go with default governor and clocks.

i had put a quick fix for that in my doubleshot build, if anybody wants to take it, it's in my github.
[Samsung Galaxy S Relay 4G] saurabhsaurabhrai:
Hey guys...

I'm not much aware of this modding/flashing/custom rom stuff...I have just updated my phone to stock JB and then rooted it...I have TWRP recovery installed on my phone...Now i want to use CM 10.2...I have also installed rom manager from play store...Can I use it for installing this custom rom.....?
[Samsung Galaxy S Relay 4G] chuckiev79:
Don't use twrp go here http://wiki.cyanogenmod.org/w/Install_CM_for_apexqtmo
[Samsung Galaxy S Relay 4G] saurabhsaurabhrai:
i tried but got confused after

*Mac OS X:

Heimdall Suite 1.4RC1 Command-line Binary: download

Place the libusb-1.0.0.dylib library from the zip inside /opt/local/lib on the machine.
[Samsung Galaxy S Relay 4G] stephenclower:
Trying to build

Greetings,

There are a few things in CM which I'd like to work on myself, and as a first step I'm setting up my build environment (Ubuntu 64-bit 12.04). Following the instructions found at http://wiki.cyanogenmod.org/w/Build_for_apexqtmo, I have been able to get as far as the step to run "breakfast apexqtmo", but I receive the following:

steve@devmac:~/android/system$ breakfast apexqtmo

including vendor/cm/vendorsetup.sh

vendor/samsung/apexqtmo/apexqtmo-vendor-blobs.mk:44: *** multiple target patterns. Stop.

Device apexqtmo not found. Attempting to retrieve device repository from Cyanoge nMod Github (http://github.com/CyanogenMod).

Found repository: android_device_samsung_apexqtmo

Default revision: cm-10.2

Checking branch info

CyanogenMod/android_device_samsung_apexqtmo already exists

Syncing repository to retrieve project.

Repository synced!

Looking for dependencies

Done

vendor/samsung/apexqtmo/apexqtmo-vendor-blobs.mk:44: *** multiple target patterns. Stop.

** Don't have a product spec for: 'cm_apexqtmo'

** Do you have the right repo manifest?

I presume I'm missing one or more dependencies, but I've yet to find out what's going wrong. Any pointers (generic or specific) would be appreciated.

Thanks,

Steve
[Samsung Galaxy S Relay 4G] CrunchBangPow:
SD Card

Anyone else have external SD card issues? Just switched over to the Official 10.2 from the old unofficial 10.2 and I can't find external SD anywhere.
[Samsung Galaxy S Relay 4G] OriginalGabriel:
That's just telling you to copy that library from the zip file to the /opt/local/lib folder on your computer
[Samsung Galaxy S Relay 4G] gee one:
what happens when you just type "brunch"?

Can you pick the relay the list from there? Mine shows "cm_apexqtmo-userdebug" as an option.

Also, I just realized that I have a local manifest from the teamapexq github. Maybe I'll try to build without it to check dependancies.
[Samsung Galaxy S Relay 4G] gee one:
I have a local cm mirror... I created a new folder, initialized the repo, and it seems to be syncing all the projects specific to the relay/d2

root@precise:~/android/cm-10.2# time brunch apexqtmo
including vendor/cm/vendorsetup.sh
ls: cannot access device/*/apexqtmo/cm.mk: No such file or directory
build/core/product_config.mk:233: *** Can not locate config makefile for product "cm_apexqtmo". Stop.
Device apexqtmo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_samsung_apexqtmo
Default revision: cm-10.2
Checking branch info
Adding dependency: CyanogenMod/android_device_samsung_apexqtmo -> device/samsung/apexqtmo
Using default branch for android_device_samsung_apexqtmo
Syncing repository to retrieve project.
remote: Counting objects: 1177, done.
remote: Compressing objects: 100% (477/477), done.
remote: Total 1177 (delta 491), reused 1147 (delta 467)
Receiving objects: 100% (1177/1177), 585.17 KiB, done.
Resolving deltas: 100% (491/491), done.
From git://github.com/CyanogenMod/android_device_samsung_apexqtmo
* [new branch] cm-10.2 -> github/cm-10.2
Fetching projects: 100% (1/1), done.

Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_samsung_qcom-common -> device/samsung/qcom-common
Using default branch for android_device_samsung_qcom-common
Adding dependency: CyanogenMod/android_device_samsung_msm8960-common -> device/samsung/msm8960-common
Using default branch for android_device_samsung_msm8960-common
Adding dependency: CyanogenMod/android_device_samsung_d2-common -> device/samsung/d2-common
Using default branch for android_device_samsung_d2-common
Adding dependency: CyanogenMod/android_kernel_samsung_d2 -> kernel/samsung/d2
Using default branch for android_kernel_samsung_d2
Adding dependency: CyanogenMod/android_hardware_samsung -> hardware/samsung
Using default branch for android_hardware_samsung
Syncing dependencies
...[blah]...

after syncing, it looks like I need to set up the device files.. What is in your vendor/samsung/apexqtmo/apexqtmo-vendor-blobs.mk file???
[Samsung Galaxy S Relay 4G] saurabhsaurabhrai:
But ther is no such folder/dir on my mac sir
[Samsung Galaxy S Relay 4G] gee one:
I think it appears when you install xcode or any other "optional" (non-stock) software.

You can probably create it yourself (as an admin), although there is probably some slick way to install dynamic libraries.

sudo mkdir -p /opt/usr/local/lib

then unzip your file to that directory.
[Samsung Galaxy S Relay 4G] gee one:
stephanclower: Line 44 should have a trailing \

vendor/samsung/apexqtmo/proprietary/vendor/firmware/libpn544_fw.so:system/vendor/firmware/libpn544_fw.so \

You can edit this directly on your machine to test, or maybe someone can push it to git to correct it properly.
[Samsung Galaxy S Relay 4G] stephenclower:
Thanks; that got it. I think I need more coffee or a boot to the head for missing such an obvious error.

Steve
[HTC Pico (Explorer)] ImPrath:
Im unable to install twrp please somebody help!
[HTC Pico (Explorer)] thewisenerd:
More info please?

Also, the twrp images are in the *.zip format. You need to extract it, and -

fastboot flash recovery [I]<name of image>[/I].img

I/most of the people will not be able to understand your question, as it seems meaningless, no offence, without any info.
[HTC Pico (Explorer)] Boyka123:
If you want flash using phone, just dowload recove flasher from store! Really simple.

Helped? Thanks maybe!
[HTC Pico (Explorer)] ImPrath:
thanks that helped :)
[Moto X General] ExonakiDev:
Post photos taken with your MOTO X.

I currently dont have a moto x so you guys can post your own....I guess!!!!!!:D

Update: planning on getting a moto x but they don't seem to launch our in India :confused:

Let's hope I get one!

~ExonakiDev:highfive:
[Moto X General] craigbailey1986:
I don't think any one has it yet....
[Moto X General] ExonakiDev:
Well they will.... Soon

$€nt fr©m My N€×us~4™
[Moto X General] imitenotbecrazy:
Here's some photos OF a Moto X and its available color options

sent from just the tip
[Moto X General] tacotino:
I just got my seed device, should have my noto in 4 days!!!!!
[Moto X General] ExonakiDev:
Cool!

$€nt fr©m My N€×us~4™
[Moto X General] karty:
Moto X sample shots

Moto X sample shots

http://www.engadget.com/gallery/moto-x-sample-shots-1/479482/#!slide=479498
[Moto X General] busixb:
Well, this is what I about expected from a Moto camera. I have seen in the right conditions and lighting pretty good shots with it, but as a 2 phone guy, this is why I will be carrying my Nokia 928 with me for photos and Moto for ecosystem and Google services. I heard most of these inadequacies can be improved upon with SW updates. We will see.
[Moto X General] solaris2k:
Gotta love the Lumia cameras. Gosh I miss my 920. It was so easy to take nice shots with that phone and every phone I've had since hasn't even come close.
[Moto X General] shea-bird:
The camera on this and the new droids quite honestly sucks. I don't think anyone is surprised, but you would think if they were going for an "iphone" like market, they would have put a little more emphasis on the shooter. the artifacts in low light pics are plain awful:crying:

Was seriously considering this to move from the N4, but not anymore. Every single review that has posted pics just don't look good at all.

I love moto, just wish they would step their camera game up a notch and not just throw around terms like clearpixel...it clearly doesn't help.

I am interested in seeing real world shots that ppl get with it though---sometimes they differ from the review photos.

Happy Shooting Moto X folks
[Moto X General] Psilocin:
Well if you were planning to get the MotoX mainly for its camera, then you obviously will be disappointed. It's not leading edge right from the start, but a simple software update to tweak how it adjusts and balances the light can easily improve the quality a bit. I always view cellphone cams as means to create passable photos.
[Moto X General] SysAdmNj:
They still look better than the N4's pics, at least I think so.
[Moto X General] shea-bird:
Yeah I'm not looking for a DSLR, but at least match the quality of the current flagships. They are a couple Gens behind with this cam (or so it appears). The S3 took better pics. My N4 is in the same boat...crappy cam, I've been looking for that vanilla phone with a good cam...Doesn't look like its gonna happen, might have to go back to the old root n rom method.

The Sony Honami could change that though.

Anyhow, still want to see the real world pics from the X...couple more days til we get a few samples.
[Moto X General] freeintruth:
Just got an email from them saying the shipping has been delayed :( does this happen to you as well?
[Moto X General] rajeshr:
Resized, but otherwise unretouched shot from my Moto X. This is just a shot from my office window - no artistic merit! :)
[Moto X General] DonDizzurp:
any comparative shots out yet? vs htc1, s4 and nexus4?
[Moto X General] rajeshr:
Here's a quick comparison shot between the MotoX & Samsung Galaxy S4. These shots were taken about 30 seconds apart and have no post processing done other than resizing each to a width of 640 pixels. The one on the left is from the Moto X and the one on the right is from the Galaxy S4.

I haven't tested the Moto X in low light or any challenging conditions.

Initial thoughts:

- The one from the GS4 os a much more accurate colour rendition of the actual scene.

- The one from the Moto X has a purplish cast to the picture (see the colour of the sky).

- There is a lot more detail in the picture taken by the GS4.
[Moto X General] shea-bird:
Exactly..Like I said...this camera is generations behind the current top shooters. Its a shame, and there's really no excuse other than being ignorant and disconnected from what customers want. They even hyped the camera with this ClearPixel nonsense - please dont hype a horrible camera. I would have DEF bought this phone had it contained a good camera.

BAH:mad:

Eager to see some more shots, but they could have done WAAY better with this.
[Moto X General] rajeshr:
There are issues but I'm not sure whether they are due to the sensor or the processing done on the resultant image. The former would be a huge issue, while the latter is something that could be addressed via a software update.
[Moto X General] 18t:
wow, S4 makes the X look like a joke.
[Moto X General] aldouse:
tonight at work.....
[Moto X General] tyleras3:
Took a picture of my dog :P
[Moto X General] gtg465x:
South bay, wut wut
[Moto X General] aldouse:
how'd you know?!?!
[Moto X General] gtg465x:
I just moved here a few months ago. It has a very distinctive look.
[Moto X General] aldouse:
lol.... thought you were going to tell me you know that structure and worked there too! haha
[Moto X General] gtg465x:
Maybe I do ;). I'll be watching you...
[Moto X General] a17o17ymous:
Out into the Pacific Ocean.
[Moto X General] ExonakiDev:
Guys did the over the air update make the camera color saturation situation better???

$€nt fr©m My N€×us~4™
[Moto X General] plammos:
NICE pic dude!
[Moto X General] SupaSwag:
Just want to see what camera apps you guys are using besides the stock moto one. I took a couple of photos comparing the stock one to ProCapture. Compared to the stock Moto X app, ProCapture tends to take better indoor shots that are less noisier. I've been using ProCapture for a long time and on previous devices I preferred to use it when on AOSP builds. I've been wanting to purchase Camera Awesome but I'm still not convinced with the $2.99 price. Anyone can vouch for Camera Awesome?

These obviously aren't the original full res shots.

Stock Moto X Camera App:

For the flower shot, I think the Moto X automatically turned on HDR mode.

ProCapture:

No HDR mode for the flower shot.
[Moto X General] wwr8bz:
Not a bad view
[Moto X General] wwr8bz:
Also used a bit of zoom on this one, didn't want to get too close!
[Moto X General] Elslunko:
Hello cat
[Moto X General] radeonboy:
Just a pic of downtown Vancouver
[Moto X General] dicarli:
What Android version are you in?
[Moto X General] A2Trip:
Second snow day in Wisconsin...gosh I hate winter lol :banghead:

Sent From My Moto X (Ghost USC XT1055)
[Moto X General] brycekerr:
Sent from my gPhone
[Moto X General] a17o17ymous:
Thanks!

---------- Post added at 09:12 PM ---------- Previous post was at 09:07 PM ----------

Sunset behind The Tower Bridge along the American River in Sacramento, Ca.
[Moto X General] dicarli:
Just took it from my room's window

Enviado de meu XT1058 usando Tapatalk
[Moto X General] mazubo:
Great pic! It's nice to know someone from the same city in here!
[Moto X General] gtg465x:
This thread need reviving.
[Moto X General] g4ess:
taken on att moto x 4.4 rooted
[Moto X General] gskelter:
A gift from my gf

Enviado desde mi XT1053 mediante Tapatalk