yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] s'pht:
Someone needs to add a commit to CM that takes the current "bar level" and add 1 then display the new value. Then the "signal problems" will go away and everyone will be happier.

You know kinda like size 10 pants at Lane Bryant being the same as a 16 at most other stores (ok, I'm guesstimating those figures, I don't buy women's pants at ANY store).
[Verizon Samsung Galaxy S III] Gordon Ramsay:
Actually lane Bryant uses standard sizing.
[Verizon Samsung Galaxy S III] funnyperson1:
There are two separate issues here though. I agree that the "number of bars" or even the "0 dBm" issues are not really a problem. I think most agree that signal strength is pretty much the same as TW.

There IS still a real issue with data-handoffs though. Now I'm not sure if it's really a "problem" with CM10.1 or if Samsung is just doing a much better job of covering up radio deficiencies with intelligent handoff mechanisms. However, in the areas where I live and work I am constantly bouncing between Wifi, 4G, and 3G and TW generally handles it in such a way that my operations are rarely disrupted. I can't say the same about CM and other AOSP ROMs, although I just flashed the latest nightly with last weeks RIL changes, so I'll see if that is any better.
[Verizon Samsung Galaxy S III] Div033:
There seems to be an issue picking up 4G in remote/low signal areas as well.

A few months ago I was in a cabin on vacation which wasn't too far from civilization. Verizon signal was still plentiful, and my brother's Rezound had a solid 4G connection. My CM10.1 GS3 only had 3G. Toggling airplane mode brought 4G back, but only for about a minute til it reverted back to 3G.

Frustrated, I flashed back to TW and voila, perfect solid 4G connection. There 's still some funkiness going on, and I've actually started learning programming (my friend is an expert C++ programmer, he's teaching me) so I can try and figure out what it is.

Hopefully the phone is still somewhat relevant by the time I have a decent level of understanding.
[Verizon Samsung Galaxy S III] pryorda:
Good luck!!!! Development is a long comber so me learning process and every one has there own style.
[Verizon Samsung Galaxy S III] mastamoon:
6/13 build in the OP

-- testing the new AV branch stuff along with the "NEXT" kernel. Let us know if you find any audio related stuff thats working better/worse

-- had to add back the 2 bluetooth reverts we were using prior as they are not merged in the NEXT kernel yet.

-- repo sync @ 9 AM EST
[Verizon Samsung Galaxy S III] dpaine88:
I agree on signal.

Just got a Samsung tab2 for work on Verizon.

I get 4g on the Tab and 3g on phone sitting right next to each other. Usually only in poor signal areas like a bar or two.
[Verizon Samsung Galaxy S III] goldsmitht:
Signal strength tied to phone radios, and not ROM or kernel. My wife has a RAZR M and gets signals where i don't, and WIFI where i don't as well.

may rethink another samsung, if it doesn't get better

:rolleyes:

---------- Post added at 01:21 PM ---------- Previous post was at 12:29 PM ----------

Did anyone else lose the ability to connect to computer to see files? Not sure if it is my setup on 6/10 version or what, but i can see it when i switch to AOKP latest. Haven't tested 6/13 yet.

like i said, i may have changed something, but any help would be appreciated.

thanks,

:confused:
[Verizon Samsung Galaxy S III] mikejr83:
Ktoonz latest kernel fixes this to some degree.
[Verizon Samsung Galaxy S III] soapinmouth:
Anyone else having an error when trying to install apps from the play store? I tried wiping data on it.

Sent from my liquid smooth gs3
[Verizon Samsung Galaxy S III] dpaine88:
Data connection is fantastic on 1-17 build

---------- Post added at 11:46 PM ---------- Previous post was at 11:41 PM ----------

What kernel aside from stock are people having success with?
[Verizon Samsung Galaxy S III] khaoskosmos:
KT747
[Verizon Samsung Galaxy S III] BlueCross:
Any way to use WiFi Tether - TrevE Mod on this ROM?
[Verizon Samsung Galaxy S III] goldsmitht:
Not sure if right forum, and apologize if wrong.

Dirty flashed 1/18 over 1/16; MMS that would go thru on 1/16 wouldn't go thru on 1/18. Same pic, same everything, just seemed to hang up and wouldn't go thru.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah its not downsizing the pic correctly so it won't go through. Will tweak on Tuesday. Till then pull MMS.apk out of 1/17 or earlier and use that. Just make sure you set permissions to rw-r-r then reboot.

http://d-h.st/BCD
[Verizon Samsung Galaxy S III] goldsmitht:
Went back to 01/16 for now, works great
[Verizon Samsung Galaxy S III] yznhmr:
What kernel would you recommend?..

---------- Post added at 03:13 PM ---------- Previous post was at 02:46 PM ----------

would a wake lock be when its not charging and screen is like 50% of your batt usage?
[Verizon Samsung Galaxy S III] mastamoon:
No that's normal screen on time.
[Verizon Samsung Galaxy S III] jspidah:
Must have gotten lucky.

Clean flashed 1/18, ran TiBu, and everything's working. GPS locked on within seconds, and I'm listening to Doggcatcher (which found my podcast instantly) on Bluetooth.
[Verizon Samsung Galaxy S III] luv2increase:
Mastamoon, will you compile your unofficial builds with Linaro? Liquid just came out with one, and I've been only flashing your builds lately. I think this will make our phones the fastest they can be.
[Verizon Samsung Galaxy S III] mpetruzz:
After playing a game or app that has a high CPU usage resulting in phone slowdown, is the only remedy a reboot??

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] soapinmouth:
Clearing recents and turning the screen off for a moment works for me

Sent from my liquid smooth gs3
[Verizon Samsung Galaxy S III] pmdied:
So is a2dp working for you guys?
[Verizon Samsung Galaxy S III] sparkerjc:
Listening to it right now. Only thing I noticed is if the phone is playing at low volume it gets loud and quiet on its own, at higher volumes its fine.
[Verizon Samsung Galaxy S III] pmdied:
This is huge! Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
http://review.cyanogenmod.org/#/c/30595/

This looks like it may fix a2dp officially.
[Verizon Samsung Galaxy S III] tducote:
(I'm a little new with this stuff so please be gentle.) This should be in the next official nightly build, yeah?
[Verizon Samsung Galaxy S III] bobby janow:
Do it! :) Sitting in nyc waiting on Moon.
[Verizon Samsung Galaxy S III] mastamoon:
Just plugged mine in.. and saw files.. worked on 6/11 and now on 6/13. You may have been bitten by the USB bug. Boot into download mode, plug into PC.. unplug and reboot.
[Verizon Samsung Galaxy S III] goldsmitht:
would that be the case if i can see it on AOKP? Rebooting into download mode takes the ROM out of the picture, and i wouldn't think it would affect it. I've had that bug before, and didn't seem to work until i clean installed. which i did with 6/10 to fix something else.

will try flashing latest and see what happens.

can you post the settings to make sure i have it all checked right?

thanks,
[Verizon Samsung Galaxy S III] Hybridnoob:
Which kernel are you running? If it's a custom kernel, do you have fast charge enabled?
[Verizon Samsung Galaxy S III] goldsmitht:
Update: AND... its working now in 6/13. NOT sure what was off in 6/10 for me, but alls well that ends well.

:good:

:D

---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------

that was my firs thought, so went through and cycled it on and then off. still wouldn't connect. BUT as my other post shows, its working now in 6/13

thanks,
[Verizon Samsung Galaxy S III] mastamoon:
Not sure what could have been off in 6/10. I would have had to plug my phone in on 6/11 (while on 6/10) to get my new build on my phone and didn't notice any problems. But its water under the bridge now! :P
[Verizon Samsung Galaxy S III] AdMire:
For what it's worth, there are times my phone won't connect to the computer either but every time I flash into recovery and wipe the caches and reboot and it connects. Not sure if wiping the caches is necessary but it works.
[Verizon Samsung Galaxy S III] sivarticus85:
What were some of the add-ons with the AV stuff in the new build today? Anything in particular we should notice?
[Verizon Samsung Galaxy S III] mastamoon:
Not sure really. From what I heard it may help some bluetooth lag when watching video. Hopefully you only notice good things and or nothing at all. :)
[Verizon Samsung Galaxy S III] mastamoon:
6/14 build in the OP

-- repo sync @ 2:30PM EST
[Verizon Samsung Galaxy S III] DvdOwens:
Firmware Flash

In order to avoid camera issues should I flash the " Recommended Firmware (VRBMB1) " after I flash this rom ? Or should I flash the firmware then the rom ?
[Verizon Samsung Galaxy S III] Obaterista93:
Afaik it doesn't matter which order.
[Verizon Samsung Galaxy S III] apacseven:
It definitely doesnt matter.
[Verizon Samsung Galaxy S III] mastamoon:
Camera issue should be resolved. If you want to run the latest firmware, you can run the full package now.
[Verizon Samsung Galaxy S III] MadWicket:
Mastamoon do you know anything about the sound issues when headphones are plugged in. The sound is blaring and I can't turn down the volume anywhere.
[Verizon Samsung Galaxy S III] mastamoon:
Did it just start?
[Verizon Samsung Galaxy S III] MadWicket:
No its been like this for a couple builds. Infant I don't think it's ever for me. If you don't mind checking my older post I described the exact problem I was having. There were other people having the same issues as well.
[Verizon Samsung Galaxy S III] sivarticus85:
I was just about to post something about that. It just started recently. Maybe something to do with the AV mods?
[Verizon Samsung Galaxy S III] ElementR:
Thanks for your work on this ROM. Any plans to add Halo?
[Verizon Samsung Galaxy S III] tv31284:
Does anyone know what CM's NEXT kernel entails exactly?
[Verizon Samsung Galaxy S III] apacseven:
I wouldn't count on that.
[Verizon Samsung Galaxy S III] GideonX:
Anyone else not able to record video on 6/13 or 6/14?

Went back to 6/10 and it works.

Stock everything.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Hybridnoob:
Working fine here on 6/14... Sorry man.
[Verizon Samsung Galaxy S III] funnyperson1:
Speaker phone is very quiet on 6/11 but the radio does seem to be quite a bit better than rc2. I also had issues with the bluetooth volume jumping around when getting directions and streaming audio.

I'll try the 6/14 to see if the new kernel changes anything.
[Verizon Samsung Galaxy S III] nbaj2k:
MHL for AppRadio 2 + AR Liberator??

I don't have an MHL cable, but does anyone know if the latest unofficial ROM has it working? I believe I read awhile back that it was never working on Cyanogen, but thought I'd check.

I've been looking to get a head unit for my car, and the Appradio 2 + AR Liberator combination looks like it would be exactly what I'm looking for (apparently I'm late to the game on this).

http://www.youtube.com/watch?v=gMJrdADRsEs

If anyone does have it working, anyone have experience with this combination and know if it works well? I'd love to be able to use in dash Google Maps and TuneIn. I don't want to drop the money on this if there are definitely going to be a lot of issues.

Any info on this would be great! Thanks in advance,

~J
[Verizon Samsung Galaxy S III] GideonX:
Time to wipe I guess, thx for the sanity check.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Jdelta9889:
Major issues??

I am thinking about giving this a try.. Anything that I should know about?? I only saw small issues with bluetooth and such in the previous pages.
[Verizon Samsung Galaxy S III] apacseven:
Bluetooth issues are the only problem I know of. Theres no reason not to give it a try. Make sure you flash the MB1 aio package before installing anything based on CM10.1, if you havent done so already.
[Verizon Samsung Galaxy S III] chadamir:
I'm on 6/7 which I know is a few days old, but I'm having an issue where the phone only rings once. Also, sometimes when texting, I will get a notification that I got a text message from the person I'm texting and I either have to mark it as read or clear notices. Expected behavior is that looking at the text within the txt message app would make it clear.
[Verizon Samsung Galaxy S III] mybook4:
I tried the 6/10 release and MHL didn't work. I reverted back to the 2/20 release because MHL works.
[Verizon Samsung Galaxy S III] funnyperson1:
Fyi speaker phone seems to work well on 6/14.
[Verizon Samsung Galaxy S III] sthpaw01:
Is ctsail still working with linaro? I wanted to try it out on this ROM again.
[Verizon Samsung Galaxy S III] mastamoon:
Been thinking of using this service, www.romdashboard.com, to allow update notifications and stuff like that for these builds. Not for any real reason besides being 'cool' to me. Made my first build with this integrated today. Anybody wanna install and test it out with me?

Ill probably do an 'update' later today but more likely tomorrow if nothing good gets merged.

On first boot you will get a notification with 3 options. The text is cut off so you cant see what it says. The left most selection is View. Click that then say OK to subscribe. I believe this is necessary for you to get updates. As you can see from the website, this is still very alpha so if things don't look right, deal with it :P

http://truelinux.net/sch-i535/mastamoon/cm-10.1-20130618-UNOFFICIAL-d2vzw-reverts.zip / 8ec09b5bdc4ebfbb21f5354a62dbfb7e

Thanks!
[Verizon Samsung Galaxy S III] s'pht:
I'm game - sounds.... fun? =)
[Verizon Samsung Galaxy S III] V3TTOO:
I haven't had any issues with blaring sound. I use speak, bluetooth, wired headset and wired to a speaker with no issues. Might want to try a clean install? Just back up and try a clean install. If it doesn't work, restore.

---------- Post added at 01:57 PM ---------- Previous post was at 01:55 PM ----------

Ill give it a go. You should update the OP with this info. :p I almost skipped this update. Here is more info on Masta's explanation. With pics! https://www.romdashboard.com/alpha/faq
[Verizon Samsung Galaxy S III] V3TTOO:
You took your link away for the latest firmware and the latest that you edited to have the TZ from the previous version. :(

Do you know how long it took me to find it online? 2 minutes. Ugg. :p
[Verizon Samsung Galaxy S III] mastamoon:
Lol sorry. The general consensus is that it's not good to run so I removed it.
[Verizon Samsung Galaxy S III] Reborn627:
I'm in

Ray
[Verizon Samsung Galaxy S III] V3TTOO:
Just saw that here: http://www.androidcentral.com/verizon-confirms-fix-works-galaxy-s3-s-android-412-update

Didn't see that anywhere were people were talking. Maybe put that in the OP in case someone heard of a newer firmware and tries it out. I am going back to VRBMB1 then. And that ROM dashboard thing works. Let's see if your next update shows up. It's cool cause you can push notifications too, not just ROM updates.
[Verizon Samsung Galaxy S III] sivarticus85:
I haven't had the issue since... Possibly just a fluke. All is working as it should now.

Gonna try out your idea Masta. Signing up as soon as I get home.
[Verizon Samsung Galaxy S III] m52 power!:
Not to sound too negative, but I don't think this ROM will ever be complete. Too many random bugs, too many features of the original missing. I love the look, feel and fluidity of CM but it fails in the most basic of ways to fail. Even worse, just because something is fixed doesn't mean it won't re-appear a month later when they try to fix another thing, but the fix for that breaks the other thing previously fixed!!! Its like having a million bucks, but when it comes to the real world its just monopoly money and bedazzler plastic diamonds.
[Verizon Samsung Galaxy S III] Hybridnoob:
I think you posted in the wrong thread.
[Verizon Samsung Galaxy S III] sivarticus85:
You're kidding, right? This ROM is one of the most stable stock 4.2 experience you'll find on this device. It's been my wife's daily for ages now.
[Verizon Samsung Galaxy S III] madhacker7:
Agreed. It just works. No muss no fuss. Nothing fancy. Just great performance and battery life. I'm sorry some folks don't see it that way. Great work masta.
[Verizon Samsung Galaxy S III] apacseven:
This is how development works, its a process. It sounds like the development process is a little too much for you to handle. Touchwiz is where you belong.
[Verizon Samsung Galaxy S III] dpaine88:
I agree for the most part.

Data and GPS leave a lot to be desired compared to TW, in my opinion
[Verizon Samsung Galaxy S III] funnyperson1:
Speaking about data and voice, can anyone confirm that simultaneous data and voice don't work on this rom?
[Verizon Samsung Galaxy S III] bobby janow:
Placebo. My gps is rock solid. Match it with tw any day of the week. Data... Well let's do a side by side. All about the signal vzw puts out. Imo, natch.
[Verizon Samsung Galaxy S III] Hybridnoob:
I use data and voice simultaneously often.
[Verizon Samsung Galaxy S III] dpaine88:
Just Goin by my experience man.

Plenty of times my GPS just won't lock even after 20+ minutes. Never happens on TW.

For the data, often times in areas I am very familiar with CM will bounce all around signal types or just not get any data at all.

Also I can put my VZW tablet next to this phone with 4g and yet the gs3 is only 3g.

Just a matter if these are worth the benefits of AOSP, my true love
[Verizon Samsung Galaxy S III] tv31284:
I didn't believe it till I tried it myself, but if you tighten the screws on the back GPS improves immeasurably. Honestly night and day. As for data, it's still not quite as good, but much better with all the new commits in the past month or so.
[Verizon Samsung Galaxy S III] bobby janow:
Yeah you've always had gps issues with aosp. And I can get a lock in 30 sec at 35000 feet. Go figure. My signal is fine all over too. Wonder what it could be. Well LS just put out 2.7. Gps lock instant.
[Verizon Samsung Galaxy S III] dpaine88:
Hmm but my GPS is awesome on Touchwiz.

I honestly thought data got a lot worse lately. The 0dbm thing went away several months ago but came back in full force lately.

---------- Post added at 09:05 PM ---------- Previous post was at 09:01 PM ----------

As far as signal strength, I know there is no difference.

But going into low signal areas is tough for aosp to handle keeping any signal st all
[Verizon Samsung Galaxy S III] bobby janow:
I agree. I just don't get it. What is wrong with these phones?

Edit... Have you looked at Goodness TW?
[Verizon Samsung Galaxy S III] myk.robinson:
Headset - Wake on Lock?

Hope this is the right place for this...

Everything is working fine for me in this ROM, except for one minor niggle...

Using either Bluetooth or the wired headset/mic that came with the phone, I cannot issue voice commands if the phone is locked. If I wake up the screen and unlock, I can hold the button and issue commands, such as dial, or whatever, using Google Now. But if the screen locks, the button does nothing when held. If i quick press it, it will play whatever song I was last playing in Google Music.

Seems like when locked, the music app takes precedence and long presses on the "call" button do nothing.

Is this an issue with the ROM, or an inherent problem with Jelly Bean, or a problem with this model phone? Is there a known fix for this issue?

Thanks,

-myk
[Verizon Samsung Galaxy S III] locozildjiangodx:
Weird....my GPS has been instantaneous and rock solid... I used to have an HTC Evo and I NEVER had GPS on that....but the GS3 with Masta has been perfect GPS.
[Verizon Samsung Galaxy S III] landale:
I will admit I had GPS problems for a while too but I just took mastamoon's advice and flashed back to TW, got a GPS lock and then went back to CM10.1 and have had no problems since. Data on the other hand I can understand as in weak areas signal isn't as good as TW but 95% of the time I have no problems.

I will add that since the new RIL was merged a few weeks ago there is a hallway in my apartment building I can no longer hold a call in, previously this was never an issue but now I got bad reception and drop calls. Not sure if anyone else has noticed this since the last RIL update? I even reverted back to before it was merged and did a test and had no problems.
[Verizon Samsung Galaxy S III] WhammyDroid:
I am a bit excited for this commit: http://review.cyanogenmod.org/#/c/43568/

Here is to hoping it fixes an issue I reported with dspmanager and lpa.
[Verizon Samsung Galaxy S III] mastamoon:
If you have been running my last couple builds, that was part of the av-test branch stuff I was using. So was your issue still present?
[Verizon Samsung Galaxy S III] WhammyDroid:
I am on the 6/11 build. Was it included then?
[Verizon Samsung Galaxy S III] mastamoon:
Nope :)
[Verizon Samsung Galaxy S III] WhammyDroid:
New build please!
[Verizon Samsung Galaxy S III] defTwitch:
Been busy with all kinds of RL stuff myself... just catching up on about 100 pages of reading and waiting for the next big build / update with new hawtness and stability to justify moving from such a stable daily driver of a much older version.

Thanks Masta!
[Verizon Samsung Galaxy S III] mastamoon:
ETA around 1pm EST. If your running my build from yesterday which is posted a few post up, you should get an update notification on your phone :)
[Verizon Samsung Galaxy S III] V3TTOO:
Got the notification and did the download. Pretty awesome! Link instructions in OP?
[Verizon Samsung Galaxy S III] mastamoon:
6/19 build in the OP

-- AV-TEST branches were merged so moved back to them, still using 'NEXT' kernel

-- bluetooth fixes are merged into the kernel now so should be all set

-- looks like the update notification works fine with this romdashboard site :good:
[Verizon Samsung Galaxy S III] mastamoon:
Yea, Ill add something in there soon.
[Verizon Samsung Galaxy S III] Reborn627:
Romdashboard worked perfectly. Got the notification right around 1:15 or so. Seemed like it downloaded faster than a manual download has in the past but maybe not.

Thank you,

Ray
[Verizon Samsung Galaxy S III] mastamoon:
Still using the same host so it shouldn't have changed but maybe you just got lucky today! :P
[Verizon Samsung Galaxy S III] funnyperson1:
That's odd, I was on the phone yesterday in full-bar LTE area (I could see 4-5 bars) but there was no data connection at all (bars were gray with no 4G symbol) until I got home and ended the call. This was on the 6/14 build.

I'll try the newer build and see if anything changes (although I don't see why it should).
[Verizon Samsung Galaxy S III] Hybridnoob:
What about putting these notes in the romdashboard announcement section? I know you said you won't use it, but that would be a good use...
[Verizon Samsung Galaxy S III] mastamoon:
I will have to play around with stuff for a bit to see what works/is worth doing. Still new :P
[Verizon Samsung Galaxy S III] WhammyDroid:
Well the audio issue I reported with DSP manager is not fixed with that commit.

Link to JIRA: https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-1355
[Verizon Samsung Galaxy S III] mybook4:
Navigation Bar Default

I'm trying not to sound like a noob, but I flashed the 6/19 build (wiped data) and the nav bar was enabled by default. The menu, back, and home buttons were also disabled by default.

Not a huge deal as I can simply overwrite/edit the appropriate keylayout files in /system/usr/keylayout and edit the build.prop to comment out qemu.hw.mainkeys=0, but I'm not sure why this was on by default.

Was this intended?