yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] JohnnyTToxic:
This is an aside and may not help your issue, but have you popped the plastic cover off and tightened all of the screws on the back of your phone? The back plastic frame also contains the GPS antenna, which connects to the main board only by virtue of two copper contacts pressing together (one springy, the other just a contact pad).

There is an issue where some units were apparently shipped with those screws not torqued down properly, or they backed out over time. I don't know the proper torque, but I do know that I really tightened mine down after my GPS all but died and that made a world of difference. I read about the issue in a forum somewhere, but I haven't looked for it. It's worth a shot. The before and after on the signal test was crazy different.
[Verizon Samsung Galaxy S III] TheGman125:
If anyone would like to use the soft keys with this Rom here is the link that will help you because it help me.

http://xdaforums.com/showthread.php?t=1788780

---------- Post added at 09:43 AM ---------- Previous post was at 09:40 AM ----------

I am running the update build but I am having issue with the data services not staying connected? Is anyone else having that problem.
[Verizon Samsung Galaxy S III] behmer:
Has anyone else noticed that its not possible to use 1 gig of ram without it forcing other applications out of memory? A lot of times it is even forcing the current running application out of memory. I don't have this issue on cm10.1 though. I was just wondering if other people have noticed this or if this is a known issue.

update: I tried to recreate this issue after a reboot. Once memory usage has gone up to 0.92 MBs, the menu and the back capacitive buttons stop working except for the vibration, and it becomes impossible to look at the memory usage for more than 1 second as it continues to close without giving a force closing message. Things just go downhill from here. Then the keyboard takes about 10 seconds to open, the launcher closes every time you leave it, random screen flashing, random screen presses, recent app menu opens and won't close, forcing you to reboot the phone.
[Verizon Samsung Galaxy S III] remillard:
Problem upgrading from 10.1 to 10.2

Guys I'm not new to flashing Roms. I've gone from CM9 to 10.1 without issue. Installed other roms PAC / ASOP etc. However every time I try to update to from 10.1 to 10.2 on my Verizon GS3. I can get it to boot first time after install. All my apps are downloaded and installed. However after rebooting or powering off and powering back on again. My device just sit at the Galaxy S3 / Cid screen. I've waited up to 5 minutes without it actually getting me to a home screen. I've tried multiple nightlies and even tried a different rom (Cleanrom 7). Does the same thing. I do a wipe data, dalvik, system, cache and internal storage and install from scratch a number of times with the same results. I've tried a battery pull, leaving it out for a few minutes, I've tried removing SD and SIM cards. After performing a full wipe I try to install the nightly and gapps (030813), first time boots to home screen but after reboot or power off / on boots to Galaxy S3 / Cid screen. I never get the circular Cyanogemod 'booting' screen. I can restore my nandroid backup and once I'm back in 10.1 I can reboot to recovery, reboot system or power off / on and device acts and boots normally. What the hell am I doing wrong? Any help or suggestions would be GREATLY appreciated.

Rem.
[Verizon Samsung Galaxy S III] sanjsrik:
Use Titanium Backup. It's pretty much a standard and I've never seen it have any issues.
[Verizon Samsung Galaxy S III] Eyalkn:
Tried it also and it would backup but won't restore. It gets stuck on 0% and the location is in my external sdcard. I use Go backup because i need the multi backups function and TiBu doesn't have it.
[Verizon Samsung Galaxy S III] sanjsrik:
Explain "multi-backup solution" you are mentioning. I run a daily scheduled backup as well as a 2am and 3am backup on Sundays using TI backup. I have also restored from TI Backup after upgrading or installing a nightly, although not a single nightly (touch wood) has caused any issues thus far.
[Verizon Samsung Galaxy S III] Eyalkn:
On each rom that I install after restoring all the backups I use an odex script which odex the entire rom (System, framework and data) and because there is no backup program that knows how the backup apps after I odex them I create a backup before I odex the data apps of only the apps themselves and then right before I want to flash another rom I backup only the data of these apps and after I flash the new rom I then restore the apps and then the data and I am good to go. I have been doing this method since the beginning of 4.3 JB and I have been flashing everything on my radar :). With TiBu I didn't find a way of doing that since I can't created 2 backups in this order, since TiBu backups are always created on top of each other and you can't save 2 separate backups.
[Verizon Samsung Galaxy S III] sanjsrik:
TI Backups are not "created on top of each other" they are distinct and can be restored based on date and time.

I'm not sure why you're going through all this workflow when it really doesn't seem necessary. You're creating a lot of extra work for yourself. Are you updating using nightlys? If so, why are you doing all this odex stuff as well? I update using nightlys and never go through all these extra hoops.
[Verizon Samsung Galaxy S III] Eyalkn:
I don't see any option in TiBu batch restore of choosing between backups (date and time). I know from my own experience that this work is worth it because of the speed gain.I used to update nightlys until they broke go backup and now I am using illusion rom which is based on slim beta 2 which is based on cm 8/24 before the go backup issue has started.
[Verizon Samsung Galaxy S III] sanjsrik:
Okay, should have been clearer. You're looking to reinstall/restore all apps. I never have done this in terms of updating between nightlys. I just restore individual apps from TI Backup (if necessary) and the UI shows me individual app backups which allow me to restore from a specific date and even time.

Your "solution" seems overkill to me and don't see any slowdown in any nightly. If you see "speed" gains, I believe you, just don't think all this effort is worth it.

I'm on 9/3 nightly.
[Verizon Samsung Galaxy S III] airmaxx23:
Since you're on the 9/3 Nightly can you do me a favor? Can you install the Cobalt Inferno theme from the Play Store and see if it survives a reboot? I've been having an issue with the last couple of nightlies and would like to see if it's just me.
[Verizon Samsung Galaxy S III] sanjsrik:
Call me chicken, but any "theme" that states when you're trying to install it that could instability in the ROM is not one I want to mess with. Sorry, I'd help out, but it seems unnecessary to install this theme for any functionality purpose. If this is the kind of issues you're reporting, and not actual "my ROM isn't working" issues, this sounds a lot more cosmetic than I'm willing to investigate.

For me, TI Backup works fine on both backup and restore (if necessary)

My device is plenty fast as is

I am updating with nightlys and having absolutely no issues

I'm sorry you're using gobackup and having issues, but I just can't replicate them. As for the theme, sorry, not willing to do it to cause unneeded issues.

Good luck.
[Verizon Samsung Galaxy S III] airmaxx23:
Something happened between the 8/28 Nightly and the 8/31 which causes my phone to boot loop once the theme is applied and I reboot. I'm just trying to see if it's something with my phone or the theme itself. I find it odd that it works on the 8/28 Nightly but crashed the 8/31 Nightly. Hopefully I can find someone to make a backup and then try the theme to see if they get the same results.
[Verizon Samsung Galaxy S III] rockingondrums:
It has been a problem for a long time, and I haven't seen anything from Cerberus indicating they'll fix it.
[Verizon Samsung Galaxy S III] annoyingduck:
I'm having the same theme bootloop issue on slim. Fyi, if you end up bootlooping and are using twrp, just boot into recovery go to the file manager in advanced, and delete the theme apk from root data, then reboot. Way easier than restoring a backup
[Verizon Samsung Galaxy S III] ssmaster:
When I woke up this morning somehow all my app data was erased. All of my apps were still there, but it did not recognize me and my game progress was lost. Luckily I was able to restore the data only from titanium backup. I am pretty much back otherwise. I was running version the 9/1 nightly. Also now cwm recovery won't let me wipe dalvik cache, it reboots after I choose it.
[Verizon Samsung Galaxy S III] airmaxx23:
Thank you for the information.
[Verizon Samsung Galaxy S III] Eyalkn:
Thanks for all your help. Using TiBu without any issues now.
[Verizon Samsung Galaxy S III] Chris Hansen:
I searched around (both here and via Google), and I couldn't find anything related to my following question.

I'm curious if I'm the only one having this problem, or if I somehow missed a setting or something?

I have no reboot option under the power menu. I have tried both checking and unchecking the option for "Advanced reboot" under developer options, but nothing shows up.

My menu looks like the following:

[B]Power
Screenshot
Airplane mode[/B]

I'm currently on the 8/30 nightly (about to update, which made me post this), and this was the same on the 8/24 nightly as well (didn't use any in between). I had dirty flashed the 8/24 build, but 8/30 I clean flashed for giggles.

It's not a big deal, but I just want to make sure I'm not going crazy. :silly:

Thanks in advance!
[Verizon Samsung Galaxy S III] airmaxx23:
You'll find the Advanced Reboot option in Developer Options, near the top.
[Verizon Samsung Galaxy S III] Chris Hansen:
Thanks, but I know where it is. I stated in my previous post that I have both checked and unchecked the option, and there is no change to the power menu.

Clean flashing the 9/4 build did not rectify the issue either.
[Verizon Samsung Galaxy S III] sanjsrik:
Just to be clear, you hold down the power button and the reboot option shows up in the list of options, you choose reboot and you DON'T see advanced reboot options such as recovery?
[Verizon Samsung Galaxy S III] rhcreed:
official 4.3 from samsung

Seems like it should be soon, will this release have any impact on this rom? (can it contribute anything?)

Just wondering, thx!
[Verizon Samsung Galaxy S III] AlphaXray:
So just throwing this back out there incase anyone else has experienced the same issue. The video portion of instagram still does not work properly. It allows you to take your first portion of video. Then when you release to start another clip the camera goes completely jagged and has purple and green coloring over everything. I know this isn't a big deal, but I hate having apps that I can't use to their full potential. If anyone else has seen this issue please let me so I know I'm not the only one.
[Verizon Samsung Galaxy S III] ryan49er:
Clean installed 9/2 nightly. All was working well. Restored a few backed up apps etc. Had the ROM running for an hour or two. Decided to reboot and won't go past galaxy s3 screen just hangs there. Tried to restore a previous back up. No dice. Wiped and flashed a different ROM same outcome. What the heck has broken my phone. Never had an issue like this.
[Verizon Samsung Galaxy S III] Chris Hansen:
I don't even have a reboot option under the power menu, just the 3 I listed earlier:

[B]Power
Screenshot
Airplane mode[/B]

I've tried taking a screenshot, but the menu doesn't show (and 3rd party apps don't appear to work with 4.3 to do so).
[Verizon Samsung Galaxy S III] Hybridnoob:
Use the volume down key + power button to take a screenshot.
[Verizon Samsung Galaxy S III] annoyingduck:
Is focal working? Is it still causing battery drain? Getting conflicting reports on this.
[Verizon Samsung Galaxy S III] PsiPhiDan:
I'm curious about Focal too. Any ROMs have it working yet for the S3?
[Verizon Samsung Galaxy S III] rockingondrums:
On my S3, it appears that everything works in the UI, but when I take a picture, the picture is corrupted and the app crashes
[Verizon Samsung Galaxy S III] Chris Hansen:
Thanks, didn't know the hardware option for this device.
[Verizon Samsung Galaxy S III] Hybridnoob:
Wow, that is odd. Try going back to the stock theme and rebooting. You can try wiping system and reinstalling ROM and GApps (won't lose data, but backup first, if you want). If that doesn't work, it may be time for a clean install.

**Nevermind, I was able to reproduce your screenshot by unchecking some options. If you go into System Settings - Buttons - Power Menu do you have the reboot menu option selected?
[Verizon Samsung Galaxy S III] uncleguito:
I've been having some issues with my clean flashes lately and figured I might be doing it wrong. In the past, I usually just do a nandroid backup, wipe, flash, etc, then restore nandroid backup data only. I never use TB- should I use it for restoring instead? If so, which process should I follow?
[Verizon Samsung Galaxy S III] Hybridnoob:
Just curious, why are you "clean" flashing that often? I clean flash maybe 1-2 times a year (and dirty flash almost every day) without issues. By the way, restoring your nandroid data is pretty much a dirty flash, but with extra steps and effort. You would get the same effect by downloading and flashing the nightly over your current setup and doing nothing else. To each his own.

TiBU or Helium should be fine to restore app data only. I normally redownload all of my apps directly from the Play Store.
[Verizon Samsung Galaxy S III] uncleguito:
What's the process for backing up and restoring properly with TB? I was always confused by which options I should be selecting.
[Verizon Samsung Galaxy S III] annoyingduck:
Restoring apps+app data from a nandroid is not the best choice if your not on the same exact rom/build. Titanium is very powerful and is probably the best choice. For the person who asked about how to use titanium, pm me so we don't clutter up this thread.
[Verizon Samsung Galaxy S III] Chris Hansen:
That did it, thanks! I didn't think to go under buttons, I'm never really in that menu. Kind of odd that it was set to off by default.

Appreciate the help!:highfive:
[Verizon Samsung Galaxy S III] zetsumeikuro:
Looks like official 9/6 build = no boot.
[Verizon Samsung Galaxy S III] NeoMagus:
Same here was just about to post up a warning. Froze mine at the "Galaxy SIII" boot animation and had to restore to last nightly, I have a feeling the commits dealing with PRODUCT_BOOTANIMATION may have something to do with it?
[Verizon Samsung Galaxy S III] 32BitWhore:
Confirmed no boot. Does not work with stock or custom kernel. Hangs at kernel screen indefinitely.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] zetsumeikuro:
Flashed 9/5 nightly and this build works. Deleted 9/6 build and redownloaded and flashed over 9/5 and still no boot.
[Verizon Samsung Galaxy S III] gczepiel:
Same here. Stuck on Cyanogen boot screen when updating to 9/6 build. Cleared dalvic and cache, reinstalled 9/5 build from cwm now all seems fine back on 9/5 build
[Verizon Samsung Galaxy S III] Restola:
Thanks for the reports everyone. I added this to the thread title and the OP. Hopefully some people will avoid the frustration!
[Verizon Samsung Galaxy S III] mastamoon:
le ouch

Fix not yet merged...

http://review.cyanogenmod.org/#/c/49972/
[Verizon Samsung Galaxy S III] Prack:
Thanks for the heads up guys. I was 10 seconds away from flashing when I noticed the message in the thread title lol.
[Verizon Samsung Galaxy S III] remillard:
*Fix* for stuck on Samsung boot screen

I had a similar problem going from 10.1 to 10.2 nightlies. After many days of frustration and G-searching found someone having a similar problem. I was using TWRP 2.6 recovery and I attempted to format data and and wipe dalvik, system, data, internal storage and cache. Then installed 10.2 as a clean install. Booted first time was able to install apps, etc. However after a reboot or power off I would get stuck at the S3 boot screen. Tried another Rom (CleanROM) with the same problem. I think this is something to do with the partitions being screwed up. Something I noticed specifically was the in the storage area the emulated/legacy folder was missing, I think this is what was causing the problem, I am by no means a Dev/Android expert.

Not sure if you're able to do this but do a complete wipe, dalvik, system, data, internal storage, cache AND a FORMAT DATA. This was the only way I was able to restore my 10.1 nandroid backup. Which allowed me to boot back into the system. From there I did the below.

In the post I found they fixed this by restoring a stock rom and recovery, however I didn't want to have to do this so I tried something a little different. This is how I fixed my issue. Firstly I restored by to my 10.1 nandroid backup. Copied the 10.2 nightly to my SD Card. Then I used Rom manager to install Clockworkmod Recovery. Using Clockworkmod I did a factory reset and wipe cache, then reinstalled the 10.2 nightly (9/3 I believe). Rebooted and let google reinstall all my apps etc. Rebooted and tested fine, then did a power off and tested fine. Then reinstalled TWRP recovery. Been 3 days without issue any problems and have been able to install nightlies. This is essentially a clean install so means you'll have to setup everything again (P.I.T.A) but at least no more getting stuck on boot screen. I hope this helps you resolve your problem.

Rem
[Verizon Samsung Galaxy S III] boricua1213:
Google Play Store Issues

I installed gapps for 10.2. Google play store FCs, and when I go to the Play store on my computer says No active devices. Any ideas? Experiences?
[Verizon Samsung Galaxy S III] Hybridnoob:
This post would be more appropriate in the CM10.2 Q&A thread. But when you post there, please add more details so someone can help. Build? GApps?, etc...
[Verizon Samsung Galaxy S III] Gibscreen:
Anyone know when cm is planning on supporting otg cables for storage? It was supposed to happen with 10.1 but still no go. Something about a lack of power to the otg cable. Unless I'm missing something...
[Verizon Samsung Galaxy S III] Carloskeee:
?

USB OTG works fine for me. 10.1.3 RC2
[Verizon Samsung Galaxy S III] Gibscreen:
Are you able to access a flash drive with the usb otg?
[Verizon Samsung Galaxy S III] Carloskeee:
Yes. I have a 32GB Sandisk USB Flash drive. Has a orange LED that comes on. I just moved a few albums to it yesterday. Works without no problem.

FTR, I use RootExplorer, and the flash drive is under STORAGE/USBOTG
[Verizon Samsung Galaxy S III] Gibscreen:
Anyone have it working on 10.2?
[Verizon Samsung Galaxy S III] iofthestorm:
Just tested on 10.2 with two different drives, no luck with either.
[Verizon Samsung Galaxy S III] sullivan1985:
Running 9/5 on the latest KT747 kernel, latest firmware and baseband from invisiblek. My LTE data crawls. Is this a RIL issue or am I missing something?
[Verizon Samsung Galaxy S III] 32BitWhore:
Same build and kernel and no LTE issues here.

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] zetsumeikuro:
Just flashed 9/7 and this build also doesn't boot. Reverting to 9/5.
[Verizon Samsung Galaxy S III] razorloves:
https://plus.google.com/+CyanogenMod/posts/ArqL2Yw8tun
[Verizon Samsung Galaxy S III] Restola:
FYI the 9/6 AND 9/7 nightly will not boot. Flashing back to the 9/5 nightly will fix this. ​
[Verizon Samsung Galaxy S III] soohyunk83:
9/8 nightly

Looks like the no-boot issue was fixed with the 9/8 build. I was able to boot with this nightly.
[Verizon Samsung Galaxy S III] Stealth111:
Sweet!

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Crewski:
9/8 is confirmed working.

Last night running the 9/5 build I had quiet hours enabled via the toggle. I have it set to disable the led however when I got an email (gmail app) in the middle of the night it started blinking. Anyone else have this issue?
[Verizon Samsung Galaxy S III] sanjsrik:
LOL, I made the mistake of flashing the 9/7 build and had to go back to a 9/5 backup. Read that 9/8 was booting, flashed it and got worried when the device stayed at the Samsung screen a bit too long. Was about to do a battery pull and the device went on and booted.

Yay, CM.
[Verizon Samsung Galaxy S III] 0xScott:
I'm not sure why you had to restore from backup. Were you not able to get into recovery (power, home, vol-down) and dirty flash the 9/5 nightly?

That's what I had to do...
[Verizon Samsung Galaxy S III] Swasser:
MF1 Firmware necessary?

I recently dirty flashed 10.2 over a 10.1 install with the 8/30 nightly. I am still on baseband MA2.

Yet, everything is running OK. Even focal didn't crash on me (though I rebooted to avoid any memory issues). My stock camera works fine and my throughput is quick.

Do I really need to flash to MF1? I understand there's an Odin version that doesn't apply the full rom, just the radio, so if it's imperative I do need to for some reason, I'd rather go that route. If there's no need to wipe data, just cache and Dalvik, then its no big deal to me, and I'll flash MF1...but I wanted to make sure.

Any issues or data/functionality loss? Thanks.
[Verizon Samsung Galaxy S III] Hybridnoob:
Supposedly, the MF1 firmware is a requirement. CM was supposed to do checks and not boot without it (for your protection). It's in your best interest to flash it, as you're asking for trouble without it. No need to wipe anything.

http://invisiblek.org/sch-i535/firmware/d2vzw_VRBMF1_firmware.zip
[Verizon Samsung Galaxy S III] Swasser:
Thanks, man. I'll flash it.
[Verizon Samsung Galaxy S III] Hybridnoob:
It's recommended that you flash that zip in recovery (instead of the Odin version) because it has a .tz file in the package that you need. I have been running MF1 for a while with no problems.
[Verizon Samsung Galaxy S III] darklavalizard:
Currently on the 9/5 nightly, and has anyone noticed sometimes when switching Bluetooth off, it will turn off for like 5 seconds then automatically turn back on? Only way to fix this seems to reboot the phone, then Bluetooth stays off for good until I toggle it again. Wondering if it is just me, or if anyone else can replicate it?

Edit: NM, didn't read the list of bugs in the 1st post.
[Verizon Samsung Galaxy S III] Hybridnoob:
You can force quit the bluetooth share app to kill it as well without rebooting.
[Verizon Samsung Galaxy S III] rockingondrums:
Bluetooth has been iffy for awhile now, though slowly getting better.
[Verizon Samsung Galaxy S III] cammykool:
Next nightly to have cmaccount. Breaking refresh button.
[Verizon Samsung Galaxy S III] iofthestorm:
It's live! Gogogo!
[Verizon Samsung Galaxy S III] Swasser:
App2SD

Is there a way to move/install apps and data to the External SD Card? app2SD kicks back an error. I'm tempted to try app2extsd, but the developer says (and hasn't updated yet) it is not compatible with CM10.x

I just got a 32GB card, and I'm damn impulsive.
[Verizon Samsung Galaxy S III] Linkford:
touchtone on keypad

Anyone having any luck with the the keyboard touch tones while in a call?
[Verizon Samsung Galaxy S III] bigdaddie:
extSD

On 09/08 nightly with KT747 kernel.

My SD card is accessible from two different directories: "external_sd" and "extSdCard"

Do I have something configured or formatted funky?

BTW- Coming from a custom TW rom and this thing kicks ass. I don't think I'll look back. No lag and great battery life. Was off charger for over 7hrs and had 85% battery remaining with light to moderate use. Great job guys!

BD
[Verizon Samsung Galaxy S III] Swasser:
That seems about right. There are a few different ways and links that are set up to access the internal and external (SD Card) storage.
[Verizon Samsung Galaxy S III] sullivan1985:
Hangouts on 4.3

Is anybody having an issue with Hangouts not notifying when it receives a message on 10.2?
[Verizon Samsung Galaxy S III] Restola:
I use hangouts all the time to chat with my wife, haven't had any issues with it. I have heard of people with that problem though. I believe the resolution was to wipe Hangout's app data and that resolved it.