yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Hans5849:
I had no data on the .2
[Verizon Samsung Galaxy S III] invisiblek:
Yea... I know...

*sigh*

The code is up there, somehow the build bot didn't pick it up or something. Stick to nightlies for now.
[Verizon Samsung Galaxy S III] rockingondrums:
There is a thread in this forum and a sticky on rootzwiki with all radios.
[Verizon Samsung Galaxy S III] quartarian:
How I fixed my Issues with 10.1.0.1

Hey Guys,

After flashing 10.1.0.1, I still had data but no phone connectivity. When I tried flashing a different rom, I still had data but got a random phone number. After odining, I was stuck on roaming.

If your still having problems, I fixed mine by a lot of guess and check, but the winning combination seemed to be odining to root66, and dialing *2767*3855#. Hope it works for you. :)

-Matt
[Verizon Samsung Galaxy S III] ElementR:
Thanks! After several hours of trying you fixed my phone.
[Verizon Samsung Galaxy S III] sanjsrik:
So, because I searched the thread and didn't find the answer, and maybe if it was there, it was buried in the last 40 pages since the 10.1.0.1 release. My data broke.

Is it enough to wipe fully and flash the 629 nightly?

Just asking because that's where I'm going next.

Any help would be most appreciated.
[Verizon Samsung Galaxy S III] buschbarber:
I just posted a few pages back that I ran into the same problem. I was able to flash RC5 and then flash 06/29. I got Data back. I have since flashed up to Nightly 07/01 without issue. I tried 10.1.0.2 but I had issues with no cell Signal. I flashed 07/01, again, and all was well.

It was just pointed out that if you are flashing Nightlys, don't bother with the Stable versions such as 10.1.0.1 or 10.1.0.2.
[Verizon Samsung Galaxy S III] sanjsrik:
Thanks for the response. Did you do a clean flash or a dirty flash over what was already there? I did a clean flash just now of 6/28 and data is still hosed. So, I'm guessing do a clean flash of RC5 and gapps and then restore apps using TI Backup.

Does that sound like the right way to go?
[Verizon Samsung Galaxy S III] buschbarber:
I have been Dirty Flashing and occasionally Cleaning the Cache. My only complaint is poor Indoor Signal Strength. I am waiting for a major update to do a Clean Flash again. My apps and camera have been working fine. I get 3G and 4G without issue.
[Verizon Samsung Galaxy S III] sanjsrik:
Okay, thanks for the update. Since I did a clean flash any way, doing another one won't make that much of a difference. I noticed that the 6/28 update alone did NOT restore my data. It said it got 4G but when I tried to surf, got timed out on pages.

---------- Post added at 11:26 AM ---------- Previous post was at 11:00 AM ----------

To ask one more question as a follow-up, would flashing back to stock and then reflashing 7/2 nightly work as well?

UPDATE: Flashing RC5 and then 7/2 fixed data.
[Verizon Samsung Galaxy S III] NeoMagus:
Thats not a bug, thats normal filesystem behavior for Android 4.2 due to multi-users. If you don't like that stay on 4.1
[Verizon Samsung Galaxy S III] WhammyDroid:
Why was this change made? Is there a bug in 10.1? Does anyone know why we cannot backup to sdcard?
[Verizon Samsung Galaxy S III] NeoMagus:
You are backing up to the sdcard, its just directed differently, it is because of the filesystem changes in Android 4.2. Because of multi-users it points everything for the main user to /sdcard/0, and for example if you make another user there stuff ends up in /sdcard/1. The old recoveries are pointing to the wrong directory by default because they don't take the multi-user folders into acct
[Verizon Samsung Galaxy S III] Restola:
Correct. This only "appears" as a bug in 2 instances that I have found:

1) You flash back to a non 4.2 ROM

2) You are using an old CWM or TWRP

If you flash to 4.2 from within recovery (and not from within CM10 using the cmupdater) and stay there the file system works

exactly

as you'd expect and the move is transparent.
[Verizon Samsung Galaxy S III] will.bates94:
All he needs to do is basically do is upgrade whatever recovery he is using.
[Verizon Samsung Galaxy S III] PerCompLLC:
build.prop edit so that the Play Store sees the device as "compatible".
[Verizon Samsung Galaxy S III] peaceofpi:
many clocks available in the play store - I am running the Nexus 4 clock myself...

---------- Post added at 01:46 PM ---------- Previous post was at 01:41 PM ----------

It will always say your device is incompatible - that's fine. But you have to do the build.prop edit - reboot then you are good as gold
[Verizon Samsung Galaxy S III] PerCompLLC:
What peaceofpi said... :)
[Verizon Samsung Galaxy S III] peaceofpi:
um has anyone used the Day Dream feature with Google Currents?

In Love!
[Verizon Samsung Galaxy S III] swirly05:
sorry i knew it was an issue and i just wanted to know, no problem. Is the volume still an issue tho?
[Verizon Samsung Galaxy S III] MWFD:
I primarily use the clock app when my phone is docked in the media dock and I dont like the 'dock' apperance/settings on 4.2 clock app (I much prefer 4.1 but didnt know if installing the apk from 4.1 would mess anything up since its a system app). Does the Nexus 4 clock you are using have the ability to be set as default when the phone is docked?
[Verizon Samsung Galaxy S III] goldsmitht:
Anyone notice airplane toggle is jot working? Also, "possible NFC fix zip works to turn on NFC. One of InvisibleK's apps
[Verizon Samsung Galaxy S III] will.bates94:
I noticed my ringtone was distorted all the way up also
[Verizon Samsung Galaxy S III] Div033:
Very interesting. Thanks for the info, this probably explains why signal seems so much worse from CM10 vs. CM10.1

Anecdotal evidence is good, don't get me wrong. However much like how I enjoyed learning about the signal issue with the info you provided, I figured people would find value in knowing what hardware overlays actually do. Based on this, its entirely possible that disabling hardware accelerated overlays could negatively impact battery life. That doesn't mean it WILL, but hey almost anything is possible!
[Verizon Samsung Galaxy S III] danstar:
I noticed on both of the 4.2 roms that are out now for the d2vzw, that my signal strength shows 0db with a high asu number quite a bit. I don't know if it is rom related or if there is issues with the tower that is 3 miles from my house.
[Verizon Samsung Galaxy S III] will.bates94:
from what i've read, each tower has a 10 mile radius...but Im not 100% sure about that.
[Verizon Samsung Galaxy S III] peaceofpi:
I don't have a dock. And when I am plugged in I use the Day Dream of Google Currents...Give it a try
[Verizon Samsung Galaxy S III] lycwolf:
Update on the flickering issue. I've installed the UN-OFFICIAL 12-19 build, and it's gone away. Still can't use hotspot... But I think the flickering may have been a flash issue when i installed the rom the first time.
[Verizon Samsung Galaxy S III] NeoMagus:
In case you missed it..

Airplane mode works fine for me both thru the power menu and the Quick Toggle in the pulldown
[Verizon Samsung Galaxy S III] will.bates94:
working on my end also
[Verizon Samsung Galaxy S III] deesto-xda:
True. And maybe this is a dumb question, but: why are the nightlies more stable than the stable releases?
[Verizon Samsung Galaxy S III] DvdOwens:
Front Camera Causes Reboot

Has anyone found a fix for the reboot that occurs when you try using the front camera in the instagram app ?
[Verizon Samsung Galaxy S III] mariod505:
I just did a clean flash to 10.1 (cleared caches) from 10.1.0.1, and I still can't activate. If I flash back to 10.0 or RC5 or nightly, will that help?
[Verizon Samsung Galaxy S III] buschbarber:
I would think so.
[Verizon Samsung Galaxy S III] zachf714:
When ICS came out Google completely reworked the os ... So now there is much more for the team to mod along with when. They do code freezes they miss much needed patches from the git
[Verizon Samsung Galaxy S III] Restola:
I believe Invisablek said there is a critical component that the build bot is missing when it builds our stable releases (10.1.0.1 and 10.1.0.2).
[Verizon Samsung Galaxy S III] damnyouwaffles:
What is the latest build that is safe to flash?
[Verizon Samsung Galaxy S III] zachf714:
The latest nightly
[Verizon Samsung Galaxy S III] JohnnyTToxic:
No, that's new to me. I can confirm it though (7-2 nightly, MF1, stock kernel).

Fired up instagram, went to photo mode, flipped to front camera, took picture, and the phone froze and rebooted. Looking through Jira, there are a number of tickets open for this (happens with a few other apps) The notes on the tickets lead me to believe that it is a kernel/driver issue and is only working on RootBox4.1 (as far as CM based roms go)

They'll likely fix it, as someone has already (Bajee Baskararasa, the RootBox rom developer/maintainer).
[Verizon Samsung Galaxy S III] uncleguito:
This has been happening for quite some time with CM 10.1 and Cerberus when the front-facing cam is used to capture shots. Phone completely crashes & reboots.
[Verizon Samsung Galaxy S III] arh2o:
Oh the irony here. Made me chuckle.
[Verizon Samsung Galaxy S III] zachf714:
Yeah I know but its true ;) the last time I use a "stable" release and it was stable was gingerbread
[Verizon Samsung Galaxy S III] Badouken:
Im on 10.1.0 and I keep seeing updates for 10.1.1 and 10.1.2 but keep reading on this thread that they just F stuff up... which is sad... I kinda want to update though... any new features that im missing? Would a Nightly be good enough / cause any issues? Or will the CM team release a stable 10.1.3 that actually is STABLE soon!
[Verizon Samsung Galaxy S III] UberSuber:
Well, snap. Accepted the 10.1.3 update without checking the thread first, and now I have no cell service. Silly me, I thought stable meant basic things like cell service would still work. Ugh. And since I did the quick and easy 1-press update from the updater, I have no nandroid to go back to. Niiiice. That 1-button update feature should be killed.

EDIT:

Whew! flashed back to rc5 and got data back. Then, flashed back to 10.1.0, and all is good. No nandroid needed. No re-activation, even. That is a relief.
[Verizon Samsung Galaxy S III] tv31284:
You can just flash a working nightly over with no ill effects.
[Verizon Samsung Galaxy S III] UberSuber:
Yup! What I did. Or, in my case, the last stable stable. :good:
[Verizon Samsung Galaxy S III] invisiblek:
10.1.0.3 is live and working. Make sure you have the latest firmware (VRBMF1)

I apologize for the problems.

https://plus.google.com/117962666888533781522/posts/3WRFRuWgPWd
[Verizon Samsung Galaxy S III] jdiamond7:
No worries. Thanks for all your hard work!
[Verizon Samsung Galaxy S III] zachf714:
It's InvisibleK to save the day :)
[Verizon Samsung Galaxy S III] Badouken:
uhhh i just flashed 10.1.3 and I swear my data is way worse now... granted I usually have 0 bars in my house... but when i go upstairs that usually turns to 1-2 bars! now im upstairs and i have 0 bars most of the time... sometimes going to 1, my signal strength says 0dBm and 99asu, it keeps jumping to -110dBm and 30asu... I need to go around town to give a better evaluation though, again my house is a total dead zone...

EDIT*: uhhh nevermind I guess, I went downstairs where i usually have 0 bars and now I have 2! So It should be fine! my bad!
[Verizon Samsung Galaxy S III] Restola:
OP updated. 10.1.0.3 works. Please use the MF1 modem

PM bug reports to me to be included in the OP. Also submit a jira ticket with a logcat against the stable builds if you'd like dev attention (or at least post a logcat in this thread with your problem described).
[Verizon Samsung Galaxy S III] mariod505:
I thought the CM ROMs included a modem, so why does the post ask us to make sure we're on the MF1 modem???

In any case, how do I check what modem I'm running?

Is is the baseband version? (I seem to have VRGL1) ....so if that's it, how do I flash a new modem?
[Verizon Samsung Galaxy S III] Restola:
The modems are separate from ROMs. You can flash back and forth between AOSP and TW and still keep the same modem. Maybe I'm using the wrong term when I say "modem" (someone correct me if I am). But yes you read this under "baseband version".

Go here http://invisiblek.org/sch-i535/firmware/

Download VRBMF1.

Flash in recovery.

Win.
[Verizon Samsung Galaxy S III] mariod505:
Thanks! I can flash the zip through the Clockwork recovery, or I need to use ADB or something?
[Verizon Samsung Galaxy S III] Restola:
CWM or TWRP
[Verizon Samsung Galaxy S III] toddley:
10.1.0.3 is great no issues here
[Verizon Samsung Galaxy S III] buschbarber:
Even with 10.1.0.3 and MF1, Signal Strength is still low.
[Verizon Samsung Galaxy S III] Restola:
I'm having one channel audio on headphones on the new stable 10.0.1.3
[Verizon Samsung Galaxy S III] titanshadow:
I'm actually getting good signal strength. Not quite as high as TW Stock, but so close that it matters very little.
[Verizon Samsung Galaxy S III] fua1:
To Wipe or Not to Wipe ...

I'm on 10.1.0 now, and just set everything up. Nominally, I wipe and clean install for major updates.

Any comments on flashing 10.1.0.3 straight on top of 10.1 without wiping ?

Thanks!
[Verizon Samsung Galaxy S III] apacseven:
Just flash it, wiping isn't necessary when you are upgrading a ROM.
[Verizon Samsung Galaxy S III] deesto-xda:
10.1.0.3 has re-added this audio problem: every other song plays on right-only channel; followed by one song in full stereo.

Also saw a problem where ringtone/notifications got muted and could not be un-muted.

I may be stuck going back to the nightlies for a while.
[Verizon Samsung Galaxy S III] soohyunk83:
Anybody have the issue where you have to hit 1 before answering a call now?

It wasn't like this, but all my calls became like this after I updated to the 6-27 nightly.
[Verizon Samsung Galaxy S III] DG4FREE:
Also getting the audio issue, although its only when using Google Play Music for me. Apollo and watching YouTube videos plays normal stereo sound through both channels fine. I uninstalled Play Music and reinstalled as well as cleared data and its still doing it so I'm going to assume its ROM related. Maybe it's linked to whatever is listed as the default player? In my case it is doing it for every song, not skipping as deesto-xda stated. I tried on both firmware/baseband versions so I know that's not the issue either.
[Verizon Samsung Galaxy S III] k.electron:
+1
[Verizon Samsung Galaxy S III] DG4FREE:
Just updated to 7/3 nightly, audio seems to work fine now. Will update if otherwise.
[Verizon Samsung Galaxy S III] Restola:
Yep audio works fine on the nightlies.
[Verizon Samsung Galaxy S III] tehloxely:
Glad to hear that! I cannot live without my personal library on G.Play Music!
[Verizon Samsung Galaxy S III] deesto-xda:
Restola: can you please update the OP to show that 10.1.0.3 seems to have broken audio again?
[Verizon Samsung Galaxy S III] Restola:
Yep just did
[Verizon Samsung Galaxy S III] iofthestorm:
That sounds like a Google Voice issue, are you using it? I think the default setting for GV is call screening enabled.
[Verizon Samsung Galaxy S III] Hans5849:
For some reason my lock screen isn't working. When I power on it goes straight to the desktop. I reboot, the lock screen works once and then doesn't work again.

Looks like it's a problem with handcent pop-up notifications not clearing.
[Verizon Samsung Galaxy S III] VinBertinelli:
I wouldn't really call this a stable since the omnipresent low recording volume still hasn't been fixed...
[Verizon Samsung Galaxy S III] sbenson1226:
This ROM is the farthest thing from stable, but that's the case with all AOSP Roms for the GS3.
[Verizon Samsung Galaxy S III] zachf714:
AOKP isn't bad.. It's the only aosp tree based ROM I will use
[Verizon Samsung Galaxy S III] mcdevil58:
Is anyone still having the one headphone only working issue on the 10.1.0.3 build?

Also is there any kind of fix for this issue
[Verizon Samsung Galaxy S III] :
flash any nightly after 10.1.0.3, it is fixed
[Verizon Samsung Galaxy S III] invisiblek:
ROFL

"The farthest thing from stable" (sorry just had to requote that)

ROFL (sorry just had to reiterate that)

Let's hear what's not so stable about it. Let's also see some logs of errors. If you don't provide either, you don't belong in this thread.

Please go to the aokp thread and let them know how much you love their rom. Posts like these have no business in this or any development thread.
[Verizon Samsung Galaxy S III] zachf714:
Sorry .... Are there ever any logs, I posted a few pages back for the front facing pics on other apps also is there a way for there to add the verizonSSO libs and apk as prebuilts ;) I'm still used to the inc where we could post what ever and everybody knew what was going on
[Verizon Samsung Galaxy S III] LLStarks:
Nightlies are amazing right now and cyandelta does a great job of keeping everything updated.

Daily kernel and system fixes, quick camera, privacy guard, and all the other new stuff that keeps landing.

With Touchwiz devs bailing left and right, now's the perfect time to be embracing cutting-edge Android experiences.

There's no hardware instability, just CM-specific annoyances such as alarms and notifications insisting on being silent.
[Verizon Samsung Galaxy S III] brockkk:
i always find myself coming back to cm. i love halo and pacolor but i just seem to get better signal with cm. any chance of halo getting added down the road? or just keeping it nice and vanilla?
[Verizon Samsung Galaxy S III] Restola:
In terms of stability, the latest nightlies have a pretty small issues list (my personal list I maintain for the OP), all are non-"stability" items...two of which are problems with apps (which may have nothing to do with CM at all). The biggest complainers recently have been around the fact that the nightlies have been more stable than the stable releases lately...big freaking deal? Flash the newest nightly instead?

The only other item is possibly slightly weaker signal strength, most noticeable on the fringes of poor reception areas.

Other issues I've read, and I read the threads several times a day, have seemed to be non-stock kernel, unrepeatable, a "feeling" about something not working "right", or no logcat provided (i.e. it didn't happen).
[Verizon Samsung Galaxy S III] zachf714:
The nightlies are like a BRICK WALL just stay with them because they run great
[Verizon Samsung Galaxy S III] Div033:
Yes I definitely agree. I was using nightlies for over two months without major issues. There is a litany quirks though, the biggest one being how the aosp RIL handles low signal being inferior to touchwiz. I've also noticed some strange visual artifacts when browsing the web and disabling hardware overlays actually slightly improves overall performance. I don't think providing logs would help as I think the devs are busier with more important things. One day I'll learn to dev and fix them myself.

I recently went back to touchwiz and I want to vomit everywhere. CM was so much faster it isn't even funny. Wtf are you doing Samsung?!?!
[Verizon Samsung Galaxy S III] zachf714:
Yup I pushed the prebuilt libs and apk to the system lastnight after flashing a nightly and it is so solid .. I think for us they mine as well just compile a nightly as a stable and slap it up :)
[Verizon Samsung Galaxy S III] Ckamc:
Any recommendations for kernel if ones phone gets hot while watching flash videos? Phone gets to 110 and currently on stock cm kernel
[Verizon Samsung Galaxy S III] zachf714:
Use taker and set it to under clock while watching videos :)
[Verizon Samsung Galaxy S III] Ckamc:
Taker? Please link or explain where it can be found.

Thank you
[Verizon Samsung Galaxy S III] sivarticus85:
He means Tasker. It's in the Play Store.
[Verizon Samsung Galaxy S III] zachf714:
Yup sorry about the misspell
[Verizon Samsung Galaxy S III] Ckamc:
Not going to recommend KT747 or Lean? If I need to under clock I might as well download setcpu again
[Verizon Samsung Galaxy S III] bigee1212:
7/1 nightly had s4 blobs merged helped the signal. Wait til other ROMs start basing off newer night lies then you can get ROMs with halo pie etc.
[Verizon Samsung Galaxy S III] Restola:
My read on this...

10.1.1 stable has been released. It is 10.1.0.3 plus security fixes (including the latest widely publicized one affecting virtually all android devices).

However these fixes were already merged into the nightly releases, and the nightly releases fix some of the issues that exist in the stable releases...so you may want to stay on the latest nightlies.

As for all recent releases, please make sure you are on the MF1 modem
[Verizon Samsung Galaxy S III] im_on_fire:
Whenever I enter an incorrect pattern or pin on the lock screen. The phone grinds to a halt and becomes basically unusable until I restart it. I've been having this problem for at last a week of nightlies and on the current 10.1.1. Anyone else having this issue?
[Verizon Samsung Galaxy S III] tech9tcv:
Privacy Guard vs OpenPdroid

What is the difference? It seems to be doing the same thing. Is PG based off of OPD? Can someone elaborate? Thanks in advance.
[Verizon Samsung Galaxy S III] BoxyBox:
My recovery is currently CWM 6.0.2.3. I want to update but I have no idea what to do with the .img file and using ROM Manager requires a donation.

Can I simply use GooManager to install the latest TWRP over CWM or will that cause issues?
[Verizon Samsung Galaxy S III] apacseven:
Can't you just use EZ Recovery?
[Verizon Samsung Galaxy S III] airmaxx23:
Bluetooth seems to be working better on the 7/11 build. It turns off much quicker and doesn't seem to get stuck anymore.
[Verizon Samsung Galaxy S III] kinnerful:
Hasn't been looking at the aosp scene for a while. Is there any plan to incorporate Android 4.3 in the near future?
[Verizon Samsung Galaxy S III] airmaxx23:
Once everything gets publicly released they may move to 4.3, we'll have to wait and see.
[Verizon Samsung Galaxy S III] RaiderX29:
I thought it was just me. It becomes unbearably slow once an incorrect pin is entered. Only solution I've found is to reboot.

Are you using any security programs? I attributed the issue to using Cerberus.
[Verizon Samsung Galaxy S III] ddggttff3:
if you have cerberus setup to take a photo after an incorrect code entry, it is that app.

Cerberus has an issue with the GS3 when it trys to take a photo with the front camera. It either slows the phone down to a halt, or freezes and reboots.
[Verizon Samsung Galaxy S III] uberbdon:
I don't have this issue with Cerebus on the TW based ROM I'm on...
[Verizon Samsung Galaxy S III] zachf714:
It has to do with the aosp kernel and drivers I think
[Verizon Samsung Galaxy S III] Chris123NT:
I noticed Bluetooth was more stable as well, waiting to see if it still hard freezes the phone every once in a while when connecting to my car for BT audio.
[Verizon Samsung Galaxy S III] toddrosenberger:
Had anyone tried the experimental signal strength build? Wondering if it is better. I'm on the 10.1.2 and it's really stable, debating if I should try the new build
[Verizon Samsung Galaxy S III] airmaxx23:
Where is the experimental signal strength build located?
[Verizon Samsung Galaxy S III] WhammyDroid:
[MENTION=2385005]invisiblek[/MENTION], I wanted to follow up on a JIRA issue I submitted and you commented on. Is there anything else you need from me on JIRA 1355? I know you and others have been busy with other aspects of CM. I just wanted to make sure I gave you everything you needed in order to investigate and hopefully resolve the issue. If there is anything else, please let me know.

JIRA: https://jira.cyanogenmod.org/browse/CYAN-1355

Edit: Latest nightly still has the issue; I have not yet checked 10.1.2.

Thanks!
[Verizon Samsung Galaxy S III] toddrosenberger:
I just downloaded it from get.cm. I went ahead and flashed it, I'll test it out to see if signal is better at home which is a low signal area
[Verizon Samsung Galaxy S III] Chris123NT:
I downloaded the signal test build as well, going to see if it improves things any, especially with weak 4g signals
[Verizon Samsung Galaxy S III] apacseven:
That build was done last night in an attempt to improve the 0 db 99asu issue. It didnt appear to solve it in initial testing.