yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] funnyperson1:
It's unfortunate that noobnl feels like that won't ever be fixed, I sure do hope he is wrong. I'm fairly certain I've seen the 0dB issue is medium to strong signal areas, but it does seem worse in low-signal areas. I disagree that the issue is purely cosmetic. When I'm out and the LTE signal starts to drop, this phone on a CM10.1 based ROM just gets confused and bounces between 0dBm LTE, 2-3 bars 3G, and 1x RTT, the phone heats up and whatever simple task I needed to use my data for fails. Even when I see the 3G symbol light up I can't do a simple google search. I recently went back to CleanROM after getting frustrated with this and when the LTE drops out, I get strong 2-3 bar 3G and it actually works, I can browse just fine, there's no jumping back and forth, it will only get back on 4G when the signal is strong enough to hold.

I still feel like maybe the phone uses the signal data to make decisions about when to switch. I could be wrong, maybe the 0dBm issues are unrelated to the data-handoff issues but it sure seems like I see both issues come up at the same time.

As I said above, I'm not sure if it's this bug or something else, but the AOSP ROMs definitely have weaker performance in low-signal areas.

I agree with you that the bug is not exclusive to low-signal areas, and believe me I understand your frustration. While it hasn't been fixed, this bug has been adressed multiple times. I think noobnl is probably more frustrated than anyone, this is the second or third stab he's taken at it. I've been watching the RIL commits and he's tried like 20 different code changes to fix this and related bugs. You've raised some good points in your post, but the attitude is unnecessary and detracts from the post.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah, I hear you man, and I know it's not directed at me. I've got to be honest I was a little thrown back by noobnl's statement to me about it. It just had this arrogant undertone that he thought I was stupid for even asking but whatever. Either way I agree with you that this is a bug, but I'm trying to stick with CM because I really like it, can't really stand some of the little nuances about TW.

Funny you mention the network extender thing, I have one of the 3G network extenders and I never see 0/99 when I'm in range of it, BUT my phone always seems to think I'm roaming when I'm near it which only started with the JB modems. Are you seeing that as well? Afraid to mention that one to noobnl, he might punch me in the face through the computer screen lol.
[Verizon Samsung Galaxy S III] airmaxx23:
So what is this bug exactly?
[Verizon Samsung Galaxy S III] Chris123NT:
Signal drops, phone reports 0DBm/99ASU and the data completely stalls when it happens.
[Verizon Samsung Galaxy S III] airmaxx23:
I've had this bug also, just didn't realize what was happening.
[Verizon Samsung Galaxy S III] zcmack:
I'm on stock (included with the rom) kernel, haven't touched any clock or voltage settings. i'm on MF1 firmware. my previous nightly (4-9) was on MB1 and I didn't have as poor of signal or the random reboots. gotta love the bleeding edge! I didn't get around to flashing yesterday so I'll flash today's build when I get some time. I also noticed the phone was occasionally reluctant/slow to wake from sleep, so maybe I need to bump up my idle mhz.
[Verizon Samsung Galaxy S III] mastamoon:
how are you on stock kernel but "need to bump my idle mhz"? AFAIK there isn't any steps lower than 384 on stock kernel.
[Verizon Samsung Galaxy S III] airmaxx23:
My phone didn't like the stock kernel at all. If it isn't freezing up all the time it's very laggy and slow. Would a last_kmsg help identify the cause of the lag?
[Verizon Samsung Galaxy S III] Chris123NT:
http://review.cyanogenmod.org/#/c/45569/

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

These commits fix a typo in the RIL code. I don't know if it would fix anything significant, but from everything I've learned, typos in code are generally not a good thing :p

Here's some interesting camera commits to fix HDR low exposure on sammy hardware:

http://review.cyanogenmod.org/#/c/45539/, http://review.cyanogenmod.org/#/c/45098/14, http://review.cyanogenmod.org/#/c/45132/9
[Verizon Samsung Galaxy S III] ugachris:
Please post your logs, and post to JIRA.
[Verizon Samsung Galaxy S III] goldsmitht:
this isn't a ROM question, but he smart people on here might be able to get me a good answer;

VZW has agreed to let me request a replacement phone, since i have one of the origional ones. I have really bad reception in my house, and they think it is probably something to do with the hardware. Would the new phone, with factory installed MF1 really help, or would it only be a placebo, and more trouble than its worth?

thanks, no this isn't a ROM issue, but this is where some of the smarter people hang out!

:fingers-crossed:
[Verizon Samsung Galaxy S III] ugachris:
I've been watching the progression on those HDR commits and wondering if they affect us. Some mention hardware HDR, which AFAIK, we don't have. But what I would really like to see is software HDR use the built-in burst mode (Steve mentioned this as a possible improvement a while ago).
[Verizon Samsung Galaxy S III] Chris123NT:
You might notice a difference. I had one of the early phones and I had to get it replaced due to a bluetooth problem (a2dp would crackle even on TW roms), and the new phone seemed to have a better signal than the old one running the same modem.
[Verizon Samsung Galaxy S III] mastamoon:
7/16 build in the OP

-- repo sync @ 3:45PM EST
[Verizon Samsung Galaxy S III] V3TTOO:
Ok, the ROM update notification service you are using is a bit useless if you miss updates. I was on the build before 07/12, so the app asked me to download it. I did, installed it, and when I got back, it was asking me to download 07/13 instead of your new 07/16. Is this app meant to download one update at a time? Why not just ask me to download the latest?
[Verizon Samsung Galaxy S III] mastamoon:
Being worked on already. :)
[Verizon Samsung Galaxy S III] V3TTOO:
Awesome. Just making sure it wasn't just me messing something up. Thanks again.
[Verizon Samsung Galaxy S III] Chris123NT:
I'll just leave this here so everyone can see :)

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

This should fix 0/99 once and for all.
[Verizon Samsung Galaxy S III] Div033:
Can it truly be true?! I saw the new signal strength test build, has anyone tried it? I think I will when I get home.

Edit: downloading now but 4G is slow here! Argh!
[Verizon Samsung Galaxy S III] sivarticus85:
Redundancy man is redundant!

Lol jk downloading now! Fingers crossed!
[Verizon Samsung Galaxy S III] Chris123NT:
Testing of this build is yielding very positive results. Noone is hitting 0/99 with it thus far.
[Verizon Samsung Galaxy S III] Stealth111:
OK, I am REALLY starting to get excited here! I just saw this as well! Ticket was an interesting read...

Ticket:

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

Code for fix:

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

WOOHOO! I hope they got it nailed down. Downloading now...

That's COMMITMENT!!

THX CM TEAM for not giving up...
[Verizon Samsung Galaxy S III] Div033:
Thank you noobnl for rickrolling us and never giving us up or letting us down.

I'll just leave this here.
[Verizon Samsung Galaxy S III] sivarticus85:
Oh boy! I'm super excited about this!
[Verizon Samsung Galaxy S III] mastamoon:
Looks good thus far at my house where I'd normally drop to 0/99 often. Real test for me will be @ my office tomorrow morning.

I think the actual signal/bars still needs some adjustment though. But this looks and works awesome thus far.
[Verizon Samsung Galaxy S III] Chris123NT:
You mean the signal decibel wise or the way it's graphically represented? Graphically signal has always displayed lower than usual on 4.2 but db has always been identical to TW.
[Verizon Samsung Galaxy S III] Chris123NT:
http://jenkins.cyanogenmod.com/job/...EXPERIMENTAL-d2vzw-SIGNALSTRENGTHTESTNEW2.zip

New test build, Patch Set 5, noobnl said he derped the if statement, so this one fixes that error.
[Verizon Samsung Galaxy S III] mastamoon:
7/17 build in the OP

-- Tunnel audio cherry pick re-added, doesnt break YouTube anymore, let me know if it breaks anything else

-- Signal Strength cherry pick fixes the 0 dbm / 99 asu bug that many of us with weak LTE signals get.

-- repo sync @ 3:30 PM EST
[Verizon Samsung Galaxy S III] cesium:
Anyone have this bluetooth issue: when I'm listening to music via bluetooth, if turn off the bluetooth device (not phone) first, and thereafter turn off bluetooth on my phone, I have to force stop bluetooth share or else it will never turn back on. I'm not entirely sure if the issue crops up every single time, but that is the only scenario in which the problem arises.
[Verizon Samsung Galaxy S III] titanshadow:
I have, but have found no solution. And, doesn't happen every time for me.
[Verizon Samsung Galaxy S III] Chris123NT:
It's an intermittent problem, I rarely ever hit it since I never turn BT off except if something is going wonky. I did notice Bluetooth got more stable once I turned NFC off, but that could just be placebo, I'm not 100% sure if it has anything to do with it.
[Verizon Samsung Galaxy S III] Reborn627:
Thanks man. I ran into a camera lock-up issue today. Even touched the screen for focusing and it locked. Had to reboot the phone. Anybody else?

Ray
[Verizon Samsung Galaxy S III] PerCompLLC:
Yup. Thought it was just a bad download or something. Phone locked every time I tried to use the camera. Reverted to this morning's cm test.
[Verizon Samsung Galaxy S III] iconrider:
Camera issue here as well. Back to the experimental build.
[Verizon Samsung Galaxy S III] mastamoon:
Crud. Hmm.
[Verizon Samsung Galaxy S III] edif30:
Hoping someone has same issue?
[Verizon Samsung Galaxy S III] dpaine88:
Looks like 10.1 M build is up..

Not sure if "M" builds = RC status or not
[Verizon Samsung Galaxy S III] odub303:
Did you really just quote yourself? Chronus is a lockscreen widget.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] biyobe:
Anybody have a chance to try this"m" release? What are the new fixes?
[Verizon Samsung Galaxy S III] edif30:
It did the job... And yes I know its a widget but I don't see any settings.
[Verizon Samsung Galaxy S III] jbdan:
Have you checked lock screen settings in settings?
[Verizon Samsung Galaxy S III] edif30:
Thanks. Found it.
[Verizon Samsung Galaxy S III] BlueCross:
Bluetooth is fixed for sure. Still a no go with encrypted tethering.
[Verizon Samsung Galaxy S III] oldmerovingian:
I am running the "m" release right now and everything seems to be working well. Of course I will need a few days to see how well it works.
[Verizon Samsung Galaxy S III] M Diddy:
Guys (Dan),

Amy chance this fixes the mic input on video recording?

http://review.cyanogenmod.org/#/c/30568/
[Verizon Samsung Galaxy S III] sparkerjc:
On 1-18 I have full video recording volume. A month back it was barely a whisper so I assumed this was fixed already.
[Verizon Samsung Galaxy S III] biyobe:
Is that on audio streaming or just calls? I can deal with leaving network open.... But I gots to have my tunes!! ;)
[Verizon Samsung Galaxy S III] PerCompLLC:
"M" is for monthly... CM10.1 is nowhere near RC yet.
[Verizon Samsung Galaxy S III] odub303:
That isn't for our device. It's for HTC.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] jb_alphamale:
BT fully working on my phone with the latest build.
[Verizon Samsung Galaxy S III] invisiblek:
We already have this: https://github.com/CyanogenMod/android_device_samsung_d2-common/blob/cm-10.1/audio/audio_policy.conf
[Verizon Samsung Galaxy S III] Rudy_Ruettiger:
BT works for me, but the volume is very low compared to previous builds (1/16, 1/18).
[Verizon Samsung Galaxy S III] bdanders:
Does that mean it has stopped getting stuck trying to turn off after toggling a few times?
[Verizon Samsung Galaxy S III] d1ez3:
What exactly is the difference between the M1 build and the 1/21 nightly? Are the majority of the most current updates in the changelog only applied to the nightly?
[Verizon Samsung Galaxy S III] RED ZMAN:
I'm glad you posted that, so I'm not the only one with this behavior? I'm on the 17 build Masta, complete wipe fresh install.

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] Chris123NT:
Crap, does it here as well.

If I had to guess I would say it's probably invisiblek's defconfig stuff doing it, that's the only thing I could think would screw the camera.
[Verizon Samsung Galaxy S III] mastamoon:
Official would do the same in that case. I think I may have aeroevan's kernel being pulled so it might be that. I'll go back to CM kernel tomorrow and see what happens.
[Verizon Samsung Galaxy S III] Chris123NT:
Oh if you're pulling aeroevan's kernel I think he mentioned something about enabling selinux on d2

Reverted to noobnl's experimental and the camera is good again, probably should have tried leankernel or something before I reverted lol.
[Verizon Samsung Galaxy S III] mastamoon:
I had been using it because CM's kernel was a few weeks behind aeroevan's with caf and korg merges. Had been working fine up till recently so it might be something cm merged in the rom that caused it to puke. We'll see tomorrow.
[Verizon Samsung Galaxy S III] dvaderx:
I commented on Jira about this (found a few dozen others have also posted about it there)

And it may be my imagination, but i think when i added comments it wasn't assigned to anyone but now it is.

so maybe that is a good sign.
[Verizon Samsung Galaxy S III] goldsmitht:
how long have you used his kernel? Seems like the last build or so my batter life took a hit. not bad, but down from about 14 hours on a day to around 8.

but with two batteries, it really never matters that much unless i'm out all day

:cyclops:
[Verizon Samsung Galaxy S III] PerCompLLC:
I know that you are asking about aeroevan's kernel, but I'll mention that on CM's kernel I am finally getting ridiculous battery life (best I've seen yet). :good: I'm running the experimental as I switched when I noticed the camera issue and didn't put any thought into the fact that it might be a kernel compatibility issue.
[Verizon Samsung Galaxy S III] Chris123NT:
Same here, getting VERY good battery on CM's kernel, better than TW I would say.
[Verizon Samsung Galaxy S III] goldsmitht:
exactly; was getting great battery life on at least 7/11 or so, and then by 7/16 i'm back to noticibly less.

otherwise, great, can't really tell the difference between TW and Mastamoon's version with CM kernel

:cyclops:
[Verizon Samsung Galaxy S III] ugachris:
Link to the jira?
[Verizon Samsung Galaxy S III] Sisren:
I've noticed the hit to the battery as well, but I'm not so sure it is the ROM. After some digging, it seems like Google Play Services is consuming an inordinate amount of battery life and I suspect that this is root cause (at least for my phone). I'm disabling the service and going to see if that helps any.
[Verizon Samsung Galaxy S III] shadrach47:
I've been having some wakelock issues with NlpCollectorWakeLock and NlpWakelock. It seems to be related to the play store for what I can find. Still trying to see how to get rid of it. RIght now I disabled location services to see if it helps. Not sure what else would be draining my battery.
[Verizon Samsung Galaxy S III] mastamoon:
7/18 build in the OP

-- new patchset for the Tunnel audio fixes the broken camera

-- Magic

-- repo sync @ 1:45PM EST
[Verizon Samsung Galaxy S III] goldsmitht:
Does this have the signal fixes?
[Verizon Samsung Galaxy S III] mastamoon:
yeah has the 0/99 fix in it.
[Verizon Samsung Galaxy S III] goldsmitht:
DUH!!! and it says so in the OP! guess i should read before i ask questions.

:eek:

:good:
[Verizon Samsung Galaxy S III] rmg88888888:
I've also been noticing Nlp wakelocks and a lot of alarms by com.google.android.gms (500 in 5 hours). I've done some searching and haven't found anything significant on it.
[Verizon Samsung Galaxy S III] cynikalJ:
I don't know what changed with the nightlies but this is the best build of aosp that I have ever ran. The 0/99 issue is gone, I get better signal and everything is flawless all around. One question though, is it safe to flash another kernel now. I like BMS but if the camera breaks I will stick with stock.

Thanks
[Verizon Samsung Galaxy S III] mastamoon:
Camera breakage wasn't kernel related. Should be able to use whatever kernel you desire.
[Verizon Samsung Galaxy S III] cynikalJ:
Right on, thanks man
[Verizon Samsung Galaxy S III] AdMire:
Signal problem still there? Never saw this before, but it did break data for a bit.

Edit: apparently I can't attach photos from this app. The signal says, 2147483647
[Verizon Samsung Galaxy S III] goldsmitht:
No real signal issues here, been running it since yesterday; even sent an MMS, so no problems there either
[Verizon Samsung Galaxy S III] mastamoon:
Thats an invalid signal. This might be due to the 0dbm/99asu work around that was put in place. Hmm. Are you on the latest?
[Verizon Samsung Galaxy S III] Hybridnoob:
Stock kernel? I had that when I tried LeanKernel on 7/17 (trying to fix the camera). I haven't seen that on stock. I'm happy to report everything works fine and as expected on 7/18 with the stock kernel.
[Verizon Samsung Galaxy S III] Chris123NT:
Haven't seen that here, are you running 7/17 or later? Before that still had the 0/99 bug and that might be how it shows with that display option, not sure.
[Verizon Samsung Galaxy S III] AdMire:
I'm on 7/18 with this kernel. Maybe it is just the attempt to fix the signal issue. Thanks a lot guys.
[Verizon Samsung Galaxy S III] Chris123NT:
Were you on LTE or 3G when it happened?
[Verizon Samsung Galaxy S III] AdMire:
As a matter of fact, I think I was on 3G. I was waiting to get a hair cut and didn't have a fast connection. Now that you mention it, I'm almost positive I was on 3G.
[Verizon Samsung Galaxy S III] Chris123NT:
Hmmm, interesting, pretty sure the 0/99 fix didn't do anything to affect signal readout while on 3G. Maybe there's another bug somewhere that needs squashing.
[Verizon Samsung Galaxy S III] nbaj2k:
Thinking about buying an MHL adapter for my Verizon S3. I'm loving this ROM, just wondered before I buy the adapter if people had good luck getting it to work well? I know there were some issues with older Cyanogen ROMs.

Thanks,

-J
[Verizon Samsung Galaxy S III] mastamoon:
7/19 build in the OP

-- aeroeven kernel back in (wasnt causing the camera issues)

-- tweaked displayed LTE signalbars a lilbit aka magic
[Verizon Samsung Galaxy S III] mastamoon:
iirc, it's not working. But I'll let somebody that has one answer.
[Verizon Samsung Galaxy S III] Hans5849:
I'm noticing the sensor for turning the screen off is a little over sensitive right now.
[Verizon Samsung Galaxy S III] mybook4:
I have the MHL adapter. MHL stopped working in CM 10.1 right around the time we switched over to the 3.4 kernel (march-ish?). I'm not sure if it's kernel or ROM related.
[Verizon Samsung Galaxy S III] Div033:
Wow! My signal is so much better on this build! I know this because of the signal bars which are the definitive representation of my signal. The "magic" really helped!

/s

Seriously though the latest build will probably be my daily for a long while. Thanks masta for stickin' with us. Many others have moved on to the S4.
[Verizon Samsung Galaxy S III] Chris123NT:
Yes, the magic is very nice, brings the bars in line with what they were on CM10, and eliminates the whole poor LTE signal looking like 0/99 used to (no bars).

Whole point of the tweak was because poor signal should be 1 bar, whereas 0 bars should be reserved for no signal at all.
[Verizon Samsung Galaxy S III] yznhmr:
Does BT4 work yet?

I want my fitbit to sync to my phone
[Verizon Samsung Galaxy S III] stearic:
BT4 won't coming until at least android 4.3. Maybe even later then that.
[Verizon Samsung Galaxy S III] funnyperson1:
BT4 won't work until Google implements it as part of the AOSP bluetooth stack (which is rumored to happen in 4.3).

Also the signal fix works great, but data handoffs are still nowhere near as smooth as TW.
[Verizon Samsung Galaxy S III] yznhmr:
Does it work on Stock?
[Verizon Samsung Galaxy S III] PerCompLLC:
Just got a warm reboot when receiving a call this morning. No changes to the Unofficial build and no changes to the kernel settings. I suspect that it is kernel related (aerovan's kernel), but that is just my gut. Switched over to the latest nightly and haven't had a problem yet.
[Verizon Samsung Galaxy S III] Chris123NT:
You still having battery issues with evan's kernel? I am noticing a little bit of battery drain. Making a build right now with the stock CM kernel to see if there's any difference.
[Verizon Samsung Galaxy S III] PerCompLLC:
Only issue I have had is a couple of warm reboots while on aerovan's kernel. I haven't been able to give it enough time to see if battery life is as good as the CM kernel, but prior to Masta using the aerovan kernel I was getting GREAT battery life with the CM kernel. All of this is probably placebo of course (with the exception of the reboots, which actually did happen).
[Verizon Samsung Galaxy S III] Chris123NT:
If you want to try the build I just made, here it is:

http://chris123nt.com/CM/cm-10.1-20130721-UNOFFICIAL-d2vzw.zip

Repo Sync 11:55 AM EST (0/99 fix is now official so it's no longer cherry-picked)

has the stock CM Kernel, and Masta's MMS tweaks with the folowing cherry-picks:

Mms: Add the ability to select recipients from a checkbox list - http://review.cyanogenmod.org/#/c/34094/

TunnelAudio: Fixes playback with Qualcomm tunnel audio for players which use gapless api - http://review.cyanogenmod.org/#/c/45439/

Fix RIL_UNSOL_CDMA_PRL_CHANGED constant typo (1/2) - http://review.cyanogenmod.org/#/c/45569/

Fix RIL_UNSOL_CDMA_PRL_CHANGED constant typo (2/2) - http://review.cyanogenmod.org/#/c/45568/

BT: Fix memory leak when BT on & off done many times - http://review.cyanogenmod.org/#/c/45090/

The BT one is an attempt to stop the freezes when turning BT off. It seems to have helped, as now when it "freezes" it only does so for about 20 seconds or so and then it DOES turn off.

Oh, and it has "Magic" :P

Not trying to steal mastamoon's thunder here, just providing a test build, and since PerComp was having trouble I figured I'd post, will help to see if it's the kernel or not. If it still happens I'm blaming that pesky tunnel audio commit :p
[Verizon Samsung Galaxy S III] Restola:
Anyone flashed the Google edition camera apk and seen if it affects recording volume in a positive way?
[Verizon Samsung Galaxy S III] mastamoon:
My battery drain seems to be directly related to Google services. How many if you have the leaked play store installed and ****ty battery? If not, how many have the newest google maps?
[Verizon Samsung Galaxy S III] Chris123NT:
I don't have the leaked play store, but I probably do have the newest google maps.
[Verizon Samsung Galaxy S III] PerCompLLC:
Thanks! Downloading now...
[Verizon Samsung Galaxy S III] juancaperez2000:
Same here no leaked playstore but running latest maps and my battery life have been horrible, in trying now latest liquid and battery life is really better not sure why

Edit: on liquid i dont install maps yet, so maybe is maps related
[Verizon Samsung Galaxy S III] Chris123NT:
I don't think that'll make a difference since the volume is controlled by the drivers and config files for the microphones.
[Verizon Samsung Galaxy S III] Sisren:
I went to manage apps, Google services and uninstalled the updates. My battery life immediately improved.

I have no idea what I am may be missing without the updates, but I have not had any issues. And as I stated above, battery life is now phenomenal.
[Verizon Samsung Galaxy S III] Obaterista93:
I don't think you can use hangouts without the update though.
[Verizon Samsung Galaxy S III] Sisren:
Ah... I don't use it anyway and if I did, I would do without it. I travel for work and can't afford the severe battery drain that it was clearly causing.
[Verizon Samsung Galaxy S III] minnysota:
Hey Masta, do you know if there is a flashable zip of the 0/99 fix? I did some digging and couldn't find one. Thanks!