yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] yznhmr:
Does BT work in the Jan 16th build?(never mind found the answer for this one)

and How can I fix sending pictures in text messaging? It just sits on sending for ever.

Im on 1/10 unofficial
[Verizon Samsung Galaxy S III] senorbuck:
Ya, I know that's usually the case but this was hours after the flash. I'll try reflashing w/ a full wipe. Always fun :)

Thanks!
[Verizon Samsung Galaxy S III] Rudy_Ruettiger:
BT works perfectly and I sent 2 pictures via text with no issue.
[Verizon Samsung Galaxy S III] bobby janow:
I flashed last night and was on wifi the whole time, no drops. Been in and out of signal all morning haven't lost data either. Batt did take some time to charge but the drain is minimal today. A2dp up next! Nice work guys.
[Verizon Samsung Galaxy S III] PerCompLLC:
You may need to clear data on the MMS app. I haven't had any issues sending text pictures ever since being on CM10.1 (starting back when CM10 first went to nightlies). I am currently on Mastamoon's 1/16 unofficial.
[Verizon Samsung Galaxy S III] minnysota:
Has anyone landed on the activation screen after a reboot?

Everything is working (data, SMS, calls), but after a reboot it just hangs on the activation screen and says "Waiting for network..." and "Activation can take a few minutes."

Any idea why that would be happening?
[Verizon Samsung Galaxy S III] MWFD:
Do you mean using the 1/16 reverts build or the first 1/16 build (without reverts)? BT music has been working on reverts since 1/10 I believe (or whenever Masta started doing the reverts) but curious to see if its working on the non-revert build. Thanks
[Verizon Samsung Galaxy S III] mpetruzz:
First off sick ass build!!! I've tried all of the other 4.2 ROMs and this is the only one working 100% for me!!

My question is on the lock screen. I use go SMS vs the stock app. Is there any way to have go SMS to be a selectable app widget on the lock screen?? The stock app is an option but not go SMS.

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] PerCompLLC:
I "think" that mastamoon only posted one 1/16 unofficial... At least I only saw one.
[Verizon Samsung Galaxy S III] yznhmr:
Ill try that, do i need to back up sms first?
[Verizon Samsung Galaxy S III] termleech:
Gosms will need to make they app compatible with the lock screen widgets to make it show up. Same is true for all apps.
[Verizon Samsung Galaxy S III] anacree:
I'm on the 03/07 unofficial build from this thread, and haven't had activiation issues. I'm scared to change anything now, as I don't want to screw up my phone. But I do still get SOD issues that force me to do a battery pull, and I get the long press home button issue. I'd like to upgrade as it sounds like these issues are more stable on a newer ROM, but I don't want to make more annoying issues either. =P *sigh* I guess I'll just stick with what I have until this gets straightened out.

On a side note, I've only tried CM 10.1 for a custom ROM (official and masta's). Anyone have a different type of custom ROM they'd recommend?

Edit: The main reason I started using Masta's unofficial was because of the bluetooth fixes.
[Verizon Samsung Galaxy S III] mastamoon:
Ive been updating nightly without issue.. just cant wipe data I believe.
[Verizon Samsung Galaxy S III] ausman89:
I did go back and try the official CM 3-1 and 3-6 builds and both still failed.

I am still running on the second unofficial test ROM from today without issues though.

Since using odin to get back to stock 4.0.4 and start over, I have left the radio untouched and am currently running VRLG1. I was on VRBMB1 when I first started having issues though.

From my understanding and experience in test flashing about 100 different ROMs now....Once you update to a non-working ROM, you can operate just fine, until you wipe data. At that point, the only way to fix it is to nandroid to a version before 2-28, or Odin back to complete factory 4.0.4 and start over.
[Verizon Samsung Galaxy S III] mastamoon:
Man that is weird!
[Verizon Samsung Galaxy S III] PerCompLLC:
Hey Masta... Any chance that this commit will solve some of the kernel problems? http://review.cyanogenmod.org/#/c/34082/
[Verizon Samsung Galaxy S III] Obaterista93:
All I know is that it is definitely a problem with CM code, and has nothing to do with the modem or anything on our end. Flashing AOSP based ROMs (like AOSPA) are fine without the activation bug, but anything based off of CM code has it.
[Verizon Samsung Galaxy S III] anacree:
So by "don't wipe data" I take that to mean doing "dirty flashes" or factory reset? Only wiping cache and system?

I've been doing clean flashes (cache, system, and factory reset) because a while back on a dirty flash I had my phone not let me add a google account.
[Verizon Samsung Galaxy S III] goldsmitht:
have you tried dirty flashing anything new over the one that works now? I've been dirty flashing since don't know when and haven't had that issue. HOWEVER, i did get it when i tried to install SOA clean, so that might be something to try. 3/13 works great for me and can use KT747 with it.

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
No idea.. jibbrish to me :eek: But Im guessing anything committed to the new kernel is going in the right direction. Hopefully.

I don't clear anything on a day to day basis.. flash and reboot. If something acts funny, I do a cache wipe.. if it persists I do a clean/factory reset install.
[Verizon Samsung Galaxy S III] ctsail410:
So I've been having much better luck with the four kernel commits merged yesterday. Vastly improved battery life. No battery pulls or reboots. Most of the lag seems to be gone. Looks to be heading in the right direction.
[Verizon Samsung Galaxy S III] mastamoon:
Funny, I had crazy battery life yesterday.. 1hr screen on time.. was sitting at 82% battery remaining. But today I had 2 hard reboots and 1 SOD. I am on a 3/18 build however. Glad to hear its looking better though.
[Verizon Samsung Galaxy S III] mastamoon:
3/20 afternoonly build in OP.

- added revert of the longpress issue bug fix which may fix activation issues that some are having. I know this may disappoint some, but trying to help the community here by testing stuff out. And actually, it was reported before 3.4 kernel was released that it cured the long press issue.. so maybe the fix is unneeded anyway. Let me know what you find!

- repo sync at 3:30pm EST
[Verizon Samsung Galaxy S III] Chris123NT:
Is there going to be an unofficial repo sync today? I know there were a few test builds for the activation issue.

Edit: LOL Masta you posted the exact same time i posted this question. Thanks!
[Verizon Samsung Galaxy S III] Stealth111:
I want to throw out my 2 cents...

I have up/down/clean flashed damn near every version out since CM10 without many unknown issues.. Well guess what.......drum roll please.... I am now in the same damn boat as others today.....GRRRRR. I did an Odin back to stock 4.0.4 last week when I was experiencing issues on the test 3.4 kernel, I let it OTA to MB1, and all was well for days, I rooted, put in CWM 6.0.3.0 and proceeded to download the latest nightly CM10.1. So I decide to brave the random lockups/battery pull issues and come back to the new 3.4 kernel builds for the hell of it, and I now have the same damn thing happening to me..

PLEASE READ THE FOLLOWING:

I want to share this info, as maybe it is nothing/maybe something. After reboot I have the same NV issue.

OK, however I am noticing something that I DID NOT see, EVER, when my phone was working fine. Upon reboot, as soon as the lockscreen comes up, at the bottom, it now says "NO SIM CARD, SEARCHING FOR SERVICE". It stays on that for a while and the screen eventually turns off like normal. it eventually changes to "Verizon Wireless". Now I go into settings and it is at NV mode like the others. I change it, airplane it, and all is well till next reboot.

Tell me if I am crazy, but is there a chance that upon bootup (due to some code change), that it is not seeing the SIM card in a timely manner, and it is defaulting the setting to NV mode because of that?

OR, is it now giving the NO SIM CARD error, because the setting went back to NV on the reboot, and now it is not looking for the SIM card in the same manner?.

Hopefully this is something to look at, I will say again, I have not seen that NO SIM CARD message since way back when CM10.1 was in its very early builds with data /phone number issues. When it all got ironed out, I never saw that message again until NOW...
[Verizon Samsung Galaxy S III] ctsail410:
I was running a 3/18 sync'd build yesterday and it was awful. Went back to 3/15.

I'm having good luck with a 3/20 sync'd build.
[Verizon Samsung Galaxy S III] ausman89:
I installed this and wiped. First reboot caused the issue, but I changed back to RUIM/SIM, in and out of airplane mode, restarted, and....4 reboots later I am still issue free.

Don't know how long this will last, if it is a fluke, or if it is a good sign. At this point I'm so confused I don't know what to think.

**UPDATE: Ran the update on a second phone and have a bit more to report. Started out with multiple reboots giving the error. Realized I had wifi off, but had wifi on with the first phone I updated. So, I went through the changing back to RUIM/SIM, in and out of airplane mode, but then I started Wifi back up, restarted, and haven't had the issue again through several reboots, and tested with both wifi on and off again. This thing is getting so crazy as to why/when the issue appears, I don't know if any of my previous theories are correct.
[Verizon Samsung Galaxy S III] goldsmitht:
Another fix for the activation bug: once you get everything fixed, set up etc, then reboot into recovery, wipe cache and dalvic then DIRTY flash whatever ROM you're having problems with. Walla, fixed it for me through three reboots so far.

:thumbup:

:confused:
[Verizon Samsung Galaxy S III] Chris123NT:
Wow, that's weird, but interesting at the same time. If turning on Wifi fixes it somehow I guess that's an "easy" way to get around it for now.

@goldsmitht, so you mean flash rom with problem, get it fixed up, reboot into recovery and wipe cache/dalvik and dirty flash the same ROM?
[Verizon Samsung Galaxy S III] goldsmitht:
That's what I did, and has gone thru three reboots with no issues. Don't ask why, but think it has to do with deleting data, as reported earlier by someone. Gonna do a nandroid backup and flash around some other ROMs and come back to test tonight to see if it holds, but working so far
[Verizon Samsung Galaxy S III] Hybridnoob:
Everything working fine here, so far. Dirty flashed over Masta's 3/13 build. Only strange thing I've noticed thus far is the CRT animation is no longer present when the screen turns off. Weird. Anyone else notice that?
[Verizon Samsung Galaxy S III] mastamoon:
Mine still has crt off on 3/20
[Verizon Samsung Galaxy S III] Chris123NT:
Mine has CRT off as well but the effect is faster than it was in previous builds.
[Verizon Samsung Galaxy S III] SilentAce07:
Thanks everyone for looking for fixes for the activation bug. Like I said earlier, I've been very busy and without the ability to flash but very pleased that it is getting the attention it needs to fix it.
[Verizon Samsung Galaxy S III] PerCompLLC:
Kernel seems to be MUCH better!

Edit: maybe I spoke too soon...
[Verizon Samsung Galaxy S III] MWFD:
Anybody know how to get (or can provide an apk) for the Google gallery with picasa sync?
[Verizon Samsung Galaxy S III] masterxchief:
Dang my phone was giving me issues all morning with battery and bad lagginess. I rebooted it a few times, now it just sits at the cyanogenmod boot logo and never boots up. I guess its time for a reset
[Verizon Samsung Galaxy S III] Chris123NT:
Noticing big performance increases with 3/20. 3/18 had issues with the sound skipping in pandora, that seems to be resolved in 3/20 which is awesome.

Hopefully the revert doesn't cause the long press issue to come back, although I do remember invisiblek saying something about that being fixed in the 3.4 kernel.
[Verizon Samsung Galaxy S III] johnwaco:
Don't know why but my activation bug has disappeared. I clean flashed 3/18 and dirty flashed 3/20, both masta builds. Not sure where it disappeared in that process but I can reboot now and not get activation screen.
[Verizon Samsung Galaxy S III] goldsmitht:
It was the dirty flash; I had bug with another cm based ROM, went thru steps to get number back, set all up, then dirty flashed same ROM over that set up, and bug was gone

Don't know why, probably has to do with erasing data

:confused:
[Verizon Samsung Galaxy S III] Stealth111:
I would like to report as of yesterday on a clean install of Official 3/20 nightly I was stuck in the NV reboot bug mode. This morning I simply allowed the built in CM Updater to update me to the Official 3/21 Nightly, and when my phone booted up, I was no longer in NV mode. Probably a result of the dirty flash by the Updater. I also did NOT have wireless on at any point.
[Verizon Samsung Galaxy S III] mastamoon:
Where is that bang head Smiley??? :mad:
[Verizon Samsung Galaxy S III] Chris123NT:
Well I guess we at least have a way of fixing it. Not an ideal way but it works. Dirty flashing over a clean install seems to fix it, which makes no sense at all lol.

---------- Post added at 08:58 AM ---------- Previous post was at 08:49 AM ----------

BTW FYI to everyone, Imoseyon has test builds of leankernel based on the 3.4 kernel:

http://imoseyon.host4droid.com/s3/aosp/test_builds/#!/view=details/lang=en/sort=na

Looks for the 5.0RC builds at the bottom.
[Verizon Samsung Galaxy S III] mastamoon:
Has anybody clean flashed my 3/20 unofficial straight up?

Need to know before my afternoonly today so I can pull that GTOD revert out if its not helping.

If this activation thing is repeatable.. maybe somebody should logcat the whole process of first boot after clean install.
[Verizon Samsung Galaxy S III] goldsmitht:
i'm a complete noob at adb, is there an app to pull the log cat if i try? I've got enough nandroids to fix anaything i break, so if someone can give me an easy way to get a logcat, i can post it.
[Verizon Samsung Galaxy S III] mastamoon:
Had a hard reboot this morning.. was trying to see if the longpress issue was going to come back with that GTOD revert. Ah well.
[Verizon Samsung Galaxy S III] goldsmitht:
also, is there a strictly AOSP based rom out there? We know it is a CM bug so far, but if there is an AOSP rom i can test, would like to see if it follows all roms or is just something CM related.

:confused:

:cyclops:
[Verizon Samsung Galaxy S III] Chris123NT:
I was trying to see the same and my phone froze on me this morning and I had to do a battery pull. The long press issue had not come back yet but the phone was also up for less than 12 hours at that point.
[Verizon Samsung Galaxy S III] V3TTOO:
Just got my phone back from repair and back to latest OTA stock. Just finished root/bootload/IMEI/CWM. Downloaded your ROM and GAPPS. Gonna do wipe and install. Also did format of /system and /sdcard. Starting baby fresh.

9:08am - Just finished installing, I got 4g and able to get updates. So far so good.

Anything I should be looking for?
[Verizon Samsung Galaxy S III] mastamoon:
The only issue I can see trying to do this is ADB secure might get in the way with a clean install. Nowadays you have to allow access, but maybe it will work.

I would do this:

boot phone into recovery

plug phone into PC

open cmd window (or terminal in linux)

type

adb logcat > logcat_firstboot.txt

install rom clean

reboot phone

At that point adb will be waiting for your phone and pc to start communicating. Hopefully you will be able to get to the activation screen issue and do what you do to bypass it.

At this point, you can close the command window to kill the logcat process. What I would then do is shut your phone off. Pull up another command window/terminal and do

adb logcat > logcat_secondboot.txt

and power your phone on. Hopefully you get the same activation issue.

IDK, I'm just hoping to see an error there that says activation couldn't happen because <?>... I guess it doesn't need to be at first boot after clean install... Just need a logcat of the process trying to happen and failing.

I'm probably overly complicating it lol
[Verizon Samsung Galaxy S III] mastamoon:
Yeah, I think Paranoid Android at this point is AOSP based, not CM based. From what others have said here, its not happening on AOSP based roms.

I was at about 18 hrs I think, but have gone as long as 50hrs before getting the issue, so may or may not have been close.

So that was a totally fresh install and no activation issue?
[Verizon Samsung Galaxy S III] ausman89:
You need to reboot. The activation issue never shows up on the first boot. It is always on the 2nd, 3rd, etc. reboot.
[Verizon Samsung Galaxy S III] V3TTOO:
Correct. Weird, but some off the apps I had installed were still there, like SwiftKey, Pandora, and SuperSU. Your ROM doesn't install its own SU does it? Anyways, I thought formatting the /system and /sdcard would delete all apps and do a clean install.

I am going to reboot in recovery and make a backup right now.
[Verizon Samsung Galaxy S III] goldsmitht:
Nope, will see what i can do. DO i need drivers installed to do this? reason i ask, is at work, and GOV will NOT let me add that kind of stuff to my work computer.

but will see what happens

edit: Nope, no go at this station: sorry, can't even find the cmd window on this system, probably due to it being govt controlled. sorry.

---------- Post added at 12:29 PM ---------- Previous post was at 12:19 PM ----------

its the first reboot when the bug starts up; if it happens, just go back into recovery, and dirty flash this rom again (just wipe cache and dalvik) and the bug should go away when you start back up again.
[Verizon Samsung Galaxy S III] mastamoon:
https://play.google.com/store/apps/...syslog&feature=nav_result#?t=W251bGwsMSwyLDNd This app can grab logcat easy.. But I guess all we really have to do is get a phone thats having the activation issue then use this app to capture the log of the phone trying to activate.
[Verizon Samsung Galaxy S III] V3TTOO:
Well, I just rebooted and I did not have an issue. Have you all tried formatting all your /data and /system folders? When you do wipe data and cache, it doesn't wipe it all. It keeps the apps and stuff. I would recommend going into recovery and formatting all partitions then doing a clean install. DO IT AT YOUR OWN RISK.
[Verizon Samsung Galaxy S III] mastamoon:
I don't get how you did a clean install and had apps remain.. :confused: :cyclops:
[Verizon Samsung Galaxy S III] goldsmitht:
did you do a clean install from 3/20 and then do a reboot? OR was there a dirty flash somewhere in between?
[Verizon Samsung Galaxy S III] masri1987:
Should I flash yesterday builds or wait for today?
[Verizon Samsung Galaxy S III] V3TTOO:
I had the phone for a day and I used some basic staple apps that I like to use. I did the wipe Data/Cache from recovery, then I did format of /system. I didn't format /data, so I am assuming the wipe didn't wipe all apps. I really don't know, but I assume wiping data doesn't mean the same as formatting.

And yes, I did a clean install from Stock 4.1.2 build, with the new MB1 radio. Just did a reboot right now, since before what I did was a backup using ROM Manager, so not sure if that makes a difference. Still working.

Edit:

I found a new root method for 4.1.2 stock, and it might be using a new bootloader, since there was this whole thing about the bootchain. Might want to check that out. The new method was added to the CM10.1 Official forum, I asked the OP to update it.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah, believe you have to do a factory reset and/or data wipe to be totally clean. When I want to do a totally fresh install, I factory reset then format system, then install. But from what others are experiencing, doing a cache wipe is enough to cause the issue so dunno lol.
[Verizon Samsung Galaxy S III] mastamoon:
Ill have a build out around 330pm EST as usual. I guess for the time being, ill keep reverting the longpress issue fix since we dont know if its actually an issue still and may or may not be causing the activation issue. Havent been able to keep my phone up long enough to see if the longpress issue comes back.
[Verizon Samsung Galaxy S III] V3TTOO:
Do build change the bootchain? Just wondering since I was using this root method: http://xdaforums.com/showthread.php?t=2046439
[Verizon Samsung Galaxy S III] razorloves:
I already posted logs showing all this for invisiblek a few days ago in the official cm thread. Feel free to grab them. Hopefully someone can figure it out soon. Sorry no link. Mobile right now.

Edit: http://xdaforums.com/showpost.php?p=39299801&postcount=1139
[Verizon Samsung Galaxy S III] mastamoon:
ORLY.. musta missed. Ill take a look. Thanks
[Verizon Samsung Galaxy S III] mastamoon:
Well I looked at it alright.. :eek:
[Verizon Samsung Galaxy S III] Chris123NT:
LOL, I by no means am good at reading log cats, but there does seem to be some stuff in there referencing RUIM not loading due to not being provisioned. Maybe that has something to do with the problem, which would be consistent with whoever said the phone would display NO SIM for a few seconds when the issue would occur.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah lots of that going on. Eventually clears up, so it seems like there is a conflict, maybe all timing of what is happening before something else. Eventually the hardware or software catches up and its ok.

But why does dirty flashing the same rom over a malfunctioning install clear it up? Maybe some permission issues going on also? Maybe the B1 modem isnt passing the info in the same timeline? But older modems dont seem to clean up the issue either.
[Verizon Samsung Galaxy S III] goldsmitht:
I don't think its' the dirty flashing that is fixing the problem, it is the deleting the data and starting over clean that seems to be where the hang up starts.

if you flash clean, meaning wiping cache, dalvik, and then Factory Reset, it wipes something that sets whether the phone is using CDMA / RUIM or NV. THEN when you clean everything up (i didn't try to just dirty flash over a malfunctioning setup - cleaned it up and THEN dirty flashed) there is a step within Factory Reset that is skipped, and thus the phone is now "fixed".

i'm not the smart people here, but that is my take on it.

:eek:

:confused:
[Verizon Samsung Galaxy S III] landale:
Hey guys just want to say that I finally made it over to London to begin my Europe vacation today and I picked up an O2 sim card. Everything works including 3G which didn't work for ATT and T-Mobile. I am on the March 12 build fwiw. So glad I didn't have to use my god awful unlocked Droid Incredible 2 for this trip. GSM roaming my not be perfect as you still have to toggle airplane mode to make it work but at least its an option for us using CM10.1
[Verizon Samsung Galaxy S III] mastamoon:
I must have missed something then. I was taking it as, you do a clean install, phone wont activate.. you go back into recovery and flash over the non activated install, now it activates. Too much head hurting here for me and way above my skill level as far as "dev"ing goes lol.
[Verizon Samsung Galaxy S III] mastamoon:
3/21 build in OP.

- added MMS Recipient Checkbox/List cherrypick

- RepoSync @ 3:00PM EST
[Verizon Samsung Galaxy S III] tcsac:
Apologies as I know it's on this forum somewhere, but I can't find it. There was a setting of some sort, I seem to recall it being a transition effect, that would cause the phone to freeze on the lock screen. I can't find the setting, but I am getting a freeze at the lock screen after a clean install of this build.

Ring a bell for anyone? (Just loaded the 3/21 build, clean install).