yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] odmejia:
That would be awweessommmeee you're the man!!
[Verizon Samsung Galaxy S III] stearic:
Having this exact issue off and on. Had it last night but no issues since then.
[Verizon Samsung Galaxy S III] thefuzz4:
Running on the experimental from earlier today and everything is working good. Strong signal (should be since I'm sitting damn near under a repeater in my office) and SMS sends and receives just fine.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah the experimental #5 has the sms fix merged as well as the RIL test fix which just got merged. By the looks of the comments they gave up on the 0dbm/99asu bug.
[Verizon Samsung Galaxy S III] Stealth111:
WHAT??!!*$@#%!!!:eek::eek::eek:

That would suck pretty badly if so......

Sent using Tapatalk
[Verizon Samsung Galaxy S III] Div033:
Yup... It's true.

"Patch Set 10: Verified+1 Code-Review+2

gave up on the 99asu, 0 dbm bug.”
[Verizon Samsung Galaxy S III] mastamoon:
Dang. Not surprised though, if it was an easy fix it would have been fixed already.

I can't believe CM would just let it go though.
[Verizon Samsung Galaxy S III] PerCompLLC:
This ^^^
[Verizon Samsung Galaxy S III] mastamoon:
Anybody have trouble playing video via YouTube app lately? I can play fine via the mobile site but the app continually caches / buffers, never plays.
[Verizon Samsung Galaxy S III] Stealth111:
I can't believe it either... This sucks..

Sent using Tapatalk
[Verizon Samsung Galaxy S III] mastamoon:
I wouldn't say is over, I'll bet that an idea will pop up in noobnl's mind and he'll have another go at it. Kinda the way this works.
[Verizon Samsung Galaxy S III] mastamoon:
Also update building now, kids took over my pcs last night so I couldn't get on.
[Verizon Samsung Galaxy S III] goldsmitht:
damn kids, don't understand what is important! LOL! JUST KIDDING! i was just happy when mine stayed away from the hacking sites and didn't start hack wars with someone who was way smarter than he was

thanks again!

:D
[Verizon Samsung Galaxy S III] thefavorite:
I had that problem as well as the SMS problem so I just flashed back a build. I'm just waiting for these to be squashed
[Verizon Samsung Galaxy S III] mastamoon:
7/13 build in the OP

-- removed RIL/0dbm99asu cherry pick

--repo sync 10:15 AM EST
[Verizon Samsung Galaxy S III] goldsmitht:
Got the notification from apk, but download file labeled 7/12; wrong name, or wrong file?
[Verizon Samsung Galaxy S III] mastamoon:
Mine showed and downloaded the correct file? Hmm
[Verizon Samsung Galaxy S III] goldsmitht:
Miner's showing 7/12 in file manager
[Verizon Samsung Galaxy S III] mastamoon:
Weird, delete it and wipe the ROMdb app data and see what happens.
[Verizon Samsung Galaxy S III] mastamoon:
I'm still having the YouTube issue, might be that other cherrypick. Meh, no time to build another today, maybe tomorrow.
[Verizon Samsung Galaxy S III] odmejia:
Just download and installed the latest nightly update from cmupdater, SMS seems to be back to normal, not stuck in sending, the signal drop 0odbm/99asu issue, haven't noticed it but now my group messaging? I received a group message and after I responded I'm getting all the responses separately instead of in one message? Anyone having this issue?
[Verizon Samsung Galaxy S III] Chris123NT:
Youtube app issue must be related to that other cherry pick. I'm currently on the official signal test #5 build and youtube videos work fine in the youtube app.
[Verizon Samsung Galaxy S III] goldsmitht:
YouTube works fine on 7/11, was able to download 7/13 from tap talk, so will probably just delete romdb apk, and try again when you put new build up Monday. Thanks again for all the hard work!
[Verizon Samsung Galaxy S III] dvaderx:
Any idea if work is being done to fix the low cam corder volume issue?
[Verizon Samsung Galaxy S III] SymbioticGenius:
To those who may be interested. I'm on 7-9 unofficial currently working fine in Japan with Japanese SIM card. Everything works however cannot confirm data works due to the expense. Will test at a later date. Great job CM team and Masta
[Verizon Samsung Galaxy S III] stearic:
Does this new update fix the sms issues?
[Verizon Samsung Galaxy S III] Chris123NT:
Yes it does :good:
[Verizon Samsung Galaxy S III] goatman101:
Yes, I was having the same problem. I thought it first surfaced on build 13. I reverted back to 12, but the problem was still there.

I ended up uninstalling the app, rebooting, installing app, then rebooted again and it started working.
[Verizon Samsung Galaxy S III] Sisren:
Just curious...

I tried CM a few months ago and loved it. However, I could not get Wifi tethering working which was a deal breaker for me.

Has this been fixed? Anyone successfully using it with WPA encryption?

Thanks for the help!
[Verizon Samsung Galaxy S III] mastamoon:
Wifi tether works great.
[Verizon Samsung Galaxy S III] goatman101:
Okay so just to update, I flashed the 7/13 build and my YouTube is borked again. Videos will not play. I tried to uninstall and reinstall but no luck.
[Verizon Samsung Galaxy S III] odmejia:
My YouTube app works but when I try to record in instagram its extremely awful
[Verizon Samsung Galaxy S III] mastamoon:
7/14 build in the OP

-- removed the tunnel audio cherry pick, youtube app seems to work again

-- repo sync @ 12PM EST
[Verizon Samsung Galaxy S III] Chris123NT:
Awesome, thanks. I'll give this a shot when I get home. Also see a couple of Bluetooth commits, wonder if that will finish stabilizing BT. Hopefully it didn't break anything :D
[Verizon Samsung Galaxy S III] goatman101:
Flashed the 7/14 build and can confirm that YouTube is working again.
[Verizon Samsung Galaxy S III] goldsmitht:
I've been using AOSP ROMs for a while, and don't have a problem at all

---------- Post added at 01:36 PM ---------- Previous post was at 01:36 PM ----------

Wow, didn't see a notice from romdb apk...
[Verizon Samsung Galaxy S III] mastamoon:
That's weird, I got it immediately when I pushed the update on romdashboard.com

Anybody else not getting notifications of recent builds?
[Verizon Samsung Galaxy S III] goldsmitht:
This was the first, and I can't see how to delete RomDB, only disable. That didn't do anything
[Verizon Samsung Galaxy S III] Hybridnoob:
It only notifies if the user is running the most recent build.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah the recording volume is a tad low but nowhere near as bad as it was a few months ago, back then it was so bad half of the voice command apps didnt even know what you were saying.
[Verizon Samsung Galaxy S III] goldsmitht:
Sorry, not seeing it, especially on this ROM. Have taped different events, and volume has been fine.
[Verizon Samsung Galaxy S III] Chris123NT:
Ever since coming back to this ROM last week it has been OK for me as well, not as loud as tw but definitely good enough where I don't even worry about it anymore.
[Verizon Samsung Galaxy S III] mastamoon:
If that's the case I'll have to bring it up to the ROMdb guys. I would expect that you should get a notification no matter what version you are on. Will ask about a check for updates button as well.

At some point cm10.1 started using CAF audio drivers/code and that may explain the better recording volume lately.
[Verizon Samsung Galaxy S III] goldsmitht:
Still on 7/11, cleared data and received notification, but its for 7/12 again.
[Verizon Samsung Galaxy S III] mastamoon:
Wtf!? :what:
[Verizon Samsung Galaxy S III] Hybridnoob:
I've noticed the same behavior.
[Verizon Samsung Galaxy S III] mastamoon:
That's odd. Did you guys update to the latest romdb app via market?

Maybe try deleting the apk from both /system/app and /data/app then reflash the latest rom. Maybe there is a conflict of data somehow?

IDK, I'll ask joeykrim about it with the other questions on Monday.
[Verizon Samsung Galaxy S III] Hybridnoob:
I have the latest version and have cleared data and / or reinstalled the app just to make sure the issue wasn't corrupted data. I have a feeling it's programmed to behave that way, because I have noticed the notifications and update details have always worked that way. I don't update the ROM every day, so I routinely notice that behavior.

If you install a build or restore a backup from a couple of days ago, you will see the same - guaranteed. I really like the app and know it's still in early development, but the dev should probably be made aware.

I love your welcome message by the way :D
[Verizon Samsung Galaxy S III] sivarticus85:
Hey guys, been using this updated camera put together here on xda and it works awesome. Has Picassa sync and photosphere.

http://d-h.st/TJq

I take no credit for this work, just sharing the wealth.
[Verizon Samsung Galaxy S III] Chris123NT:
It allows saving to the SD card right? So happy that option is finally in the default CM camera.
[Verizon Samsung Galaxy S III] sivarticus85:
No I don't think so. I just found out that it freezes when Location is turned on. I don't use it, I just forgot to turn it off, and I like Picasa sync and the new interface. Everything else works otherwise that I can tell.
[Verizon Samsung Galaxy S III] goldsmitht:
Do you have to touch to focus to avert causing FC's?
[Verizon Samsung Galaxy S III] dvaderx:
I tracked this back to around march of 2012. CM switched to an "open source" driver and the volume recording has never been the same since.

Yes if you hold the phone right in front of your face, it will pick up your voice just fine.

however (as a test) if you sit on the sofa and record the TV with a touch wiz rom, you can hear the tv just fine on the play back

if you play it back on the CM 10/10.1 you can't hear it at all.

So if you have kids and are recording them doing something away from you, on TW you get it, on CM you get video only and almost no existent sound. I feel like people press record, talk in to the phone and go yep it works fine. but there is more to it than just picking up close audio. and even that isn't all that great. i tried the built in voice recorder, it has an analog like needle. and i had to practically yell into the phone to get it to red line.

My guess is that the open source drivers do not engage all the MIC's on the phone and/or the gain is set to nothing.

either way, I have checked about once a month since 03/2012 on every CM and CM based rom and it's still not been fixed.

I filed a bug report with CM (it's been a while but last i had checked there were dozens of people reporting the same issue) but it seems to have been over looked.

sadly since i have kids, it keeps me from running a CM based rom :(
[Verizon Samsung Galaxy S III] goldsmitht:
not sure when you last used it, but i've taped my dogs playing and barking inside, a greek festival outside, and other stuff, and have had no problems with the video sound. might be an issue with the version you are using, or perhaps a bad download/install. but i have no problems with it.

:confused:

---------- Post added at 08:25 AM ---------- Previous post was at 08:20 AM ----------

On another note, downloaded 7/14 from the website last night (didn't use ROMdB) and it downloaded and installed fine (a little slow) then enabled the ROMdB apk, and it now shows the correct download and doesn't show an available nightly build. SO... might be working now.

Probably has to do with when you skip an nightly build, and try to go to one later in the list.

:cyclops:
[Verizon Samsung Galaxy S III] Chris123NT:
I had the BT Audio connection freeze (Phone locks completely unresponsive) again today when getting in my car to leave work to run an errand. Interesting thing is this only seems to happen when I'm leaving work. Going out all weekend from various locations this never happened, but it seems to happen leaving work every time unless I unlock the phone before starting the car. Starting to wonder if it's something to do with the wifi here as that's the only thing that's different from when I have the phone at other locations.
[Verizon Samsung Galaxy S III] sivarticus85:
I have not experienced this issue. I was burst shooting my dogs last night without fail.
[Verizon Samsung Galaxy S III] mastamoon:
Thats really weird. Are you still on wifi when you get in your car? I rarely if ever am connected to wifi here at work when I get to my car so I cant try this. But I am on wifi at my house when I leave in the morning and I never have bluetooth issues. Are you toggling wifi/bt on and off as you get in and out of your car, or do you leave both on all the time?
[Verizon Samsung Galaxy S III] Chris123NT:
I leave both on all the time usually, and I'm connected to wifi still when I get in the car at work. Usually still connected to wifi when I get in at home as well but it hasn't ever happened when leaving home. Thinking maybe it's something with the router at work, it's an ancient WRT54GS lol.

Are you toggling BT during the day or leaving it on like me?
[Verizon Samsung Galaxy S III] mastamoon:
I leave BT and WIFI on all the time. I guess you could try to disconnect from wifi before getting in your car.
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah I'm gonna try that today when I go home, I'll let you know if that resolves it.
[Verizon Samsung Galaxy S III] mastamoon:
I believe wifi and bt are on the same chip, so if its so, it might be an issue with like what security your work uses on its wifi, or what permissions are needed when you join their network (security wise). Something is causing bt to 'wait/hang'.
[Verizon Samsung Galaxy S III] bluezr1:
I clean flashed yesterday's build (last night) and words with friends kept freezing up. So I clean flashed it again and had the same outcome. Then I flashed leankernel and still had the same problem. If I waited it would begin to work again but would (within seconds) freeze up again. So I went back to 7-3 build and have so played maybe 10 games without one freeze-up. Just passing it along, otherwise I'm not having any other problems. Thank you,
[Verizon Samsung Galaxy S III] zcmack:
i have had 2-3 random reboots a day on the 7-9 build. twice while listening to google music (once was connected via bluetooth a2dp) and several other at completely different, seemingly random times (once while the phone was idle in my pocket).

i'm going to flash the latest nightly tonight to see if it persists, but i figured it was worth a mention considering i was on the 4-22 nightly for three months and i never had a reboot.
[Verizon Samsung Galaxy S III] Chris123NT:
I haven't had that problem. Is that with the stock kernel or another kernel like lean or KT?
[Verizon Samsung Galaxy S III] mastamoon:
Make sure your on the latest firmware. Sounds like the old reboot issue that was fixed by updating the Tz firmware.
[Verizon Samsung Galaxy S III] PerCompLLC:
Just had my very first random reboot... 7/14 unofficial, stock kernel.
[Verizon Samsung Galaxy S III] ugachris:
What firmware? See the post above yours.
[Verizon Samsung Galaxy S III] PerCompLLC:
Latest and greatest...
[Verizon Samsung Galaxy S III] goldsmitht:
what were you or the phone doing at the time? Using any apps, or just sittin there? Stock kernel, but with stock settings? OC / UV?

inquiring minds want to know

:cyclops:

---------- Post added at 03:27 PM ---------- Previous post was at 03:25 PM ----------

AND... 7/15 nightly just hit ROMdB and landed in my notification box!!! WOOO HOOO!!! Just like it's supposed to. Now if I can just download it before i have to leave work...
[Verizon Samsung Galaxy S III] PerCompLLC:
Stock kernel, stock settings. I was typing an email. That said, I was plugged in to power. After the reboot I unplugged and was able to complete the task without incident. I think being plugged in has something to do with it...
[Verizon Samsung Galaxy S III] mastamoon:
Totally forgot to update first post, so please grab today's build from my ftp server.

http://truelinux.net/sch-i535/mastamoon/
[Verizon Samsung Galaxy S III] Chris123NT:
Disconnected from wifi before getting in the car and there was no freeze when the bluetooth connected, so my guess is it's definitely something to do with the wifi at work. I'll have to check into it since I control all of that stuff :p
[Verizon Samsung Galaxy S III] cornelious1212:
Have you had any problems with this camera? I had it installed for a few days, today went to take a picture, and it hung on a black screen after the picture for about 30 seconds. After that I got the "can't connect to camera". Rebooted and the camera would connect again, but would force a reboot when I took a picture. Just wondering if its just me.
[Verizon Samsung Galaxy S III] dvaderx:
I've tried official and un-official CM's, aokp. carbon roms. etc. (anything CM or CM based)

I was hoping 10.1 would offer a fix for this, but I grabbed cm-10.1-20130709-UNOFFICIAL-d2vzw.zip and still the same issue.

As soon as i go back to a TW based rom, recording is normal.

I will grab the latest CM nightly and make test recordings and post them so you can see/hear the difference.
[Verizon Samsung Galaxy S III] dpaine88:
Random reboot today here as well
[Verizon Samsung Galaxy S III] sivarticus85:
Now that you mention it, I just started having this issue. Guess it's not as stable as I thought. Sorry bout that. I used it for almost a week before posting it here, so I figured it was solid. Has a few bugs after all.
[Verizon Samsung Galaxy S III] Restola:
Its OK, until you hear it next to TW. And it depends on the setting/situation. Often I have to max out volume on YouTube and my computer to hear voices.

Older video, but its the same today on cm10.1.

https://www.youtube.com/watch?v=oI8fuL44mNQ&feature=youtube_gdata_player
[Verizon Samsung Galaxy S III] sivarticus85:
I thought the faux sound mod in some of the kernels would help this issue, since there's a setting for camcorder mic gain, but it doesn't work.
[Verizon Samsung Galaxy S III] Chris123NT:
Was driving around in a spotty signal area tonight and the 0/99 issue was the worst I've ever seen it. Could have been the area, but I seriously hope CM resolves it soon, it really is the last really big issue with CM 10.1. If they can get the RIL to be as good as it was on the later CM10 builds I would be so happy.
[Verizon Samsung Galaxy S III] dvaderx:
Yeah i thought and hoped the same thing, but it didn't really help.

---------- Post added at 09:10 PM ---------- Previous post was at 08:58 PM ----------

wow so i used a decibel measuring app and under the same exact conditions the TW rom recorded a 30 second test tone @ 67.2 DB

but when i switched to a CM 10.x rom it recorded 45-48 DB

I kept logs, so i will post up the results when i pull them from the phone
[Verizon Samsung Galaxy S III] dvaderx:
I don't want to hijack the thread to much but my results show there is about a 20-25 DB loss in the AOSP roms
[Verizon Samsung Galaxy S III] Chris123NT:
Just a heads up, I asked noobnl about the 0/99 issue and he pretty much said that it won't be fixed because it's a symptom of poor signal areas etc... He mentioned something about TW Roms having a higher retention time for signal which basically gives the illusion that they are better. It makes sense in a way I guess. Does anyone get call drops when the 0/99 thing hits? I haven't been on the phone when it hit in a while so I'm not 100% sure.
[Verizon Samsung Galaxy S III] MG386:
The 0/99 issue is with LTE data. Calls still run through CDMA, so its not likely the two have anything to do with each other.
[Verizon Samsung Galaxy S III] Chris123NT:
Okay, yeah figured it was an LTE problem since when I'm in an area that has the problem I can get data back by toggling LTE off and running on 3G.
[Verizon Samsung Galaxy S III] titanshadow:
Perhaps this is a dumb question but, what problem is this exactly? I have 2 jobs now so I can't keep up like I used to but I have noticed some odd data dropouts on my phone where it goes to 3G where it didn't before. Wondering if it is this bug or something else perhaps?

My first job is in a pretty bad reception area where it fluctuates wildly sometimes so it could just be that too.
[Verizon Samsung Galaxy S III] Stealth111:
I have to definitely disagree with noobnl's statement. I too experience this WAY too often, and it was all but fixed a few months back, but that is not my point. If you know about how a Verizon Network Extender works, then explian to me how the statement of poor signal is the cause of the 0/99? If I am sitting 1 foot away from my extender with 5 damn bars of signal, how do you explain away the 0/99 then, because it still happens then? Matter of fact, when I am at work, we have a tower just up the road, I get great reception there and still get 0/99. There is more to this... I really hope they don't give up on this bug, it really is a very big one...

Please don't take this as me yelling at you about it, but it is beyond frustrating to see it not get addressed, with the possibility of NEVER getting fixed. It makes the phone UNUSABLE... GET IT???? It needs fixed....

I am also sure some dweeb will reply " If you don't like it, don't use it". Save your breath, better yet, try to hold your breath for 15 minutes...

Chris123NT, this in NO WAY was directed at you....

Sent using Tapatalk
[Verizon Samsung Galaxy S III] titanshadow:
You know, I'm going to say it. Yeah, don't like it, don't use it. These developers don't owe you ANYTHING. Not a single solitary thing. You could perhaps try to learn how to code and try to fix it yourself since you have so many cases where you could test your work. Or is that just for other people to do and have you go OFF on them about it? And, hold my breath for 15 minutes? Grow up! If you want a professionally developed pure Google phone then go out and BUY one from Google.

Programming is hard. Programming a fix for an intermittent bug is harder still. Programming for a bug that you don't see and that is intermittent is insane. But if you think you could do better and it MUST be done because YOU need it so freaking bad then DO IT. But then, I would be willing to bet you've never written a device driver or other such thing that had to be reverse engineered, that you don't have the operating specs for or API call details for, or experience other issues that would come with hacking a device to build a custom ROM (not modifying one but building one from scratch), or perhaps you think the devs can call Verizon and be like... Yeah, that stuff the modem has to do to work with your network, yeah can I see that please? Or perhaps you think that if they ask Samsung they would get an answer?

Besides which, the actual usability of TouchWiz is a pain but it is a perfectly serviceable ROM, yes there is garbage tacked on, and no I don't like it either. However, you are getting CM for free. It costs you nothing. Either go back to TW, help develop the code to fix the issue, stop crying about it.

Or do you think that being a spoiled brat and yelling about it is going to make the developers cry real unicorn tears for your plight and work really hard so you'll like them? Have some respect!

Great job devs, please keep up the good work.
[Verizon Samsung Galaxy S III] Stealth111:
Boy, titanshadow, you are way off course on that rant. I wont even waste the time by pointing it out...

P.S. I am satisfied, however, with the taste of your unicorn tears! :D

Sent using Tapatalk