yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Restola:
There's no such thing as a stupid question, just stupid people

1: How do I fix Titanium Backup?

http://xdaforums.com/showthread.php?p=44612424#post44612424

2: How do I fix root?

http://xdaforums.com/showthread.php?p=44614991#post44614991

3: Is camcorder record volume fixed?

Yes! It is fixed as on 8/19/13 nightly

4: Is focal working?

No, and if you open it it will wake-lock your phone causing massive battery drain.

5: Why do all my apps have persistent notifications?

Stock 4.3 change, working as intended - http://www.androidauthority.com/android-4-3-persistent-notification-background-apps-250448/

6: Why does the keyboard force close at the setup screen?

You didn't flash the new gapps.

7: How is your new baby doing?

Baby and wife are doing great. Born 8/10, 7lbs 0oz, 20", and healthy as a horse.

8: Why is my location messed up in .... app?

If you enable Privacy Guard for an app that uses location, it will not be able to determine your actual location (that's one of the points of privacy guard).

9: My phone is stuck at the CM mascot after rebooting?

Odds are you're using TWRP. Switch to CWM and the issue will go away. I have no idea what's actually wrong, only that the issue doesn't occur with CWM.

10: Why does my gmail wipe after each new nightly?

It's a problem with the 8/13 gapps. Mastamoon fixed it and provided us with a new 8/20 gapps (available above)
[Verizon Samsung Galaxy S III] cynikalJ:
Sooo does focal work on the official because it doesn't on mastamoons
[Verizon Samsung Galaxy S III] Sora1995:
I'll test and let you know. I just flashed it.

EDIT: That's a negative. I repeatedly tapped the capture button and it froze, then couldn't connect to camera. Still isn't working it seems.
[Verizon Samsung Galaxy S III] airmaxx23:
I installed the newest build and everything is working fine so far except Focal which is still only partially working.

Edit: Bluetooth still doesn't always turn off and can require multiple "turn off" presses to get it to turn off properly.
[Verizon Samsung Galaxy S III] TheBr0ken:
The very last line in the OP:

"Reinstall Titanium Backup/Mybackup Pro/SMS Backup+ and restore the stuff you have to have, but its better to reinstall things from the market if possible (keep in mind your backups will be located in sdcard/0/) (if you want)"

Is incorrect. backups will be in /storage/emulated/legacy/

Hit menu > Preferences > Backup folder location

click detect, search whole device, two folders will be found. Make sure you choose the location with legacy or your backups will not restore
[Verizon Samsung Galaxy S III] juancaperez2000:
It is focal working on official? Or is the same than mastas
[Verizon Samsung Galaxy S III] samsgun357:
Not yet.

This is my rifle, I am The Gun!
[Verizon Samsung Galaxy S III] GPS3:
The 10.2 nighly is working flawless for me so far.

I flashed over 10.1.2 stable and used 20130813 GAPPS

Focal is working just fine too. EDIT: no it isn't.

FYI a new GAPPS was released yesterday. 20130813.
[Verizon Samsung Galaxy S III] airmaxx23:
You tried all the settings and video?
[Verizon Samsung Galaxy S III] Restola:
Thanks, OP updated

Also I'm working on a gapps mirror, waiting for it to download first.
[Verizon Samsung Galaxy S III] rhcreed:
root?

followed OP procedure, have lost root,

any suggestions?

(coming from 10.1.2, was rooted already)

Thx!
[Verizon Samsung Galaxy S III] uncleguito:
Not really a CM issue, but anyone else having issues getting SuperSU to work? Won't update the binary for me.
[Verizon Samsung Galaxy S III] Restola:
Root was an issue on the unofficials as well. There is an easy process to get it back but I cant remember. If someone can post the short how-to I'll link it in the OP.
[Verizon Samsung Galaxy S III] uncleguito:
Well it looks like SuperSU still functions properly and assigns su access properly (to terminal, greenify, etc), it just won't update the binary.

Everything else works fine from what I can tell.

4.3 is silky smooth on this build. Focal is working on my end as well.
[Verizon Samsung Galaxy S III] :
Try changing root access to adb and apps in developer options.
[Verizon Samsung Galaxy S III] ddggttff3:
This is what fixed it for me.
[Verizon Samsung Galaxy S III] rhcreed:
root?

ddggttff3, did you have to do anything beyond that permission change? I've made that change, tried re-flashing supersu in recovery, still no luck.

not a huge deal, but I would like to get root back.

Thanks!
[Verizon Samsung Galaxy S III] ddggttff3:
If I remember correctly, flashing supersu replaces the su binary. For me, I installed the rom, enabled dev settings, set it to apps and adb, then rebooted, and root apps started working.
[Verizon Samsung Galaxy S III] ericsdeadinside:
I guess others have narrowed down the touch sounds/audio and music issues to using any equalizer apps. So disable dspmanager and you can use touch sounds without disrupting music.
[Verizon Samsung Galaxy S III] Prack:
Was wondering the same thing, didn't see an 8/23 build yet either.
[Verizon Samsung Galaxy S III] J33per:
I am running the 10.2-20130821-NIGHTLY-d2vzw on my S3, I just flashed it yesterday, and this morning waking up for a full charge I only got 4 hours battery life with it having screen off most of the time. Is this a known issue and is there a fix?

Thank You,

TechJeeper
[Verizon Samsung Galaxy S III] SubwayJrd:
Did you launch Focal? If so that's your problem. There's a bug (that I believe is going to be patched out in the next build, if I'm reading the notes correctly) that leaves a service running that will demolish your battery. The only fix currently (without the patch being part of the build) is to reboot your phone.

My phone is getting battery life right on par if not better than with CM 10.1, so it's not a known issue to get only 4 hours as far as I can tell.
[Verizon Samsung Galaxy S III] J33per:
Why yes I did - and it force closed! Thanks for the info I will do a test without focal. :good:
[Verizon Samsung Galaxy S III] SubwayJrd:
I guess technically that would be a "known issue" to get you only 4 hours of battery life then :p

Got the info about the patch from http://review.cyanogenmod.org/#/c/48770/ which I found at http://10.2.cmxlog.com/?device=d2vzw
[Verizon Samsung Galaxy S III] :
This appears to be fixed in the 8/23 nightly and there is an option now to save to the external sd card. Make sure you still are only using the stock camera app though as Focal is still force closing.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Hey all,

I installed the stable build of 10.2.1. I wiped the 3...formatted the system...installed the 8/13 gapps. I have done this a couple times and each time the AOSP keyboard keeps crashing and I can't get anywhere. I went into the Apps under Settings but it just takes me to the keyboard settings which yet again just crashes. Any ideas on why this is happening. I am using the MF1 firmware as well.
[Verizon Samsung Galaxy S III] titanshadow:
Just some information... I went to use Focal since it said a lot of the crashes were fixed and... It didn't crash and I was able to take pictures, and the stock camera app worked too. Problem comes in that it didn't actually save the pictures anywhere, grey slots for them appeared in the gallery but no files in DCIM/Camera on the internal SD (emulated/0) or the external SD (/storage/sdcard1) in the expected DCIM/Camera. I also couldn't record video from Focal either. I don't mind I was just trying it out.

I tried this on my GS3 and on my Tab 2 7. But, it didn't crash and that is a serious move forward!

As a PS... Thanks devs for getting that save to sd feature back in the stock camera app, much appreciated and as always, awesome job.
[Verizon Samsung Galaxy S III] eris72:
I don't believe there is a stable build of 10.2, did u flash 10.1 with the 8/13 4.3 gapps? I imagine that could muck things up a bit
[Verizon Samsung Galaxy S III] AlphaXray:
Definitely a step forward. Mine did end up crashing after taking about 8 pictures though. Also I have no idea where they saved. Stock camera is great with the save to SD card feature back though.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Yep that's what it was. I flashed the latest nightly with 820 gapps and all is well. Only issue I had was focal. I did the photosphere option and after 3 shots it froze up and crashed.
[Verizon Samsung Galaxy S III] sanjsrik:
I can verify fixed. I changed my storage location for camera to SD card.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Clean flash but the battery life isn't good. I'm down to 37% after only 2 hours. No custom kernel. I was on SlimRom and it would last me all day.
[Verizon Samsung Galaxy S III] sanjsrik:
As asked a few times. Have you used Focal? If so, known issue with battery drain. I get at least 6 hours on my device and that's using it normally. Sometimes longer.
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Yes I used it but when it crashed I rebooted the phone like it said to do. Still getting horrible life. I guess I will power it off completely to see if that helps.
[Verizon Samsung Galaxy S III] RedRumy3:
I am not sure if anyone posted this yet but I can't seem to change my ringtone or notification sounds. Anyone else have this problem I just did a fresh install of latest nightly and everything is great except this one problem.

Edit : 8/24 Latest nightly just fixed it for me. Weird but awesome.
[Verizon Samsung Galaxy S III] Gibscreen:
I've been trying to find the option to disable the backlight for the secondary hardware keys. Am I missing something or is this no longer an option?
[Verizon Samsung Galaxy S III] airmaxx23:
Advanced Settings is not currently in the ROM but they can be access through Apex or Nova Launcher. Just long press on the homescreen, press Shortcuts, then Activities, then Advanced Settings, then Advanced Settings again. This will create a shortcut on your homescreen to the Advanced Settings where you can disable the backlights.
[Verizon Samsung Galaxy S III] Gibscreen:
Wonderful. Thanks!
[Verizon Samsung Galaxy S III] sanjsrik:
Since 2.3, I've had an issue with SMS sounds not playing at all. I've checked all sounds. I've tried numerous SMs programs such as Handcent and GoSMS and native built in SMS, and when I receive a message, NO sounds at all.

Anyone have any suggestions, options?

Please and thank you in advance.

Everything else is working fine.
[Verizon Samsung Galaxy S III] devo1929:
Delete...

Sent from my GS3
[Verizon Samsung Galaxy S III] titanshadow:
I've noticed a lot of stuff about a vold and disk type stuff going into "recovery" on the change log. It all sounds really nice, what do I have to do to make use of these items? As far as I understood CWM is separate from CM - or do I misunderstand something? Or are these API's that can be used by an installed recovery?
[Verizon Samsung Galaxy S III] SlimSnoopOS:
I follow a few AOSP threads fairly closely and remember this was posted recently:

Edit: Sorry guys, apparently Tapatalk does not want me to quote this post and paste it in a Q/A thread. This was not intended for this dev thread. Please disregard.
[Verizon Samsung Galaxy S III] kenbrownstone:
Why no official for 8/26?
[Verizon Samsung Galaxy S III] iofthestorm:
The build bot seems to be broken for d2vzw, not sure why since other devices are working and it seems the tree is fine since people doing unofficial builds are not affected.
[Verizon Samsung Galaxy S III] airmaxx23:
Button backlight control has been added to the "Buttons" Settings on the 8/27 build.
[Verizon Samsung Galaxy S III] Gibscreen:
Anyone know why they messed with the notification drawer icons? Used to be you could set brightness levels just by toggling through presets. Now it just opens the brightness control. The new icons only allow 5 across the screen instead of 6 too. Just weird that they took the time to change something without a perceived advantage.
[Verizon Samsung Galaxy S III] juryben:
Nightly 8/27 put my phone in a bootloop.

Time to flash thru download mode again.
[Verizon Samsung Galaxy S III] airmaxx23:
Here is some info on the new "access ribbon". You could always set up the brightness to adjust by sliding your finger across the status bar.

http://www.androidpolice.com/2013/08/23/cyanogenmod-set-to-bring-about-the-death-of-power-widgets-in-favor-of-quick-access-ribbon/

---------- Post added at 01:52 PM ---------- Previous post was at 01:51 PM ----------

It may be a bad download, it installed fine for me.
[Verizon Samsung Galaxy S III] juryben:
I used CM updater on the phone. Went from 7/30 -> 8/27. Recovery is broken too. I gotta flash with odin and do it all over again :(
[Verizon Samsung Galaxy S III] airmaxx23:
I've had recovery get stuck a few times and after a few battery pulls it's finally booted up.
[Verizon Samsung Galaxy S III] rodstar87:
Is there any support to see emoji in apps other that SMS??
[Verizon Samsung Galaxy S III] Restola:
flashed ok here
[Verizon Samsung Galaxy S III] RedRumy3:
No problems here with 8/27 as well, updated fine and no problems.
[Verizon Samsung Galaxy S III] soohyunk83:
GPS issues?

Anybody having troubles with the GPS locking?

I can't seem to get a signal lock.

Not sure if it's a google maps issue or an issue with the latest nightlies. 8/27
[Verizon Samsung Galaxy S III] Restola:
Working here, Google maps took 4 seconds to find me in my kitchen.
[Verizon Samsung Galaxy S III] SubwayJrd:
Toggle your location settings off then back on again, accepting the Google agreement. I've had the same thing happen several times, and this has fixed it for me every time.

Edit: Should mention this has happened to me only randomly when I flash some new nightlies (no good pattern as to why), and after I toggle Location Settings off then back on that nightly never has a problem again.
[Verizon Samsung Galaxy S III] soohyunk83:
Thanks!!

That worked for me.
[Verizon Samsung Galaxy S III] Restola:
After leaving my house and coming back my wifi refuses to connect. Goes through "Obtaining IP address" then gets stuck at "Authenticating", then disconnects and tries again.

I was on 8/29. I wiped cache/dalvik with no effect. I then flashed 8/28 with no effect. Any ideas?
[Verizon Samsung Galaxy S III] sanjsrik:
You try deleting and readding your wifi connection?
[Verizon Samsung Galaxy S III] Restola:
Yes several times. No other devices in the house have a problem.
[Verizon Samsung Galaxy S III] Hybridnoob:
Try wiping system, then reflashing the ROM.
[Verizon Samsung Galaxy S III] Restola:
Turned out to be a router issue after all. All fixed.
[Verizon Samsung Galaxy S III] bigee1212:
Anyone here that used Cerberus and using the feature to take a front facing photo when a wrong unlock code is inputted will cause the phone to bootloop.
[Verizon Samsung Galaxy S III] soohyunk83:
Anybody else notice how the phone gets laggy and unstable when battery life is below 15%?
[Verizon Samsung Galaxy S III] Eyalkn:
Go Backup and Titanium Backup are refusing to recognize or restore my app's data (I backed it up right before I clean flashed the 8/29 nightly). When I try to backup using Go Backup it won't and say "an error as occurred" (I tested it by installing an app through the play store and the trying to back it up right after). The weird part about this is that it only happens on nightlys after 8/25 (In 8/25 nightly it does recognize, restore and backup). It occurred to me that it could be a root issue but I did choose in developer tools "App and ADB" and Go Backup and TiBu do prompt me for root and and recognize the device as rooted. In Go Backup the "Choose path for local backup" is grayed out and doesn't recognize my external storage but when I use a rooted explorer I do see the external SD and can access it without problems, I moved the backup folder to the internal storage and it shows the backups but fails to restore. Like I said it works fine on 8/25 and below.
[Verizon Samsung Galaxy S III] airmaxx23:
You still have some data files left over from your previous ROM which are messing with TiBu. Go into data/data and delete the file that correspond with the apps that won't restore and it should then work.
[Verizon Samsung Galaxy S III] Eyalkn:
Thank you for the response. there is no data since I did a clean install clearing data, cache and dalvik. I just checked Data/Data and it only has the apps that got installed form the rom itself. It also doesn't change the fact that I can't backup using Go Backup on nightlys after 8/25.
[Verizon Samsung Galaxy S III] airmaxx23:
I did a clean install yesterday and had the same issue with TiBu and even though I wiped data I still had files in data/data that shouldn't have been there. Try installing one of them from the Play Store and see if you get error -24.
[Verizon Samsung Galaxy S III] Eyalkn:
Installing from the play store does work but won't get backuped right after using Go Backup. I did delete all the data/data files after your post but still not able to restore or backup using GoBackup.

Can you please install Go Backup and see if in settings you can choose "Choose path for local backup" and that it is not grayed out and please even try to back up an app and see of you don't get an error.
[Verizon Samsung Galaxy S III] Interflop:
The latest 10.2 nightlies don't seem to be compatible with my car's Bluetooth audio system. I can connect to it no problem but I can only output phone audio and not media audio.
[Verizon Samsung Galaxy S III] airmaxx23:
Go Backup works fine for me and the "Choose Path" option lets me pick internal or external.
[Verizon Samsung Galaxy S III] Eyalkn:
Which nightly are you on?
[Verizon Samsung Galaxy S III] airmaxx23:
8/29 Official.
[Verizon Samsung Galaxy S III] Eyalkn:
Thanks for all your help. I have no idea what can cause all my backup us to not function after a clean install. Will stay in illusion rom and when something new comes that will be based in the latest cm I will try to flash it and see if I can backup or restore.
[Verizon Samsung Galaxy S III] iofthestorm:
You're not seeing random apps crash are you? Might be worth checking the SELinux status in settings - > about to see if it's something other than permissive.
[Verizon Samsung Galaxy S III] Eyalkn:
I am back with illusion rom. SELinux is disabled. How do I enable it? What does it do?
[Verizon Samsung Galaxy S III] iofthestorm:
Right now, it breaks most of your apps lol. I just asked because when I accidentally enabled it it caused my root apps to break.
[Verizon Samsung Galaxy S III] Eyalkn:
How do I change it?
[Verizon Samsung Galaxy S III] Hybridnoob:
About Phone - then tap on SELinux a bunch of times to toggle. But be prepared to break all the apps... ;)
[Verizon Samsung Galaxy S III] Eyalkn:
It didn't do anything and I tapped it nonstop
[Verizon Samsung Galaxy S III] Hybridnoob:
It works for me, but I have tap it four times pretty fast to get it to start toggling.
[Verizon Samsung Galaxy S III] Eyalkn:
In illusion rom there is only disabled option and I have no issues with any of the apps I am using and all the backup apps work properly. I reflashed the nandroid of the cm10.2 official 8/29 nightly and it is on permissive and as I said before non of the backup apps work and I didn't install anything except for go backup from the play store. I have no idea why it is working for others. I use cmw recovery and did a clean install and when I then did a clean install of the illusion rom right after the cm nightly it worked without issues and I didn't change anything in my external sd card.
[Verizon Samsung Galaxy S III] iofthestorm:
Lol dude you don't want SELinux enabled, sorry if I confused you. Right now android apps aren't built to work with it properly, they're just getting ready to enable it in a future version of Android and make things more secure then.

Dunno why your backup software isn't working, but I'm a logcat could help if you could get one when it's not working.
[Verizon Samsung Galaxy S III] Eyalkn:
I am definitely up for it. How do I create a logcat? I just made another test and got something really interesting. I flashed 8/24 nightly+gapps after a clean install and just opened the play store and installed go backup and it is working perfectly recognizing my external sd card. So went into recovery and dirty flashed 8/30 nightly on top of it and now when I run go backup it doesn't work anymore like I said in my earlier posts and gives me an error (see pic). And the sd card does work on that nightly with any file explorer.
[Verizon Samsung Galaxy S III] airmaxx23:
I'm on the 8/31 nightly and Go Backup gives me the same error but the SDCard works fine with Root Explorer and TiBu works fine as well.

Edit: Just a heads up that the Google Services (System Update Service) is still causing wakelock issues on the Official 8/31 Nightly. Just force stop Google Services Framework and it will be fine.

Edit 2: Phone (RILJ) seems to be causing wakelock issues now right after a reboot also. Force stopping Phone fixes it as well and it doesn't cause wakelock issues if you use the phone afterward.
[Verizon Samsung Galaxy S III] iofthestorm:
Here's an app that makes it easy to record and upload logs: https://play.google.com/store/apps/details?id=com.tortel.syslog

You probably just need the main log for this issue. I think what you want to do us try to run your backup app, then after it fails run Syslog and upload the log somewhere and post it here. You can try looking through it yourself too to see if there are any errors that are clearly related to the problem.
[Verizon Samsung Galaxy S III] Eyalkn:
5

This is the procedure I did to produce the logcat:

1. Opened cmw recovery and wiped system, cleared data, cache, dalvik. Flashed nightly 8/31+8/13 gapps signed.

2. Run the rom and signed into google and my Wi-Fi.

3. Installed logcat extreme from my sd card and run it. This us when the log has begun.

4. Installed go backup and run it and went to the menu to see again that the external sd card option is grayed out since it doesn't recognize it and I pressed it couple of times.

5. Went to the play store and installed YouTube and run it and played a video to create data.

6. Went back to give backup and chose to backup just YouTube and it did (last time when I did the same procedure it failed). So I did a backup again but for the 2 exciting apps and than it failed both.

7. I stopped the log.

If you want us can do the exact same procedure on 8/24 nightly where there are no issues.

Edit: I uploaded the log here.

http://www.sendspace.com/file/1ejw49
[Verizon Samsung Galaxy S III] iofthestorm:
Hmm could you post the log? I'm not a CM developer so I can't promise anything but I poke around in the code from time to time. Actually I think I've noticed recently that apps aren't detecting the external SD but it's still mounted and accessible. They may have just mounted it to a different point and not exposed it in the framework API properly. Can you set a custom backup path and set it to something like "/storage/sdcard1/path/you/want" and see if it works?
[Verizon Samsung Galaxy S III] Eyalkn:
In go backup there is no option for setting a custom path. There is just a choice of external or internal and scan for old backups which it already does automatically when you run it. I did a test where I dirty flashed 8/31 on 8/24 nightly (which like I said in my last posts didn't have this issue) and then run go backup and it gave me this error message

Edit: in case you missed it, I posted the log in my post before.
[Verizon Samsung Galaxy S III] cammykool:
Focal seems to work in this build. Didn't test wakelovk
[Verizon Samsung Galaxy S III] chowner:
I've done this and I still have lock issues. I've been updating nightly hoping for resolution,but nothing yet.

Anyone else having the same issues or know of resolution?

Thanks