yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Appreciate taking time to test this. Can you please share the log when you get that error?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Another test build for FFC:

https://www.androidfilehost.com/?fid=24499762636002026

Please share log with proper explanation on how the bug can be replicated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Any feedback on this build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
plz any1 around can test this.. Cant do heavy dloads at the moment..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yoshkapundrick:
Novice

I did a clean install with test build 4/17.

With Open Camera app the rear camera works with video and stills. However, the front camera it hangs with both stills and video. Further while using the front camera for both stills the camera itself becomes unresponsive. (if you then try to use the stock camera app (after using Open Camera and not rebooting) it errors out stating the camera is unavailable).

The stock camera app rear camera works with both video and stills. However if you switch the front camera the app crashes or the entire phone locks up. With the simple hang, a pop up occurs with the statement "Camera is not responding. Do you want to close it?" .

---------- Post added at 06:09 PM ---------- Previous post was at 06:00 PM ----------

sorry but unrelated to the front camera issue the stock app File Manager in this build is unresponsive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nomelas:
should I update via the cyanogenmod update? or only update from the downloads on this thread?

also how is this different from the nightlies?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Edgehead123:
Use the download links on this page, matrixzones are not the same as official nighties.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Edgehead123:
Ffc crash i747m on 04/17 FFC test build

Wiped both caches, data, internal storage

Flashed with open gapp pico

Set open camera as default

Never opened cyanogenmod camera

In open camera: pressing capture button for FFC picture results in the app becoming completely unresponsive. Clearing all open apps and force stopping open camera results in open camera opening with a black and error message saying another app is using the camera. Same result if you try to open cyanogenmod camera.

Both apps remain like this until the phone is restarted, then they work like normal.

Attached below are 2 sections of a catlog taken as open camera was crashing. I'll try again for a larger one, I've been having problem's keeping it under 500kb, but these 2 look too small.

So yea, brand new flash with a completely clean internal storage and the FFC crashes the same way as it always has the last few months.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Edgehead123:
Did another FFC open camera picture crash. This time selected partial from "beginning of crash" line in catlog.

Side note, Bluetooth media works :D

Notification light still trapped in blue only :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Thank you.. Can you do this again with stock camera and share log ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
I don't think I need any more log. Thanks for your effort [MENTION=6738419]Edgehead123[/MENTION]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Regarding Bluetooth, were you able to get media and phone enabled at the same time and working? I have been busy at work lately and am unable to spare the 2 hours it takes to back things up and then flash and let apps optimize.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cLogic:
flashed 04-20 build last nite ... was running fine ...

just got off the phone after two calls, attempted to use ffc in imo to take a pic ...

device froze, then rebooted ... seemed ok

noticed that it said no service

baseband is correct

imei = unknown sv = 00

eventually received service, but non-functional and from different (prolly backup) carrier, in roaming mode

multiple reboots .. no change

pulled and re-inserted sim ... no change

imei = unknown sv = 10

restored twrp backup of 04-18 build ... no change

backed up internal data partition to sdcard

flashed stock nh4 .. no change

anyone have any known working method on s3 4.4+ to fix imei (baseband is ok) ?

thanks in advance

---------- Post added at 06:31 PM ---------- Previous post was at 06:26 PM ----------

sorry ... wrong thread ... altho help would be appreciated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Origin_X:
Is bluetooth working in the new test build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Status Update - I am stuck with some boot problem of my VM for the last 1 week. I am not sure what happened, so with no leads on how to fix this - I have restored my Old Backup (Comes to my rescue)

I will keep you guys posted.

I have some leads to fix the FFC which I will try once the VM problem is fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OffsetX:
how to fix speaker volume? very load. I fix this bug vol+ to max, then vol- to min.

After that, the sound becomes normal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Something is not allowing shell access

I finally, after a bunch of RRs on TW, decided to install this build.

When trying to access a shell on 4/17, I get traceroute and traceroute6 screwing up the commands. I saw this in another device's CM13 thread.

This also appears to be affecting root access in apps like TiBu and FX Root Access.

Because for some reason I can't upload from the browser, I typed out the important info. This was from opening the built in terminal.

traceroute: unknown host ro.cm.device
id: invalid option -- u
Usage: traceroute6 [-dnrvV] ...blah blah blah
@:/ $ cd sdcard
@:/sdcard $ ls
Usage: traceroute6 ...blah blah blah
@:/sdcard $

I am running this on a d2can, this is the first time on this rom, and it was installed on a clean system. I installed 4/17 then open gapps 4/10 nano. I didn't feel like redownloading a package.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
[MENTION=4551784]matrixzone[/MENTION]

I think I figured it out. That build has a bad Toybox installation. I fixed it by copying toybox from my other phone on a newer CM13. Everything, so far, works now.

Edit: Could we please see a (maybe separate) kernel with some stuff from the featured ones like KT747? I would like to see some more governors, maybe like smartassv2, gaming, asswax, scary, pegasusq, ktoonservative, lionheart, badass, fantasy, etc. (Dont need them all). OC, S2W, fast charge and voltage control would be nice, too. Obviously not a priority.

Thanks in advance; and I can understand if you can't do it or don't want to.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Fix for 4/17

Flash this in TWRP. It fixes ADB shell, terminal, file manager and root access.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Would feel more comfortable with a listing of what is fixed. Like, front camera, Bluetooth, loud audio, GPS hanging, compass not calibrating....?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Uh… no. ?

I literally just installed this ROM two days ago.

This fixes mostly software stuff, especially root things:

ADB shell

Terminal access

File manager

practically every root program

That is what is fixed.

BT issues I think is an upstream bug.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Thank you for the list. You can't just say it fixes literally everything, because obviously it barely touches on the number of issues people are having.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
I never said literally everything, I said virtually everything.

But yeah, it was a bit misleading. Sorry.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
So I randomly decided to try Bluetooth audio on the latest nightly (04/26), and it works!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Cool. I will have to download the new build. I don't use BT Audio, but I am assuming Toybox will be fixed.

As for the looooud audio, I heard that installing viper4android will help that, though those were coming from the ones with the more common issue, too quiet.

I'll try it and report back.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Does it work with phone and audio both enabled at the same time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Workaround for Loud Audio

Workaround for loud audio

Instructions: (follow carefully, or you might get a bootloop)

When you get a permission request or a SuperSU dialog, allow it.

1. Flash the two attached zips and reboot. This will switch you to SuperSU Systemless. You will need to re-grant root access to your apps. Your phone can, and will fail to boot a few times, give it ~5 minutes then reflash the rom if it is still bootlooping.

2. Open the newly installed ViPER4Android and follow its instructions, reboot.

If it doesn't work:

• go to Settings, Developer options, Local terminal and check it.

• Open Terminal.

• Carefully type "su" without quotes and hit enter.

• Type "setenforce 0" and hit enter

If that fails, flash my toybox_patch.zip fromba few posts before.

• Now repeat the ViPER4Android setup.

3. If you haven't already done so, reboot.

4. Open ViPER and do Menu, Driver Status and make sure it says running. Press back. Now do exactly as I say.

5. Press Menu > UI Setting >Moderate.

6. In phone speaker, check Enable (the first check in the list).

7. Scroll all the way down.

8. Click the last item, "Output gain".

9. Now this comes down to personal preference. You want a negative value, I use -14dB; higher number = louder. 0 is the default, don't go above 0!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Reaper1015:
HI

um when i install the ROM it tells me insert sim card. when i had the stock ROM, the phone was unlocked and any sim card worked. ive tried different cm13 ROMs but all do the same. however since i got this error i did not move further to install GAPPs so yah thats my prob. :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
What model of s3 do you have and are you running the latest modem/bootloader combo for that model?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mattaw2001:
Alert: Google has broken Chrome 50 & 51 on the Qualcomm s3's running 6.01 as our CPU has a buggy neon accelerator :(. The left out a "don't use neon" on our chipset.

Error is: ERR_SSL_BAD_RECORD_MAC_ALERT

Bug report here:

https://bugs.chromium.org/p/chromium/issues/detail?id=606629

Patch appears to be in the works, for now use Firefox or similar.

Note: seems some Qualcomm s3s have a bug fixed chip revision in them
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Firefox and Opera, they be good.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Try flashing gapps also when you first flash the rom.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AutomatorXV:
I'm currently on the last 12.1 nightly, which I use as a daily driver. Would y'all recommend updating to either Matrixzone's or the Official nightlies as daily drivers? 12.1 seems to be getting more unstable by the day :\
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
A month ago I'd recommend matrix's builds but now I'd say the official nightlies are pretty solid.. I haven't had the need to wipe my phone for months
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
So should I flash the latest official nightlies? Or stay on 4/13?

Is volume working right?

Is performance good?

Is FFC working?

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
For me , everything works flawlessly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
He did ask some specific things.

I'm on 05/02 nightly and performance is good, volume is personal preference but I have no complaints yet. As for ffc, I've not got it to work consistent.

Would really be cool if all the remaining developers around here for this old phone could all team up on just CM to try and fix all the remaining nagging issues. There are some really great developers here but they seem to all be working their own thing.

Sorry for the rant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
If that's the case, then i guess I'll have to dirty flash the latest nightly then. Been on the 4/13 matrix version. Other than the FFC prob, every other thing works for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Edgehead123:
Which version are you on? When did FFC start working without problems for you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
It started working fine back in January with matrix's builds before the official nightlies were out. Snapchat used to crash randomly, but around February, that was fixed too
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Even in dark and lighted areas... ??? And if I may ask..? Which of the matrix version are you on now ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Arunscape:
If outside in the sun counts as lighted... I'm on the official nightlies right now. Everything seems to work flawlessly for me , with the exception of Google camera crashing when switching to video. Other camera apps work fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Weird because I am on nightly and my ffc didn't work correctly in apps or in the cm camera or open camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
I am on the nightlies now and I don't see a difference.

Same deafening audio in the speakers, though. Alarms, media, phone calls, speakerphone, ringtones, etc all are incredibly loud. It seems that it is a whole 2-3dB off (3db = double the sound). 50% volume is “normal” 100% volume. I wish that the devs can get their heads together and fix this bug. I don’t know how to fix this for good. (And yet the alarm still doesn’t get me up ?)

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tank Weston:
[MENTION=4551784]matrixzone[/MENTION] other than the obvious and repetitive camera issue and few other bugs, this build seems fairly stable. Great work and much thanks. If you need any help testing anything just give me a yell
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Oscargl15:
Very good job my only issue is that the screen pin of lolipop doesn't let you unpin and the microphone of the cell phone doesn't work well with this rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dapriett:
Is there any difference between this ROM and the one posted here: http://xdaforums.com/galaxy-s3-att/orig-development/rom-cm12-d2att-alpha-builds-t2959561
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
For one, this one is updated more frequently. Both at CM based.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
USB Connection Broken after New Years Update

I have the samsung driver installed on my computer but after the new years update my computer does not recognize my s3. I reinstalled drivers and everything. It was working fine on the previous update. Your help would be greatly appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] keith.macdonald:
Something I've noticed with A2DP

I don't follow CM 12 development, maybe someone who does know why this is: I've noticed that A2DP playback is fine so long as the device doesn't support unified volume changing (change the volume on device or phone changes it in both places). For devices that DO support unified volume changing though, the audio clips, and eventually breaks up so often and frequently that it's NOT playing more than it is (I'm assuming it's a synchronization issue).

Anyway, I guess it's a bug that'll be ironed out before CM 12 is released, I just wanted to share my observations...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tccool:
Uninstall all drivers you have for the device, and then try letting the PC download the drivers for you. This is what I did back when I got my first CM11 nightly.

---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------

Last 8 years. LAST 8 YEARS, ahahaha :confused: :laugh:

Yeah, I've been running it for 12 years. Beat that. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Sorry changes the typo error
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andPS2:
so right now recording video isnt working anymore in any apps correct?

opencamera hangs

camera zoom fx doesnt have video recording and just uses either stock camera or google camera which both dont work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
I was wondering if anyone would comment on the mention of eight years.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tccool:
Video recording works in no known apps at the moment.

Camera Zoom FX Pro should be working properly, I find it's the most stable.

---------- Post added at 12:50 AM ---------- Previous post was at 12:17 AM ----------

Newest update broke my cell signal at first. Cleared cache and it was fixed. New build seems to be working fine and stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenetix:
Keyboard question

I have noticed something on all these cm12 roms that i have run. After using the keyboard for a few days, it seems like i type faster than it can keep up with. Is there some trick to speed that back up. Is there some temporary file to clean? Are you guys running a separate kernel? Just a question to throw out there and see what everybody thinks. Rom is quick and smooth. I love the "bubble" effect when you touch stuff. All pretty cool, and open camera works awesome. So, anybody out there wiser than me ( and that ain't hard to find), let me know of any speed hacks. Thanks, matrix & all who brought this rom to us.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
How long does it loop?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbrian27:
I let it go for every bit of 10-15 minutes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Guys

We don't official device maintainer for d2att. Dont know how this will impact the CM support for our device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dracinn:
Dude don't worry about it the S3 isn't even that old.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
That sucks. Will that end all custom Roms too?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Kind off. If CM stops the support, there will be no source for any custom rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheGeekyNimrod:
There's still Slim and Omni that can be used a bases for custom roms.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Yep....and slim has always been good to my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
Did you do a full wipe? I'm on the nightlies after a full wipe (05/01). Bluetooth call volume is a little low, but the rest after. adjusting are fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Thanks for the swift reply.. But pls I got alotta app already on my fone. So just wanna know if its quite cool to dirty flash the night lies onto matrix version .. ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
I dirty flashed and didn't see any issue.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geearf:
No issue with speakers, but I do find the bluetooth audio a little weak, even at max volume.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Hmm. Which nightly are you on?

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geearf:
Yesterday's.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Hmm. So am I.

Which S3 are you on? I am on the d2can.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geearf:
d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] evuraan:
full wipe, running 05/14 - FFC (front camera) is un-usable. also felt a slightly higher power drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wrenhal:
If you are on the official nightlies then this is the wrong thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaws4God:
so the front facing camera does work (all light conditions) on this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anishs:
experiencing a really odd issue

after a proper installation, gapps can't access the Internet

If I do a fresh re-install without gapps the Internet is fine

Any suggestions?

Using a I747M

---------- Post added at 11:15 AM ---------- Previous post was at 11:15 AM ----------

ffc seems to be just fine in both the aosp and google camera apps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaws4God:
awesome! now i'm assuming i can't flash a d2att rom on my Verizon (d2vzw) phone?

I wonder if this fix can be implemented on the d2vzw variant. [MENTION=3860593]semdoc[/MENTION] :good: ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] anishs:
Unfortunately you can't flash Roms interchangeably on these variants

That being said the fix is easily implemented, mention it to the person maintaining the rom for your variant!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Easy_as_Pi_3.14:
Yeah; for a while, CM had unified builds which used different blobs. I think the only difference was RIL.

A good thing to investigate.

Next build I will flash over nightlies. Unfortunately, just flashed official 4/18. Wasn't aware of 4/17.

[font="Roboto,Helvetica,Arial,sans-serif"]Sent fr​om my SGH-I747 using AWESOME COLORS!!![/font]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jaws4God:
i was curious because i have seen that we (d2vzw variant) can flash the d2lte versions.. :good::)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Groot:
I've had this problem since the first official nightly. Some of my installed apps that uses the material loading icon thingy (the rotating circle) force closes if the loading icon messes up itself. Has somebody experienced this before? If so please share your fixes or workarounds. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geearf:
That's because d2lte was the global build for the various variants, but it's been canceled since then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drbg:
I've been using this mod for a few months now and have loved the new life it brought into my S3. But, after the last 2 nightly updates I've been getting the near constant "Unfortunately, Google Play services has stopped" popup that makes the phone almost unusable. I've tried stopping and clearing the cache but the buttons are not clickable. Any help with this would be greatly appreciated. Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mydnytefantasy89:
This is a classic problem with the gapps package and the new permission style of MM. You'll need to go into settings>apps>menu(the three dots at the top)>and select "show system", and then sift through for Google Play Services, and pretty much anything Google related, and select it, then go into permissions and grant it anything it hasn't been granted. Do the same with Setup Wizard, the one with the Android logo