yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] RaiderX29:
7/12 nightly broke SMS for me. I was able to send SMS, but the status was stuck as "sending". The recipient would actually receive the message, but I would eventually receive a failed notification on my end.

I reverted to 7/11 nightly and all is well again. Anyone else notice this?
[Verizon Samsung Galaxy S III] buschbarber:
I just flashed 07/12, this morning. I just replied to an SMS without a problem. With the Gmail app, I have experienced times where I would Reply To or Send a message, and sometimes, it would remain in the Sending status until I deleted it and resent it. This has been going on for years, with various phones, but not often.
[Verizon Samsung Galaxy S III] Obaterista93:
I'm experiencing the exact same thing. I was actually coming to post about it til I saw your post. I'm not even sure how to get a logcat of something like that because it isn't technically failing, just displaying as failing.
[Verizon Samsung Galaxy S III] Amphibliam:
On 10.1.1, I've had random rebooting issues and lockups using the stock kernel. Battery life has been pretty terrible too.
[Verizon Samsung Galaxy S III] apacseven:
Just make a logcat of sending a message and submit that. Whatever is happening is happening and the logcat will reflect that.
[Verizon Samsung Galaxy S III] ddggttff3:
http://xdaforums.com/showthread.php?t=1788313

You need to update to FM1.
[Verizon Samsung Galaxy S III] airmaxx23:
I'm on the newest (MF1) firmware but my phone does not like the stock kernel. I can only go about 30 seconds to a minute after a reboot before my phone locks up. Once I switch to KT747 kernel everything is fine.
[Verizon Samsung Galaxy S III] ddggttff3:
try to get a kernel log for the devs. Have you tried wiping cache/dalvik cache?
[Verizon Samsung Galaxy S III] Obaterista93:
Looks like they already caught it in CM code review. :thumbup:
[Verizon Samsung Galaxy S III] airmaxx23:
Even on a fresh, clean install I get the lock ups, it's been happening with the stock kernel for a long time. How do I get a kernel log?
[Verizon Samsung Galaxy S III] zachf714:
A last_kmsg ....
[Verizon Samsung Galaxy S III] airmaxx23:
Duh, I forgot about that, thanks.
[Verizon Samsung Galaxy S III] Amphibliam:
Already tried that.
[Verizon Samsung Galaxy S III] zachf714:
Yup :D
[Verizon Samsung Galaxy S III] Gibscreen:
I'm on the 7-12 nighly and mf1 modem. When I send texts they go through to the recipient, but on my phone it's still shown as sending and then it times out saying the message wasn't sent. Tried reverting back to mb1 modem since my wife's non-rooted phone had a similar issue with the md3 modem. But that didn't help.

Ideas?
[Verizon Samsung Galaxy S III] Chris123NT:
Its a bug, should be fixed in the next nightly.
[Verizon Samsung Galaxy S III] buschbarber:
I am not seeing that bug. I am using the apps Verizon Messaging and Extra.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah that doesn't matter since the bug is in the telephony framework of the 7/12 nightly, a commit is already merged to fix it for the 7/13 build.
[Verizon Samsung Galaxy S III] syde1020:
Anyone having trouble with the left speaker when using ear buds?? Only during music apps not during calls
[Verizon Samsung Galaxy S III] Restola:
Fixed already in recent nightlies and newest stable.
[Verizon Samsung Galaxy S III] syde1020:
Using latest stable. I'll try the newest nightly
[Verizon Samsung Galaxy S III] Restola:
Thanks please let me know. I tried on the nightlies and it worked, was told the latest stable fixed it but maybe not.
[Verizon Samsung Galaxy S III] Chris123NT:
FYI Guys the newest signal test build (#5) also has the SMS fix merged, so it won't get stuck on sending. Still has the 0 DB / 99 ASU bug though.
[Verizon Samsung Galaxy S III] Gibscreen:
Fixed. Nice!
[Verizon Samsung Galaxy S III] ddrum2000:
Can someone confirm or deny the ability of the VZW sgs3 to use international sim cards with cm10.1. Last time I tried it a few months ago, I could not find a way to change apns or select a specific mobile network.
[Verizon Samsung Galaxy S III] tehloxely:
Did the latest nightly fix it?
[Verizon Samsung Galaxy S III] landale:
Is there anyone else that really hates this new merge?

http://review.cyanogenmod.org/#/c/45434/

I am not sure what the purpose of this is but to me they should have made it an option, not standard. I have quite a few apps that I can perform actions using expanded jelly bean notifications and then dismiss them all in one step. Now with this merge I still have swipe up to close the notification bar as an added step. Really annoying if you ask me.
[Verizon Samsung Galaxy S III] Chris123NT:
Indeed, I don't get why they say it didn't work as advertised. It always worked exactly the way I felt it should on my phone.
[Verizon Samsung Galaxy S III] landale:
Glad I am not the only one. I think the intent of this commit was to revert the recent merge which auto-closed the notification tray when the last non-persistent notification was dismissed as on AOSP the tray would stay open if there was still a persistent notification. This new commit goes beyond that and keeps it open even if there are no other notifications at all unless the notification is swiped away not if dismissed using an expanded action. I emailed the person that submit this commit and hopefully they will take a look but I am sure it couldn't hurt if others mentioned the problems with this commit.
[Verizon Samsung Galaxy S III] WhammyDroid:
Here's an idea if you do not like it. Submit a JIRA enhancement stating your request or develop the solution yourself.

One person's annoyance is another person's feature request. I am actually glad they did this and reverted the change.
[Verizon Samsung Galaxy S III] landale:
Wasn't trying to offend anyone so not sure why you need to take such a tone, was just asking a question about a commit that didn't seem to work as intended. I did contact the dev about this commit and he is looking into fixing it. This commit was only supposed to to prevent auto-close when an app self-dismissed its own notification, not when a user does it using a means other then swiping it away. The problem with it now is that if one dismisses the last notification (when there are no persistent ones) using an actionable expanded jelly bean notification button the notification tray stays open even though there is nothing in it. My point was simply that I can't see the use of having a completely empty notification tray to stay open when the user dismisses their last notification but does so using an actionable button and not swiping it away.
[Verizon Samsung Galaxy S III] aromig:
I did exactly that with no issues. Lovin' TWRP btw.

Sent via XDA Premium using my GS3 running PAC-Man Nightlies with BetterBean Blue blackout theme
[Verizon Samsung Galaxy S III] mattoaida:
Does stock kernel have both CPU cores online
[Verizon Samsung Galaxy S III] Badouken:
Anyone know what the experimental build does? It says signal strength test 5 in the name! Does that mean it has better signal? but its experimental so its probably not stable and usable everyday?
[Verizon Samsung Galaxy S III] mastamoon:
They were test builds. Ignore them, they didn't help anything.
[Verizon Samsung Galaxy S III] Chris123NT:
They were testing various iterations of a commit that was merged into the 7/14 nightly. So if you flash 7/14 you'll have the commit those tests builds were toying with, although it doesn't really do anything to help the 0dbm/99asu issue.
[Verizon Samsung Galaxy S III] Restola:
I am temporarily back on TW as my first child will be born in the next 2 weeks and I need the camcorder volume (i know it pretty much works, I've lived with it on vacation and stuff...but this is kind of important :) )

So please PM me bugs from the latest nightlies so I can keep the OP updated (reproducible and found on the stock kernel). I wont be able to find them myself until I stop needing to take baby videos, I decide my baby isn't cute enough to be recorded, or the recording volume can be increased.
[Verizon Samsung Galaxy S III] Hybridnoob:
Congrats!!
[Verizon Samsung Galaxy S III] rockets95:
Wifi issues with MF1 modem

Has anyone else had issues with wifi randomly disconnecting when you wake the device ever since switching over to the MF1 modem?

I recently moved to that modem along with the latest CM nightlies, now I'm seeing that sometimes when I wake my device it's disconnected from my home wifi. I have to either turn wifi off/on or manually select it to reestablish a connection. In my wifi settings I have the sleep policy set to "Always On" and I don't have "Avoid Poor Connections" checked.

I've used a Wifi Analyzer app to make sure I'm on a channel without much contention.

I never had any issues like this previously when I was running the MB1 modem on older CM levels. RC5 seemed to be the most solid level for me, previously. I'm running the 0713 nightly, but I haven't seen any change in this issue going from the 0709 nightly to the 0713.
[Verizon Samsung Galaxy S III] airmaxx23:
I have not had any issues with wifi disconnecting after updating to the MF1 firmware.
[Verizon Samsung Galaxy S III] buschbarber:
I have not had that issue either.
[Verizon Samsung Galaxy S III] sanjsrik:
Running 715 Nightly, I'm getting random screen flicker. I flashed over the previous nightly.

Anyone else getting this?

Also, anyone know why I can't do a search on the forum to find if this has been posted before?
[Verizon Samsung Galaxy S III] Stealth111:
OK, I am REALLY starting to get excited here! In regards to the 0dBm/99asu issue I stumbled upon this GREAT read!, and if you look at the bottom, it says they FIXED it!

Ticket:

https://jira.cyanogenmod.org/browse/CYAN-1209

Code for fix:

http://review.cyanogenmod.org/#/c/45653/

Shareef Ali added a comment - 16/Jul/13 8:22 PM

confirmed fixed

WOOHOO! I hope they got it nailed down.

That's COMMITMENT!!

THX CM TEAM for not giving up...
[Verizon Samsung Galaxy S III] :
Thats one issue I have never had with any nightly.

I'm just sticking with 10.1.2, its been running great
[Verizon Samsung Galaxy S III] noobnl:
I am Shareef Ali

here is a build

http://jenkins.cyanogenmod.com/job/...-EXPERIMENTAL-d2vzw-SIGNALSTRENGTHTESTNEW.zip
[Verizon Samsung Galaxy S III] MG386:
works good here! Woot Woot :D
[Verizon Samsung Galaxy S III] mastamoon:
Thanks for working on this again noobnl.
[Verizon Samsung Galaxy S III] jamesd1085:
Great work!

Battery stats now shows 0 time without signal! Killed yet another battery drain.
[Verizon Samsung Galaxy S III] mcdevil58:
I updated to the newest test builds and I noticed my signal bars just stay gray all the time, has anyone else noticed this?
[Verizon Samsung Galaxy S III] airmaxx23:
Not at all.
[Verizon Samsung Galaxy S III] bmeek:
Did this make it into the 7/17 nightly?
[Verizon Samsung Galaxy S III] Chris123NT:
No, the commit is not merged yet, so if you want to test, download the signalstrengthtestnew2 build.
[Verizon Samsung Galaxy S III] airmaxx23:
Here is a direct link to the download for those who need it.

http://get.cm/get/jenkins/34880/cm-10.1-20130717-EXPERIMENTAL-d2vzw-SIGNALSTRENGTHTESTNEW2.zip
[Verizon Samsung Galaxy S III] mcdevil58:
Okay, I'll try to reflash and see if that helps
[Verizon Samsung Galaxy S III] ayush20m:
Unable to install some market apps

I had this issue when I first installed CM 10.1 (don't remember which build). Again I don't remember which app it was but it would get stuck at 8.00KB. It wasn't a very useful app so I didn't bother and forgot about that issue and it didn't happen after that.

Today while trying to install Helium, I again have that issue. I am currently running 6/29 nighty. It gets stuck at 8.00KB and if it let it be for like 10 mins it'll go to 40% and that is it. I am able to download/update other apps from the market without issue. I was also able to install Helium on S2 running latest CM 10.1.

Has anyone else encountered this issue? I am going to update my S3 CM too and will update this but I am curious about this strange issue.

Update: Even on CM10.1.2 I have the same issue with this app.
[Verizon Samsung Galaxy S III] ecooce:
Ok, I know im not crazy, I have modded every keylayout file that had "Home Wake" and my phone still wakes when hitting the home button. I just updated to the latest nightly from a nightly about 2 months back, 5/16 or 5/17... Any ideas?

Sup noobnl...

Follow me on...

Youtube http://bit.ly/To93d6

Google+ http://bit.ly/RqyYPa

Facebook http://on.fb.me/RFIADb

Twitter [MENTION=2601927]jason_[/MENTION]Feriani http://bit.ly/Qa3Yyu
[Verizon Samsung Galaxy S III] slambert27:
Low Recording Volume / Response to Knuckleheads

Sorry to bring back a somewhat older post but...Let me preface this by saying I wholeheartedly agree with your responses to these two. This ROM has been "Stable" for quite some time now and the above statement from sbenson1226 is the "farthest" thing from the truth. :highfive:

With that being said, I was hoping someone of your caliber could speak to what the odds of the recording volume ever being up to that of the stock TW camcorder? Notice I have not termed this a bug... but a deficiency if you will.

I would certainly be willing to provide whatever help I can to aid in troubleshooting the issue although I am sure people much more seasoned than I have already done their best. Please let me know what your thoughts are on this issue.

Respectfully,

SLambert
[Verizon Samsung Galaxy S III] dincfool:
Just flashed a build Nightly from a couple days ago. I've ran cm and aokp, any other options that this rom has that I should know about? And where do you get new themes?

Also how do you change the degrees to Fahrenheit?
[Verizon Samsung Galaxy S III] Whisk_33:
These are not developer questions. They do not belong in this forum. These questions should be in the cm Q&A thread. Link is in the op.

You can down load themes from the play store. You can get an app like theme chooser. You can change degrees to imperial/metric in the options of the settings. Try not to be so lazy and perform a little search.
[Verizon Samsung Galaxy S III] airmaxx23:
There is an option to turn it off in: system settings> display> home button.
[Verizon Samsung Galaxy S III] avettraino:
Signal Strength Cnanges

Did the signal strength changes make it into the build for 7/18?
[Verizon Samsung Galaxy S III] Chris123NT:
Nope.
[Verizon Samsung Galaxy S III] dTardis:
Bluetooth Phone Ring problem

I did search this thread, but I was unable to find a solution.

When my bluetooth is on my phone wont ring through the speaker. Is there a solution for this? I have not been able to find it in the settings, but I might have missed it.
[Verizon Samsung Galaxy S III] mastamoon:
Is the camera working ok on last nights build?
[Verizon Samsung Galaxy S III] ecooce:
WOW, love how things get added and I never notice it :)

Follow me on...

Youtube http://bit.ly/To93d6

Google+ http://bit.ly/RqyYPa

Facebook http://on.fb.me/RFIADb

Twitter [MENTION=2601927]jason_[/MENTION]Feriani http://bit.ly/Qa3Yyu
[Verizon Samsung Galaxy S III] airmaxx23:
I installed it to check for you and the camera is working fine. I'm headed back to the experimental signal strength build 2 until the fix gets merged into the nightlies.
[Verizon Samsung Galaxy S III] brockkk:
sorry to post this here but hopefully someone can help me. installed newest nightly this morning before i flew across country on vaca. put my phone on airplane mode and when i took it off i was roaming. wifes iphone is on 3g not roaming, father in laws 4s is on 4g no roaming. network type is lte/cdma/evdo, system select is auto, rium/sim is selected. and it roams. if i change the system select to home only then i get 4g data but i am unable to make or recieve phone calls. any ideas? i even tried rolling back to a earlier build no dice. imei and meid still in tact also.
[Verizon Samsung Galaxy S III] bmeek:
I've noticed this too, but haven't really hunted for a way to get the phone to ring out loud when my (a2dp-capable) Bluetooth headset is connected.

I'm suspecting the only way at present might be to deselect the media audio from the Bluetooth device (a bummer of a workaround for this issue).

Edit: confirmed that if you go into the settings for the Bluetooth device and deselect the media audio, the phone will ring out loud with the current ringtone as the Bluetooth device (connected using "phone audio") also notifies you of the incoming call.

Ideally, the ringtone audio should be independent of the media audio, and should not be redirected to an a2dp Bluetooth device.
[Verizon Samsung Galaxy S III] dTardis:
bluetooth Ring

That's too bad. I know it use to be a setting in earlier versions of the ROM. I wounder why they changed it? I also wounder if there is an app?
[Verizon Samsung Galaxy S III] airmaxx23:
Hopefully this is something that can eventually be addressed.
[Verizon Samsung Galaxy S III] titanshadow:
I had a very similar issue, but mine got a 403 error on every update. I ended up having to remove my google accounts (all of them) from the device, reboot into recovery, clear the cache, boot back into normal, and then add the accounts again.

---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------

I just want to confirm something with all of you. There is an option in the cellular settings to use only 2G service to save on battery. Well, I really needed to do this as my phone had only 10% battery left for an 8 hour shift and I was waiting for a text from my wife that was actually really important. I had no charging options so, I turned off LTE, GPS, and WiFi. I figured, you know, they used to have EVDO and RT/1x for my old Verizon flip phone and I could receive texts on either.

Figuring that there HAS to be compatibility below 3G (2G or 1x in modern terms I suppose) I wanted to turn off the 3G radio too and just go bare bones, in hopes that my phone would last through enough of the 8 hours to get the text. When I selected the option to only use 2G, I couldn't get a data connection, I had no bars at all.

I tried it twice before I figured it was wasting more power than it was worth to try it, can someone else with Verizon service replicate this? It could be just me!
[Verizon Samsung Galaxy S III] airmaxx23:
I just tried the 2G and I can't get any type of data connection either.
[Verizon Samsung Galaxy S III] ayush20m:
Can you also check this that if you are playing music through bluetooth and you receive a call after the call the music will not play through bluetooth?

I thought I was the only one having this issue.
[Verizon Samsung Galaxy S III] rhcreed:
what version?

Hey all, just ordered my S3 from vzw... what nightly should I flash (just want a clean stable build, not looking for bleeding edge) latest nightly or what? thx!!
[Verizon Samsung Galaxy S III] kenbrownstone:
I would go with latest experimental test signal. The signal is a lot better. But if there is a nightly tonight they might have implemented the fix. As of the 18th nightly it wasn't in yet.
[Verizon Samsung Galaxy S III] Chris123NT:
The signal fix isn't officially merged yet, when it is you'll see it here:

http://10.1.cmxlog.com/?device=d2vzw

If you want the signal fix with the latest repo syncs then give mastamoon's unofficial builds a try, same as official with the exception of using aeroevan's kernel (CM kernel with some newer commits) and the signal fix, and some misc tweaks.
[Verizon Samsung Galaxy S III] kenbrownstone:
Were do I find moons ROM....I'm must have over looked it
[Verizon Samsung Galaxy S III] Chris123NT:
Here you go:

http://xdaforums.com/showthread.php?t=2094251
[Verizon Samsung Galaxy S III] kenbrownstone:
Thanks ....I've just never seen his name....loading now
[Verizon Samsung Galaxy S III] tehloxely:
Where can I get aerovans kernel? I cannot find it anywhere.
[Verizon Samsung Galaxy S III] SilverFox66:
Just bought a new VZ I535 and ran casual root/unlock, then flashed the latest stable (7-11?) CM. I live in a fringe area with a signal normally around -95 to -110. I ahvent had any troubles with phone reception. 4G does not reach where I live, so even though I leave my phone set to LTE, I only pull 3G on data. What seems to be the reception issue everyone talks about? Is it a data issue or a voice issue?
[Verizon Samsung Galaxy S III] ddggttff3:
its just an issue on how CM10.1 reports signal. It shows less bars then stock, but it has the same dbm, so its actually the same. There was an issue with 4G dropping (the -99dbm issue) but a patch is out for that, and should get merged any night now.
[Verizon Samsung Galaxy S III] SilverFox66:
ah, thank you! I never pay attention to the bars anyway (I always have 1 bar, which seems appropriate per my db strength) and havent had any issues with voice calls or data in any way, so was just wondering. Thanks again :good:
[Verizon Samsung Galaxy S III] buschbarber:
For me, it is the voice reception. Dropped calls or intermittent voice at -110dBm. I get 4G, but one bar. There are places where I get 4 bars (-75dBm), but it is not consistent.
[Verizon Samsung Galaxy S III] SilverFox66:
this is why I had to leave AT&T. I had a HTC One X setup exactly how I wanted it, and was happy as could be for 6 months. Then, they upgraded the local tower to 4G/LTE. I had the same signal strength as before the upgrade, but it wasnt usable or dependable.... always dropping calls, fading in and out, sound like under water etc... I finally got tired of it after 2 months of basically not being able to make any voice calls reliably, and went to VZ.

I thought the voice calls still went over 2G/3G though. If this is the case, why does the 4G mess up the voice calls? Please, be gentle with me lol
[Verizon Samsung Galaxy S III] buschbarber:
I have had Verizon for years, and 4G for years, but this dropped call problem is new.
[Verizon Samsung Galaxy S III] soohyunk83:
low volume on Bluetooth

Anybody have issues with low volume when using Bluetooth during calls? Or is this a known issue that's not been addressed yet?
[Verizon Samsung Galaxy S III] SilverFox66:
I dont. I actually hear better on bluetooth with the GS3 on CM (using HM1900) than I did with the same headset on other phones/ROMS :good:
[Verizon Samsung Galaxy S III] Chris123NT:
https://github.com/aeroevan/android_kernel_samsung_d2

That's the git for his kernel, I dunno if he has a compiled version of the standalone kernel, but mastamoon just compiles his builds with the kernel from that git repository.
[Verizon Samsung Galaxy S III] funnyperson1:
As ddggtfff3 said the signal strength in dBm is the same between TW and CM10.1. In a strong 4G or strong 3G area, you will get the same level of performance.

However, in areas where there needs to be frequent handoffs between 3G and 4G, stock TW is still SO much better. I've been hopping back and forth to test it. So every day coming home on the bus there is an area where LTE drops off, but there is still a strong 3G signal. On touchwiz I see a momentary data slowdown and a drop for less than 15 seconds before it decides to go to 3G. CM (and the other AOSP ROMs) try to hold onto that 4G signal even at less than -120dBm and data doesn't work at all until it decides to drop to 3G, sometimes several minutes earlier...sometimes I just have to turn 4G off or toggle airplane mode.
[Verizon Samsung Galaxy S III] mastamoon:
Looks like the 0/99 commit was merged so nightlies should be good to go soon.
[Verizon Samsung Galaxy S III] SilverFox66:
???Good to go????

I thought the Nightlies were already good to go with a new version almost every night?
[Verizon Samsung Galaxy S III] mastamoon:
According to the merge list, it got merged recently so any build (besides the "signal fix" test build) wasn't using this fix yet. My unofficial builds have been using it for a week though.
[Verizon Samsung Galaxy S III] SilverFox66:
ah. when you said "nightlies should be good to go soon".... it made it sound like there was a problem/holdup with the nightlies themselves... it threw me
[Verizon Samsung Galaxy S III] zachf714:
Na it will be in tonight
[Verizon Samsung Galaxy S III] zachf714:
I implemented it into builds that I do for myself and it definitely helps