yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] iofthestorm:
Have you tried the download mode trick? Reboot into download mode, plug in the USB to your phone and computer, and then unplug it. After a reboot it should work.
[Verizon Samsung Galaxy S III] AlphaXray:
So my SD card fried after letting a friend use it. Now I can't take pictures because for some reason the save to SD card or internal memory option has been taken out, so mine is defaulting to the SD card. Any work around or does anyone remember the last build that had that option on the camera??
[Verizon Samsung Galaxy S III] AlphaXray:
Ok so now I've run into an even larger issue. If anyone out there knows of something to try please let me know. In an attempt to fix my camera issue I decided to try and flash back to the last 10.1 release candidate. I did this and it would not load up. I figured this may be because it needed the older modem (MB1). So I then reflashed to the the latest nightly. Uploaded the MB1 modem to the internal SD. Rebooted into recovery. Flashed the MB1 Modem, then flashed the 10.1 RC3. Tried to reboot and it still didn't work. Flashed back to the newer MF1 modem, then flashed to the latest nightly. Now I cannot connect to my wi-fi or cellular data. It looks like it connects but everything stays grey. I can receive texts and send. But can't use data in any way. I tried flashing the MF1 a second time just to be sure. Still no luck. Also tried reverting to the 10/11 nightly and still nothing. Please, please give me an answer if anyone knows if I did something stupid or what I can try to do to get my Data and Wi-Fi working again.
[Verizon Samsung Galaxy S III] titanshadow:
Well, you shouldn't have to flash the modem at all between RC3 and the current nightlies. RC3 came out after the latest modem did so, it should work.

To take a look at your main problem, your data. The blue icons come from (if I remember) Google Services being able to reach Google over the network. So, make sure you've got the latest modem installed and just to be safe have your recovery wipe your cache and dalvik cache then fix permissions. All that flashing could have given your phone a migraine. Then, I would get the latest GApps and flash those.

Flashing the latest GApps should take care of any lingering issues with Google Services. Reboot your phone, and then after you get your phone connected to the network and if it doesn't turn blue go into accounts and your google account, then manually tell it to sync from there. I'd also get Speedtest, which should try to get out to the Internet even if Google can't connect and see if it fires up alright and can do its thing (measure your speed and ping).

A few things after that... Your connection should turn blue if your've got a live line to the Internet and manually tell the phone to sync your Google account. If it doesn't but speed test shows you've got a live network connection, I'd say the problem is with GApps. If it doesn't and speed test confirms no Internet connection then you've got a bigger problem.

If it is the bigger problem, you may have to go nuclear with the thing and try actually wiping the phone entirely and seeing if it'll connect to the network properly when you've clean-flashed the latest nightly and the latest gapps. There is also the really-really-really nuclear option of using odin to go back to start - a stock phone - and then (if you can connect to the network there) go in and root again, flash again, see if that helps.

If it is a gapps problem then I'm not sure what you might want to do. I'm using a gapps version from 8/20 myself which I got off of mastamoon's post with his custom ROM, might try that if you're using the 8/13 version that is on goo.im. Barring that, you'll have to do some research about how to perhaps fix gapps.

On the other hand, if you're unable to connect to a network properly even after going the full on super nuclear option of back to stock then something is wrong with your phone on a deeper level (SIM issue perhaps - even though that wouldn't explain wifi problems).

Now, assuming anything works and you're back to square one with an odd issue about your SDCard not working and the camera not letting your store stuff on the internal SD card (I'm assuming that you have a microsdcard that you loaned your friend and it stopped working). Check your available storage of the phone, clear stuff off so you have enough for a decent amount of pictures, go in and wipe the data for the gallery and see if that fixes it. Also, don't have a microsdcard in the slot that doesn't work, it might confuse the phone if you leave it inserted but the phone is unable to ever actually use it.

Hope this helped.
[Verizon Samsung Galaxy S III] kls629:
how do you get icons back in the status bar? like wi-fi, gps, sound, etc.

edit: found they changed it to settings/interface/notification drawer/quick access ribbon

a little different
[Verizon Samsung Galaxy S III] sanjsrik:
Are you asking where are my applications? I think if you just flashed, sometimes startup applications don't always start on boot and you have to sometimes manually start them. You could try starting those startup applications manually, the next time you reboot, they should start up automatically again.

If you're asking what happened to your icons and it says no icon packs are installed, did you HAVE icon packs installed before and if so, reinstall them, maybe they were accidentally deleted.
[Verizon Samsung Galaxy S III] AlphaXray:
Thank you so much! Can't believe it was just the GAPPS. Glad I have that knowledge now. Also cleared the gallery data and it worked perfectly. You are amazing. Thank you again.
[Verizon Samsung Galaxy S III] kls629:
thanks for the help

i have no idea what icon packs are, but it was the notification bar / status bar icons that were missing and hard for me to find in the settings.

they are under interface now
[Verizon Samsung Galaxy S III] sanjsrik:
I have no idea where "icon packs" are located where you're stating. I just looked in:

Settings > Interface > Status Bar and I don't see anything about icon packs.

Are you sure you're not asking about some launcher application you have installed that isn't showing icons?
[Verizon Samsung Galaxy S III] kls629:
settings / home screen / general / icon pack

i do not know what that is

but my problem is resolved. icons i wanted are in the notification bar and are located in settings / interface / notification drawer
[Verizon Samsung Galaxy S III] annoyingduck:
Your talking about the power widgets which have been removed. What replaces them are the new ribbons, which are linked to the quick settings tiles. Cm offers the ability to "place" them like the older power widgets.
[Verizon Samsung Galaxy S III] FReQ Z:
Anyone?
[Verizon Samsung Galaxy S III] SymbioticGenius:
Probably a bad download. Re download and try again. If issue continues download on a PC then move to phone and install
[Verizon Samsung Galaxy S III] FReQ Z:
MD5 matched up. Weird. I'll try a PC download, see what happens.
[Verizon Samsung Galaxy S III] sanjsrik:
Did you check to see the following:

1. Have enough space on your internal storage?

2. Redownloaded the file and see if you can reflash, maybe the MD5 was bad or the downloaded file was corrupted?
[Verizon Samsung Galaxy S III] sanjsrik:
Latest nightly, WiFi connection issues?

Hi all,

Is anyone getting WiFi connection issues with the latest nightly? I downloaded and flashed over the previous nightly with the 10162013 nightly and I can see that the device is trying to connect to my router but it just keeps going back to "saved" and doesn't connect.

Any help would be most appreciated.

thanks in advance.
[Verizon Samsung Galaxy S III] annoyingduck:
Are you by chance trying to connect to a 5g network?
[Verizon Samsung Galaxy S III] sanjsrik:
My WiFi connection worked fine on the 10142013 build, and now it's not working either after flashing back down to the previous build. My only thought is to reflash the modem and see if that helps.

thanks for the reply.

Not sure what a 5G network is though. Nothing on my side changed from the 10142013 build which leads me to believe it's the 10162013 build.
[Verizon Samsung Galaxy S III] annoyingduck:
Well for future reference, on a 5g network (dual band router) you must set your channel below 48. Your issue is the exact symptom of what happens if you don't.
[Verizon Samsung Galaxy S III] sanjsrik:
I appreciate the advice, but I haven't changed anything from yesterday to today at all to have this happen except update to the latest nightly.

So, that was why I was asking if anyone else is having the issue with WiFi not connecting after updating to the latest 10162013 nightly.

**UPDATE**

Seems it was the modem AND router that needed to be rebooted. I rebooted both of those and the WiFi is working fine. I am, however, looking at the channel issue to see if that also needs to be addressed. Thank you so much for your advice.
[Verizon Samsung Galaxy S III] titanshadow:
I don't mean to nitpick but 5G and a 5 Ghz signal are not the same thing. You are refering to a dual band router which is just called that, a dual band router. A dual band router supports the 5 Ghz spectrum which is called just called 5 Ghz.

5G refers to the 5th generation of wireless mobile networks which is currently being researched as the successor to the 4G technology we all love so much, http://en.wikipedia.org/wiki/5G gives a good primer on what 5G is. There are currently no standards in place for 5G as it is still being researched and thus no phone support 5G as that would make them from the future. :P

Using 5G as a term for 5Ghz wifi (802.11ac for example) is quite confusing.
[Verizon Samsung Galaxy S III] zetsumeikuro:
http://techcrunch.com/2013/05/12/samsung-to-launch-5g-by-2020-hits-speeds-of-1gbps-in-tests/ by 2020 supposedly. Also I'm wondering since Cyanogen has added all sorts of features etc.. How come they haven't fixed the jank yet? Is it beyond their abilities and it's something that we will have to wait for Google to rectify?
[Verizon Samsung Galaxy S III] titanshadow:
The what?
[Verizon Samsung Galaxy S III] zetsumeikuro:
http://lokeshv.wordpress.com/2012/0...roject-butter-how-it-works-and-what-it-added/

It explains it here :P.
[Verizon Samsung Galaxy S III] cammykool:
Odd...
[Verizon Samsung Galaxy S III] zetsumeikuro:
You have the updater to only look for stable releases. Select New versions (Incl. Nightlies) and you'll be good to go.
[Verizon Samsung Galaxy S III] 32BitWhore:
Anyone else have really strange graphics glitching on the 10/19 build? Colors are wrong, boot logo freaked out, etc. Flashed back to 10/16 and all is good.

Sent from my CM Powered Galaxy S III
[Verizon Samsung Galaxy S III] sanjsrik:
Fine here.

So far.
[Verizon Samsung Galaxy S III] SJonesGSO:
This has me wondering..can you simply dirty-flash an older nightly on top of a new one? Like if 10/19 did have issues, say, could one simply dowload and flash 10/16?
[Verizon Samsung Galaxy S III] mastamoon:
You flashed another kernel I'm guessing?

Yes.
[Verizon Samsung Galaxy S III] SJonesGSO:
Cool, thanks for the info!
[Verizon Samsung Galaxy S III] Prack:
I had the same problem after flashing BMS 10/16 kernel with the 10/19 cm nightly. Issue went away when I reflashed the rom over it to remove the kernel. Guess I will wait for an update for BMS.
[Verizon Samsung Galaxy S III] kcoop99:
Tethering didn't work on 10/16.
[Verizon Samsung Galaxy S III] cammykool:
Problem solved! Thank you!
[Verizon Samsung Galaxy S III] headcheese:
Having a few random reboots today on 10/19. Before that these builds have been pretty stable.
[Verizon Samsung Galaxy S III] Hybridnoob:
Same here. I've had 2 or 3 since this AM, but it's manageable.
[Verizon Samsung Galaxy S III] titanshadow:
Just had a very strange problem on not the latest build but the one before it where the phone completely freezes up at the lock screen when I try to use it. I had to pull the battery to reboot it. Happened twice in a row, hasn't happened since though. Going to try to flash the latest nightly.
[Verizon Samsung Galaxy S III] lou1210:
I wanted to add this regarding the CM 10.2 ROM. I just went 510 hours of up time on my phone. Only issue was occasional trebuchet closes but haven't had any other problems with this ROM. It is a nightly. I installed it 3 weeks ago. Just wanted to say how stable it has been on my phone.
[Verizon Samsung Galaxy S III] Hybridnoob:
Thanks for the perspective. I've been running this ROM (CM10.2 specifically) since more than two months ago. I only reported the random reboots because they were out of the norm for me on any nightly since CM10.2 dropped. It's been very stable overall for me as well.
[Verizon Samsung Galaxy S III] behmer:
The back press animation in settings is messed up since the 10-20 build. Its a little glitchy, try going to performance settings and pressing back.
[Verizon Samsung Galaxy S III] sanjsrik:
No issues for me. I just tried what you wrote and I don't see anything wrong.
[Verizon Samsung Galaxy S III] sephirothhoo:
I see the same issue. When you deep dive into two level menu and click on back button, the menu minimize to a box before fade away.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Yea, I can confirm this on 10/21 as well. I assumed it was a design choice/WIP that someone hadn't quite polished.
[Verizon Samsung Galaxy S III] cammykool:
anyone having nasty battery drain all of a sudden?
[Verizon Samsung Galaxy S III] alershka:
10/22 Nightly fc's com.android.telephone on reboot . I tried a clean and a dirty install, wiping phone data per the information on Mastamoon's non official build thread.

EDIT: FC was related to Imoseyon Kernel. Stock Kernel fixed the problem.
[Verizon Samsung Galaxy S III] vtmike:
10/22 has the slow back animation in settings too. 10/19 is also doing it for me too. I have an old backup that works right.
[Verizon Samsung Galaxy S III] scadilla:
Just had a strange thing happen on the latest nightly dirty install. Power button wouldn't shut the screen off but if I long pressed I'd get the power menu. Shortly after this phone rebooted, after rebooting my corporate exchange account was completely wiped out. Any ideas?
[Verizon Samsung Galaxy S III] chowner:
Anyone having troubles receiving video messages? (I know video message are antiquated) I receive picture messages no issue, but on video message I only receive notice that I got a text but I never receive anything.

Any help would be appreciated.

Thanks
[Verizon Samsung Galaxy S III] mastamoon:
For now you can disable hw overlays in developer settings.. Or set debug.composition.type to gpu in build.prop and reboot.
[Verizon Samsung Galaxy S III] zetsumeikuro:
They both do the same thing correct? Just the build.prop edit persists through reboots? I noticed with disable HW Overlays selected all the jank is pretty much gone. Is there any downside to disabling the overlays except for some additional CPU usage? I read the article on another site saying it's not advisable, but that was for devices wth older socs. Thank you.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I believe they do the same thing and it definitely cleans up the animation lag. I think it might tax the battery a bit more but I dont think there are many downsides. Some phones come with gpu as standard. Leaving the graphic up to the GPU sounds right to me though :eek:
[Verizon Samsung Galaxy S III] zetsumeikuro:
I remember in the beginning it was pretty much mandatory do have disable HW overlays checked for AOSP roms due to the flickering. I'm not too concerned about my battery since I do have the zero lemon 7k :good:. I really do wonder when Android will get it together give us a jank free experience (boy that sounds so wrong) :laugh:. It is disheartening to see animation stutters and lag on high end devices :(.
[Verizon Samsung Galaxy S III] titanshadow:
Anyone else having issues signing into google services? Had com.android.phone crashing constantly and finally did a factory reset which ended that problem but now I'm having issues logging into Google's services. Keeps telling me to try again in a few minutes. I also tried reflashing the gapps to no avail.
[Verizon Samsung Galaxy S III] Restola:
It's an issue with Google today. It's on some blogs.
[Verizon Samsung Galaxy S III] titanshadow:
It's not really Google's responsibility to do this. The software is open source, then it is modified and added onto for each device that is supported by CM. Your AOSP code includes no compatibility with anything AFAIK. It is just the frame and a few walls, then it is up to developers (like phone manufacturers or our goof friends at Cyanogen) to put everything in.
[Verizon Samsung Galaxy S III] zetsumeikuro:
The stuttering pretty much occurs on every device even the latest Nexi devices. Every ROM I have tried has the animation stuttering. 4.1 didnt have it, the stutters hit 4.2 and got worse with 4.2.2. The stuttering has gotten a bit better with 4.3. So clearly it would be beneficial for Google to address this issue as it is plaguing all devices.
[Verizon Samsung Galaxy S III] rockingondrums:
Is it just me, or does the 10/25 nightly remove anyone else's camera? I got so excited to see burst mode making a reappearance in the commits... :(

I tried manually adding the Gallery2.apk to system, but no new features. Then I re flashed the nightly and the camera was gone again.
[Verizon Samsung Galaxy S III] siriusgamer:
Is the cm 10.1.3 stable the most stable version or are the nightlies better?
[Verizon Samsung Galaxy S III] moparfreak426:
Omgb.... Duh! "stable" is stable. "nightlies" are nightlies

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] titanshadow:
I really don't think that answers the actual question asked. Just stating the names doesn't really answer what they are or how they compare in stabilities.

---------- Post added at 09:59 PM ---------- Previous post was at 09:54 PM ----------

The major difference between is that 10.2 doesn't have a "stable" release yet so, if you are looking for rock-solid stable and heavily tested, I'd say the stable release of 10.1.3 is your best bet. It is rigorously tested and I would recommend it for anyone who wants to do a CM ROM on their device but who really just needed it to always work every time they want to use it.

The nightlies are bleeding edge and while 99% of the time I don't have any issue with the nightlies on my device there are things that occasionally don't work. Features don't work, they sometimes crash, some apps and the ROM don't always get along. Let me emphasise, however, that I have very high reliability for my devices running CM 10.2 in the latest nightly.

Stable is really mostly for people who want a better Google experience but don't want to mess with it on a regular basis, aren't really interested in the bleeding edge, and while they want something cleaner than Samsung makes (not hard to do) they want something they only need to worry about updating once in a while.

Nightly is for people who are interested in the bleeding edge, don't mind messing with it, and don't mind occasionally if they update the phone and it won't boot, or the phone app crashes. While it doesn't happen often, it does happen. A lot of people go to a nightly and stick with it for a good long while. I myself am a crack-flasher, I flash nearly every nightly onto the device whatever it happens to do. That's me.

I hope this answers your question.
[Verizon Samsung Galaxy S III] moparfreak426:
Forgive my previous statement. I sometimes forget that people don't know as much about flashing roms or even rooting. But stable is in the name so....

Sent from my SCH-I535 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] M4gicM@:
Hello all,

I have been running the nightlys for a loooong while but last Tuesday I updated to 10/21 and got the phone FC. I had to do a reset and use my TW nandroid backup. Somehow my sdcard became corrupted and I lost the stable-for-build of 9/26. I have had to stick with the 9/26 build because I get odd behavior that I don't see people posting here.

For all of October every nightly has this weird issue with becoming unresponsive. The screen stays black and will not wake up, I then have to remove the battery. Other times the phone will lock up while in use and may or may not restart. These events seem to happen in fits. It will be stable for a few hours or maybe a day and then start going into constant lockup mode about every 15m to an hour provided I pull the battery and start the phone up. Recently, on boot up, the phone has locked up in the early stages of the CM boot and I have to do a battery pull. The crazy thing is is that the 9/26 build had none of these issues.

I waited to post here to see if I could figure it out but I ran out of ideas. I tried logcating but have yet to catch what is happening on tape. It is like it behaves when I monitor it. I did figure out that it seems to not charge while in the black unresponsive screen state.

Well if anyone has a copy of the 9/26 build I would love it :D or any suggestions to catch some debugging info so I can follow up with some more scientific data.

Oh I don't want to go to CM10.1.3 since it does not support WiFi 5ghz channels greater then 149. I dont even think they see this is a bug.

Well hopefully we can get to bottom of this. I loved the stability of 10.2 9/26 and would love to be back on CM.
[Verizon Samsung Galaxy S III] Restola:
[MENTION=2550033]M4gicM@[/MENTION] can you try a clean install, do not install any apps you don't absolutely need, and see if it comes back? May be an app or widget causing the issues.
[Verizon Samsung Galaxy S III] cammykool:
Anyone having GPS issues?
[Verizon Samsung Galaxy S III] lou1210:
Cammy - what version of the ROM are you on? Did you clean or dirty flash, what error are you getting? Please give more details....
[Verizon Samsung Galaxy S III] rockingondrums:
I just want to expand on this because at any given moment, the nightlies can be better than stable, to much worse, to anything in between. It kind of bothers me when people just generally lump nightlies as more stable than stable (not you). As it says right on the cm page, you cannot report bugs on nightlies. There can be VERY BIG ones. Sometimes people get all agro when the nightlies do something terrible, but that is a risk you take when running them. OTOH, if you encounter problems with stable, there's probably a fix and if not there is bug tracker for it.

FWIW, 10.2 has been good to me and many others, but that could change tonight, or tomorrow night. If you can't risk it, don't flash it. If you flash it, don't get pissy if it craps out on you.
[Verizon Samsung Galaxy S III] titanshadow:
I did once, a few nightlies back but a reboot fixed it.
[Verizon Samsung Galaxy S III] dewhashish:
No advanced menu, I go in there to turn off the lights to the capacitive buttons, has it been moved?
[Verizon Samsung Galaxy S III] Worm1996:
Everything works fine here.
[Verizon Samsung Galaxy S III] NegativeOne:
Are you freaking kidding me? Google is doing EVERYTHING possible to make me not want to be their customer. Forgive the useless post but I'm pretty enraged. I don't need to be protected from myself. I know what I put on my phone, and I don't want to have to live with a cluttered-up status bar
[Verizon Samsung Galaxy S III] Gerr1985:
Restores via Titanium Backup just hang.

Apps can be installed via Play store.

Attempt data restore only, causes force closures on the apps.

*sadface*
[Verizon Samsung Galaxy S III] thelangosta:
When I did this my phone would not reboot. It got stuck on the splash screen that says galaxy sIII and has the blue cid. Battery pull and reboot did not fix it. All stock cm with latest gapps. Then twrp wouldn't let me restore a nandroid. Had to flash a TW ROM to get it functional again. Weird, and the first time I was that stuck ever. Phone is squeaky clean now after wiping everything except extsd. Will try again later. Wish I could have been hooked up to the pc for a log.