yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] hamagc:
Ha so sure enough, I flashed TPR this morning and downloaded the NFL app and it came right up for me. Very strange!!

however looking at the app, it says NFL Mobile from Verizon? Not sure if they all do but it's the same app in the market. I don't have a non-rooted phone to compare it with lol.
[Sprint Samsung Galaxy S III] carrilloevo:
It's there a flash able zip that changes status on phone from modified to normal ?
[Sprint Samsung Galaxy S III] KennyG123:
Cool! And yes Verizon owns it at the moment. Subscription and streaming only available on their service.
[Sprint Samsung Galaxy S III] hamagc:
The modified status doesn't seem to be the issue as my moar ROM is set as normal. I'm assuming something else deeper in the ROM.
[Sprint Samsung Galaxy S III] lvpre:
Just read this:

http://www.androidcentral.com/nfl-redesigns-mobile-app-inexplicably-blocks-rooted-users

May answer your question
[Sprint Samsung Galaxy S III] KennyG123:
Apparently not so inexplicably...lol. Now if someone can find out what the app is looking for (logcat?) and why TPR is working someone can make a bypass of the root check. I am pretty sure MOAR uses Supersu like TPR and not Superuser, so it is not that.
[Sprint Samsung Galaxy S III] lvpre:
I wonder what happens if you disable supersu in the app? Then run the program.
[Sprint Samsung Galaxy S III] hamagc:
I have supersu on moar. Tried disable and remove root. Even unrooted was a no go. Wife has rooted md4 with superuser, same results.

Kenny I'll try to get a logcat posted today.
[Sprint Samsung Galaxy S III] CNexus:
Don't do a regular adb logcat...it won't catch everything

Instead, run the following to grab all logcat buffers that it might shoot the "goods" into:

adb logcat -b system -b main -b events

Then post the logcat...this is interesting though because I'd like to see how exactly they are determining "modified" status...

Can someone upload the apk of the version that blocks access on rooted phones? I wanna see if I can't decompile it and find out where it's blocking access...
[Sprint Samsung Galaxy S III] hamagc:
ok see attached log. had to rar it since it's too big for pastebin and too big to attach as a txt file.

This is running the command per cnexus, tapping on nfl mobile, letting it load then clicking ok on the root message.

let me know if you need any or commands or anything run.
[Sprint Samsung Galaxy S III] hamagc:
See attached. This is new NFL app not working on root.

http://db.tt/8S5VidQ6
[Sprint Samsung Galaxy S III] KennyG123:
Called NFL Mobile in Play.
[Sprint Samsung Galaxy S III] CNexus:
No internet connection except though a computer ATM :)

Can someone give me the

exact

message that shows up when it blocks access? [MENTION=2138255]hamagc[/MENTION] maybe you could open it up and then post the message real quick?

EDIT: Nvm, I found it. Let's break some denied access!

EDIT2: About to test it now

EDIT3: Tested and it works :)

Check themes and apps if you want it :good::good:
[Sprint Samsung Galaxy S III] dj_aj:
Bloody hell...brilliant and fast work on that...

Now just awaiting for you to upload the apk! Thanks Bud!
[Sprint Samsung Galaxy S III] hamagc:
Amazing!!
[Sprint Samsung Galaxy S III] CNexus:
App is here: http://xdaforums.com/showthread.php?t=2395333

Enjoy!
[Sprint Samsung Galaxy S III] hamagc:
Working beautifully! You may have just made a few thousand fans happy lol
[Sprint Samsung Galaxy S III] KennyG123:
You may Want to post that in Android themes and apps as I have seen requests in all the Sprint and AT&T forums.
[Sprint Samsung Galaxy S III] CNexus:
Will do. Maybe you can move the thread over there?
[Sprint Samsung Galaxy S III] flastnoles11:
Lol, just said the same thing in the other thread... ;)
[Sprint Samsung Galaxy S III] tkeyes:
nfl mobile or nfl mobile 1.0

which nfl mobile are you using, since there are 2 in the market

NFL Mobile

https://play.google.com/store/apps/details?id=com.gotv.nflgamecenter.us.lite

or

NFL Mobile 1.0

https://play.google.com/store/apps/details?id=com.mobitv.client.nfl2010

both apps have been updated in the past month

and the people that have been use the app; in odin mode does it official because i have unrooted and it since doesnt work.
[Sprint Samsung Galaxy S III] flastnoles11:
Second one is for Verizon only and since I'm on sprint must be the first one ;)
[Sprint Samsung Galaxy S III] Speedin07si:
Just a heads up there is a update for the app, this time it clearly states it won't work on rooted devices.

Sent from Under water
[Sprint Samsung Galaxy S III] CNexus:
Haha, nfl makes me laugh

Already patched it and uploaded to my thread btw
[Samsung Galaxy S Relay 4G] Nardholio:
Android 4.3 for the best slider on the planet.

Preview of soon to come official CyanogenMod!

Features: Inheritance from d2! This includes oddities like d2 RIL blobs! See as they request LTE and your phone LAUGHS IN THEIR FACE (doesn't actually affect performance)

The camera actually works! This includes flash while video recording!

Pheer the multi gigabyte d2 MMS sizes that your CARRIER WON'T LIKE

Screenshots: Submit some and I will post them.

IMPORTANT: TWRP DOES NOT WORK TO FLASH THIS. YOU WILL NOT GET WIFI IF YOU USE TWRP

Credits:

Noptys: without him we wouldn't have AOSP at all on this phone

Teferi: Did something to make the camera work or something

Kornyone: Inspired us to keep going

Infernix: Owns a build server that can make a full clobber build in 12 minutes.

Lbcoder: Made the camera work, again

Me: Showed d2 who was BOSS

Gapps package: http://goo.im/gapps/gapps-jb-20130813-signed.zip

Nightlies: http://ls.infernix.net/jenkins/job/apexq/

Build Manifest: https://github.com/TeamApexQ/hudson/blob/cm-10.2/cm-10.2.xml

Latest Bootloader/Modem (required): http://xdaforums.com/showpost.php?p=41209211&postcount=1
[Samsung Galaxy S Relay 4G] Nardholio:
Bug list:

Wifi/Bluetooth at same time is no worky

USB charging is very slow

You tell me.
[Samsung Galaxy S Relay 4G] janejunx:
CWM

Does anyone have a CWM recovery-flashable zip handy? I only see the odin-flashable one in the Contents thread.
[Samsung Galaxy S Relay 4G] janejunx:
Nevermind, found it. Posting it here for anyone else who need to switch to CWM.
[Samsung Galaxy S Relay 4G] dillalade:
That's old, get 6.0.3.3

How, I here you ask?

From jenkins on either of the latest nightlies pages, below the actual Rom zip download you will see a recovery.img (yes they publish a cwm recovery with every nightly if not already noticed.)

Download it!

Now using that recovery zip of 6.0.2.8 you've just posted above, replace the recovery.img in that zip with the one you just downloaded from jenkins.

That simple.

Flash your moded zip file from within recovery.

Goto Advanced, Reboot into recovery, to ensure the recovery did indeed flash correctly and that you've subsequently bumped up from 6.0.2.8 to 6.0.3.3 (unless 6.0.3.3 has been superseded by an even newer version.)

Job done son :thumbup:
[Samsung Galaxy S Relay 4G] janejunx:
I'd done so, but 6.0.3.3 didn't have the ability to flash from an external sd card, so I went with this one.
[Samsung Galaxy S Relay 4G] Nardholio:
fstab changed in 4.3, CWM still hasn't updated yet to support external sd, I think
[Samsung Galaxy S Relay 4G] croogrog:
Are there any charging issues? Other than usb charging. They kept me away from the 3.4 kernel previously.
[Samsung Galaxy S Relay 4G] Nardholio:
Charger issues all fixed, except USB is stuck at 100mA instead of the normal 500mA. Normal AC/dumb/fast chargers are unaffected.
[Samsung Galaxy S Relay 4G] dillalade:
Hmmm, weird. I'm on a 6.0.3.3 cwm and have only been flashing from extSd. Anyway this is off topic, create a new thread and let's get it resolved there :thumbup:
[Samsung Galaxy S Relay 4G] Nardholio:
One note about Android 4.3, it requires selinux, which is a security auditing policy. We're working on properly implementing those. In the meantime, you could delete /system/bin/auditd to prevent it from trying and failing to enforce the policies constantly (battery drain)
[Samsung Galaxy S Relay 4G] stanelie:
Hello.

I just flashed this rom.

Somehow, I do not get prompted for root whenever an app requesting root is launched. It just fails saying it needs root without giving me the possibility to enable root.

Thoughts?

Edit :

Never mind, I managed to enable it by turning on developer mode by tapping repeatedly on the build number in the about menu.
[Samsung Galaxy S Relay 4G] chris122380:
CM does have an official source for the Galaxy S Relay 4G. It would be nice to see a official stable build of CM 10.2.

CM info page: http://wiki.cyanogenmod.org/w/Apexqtmo_Info

Source Repositories:

Device: http://www.github.com/cyanogenmod/android_device_samsung_apexqtmo

Kernel: http://www.github.com/cyanogenmod/android_kernel_samsung_d2

I have not yet tested this or rooted my phone. I would once there is a stable version. Just thought I would let you know where to get the official source code from and maybe if your a dev you could help make it stable.
[Samsung Galaxy S Relay 4G] dillalade:
LoL.

Do you know who your responding to.

Funny
[Samsung Galaxy S Relay 4G] chris122380:
Sorry but the page said Unofficial and the source URLs are different.

I am waiting to root my phone once there is a good stable ROM.
[Samsung Galaxy S Relay 4G] dillalade:
Well to put it politely, the person you are questioning above is a leading member of team ApexQ who have collectively managed to get those CM sources in to the CM tree you listed with there hard work & determination.

Read the threads and become familiar with your device & the team behind the developments for our device.

Those CM sources didn't get there on there own ;)

You will stumble across stable Roms, not least CM10.1 thread, they are stable and kick the cr@p out of the stock touchwiz you are currently running.
[Samsung Galaxy S Relay 4G] Nardholio:
Lbcoder fixed all the camera bugs. Also if you check our build manifest, this is 100% pure CyanogenMod.

that just leaves buglist as slow usb charging, and usb/bluetooth at the same time.
[Samsung Galaxy S Relay 4G] janejunx:
As of build 290, my front-facing camera's image is upside-down?
[Samsung Galaxy S Relay 4G] Jason78729:
Great work devs. I'm working tomorrow but if time allows I'm going to update to the latest nightly to start testing.
[Samsung Galaxy S Relay 4G] Nardholio:
Try clearing data in the gallery app
[Samsung Galaxy S Relay 4G] janejunx:
No go. This is in Focal. Live image is flipped on front-facing camera and when I try to take a picture, it crashes.

Clearing data didn't do anything. Even cleared QuickPic's data just to make sure.
[Samsung Galaxy S Relay 4G] stanelie:
I am unable to charge using a little Apple white charger cube that I have been using for years with this and other phones.

I can only charge when I hook up to a computer.
[Samsung Galaxy S Relay 4G] klokwyze:
Looks like I'll wait on upgrading since my current is working great. Pretty much flawless. 10.1 (2013-07-07).
[Samsung Galaxy S Relay 4G] killkillkill:
I'll give you a little hint: You see the link that says ***BUILD MANIFEST***? CLICK IT AND READ!!!!

---------- Post added at 03:21 PM ---------- Previous post was at 03:19 PM ----------

That's not a camera bug. That's just FOCAL. Focal is basically way, way, way, WAY pre-alpha. Totally unsuitable for human consumption. Only good for vampires while in the state of being a bat and hanging from the ceiling.

---------- Post added at 03:22 PM ---------- Previous post was at 03:21 PM ----------

10.2 is far more flawless.
[Samsung Galaxy S Relay 4G] :
https://twitter.com/wonkydude/status/365479239685906435

:(
[Samsung Galaxy S Relay 4G] Kueber:
Um.. wtf? "Fake version"?
[Samsung Galaxy S Relay 4G] :
I need more information. I need to know what build number you are running. Please provide me with a pic of the bottom of the charger showing the model number/etc of the charger. And if you could, please go to an adb shell and type "cat /proc/kmesg" and send me the log showing you plugging and unplugging the charger. Also please give me a better description of what happens besides "unable to charge".
[Samsung Galaxy S Relay 4G] :
trololol
[Samsung Galaxy S Relay 4G] janejunx:
Got it! I'll switch back.
[Samsung Galaxy S Relay 4G] Braccoz:
lol who is he?
[Samsung Galaxy S Relay 4G] gtmaster303:
http://trololololololololololo.com/ :D
[Samsung Galaxy S Relay 4G] gee one:
I just watched that and I'll never get those 3 minutes back.

In build related news, I built from source and everything seems fine. Keep it quiet because I don't want to get reported to the repo police. I haven't flashed it yet because I forgot my phone today. I will sync and flash this weekend.

Thanks- I think it's impressive to have 4.3 on our device so quickly.
[Samsung Galaxy S Relay 4G] dillalade:
It's very impressive.

Our team of devs are kicking ass, CM uptream is to too slow for ApexQ hahaha

Thanks for making this device what it ought to be, big respect :thumbup:
[Samsung Galaxy S Relay 4G] stanelie:
Hum...

I have no idea what was wrong, but today, it works.

Yesterday, with build 289, it wasn't doing anything when I was connecting to the charger, it was only detecting something when I was connecting to the computer, using the same USB cable...

Weird... I'll send you those logs if I can reproduce the issue.

Thanks!
[Samsung Galaxy S Relay 4G] gtmaster303:
Not CM related.

EDIT: thanks mod for cleaning post
[Samsung Galaxy S Relay 4G] croogrog:
Having the same problem on build 291. Not one root request in my su logs, even with developer options enabled.

Got it to work by changing 'developer options>root access' to apps and adb from apps only.
[Samsung Galaxy S Relay 4G] kilr00y:
so did i, hoping for the guy getting shot in the head at the end or something... but nothing.. bah...

btw: i'm back online.. my it equipment had a meeting of the third kind with a power surge... all of it.. still scraping files tpgether from randomly made dvd/cd backups.. having a RAID5 is nice because you don't need backups... unless lightning strikes 3 out of 5 discs :-/

expect me to be more active again :)
[Samsung Galaxy S Relay 4G] DOMF:
Your example is the very reason that no one ever says you do not need backups with RAID-5 ;)
[Samsung Galaxy S Relay 4G] gee one:
I have 10TB of raid 6 and I do monthly offsite backups of critical data. Don't tell the NSA.

In build related news, I'm building nightly's from source. They work well, although I get server errors when I try to install or update from google play. Also video camera display resolution is pixellated and hangs when done recording.

I get random "stop responding" toasts from google music and other google apps. I did not wipe data... yet. I've just been too lazy.

sent while running with scissors
[Samsung Galaxy S Relay 4G] stephenclower:
I'm about a week late coming into this thread, but so far 4.3 is running way better than at the end of July. Out of curiosity, why was switching back to CWM necessary for Wifi to operate? Also, is it still required to remove the /system/bin/auditd file? I have for the moment to keep battery levels optimal.

Thanks,

Steve
[Samsung Galaxy S Relay 4G] :
We have an install script to patch the wifi NV file with your MAC address (a rather ingenious solution, quite a bit different from other phones with the same wifi chip. You can thank Lbcoder for this as well as fixing the camera). The script didn't change between cm-10.1 and 10.2 but it just straight up doesn't run with TWRP on cm-10.2. I have no idea why. A newer TWRP might fix it but I haven't had time to produce one.

Auditd still does nothing but eat battery. Upstream d2 needs to get their selinux fixed.

In other recent news, Lbcoder also fixed a slighlty blue tinge to the colors you may (or may not) have noticed and introduced a color shifting mod, that you can find in Advanced settings for now. CM-10.2 will eventually do away with device specific settings modules but the option will not be lost, it will simply shift somewhere like display options.

I've heard it said that audio quality increased quite a bit when we switched kernels. We also implemented much higher speed wifi by switching to a newer driver. I spent most of the weekend debugging running BT and wifi at the same time and as far as I can tell we're just running too much data through at the same time, and wifi suffers while BT does not. (I found that by playing with options I could make the opposite result true, make wifi stable but cut out BT). Hopefully we can make the pipe or the buffers bigger, otherwise we may have to cut audio quality or wifi speed to make all the data fit at the same time.
[Samsung Galaxy S Relay 4G] :
Camera currently does not work without gerrit cherry-picks. You can get the current list of cherries by clicking on build parameters on the Jenkins server (so http://ls.infernix.net/jenkins/job/apexq/303/parameters/? for instance). You can download the cherries from review.cyanogenmod.org, which is where new code for Cyanogenmod is stored for review.
[Samsung Galaxy S Relay 4G] stephenclower:
Thanks for the info. I'll be sure to kill auditd when I flash new builds until the selinux jazz is sorted out. Re audio quality, are you referring to the built-in speaker or BT?

Thanks as always for the hard work you guys have been doing.

Steve
[Samsung Galaxy S Relay 4G] Renae27:
UGH!

Is anyone else having an issue where the device simply turns off? This has happened to me about 100 times now, or more, since about 12 midnight when I started attempting to move from the "cm-10.1-20130309-UNOFFICIAL-apexqtmo.zip" (I'm sorry I don't remember the build number but I am certain it would be a single build day) to cm10.2 build 303 "cm-10.2-20130812-EXPERIMENTAL-apexqtmo-303.zip". I don't remember ever having this issue when I flashed the original ROM I mentioned above. I did just flash down to build 263, the last stable 10.1, and while entering my GMail account info in the setup phase it did the same thing, just turned off. I left it for about 20 minutes and booted it again and it's since been working, a welcome change to what I've been dealing with after installing 10.2.

To be clear, my device will turn off at random times. It will usually stay on if I don't touch it and simply turn the screen on to see if it's still on. But mainly I've been doing things to restore my apps. It always turns off when in the setup phase, usually 3 or 4 times, although it will remember most of what I had done so each time I turn it back on it continues from a later position. When it turns off the LED at the top is sometimes on and sometimes off when it's plugged in, although this may have more to do with the temperature of the device (disabled charging after a certain temp). One other thing to note, when I leave it and only use it when needed I have answered a couple calls and it never turned off mid-call.

My device is usually reading low 40's when turned on to as much as 52 degrees Celsius when it's running processes. It can be at any temp and turn off. At one point I was sitting in front of an AC and the device was as low as about 28 degrees and it still turned off so I don't think it's strictly temperature related. Although I think this device runs hotter (under normal use) than any smart phone I've had over the past 15 years.

To turn it back on I have to remove the battery about 90% of the time. I always try the power switch about 3 times over about 20 seconds before resorting to pulling the battery.

PS - Looks like build 263 turned off again in the time it took to write the last 3 paragraphs. The LED was off. I removed the 1A USB charge and plugged it back in and the red LED came on and the phone kept vibrating once a second. I couldn't get it turned on until I pulled the battery to power it back up.

I have 2 official Samsung batteries. I am rooted and unlocked and running CWM (latest from the nightly builds as of 12am this morning), baseband is T699UVLH1.

I think it's an old modem (if baseband is the modem) but I couldn't find mention of modem version needed for 10.2. I'll see if there is an update...
[Samsung Galaxy S Relay 4G] Renae27:
I have an almost exactly detailed account of what happened right after my lost post until 18:12 EST. A lot of shut downs after installing 10.2 again.

Shortly after that on my bike ride home tonight (about 30 minutes) I flashed back to my original 10.1 build mentioned initially and not one shut down. I was able to install almost all my main apps and settings within my 30 minute bike ride. So I don't think it's my phone and it's definitely something in the 10.1 build. I would like to try, if possible, the last non 3.4 kernel and the first 3.4 kernel to see if that's what's not working on my phone.

I'll start a new thread if desired. I can post the mile long short hand list of everything that happened in the hour or two after the last post. I would also be very willing to send any logs, which is probably 100 times more valuable than my notes, please let me know exactly what you want and I will flash back.
[Samsung Galaxy S Relay 4G] :
As of build 304, there will be a hard-coded requirement for the latest bootloader and modem. The rom will not flash without it.

https://github.com/CyanogenMod/andr...mmit/cc73bf4fd0b9212f0b56c93427c0442fdaba6fb2
[Samsung Galaxy S Relay 4G] Renae27:
I flashed the modem and bootloader from your 10.1/3.4 thread with no change at all. I didn't find any mention of the modem or bootloader elsewhere in this thread or in the install guide so that may have been a bad assumption on my part. Please let me know if those are not the right files.
[Samsung Galaxy S Relay 4G] :
Also as of build 304, selinux is enabled, albeit with no rules. Do not delete auditd anymore
[Samsung Galaxy S Relay 4G] :
If a wipe of your phone doesn't fix your problems, I got nothing man. I've never heard of anything that bad before.
[Samsung Galaxy S Relay 4G] killkillkill:
Uh yeah... typically, one would read the very first post of a thread to get the general idea. Especially the very last line of the first post. Hint: READ IT.

---------- Post added at 03:01 AM ---------- Previous post was at 02:21 AM ----------

Except when something is running right out of control, it should be running quite COOL. This is a very cool running phone compared to most others. Sounds like there must be something particularly unique about yours.

I would like you to check if there are any processes running out of control (i.e. using a lot of CPU) -- check (in a terminal) what says from "busybox top" command. Install the application "cpu spy" and check how much time is being spent in what frequencies. Make sure its spending most time in DEEP SLEEP. If not, you will need to check what is stopping it.

What gapps package (if any) did you install? There are ones KNOWN to cause problems. You did upgrade to a 4.3 gapps, didn't you?
[Samsung Galaxy S Relay 4G] chuckiev79:
Running 0810 build and all is well except two small issues. One I have many apps and group some together on homescreen and after a time some are dropped out. The second is the alt function does not enable the special characters on physical keyboard aka ) - *! And ;
[Samsung Galaxy S Relay 4G] Jason78729:
Just FYI , if you update your recovery to the newer clockwork mod 6.3.5 (or as of build 304 I installed) the you don't have the option to flash from the external sdcard. Thought for a second I was going to have to start from scratch cuz all my flashable zips are on my external sdcard.
[Samsung Galaxy S Relay 4G] croogrog:
I had to do that with the 291 build. My custom flash counter is at 2 now.

Let us know when "install zip from extSDcard" is available again in the recovery.img.
[Samsung Galaxy S Relay 4G] infernix:
A quick workaround while in recovery:

adb shell 'mkdir /data/media/1; mount /dev/block/mmcblk1p1 /data/media/1'

We'll look into it.