yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] ugachris:
Updating recovery usually fixes the 0 folder issue. Wiping data and caches usually fixes boot problems.
[Verizon Samsung Galaxy S III] jlokos:
Is this what you are looking for? http://xdaforums.com/showthread.php?t=2181743
[Verizon Samsung Galaxy S III] landale:
It should. I have a similar trip coming up in a week and got a prepaid T-Mobile SIM card here to test it out in advance as well as testing with a friends AT&T one. I can confirm voice and data works (Edge data only for both as it seems the Verizon S3 has a block to prevent 3G connections on either carrier but I would assume 3G should work on foreign carriers).

There are a few hoops you have to go through to get it working my experience though. After you insert the SIM card and power the device on the phone must be in a CDMA mode whether it be LTE/CDMA or Evdo/CDMA only or whatever. Then you can toggle to a GSM mode such as WCDMA preferred. It will connect but not with data. Then you can turn on airplane mode and turn it off and when it comes back everything should work. If you have to power your device off you will need to repeat this process again as for some reason the first connection attempt has to be a CDMA based one and not a GSM one. Again I am not sure if this is the case with all GSM networks or just US based ones but just something to keep in mind from my experience using it on T-Mobile.
[Verizon Samsung Galaxy S III] sivarticus85:
Anyone getting data drops on the latest MB1 modem? Seems to me like data is more stable on the LK3 modem.
[Verizon Samsung Galaxy S III] jlokos:
No data drops for me. It seems to be working fine.
[Verizon Samsung Galaxy S III] no0n:
I flashed mastas yesterday afternoon build. I've had the phone not be able to wake back up from sleep 3 times in the past hour. Had to battery pull. Any suggestions? I did a full clean wipe before flashing last night. No other problems

To the person asking about camcorder volume. I too went stock but its much better now. A little quieter but nothing like it was before
[Verizon Samsung Galaxy S III] Stealth111:
While on MB1, it killed my data while on my Network Extender, as well as some definite data anomalies while out and about (0dB and 99asu randomly). I went back to MA2 which was running perfect for me since it came out! I am sure I will not leave well enough alone and eventually mess with MB1 again in the future.
[Verizon Samsung Galaxy S III] sivarticus85:
Exactly what I've been experiencing. MA2 modem did the same thing as well. LK3 has given me the best performance. Sticking with it for now.
[Verizon Samsung Galaxy S III] nbaj2k:
LK3 definitely has been working better for me. Constantly had data drops with MA2. At times it said that I had data signal even though I really didn't. No issues after switching back to LK3.

-J
[Verizon Samsung Galaxy S III] alee:
Just to confirm, I know there was a revert fix and then there was the CM official fix. Are the CM builds the last few days still ok on this?
[Verizon Samsung Galaxy S III] landale:
I am on mastamoon's 3/12 build and it's working for me. I believe now that the fix has been merged in CM all builds will work. All that mastamoon's cherry pick does is add GSM roaming as an option under mobile networks but you don't need that for GSM. You can also adjust it but dialing *#*#4636#*#* and going to phone information.
[Verizon Samsung Galaxy S III] PVLMTREE:
Each build seems to get more stable and efficient for me. It's starting to look like I'm enjoying CM more than worrying about dealing with bugs.

On the side note, i want to thank invisiblek and mastamoon for giving us your Unofficial builds; it has been my go-to ROMs now. Especially, for helping us push a GSM fix. Without you guys, I would have never been so sane and stressless, haha.
[Verizon Samsung Galaxy S III] -Maverick-:
Just tried the new 3/12 from mastamoon, and it's working great! I'm currently trying it out with a T-Mobile US sim and no problems so far, getting edge only but I expected that considering the locked bands.

Now to finally try kernel 3.4.
[Verizon Samsung Galaxy S III] PerCompLLC:
Had the same problem when I flashed. Did a battery pull and flashed LeanKernel 2.9. No problems since. I'm not sure that the CM team has the new kernel ironed out yet...
[Verizon Samsung Galaxy S III] mastamoon:
Ive had no SoD issues on 3/12 or 3/13.

-- Question. Would you guys like to have that GSM selection cherrypick in every build? I guess GSM still works without it and those that are doing SIM swapping know how to manually switch over. Personally, Id rather not have an option in there that somebody could possibly turn on by mistake.
[Verizon Samsung Galaxy S III] landale:
I am fine with it being removed as all it adds is a convenience for the first toggle to GSM mode. You still have to go into the Phone Information screen to get it working again on a reboot so might as well just do everything from there.
[Verizon Samsung Galaxy S III] no0n:
Did you mean to say 2.0? I flashed that at first but phone wouldn't boot. Maybe I'll try again if you confirm the version
[Verizon Samsung Galaxy S III] mastamoon:
No, 2.9 http://rootzwiki.com/topic/32286-kernel-aosp-jb-leankernel-minimalistic-kernel-jb-42x-v29-3913/

Make sure you grab the AOSP build and not the TW, he does both.
[Verizon Samsung Galaxy S III] jlokos:
I'm on 3/13 build with LK 2.9exp. Everything works great. With respect to GSM mode, I'm a little dense. How is this different from what is available in stock roms, i.e., do we still have to go into phone info screen to get it to work?
[Verizon Samsung Galaxy S III] PVLMTREE:
With the revert on the official nightlies, I believe the GSM option won't be needed, thanks to invisiblek.

On other note, does anyone encounter lag from playing music via Google Play Music when multitasking? It's horrid. Running masta's 3/13.
[Verizon Samsung Galaxy S III] no0n:
That would explain it :D Thanks
[Verizon Samsung Galaxy S III] mastamoon:
I know GSM functionality is back, but without the cherry pick the GSM switch in Settings>Mobile Networks>Network Mode wont be there by default. Ive never used the phone in this manner so I don't know what is more convenient for those users. Its no big deal to pull the patch in, but if you still have to jump through hoops whether or not that option is there, ill just leave it out.
[Verizon Samsung Galaxy S III] luv2increase:
Where is the 3.4 kernel?

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] odub303:
You wouldn't want it. It isn't compiled with Linaro.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] CrustyMcLovin:
I had data drops using the previous MA2 modem and for a long time I had stayed with HE just because it was stable and worked. Then I tried the latest MB1 last week and so far its been really good. The true test for me is when I drive along remote highways where you see a lot of 3g/4g handoffs, this is really the best I've seen so far.

Interesting though to see that a lot of others don't seem to like this one. To each their own I suppose.
[Verizon Samsung Galaxy S III] mastamoon:
I believe invisiblek's roms are being built with 3.4.
[Verizon Samsung Galaxy S III] luv2increase:
:(

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] -Maverick-:
The cherry pick is useful, it sticks after a reboot. :good: I couldn't find the option in the official nightles, so I have no way of switching. I'm pretty sure I have to dial a # to make the switch, I just forgot what it was. I don't mind doing it manually if the cherry pick is removed, as long as the option selected sticks after a reboot. :fingers-crossed:
[Verizon Samsung Galaxy S III] PVLMTREE:
*#*#4636#*#* (*#*#info#*#*)

For me, it sticks after a boot (:
[Verizon Samsung Galaxy S III] -Maverick-:
Thank you, I'll give it a try if the GSM cherry pick is removed.
[Verizon Samsung Galaxy S III] anacree:
Can anyone confirm whether bluetooth mic input works with Google Now search. Mine doesn't seem to be...didn't know if this was normal. If it is, anyone know of an app I can get that will let me control my phone using my bluetooth mic?
[Verizon Samsung Galaxy S III] SilentAce07:
Try unchecking the box for system touch sounds. I had that problem before.
[Verizon Samsung Galaxy S III] PVLMTREE:
Thanks! So far, it reduced a little bit of audio lag, but can still hear just a tad. But now it's bearable.
[Verizon Samsung Galaxy S III] SilentAce07:
I keep getting the activation screen upon reboot. This has happened for 2 builds now. After I bypass, it shows a jumbled wrong number under status for my phone number.
[Verizon Samsung Galaxy S III] ugachris:
See post number 2 in the Q&A thread:

http://xdaforums.com/showpost.php?p=35600769&postcount=2
[Verizon Samsung Galaxy S III] SilentAce07:
Thank you. I was worried I'd have to quit using this. Turns out, I just missed that!

---------- Post added at 07:52 PM ---------- Previous post was at 07:24 PM ----------

Tried the first two options and neither worked.

Also, the nav bar no longer appears when I edit the build prop. It boots with a black area with nothing there and then goes away soon after.
[Verizon Samsung Galaxy S III] johnwaco:
Reboot into recovery and wipe cache and dalvic cache. That's what worked me.
[Verizon Samsung Galaxy S III] SilentAce07:
Wow. I've been trying to fix this issue across two different roms today on my phone and that seems to have fixed it.

Thanks a ton. Good lord.
[Verizon Samsung Galaxy S III] SilentAce07:
Okay so my phone is still going into the activation screen every time I reboot unless I clear cache and dalvik beforehand. What the heck is wrong with my phone? It's happened across this rom, Slim Bean, Jedi, etc. I'm incredibly frustrated and have been looking for answers for 8+ hours now.
[Verizon Samsung Galaxy S III] prototype7:
Not sure why it does that, mine does too occasionally. You can exit out of it by just pressing home, never actually caused an issue so I've just ignored it.
[Verizon Samsung Galaxy S III] SilentAce07:
Hmm. Can you send mms after you skip an activation screen? Aka have a jumbled incorrect phone number under status?
[Verizon Samsung Galaxy S III] luv2increase:
Try it and see lol

Sent via Crossbreeded, 100% V6 Supercharged. KT747'd and Linaro Built Paranoid Android 3.10
[Verizon Samsung Galaxy S III] Obaterista93:
I was having an issue with MMS the last time I was on CM10.1 (Wednesday I think) after I skipped activation, but I didn't check out the phone number.
[Verizon Samsung Galaxy S III] SilentAce07:
Edit: Sorry guys. Didn't realize I should report the bug in the official thread rather than here!

I can't. I can confirm it's something wrong in the rom. I've flashed 5-6 different roms (all CM base) and had this problem. I don't have the problem with a build from last month by Masta.

To sum up the problem:

On first boot, everything is fine.

On second boot, the phone will goto an activation screen and won't do anything else. If you skip it and check your phone status, your number will be jumbled.

Neither of the solutions work in the 2nd post I've been directed to. However, data and voice works. What doesn't work for sure is MMS. Anytime that number is wrong, the mms doesnt work.

You can avoid this happening by wiping cache and dalvik before the 2nd boot, and it wont do the phone activation thing, and youll have your number still.

However, anytime you reboot, you need to do this, or itll lose your number and mms wont work.

I've spent a good 10+ hours today working to get my phone working (stubbornly). I've tried rolling back to an older modem/rpm, a different kernel, a different rom (Slim Bean, Jedi, both unofficial CM builds (newest) both w/ linaro and w/out). Regardless of what I changed, it would do this.

If I flash a touchwiz rom OR a dated CM rom, this bug doesn't happen. (using February 20th is the last one I have before March 8th, which has this problem, as do all newer roms). Hopefully that narrows it down.
[Verizon Samsung Galaxy S III] tcsac:
That would be the page r00tzwiki sends you to... per the description on the download page.
[Verizon Samsung Galaxy S III] mastamoon:
Have you tried installing clean and without Gapps?
[Verizon Samsung Galaxy S III] goldsmitht:
RILJ... again?

Ok, hasn't happened in a WHILE, but recently started getting the dreaded RILJ wakelock on lastest(S) unofficial. will clear out with a cache and dalvik wipe, but will kill the battery if i don't catch it.

can't find the answer, was looking but was on phone. any advice would be greatly appreciated! The unofficial is the only version i can get my GPS to work on, and have normally had GREAT battery life with it and KT747.

thanks!

:cyclops:
[Verizon Samsung Galaxy S III] odub303:
I'm on the latest unofficial and have not had the issue yet, but will keep an eye out. Can you grab a logcat, pastebin it and link it in the irc channel?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] SilentAce07:
I have, but I think only to set the proper NV / RUIM/SIM setting first like it said in post #2. I havent gone through several reboots without Gapps at all, but I can if you think it'd help.

Originally, I thought the problem was that the phone would default to NV (because it would always be set to that again after a reboot). I noticed that on every restart, it immediately says "No SIM card - searching for service" briefly before connecting and then trying to activate. Then when I check the cdma subscription it says NV. So I assume my setting wont stick because on every reboot (unless I clear cache and dalvik), it fails to see the SIM and then resorts to nv.
[Verizon Samsung Galaxy S III] goldsmitht:
If phone having problems reading sim card, that might be the issue; think you can just replacement sim from VZW, but might be wrong. Still would be good to eliminate that, especially if this is happening across various ROMs
[Verizon Samsung Galaxy S III] SymbioticGenius:
I am still running the 3-07-13 build no such issues. Any possibility flashing to an older build might help you guys out?
[Verizon Samsung Galaxy S III] SilentAce07:
No, because if I flash an older build it doesn't have this issue. And doesn't have this issue on non-cm base roms.
[Verizon Samsung Galaxy S III] prototype7:
Looks like the number is screwed up, didn't notice that issue since I don't usually send MMS.
[Verizon Samsung Galaxy S III] SilentAce07:
Honestly, I'm thinking other people would have this issue too but it's not that often that you restart your phone without flashing something (which usually uses a cache/dalvik) wipe. And even if you do, you can skip the activation and nothing seems wrong with it until you do something like send mms (which I can confirm is related, I tested that yesterday).
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm sorry you're going through that, but I reboot every few days and send MMS' and don't ever get the activation screen. I've been running this ROM for months. I'm now on March 13 one.

I've also heard some people (very rarely) were only able to fix their issues by going back completely factory stock, accepting OTA's, and then rooting flashing CM. I'd consider that if NOTHING else fixes it.
[Verizon Samsung Galaxy S III] SilentAce07:
Thanks for the heads up.

---------- Post added at 06:34 PM ---------- Previous post was at 06:17 PM ----------

Just did that now to see. No activation screen but it did lose my number under phone status. So odd. Voice and data works. Edit: it lost my number on an old build too.

Alright sorry guys. No need to look into it further until I further nail down the problem. I'll try to odin back to proper stock rooted and back and see if it helps.
[Verizon Samsung Galaxy S III] Stupifier:
I have also noticed this once recently. I frequently check my wakelocks and saw RILJ eating away at my battery 11%/hr. I wiped cache/dalvik/fix permissions....issue seems to be gone.
[Verizon Samsung Galaxy S III] Hybridnoob:
Hopefully, you backed up your IMEI

http://xdaforums.com/showthread.php?p=30682712
[Verizon Samsung Galaxy S III] SilentAce07:
I have. Is it possible I lost that? Wouldnt my data/voice not work?
[Verizon Samsung Galaxy S III] Hybridnoob:
I'm not sure. Do you have an IMEI in your phone status?
[Verizon Samsung Galaxy S III] SilentAce07:
Yeah. Hmm.. Also, someone suggested in another thread using CWM instead of TWRP. Same issue.

May try to odin to a stock rooted image and then flash and see if that helps.
[Verizon Samsung Galaxy S III] cammykool:
found this in offical CM thread

and reverting to the 2/18 build seems to have fixed it. i think ill run this one for a while
[Verizon Samsung Galaxy S III] SilentAce07:
Yeah I left to paranoid android til they fix it. Others are coming forward too now with this problem.
[Verizon Samsung Galaxy S III] goldsmitht:
When you say MMS doesn't work, is it just hanging and not sending? Mastamoon had a fix in to increase the size (or something like that), but not sure if it is still in. Maybe that's it? Just guessing here, sorry
[Verizon Samsung Galaxy S III] RoboJoe:
Dammit

Hey, I flashed the latest version and by phone behaved very erratically, so I booted into Recovery (TWRP) and got stuck at the TWRP logo. My phone won't boot normally *OR* in bootloader mode.

At the TWRP logo, I can get into adb shell, but very few commands are available.

I looked on the internet, but the only guy who had the same problem had it magically go away.

Any advice?

Edit: To clarify, I get a vibration and the samsung screen, then nothing, when booting normally. Also, many times I can't get into recovery, even to the logo.
[Verizon Samsung Galaxy S III] Hybridnoob:
Which version of TWRP?
[Verizon Samsung Galaxy S III] RoboJoe:
2.4.4.0 (The latest one.)

I got into bootloader and attempted to reflash TWRP via Odin-- it's stuck on "NAND Write Start" for about 10 minutes.

I'm about to freak out. :-/
[Verizon Samsung Galaxy S III] mastamoon:
By bootloader mode do you mean recovery or download mode?
[Verizon Samsung Galaxy S III] RoboJoe:
sorry, by bootloader I mean download mode.

The general consensus on the forums for being stuck at the NAND Write is to flash a pit file, but for some reason that makes me very, very worried.

I haven't freaked out... yet.

Thanks guys.
[Verizon Samsung Galaxy S III] SilentAce07:
No. It doesnt work because your phone doesn't detect your sim until you toggle airplane mode and select ruin/sim.

Also just got this private message:
[Verizon Samsung Galaxy S III] mastamoon:
As long as you use the correct pit file with the correct Odin flushable rom you should be fine. It's dummy proof if you heed the warnings of any post about Odin.
[Verizon Samsung Galaxy S III] mastamoon:
Have had 4 SODs today. Was using my 3/13 build with a 3.4 kernel though. Annoying to say the least.
[Verizon Samsung Galaxy S III] RoboJoe:
It said there was no PIT, when attempting to flash a PIT. That means I'm done, yes?

Those failed Odin flashes bumped my flash counter up by two.. that means I'm really screwed, right?
[Verizon Samsung Galaxy S III] mastamoon:
Did you download and select a pit file in Odin?

Triangle away in the market can reset you flash counter if need be.
[Verizon Samsung Galaxy S III] Stealth111:
Had that problerm as well a few days ago. Was using Official Nightly with 3-10 build 3.4 kernel. It was blowing out my battery, phone was really struggling, even with basic audio. I decided to go away from kernel for the time being, and flashed the next nightly. I was greeted with the random phone locks while on a call, as well as random black screens of death. Was getting a bit worried about state of my phone, so I blew it back to 4.0.4 stock, did the phone number wipe, and let it OTA up to 4.1.2. Rooted, and unlocked bootloader so I am ready to go wherever I need next. Phone has been rock solid since! Whew! I was really thinking my phone was going downhill there for a minute. I will just wait and see when things seems to get back to the norm on the nightlies and then I will move back..
[Verizon Samsung Galaxy S III] dpaine88:
Anyone know why my cLock Lockscreen widget looks weird with the appointment showing minimized?
[Verizon Samsung Galaxy S III] prototype7:
Did you change the DPI? That can make it a little screwed up, I just use DashClock and don't have that issue.
[Verizon Samsung Galaxy S III] dpaine88:
Did not change DPI
[Verizon Samsung Galaxy S III] NegativeOne:
i'm on the 3.4 kernel and am having issues with push notifications from gchat and possibly google voice. I get no notifications until i turn my screen on if the phone is asleep. I have not flashed a new build of CM in a few days, but did update the kernel recently, so I'm guessing the kernel is doing something awful when phone goes to sleep.

Also battery life is still crappy. .5% batt gone per minute of screen time.That's worse than usual.
[Verizon Samsung Galaxy S III] goldsmitht:
Make sure you click on allow full widgets, or something like that on lock screen. Should fix that.

Menu - system - lock screen - maximize widgets
[Verizon Samsung Galaxy S III] mastamoon:
3/18 build is in OP

- added a new cherry pick http://review.cyanogenmod.org/#/c/33321/

- repo sync @ 3pm EST
[Verizon Samsung Galaxy S III] mastamoon:
Can somebody that's having the activation issue take a telephony-common.jar from a known working "non repeating activation" build and throw it on there install that's having the issue.

I know invisiblek did a test working around that change that was made to get gsm working, but I'd just like to see if this has any effect for ****s-n-giggles.
[Verizon Samsung Galaxy S III] ausman89:
You started to get my hopes up.... But that didn't work for me. :(

I've got a new phone sitting here to give someone and don't want to give it to them until I get theirs fixed. Mine is running the same ROM without any issues. (tried both your build and the latest official nightly)

Weird thing is that I can make the phone work fine by restoring from a previous build from my working phone, but as soon as I do a wipe of the data and cache it screws up again.

EDIT: Since I also have two phones sitting right here, 1 working and 1 not, let me know if anyone else wants to try something.
[Verizon Samsung Galaxy S III] mastamoon:
Dang! Thanks for trying. Was a shot in the dark. Wish we had a tighter time frame.
[Verizon Samsung Galaxy S III] ugachris:
I'm just curious, did the people having problems do an nvbackup? Here's what I'm referring to:

http://xdaforums.com/showthread.php?t=1852255
[Verizon Samsung Galaxy S III] SilentAce07:
Yeah, I tried nvrestore and it resulted in an unbootable device. Really thought it was bricked. Absolutely zero response except a quick vibrate. No screen. Luckily I was able to boot recovery and restore a backup. Without that, I don't know what I'd have done. Odin I guess.

Edit: and yes, I had used nvbackup before this issue came up.

I also flashed my imei backup with the synergy method. No luck.

There was a thread in the help section a few weeks ago where a few people were having this problem and it went unnoticed.

One of the guys concluded it was an corrupt nvram which was fixed only by a root66 Odin. But then the problem occurred again when he flashed another nightly so it may have been a false conclusion.

By the way, he also tried rvrestore and was given an unbootable device like myself.

If you need to find it, search for corrupt nvmram activation and it can be found. He did a good amount of testing too.
[Verizon Samsung Galaxy S III] WhammyDroid:
All,

Masta's 3/18 build does not play nice at all with KT's 3/14 kernel. I could not get the device to boot.

Edit: Both 3/5 and 3/14 kernel builds by ktoonsez do not allow the ROM to boot. Only stock 3.4 kernel will boot.
[Verizon Samsung Galaxy S III] mastamoon:
Looking like any 3.4 kernel based rom might not be playing nice with 3.0 kernels. Will have to wait for the kernel devs to go 3.4 or find out why they won't boot.
[Verizon Samsung Galaxy S III] WhammyDroid:
Yep, just makin' people aware.