yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] cesium:
Anyone having problem with really spotty reception since flashing the modified radio package? Also getting phone.apk force closes. Running 5-31 with system and caches wiped.
[Verizon Samsung Galaxy S III] sivarticus85:
The new modem sucks a$$. I switched back to MB1. Not having phone.apk issues though.
[Verizon Samsung Galaxy S III] goldsmitht:
If you Google it, or read other forums, you'll see that the upgrade / new modems, are having problems. Most people who tried it, have gone back
[Verizon Samsung Galaxy S III] titanshadow:
Yeah, I've noticed that I've had to reboot the phone to make calls a few times and reception has been absolute ****. I'll probably switch before before too much longer, though I like to give a new modem time to see if perhaps the network has to adjust or something. Sounds silly saying it though. :P
[Verizon Samsung Galaxy S III] mastamoon:
I added the B1 firmware pack to the OP as the recommended firmware for now. I switched back after having a total data drop on my way home from work. Will wait to see if anything pops up from VZW in regards to this update causing issues.
[Verizon Samsung Galaxy S III] jalewis:
I had the same results with the new modem. Does anyone know where I can find the modems that were released before MB1? I know that reception is typically lower on AOSP roms, but I'd really like to try the older ones to see if they work better in my area.

Edit:

Nevermind, I found them here: goo.im/devs/invisiblek/i535. You'll have to add the http, I can't post an outside link until 10 posts.

---------- Post added at 10:16 AM ---------- Previous post was at 10:06 AM ----------

Can I flash just the modem? Or do I need the RPM as well?
[Verizon Samsung Galaxy S III] V3TTOO:
Why would you want pre-B1 modem? I thought the problem was with D3 modem, that was just released.
[Verizon Samsung Galaxy S III] Ymees:
On 06/03 but still getting BT disconnects. Any ideas?
[Verizon Samsung Galaxy S III] jalewis:
Because there are people that have seen worse reception from the B1 modem and have gone back to LK1 or LK3 with more success. I want to try a couple different ones to see how they affect the reception in my area.
[Verizon Samsung Galaxy S III] mastamoon:
6/04 build in the OP

-- repo sync @ 11:00 AM EST
[Verizon Samsung Galaxy S III] PerCompLLC:
Doesn't look like there's much of anything new...
[Verizon Samsung Galaxy S III] mastamoon:
Yep nothing much to speak about.
[Verizon Samsung Galaxy S III] V3TTOO:
Oh alright. Thank you for clarifying that.
[Verizon Samsung Galaxy S III] Reborn627:
Just an FYI, Bluetooth MAP seems to be working. Well, at the very least the authorization for the Ford Sync system to access messages is now working. I'm still waiting to receive a text to verify that it is fully functional. If any reading this were involved in getting MAP back into CM10.1 I am very grateful. Thanks for your hard work!

Peace,

Ray
[Verizon Samsung Galaxy S III] fromthesticks:
Bx.

Edit: was cleaning screen. Posted by accident
[Verizon Samsung Galaxy S III] mastamoon:
Yeah there was some movement on it last week. It seems more functional than it was, but it still doesn't work for me on my pioneer head unit and my brother just bought a new car and it tells him "transfer messages" but eventually it says "messages didn't transfer".

https://jira.cyanogenmod.org/browse/CYAN-41
[Verizon Samsung Galaxy S III] mastamoon:
06/05 build in the OP

-- Some moar RIL tweaking by NOOBNL

-- repo sync @ 3PM EST
[Verizon Samsung Galaxy S III] goldsmitht:
regarding the BT disconnect bug; I've always gotten it, and still do. HOWEVER, ONLY when i go outside of my car. When i'm in the car, and the phone is on center console, no disconnects. but let me step ONE foot out of the car, and instant disconnect.

It usually reconnects, and especially when i go inside, as long as i have service. Maybe the problem is the bluetooth signal being put out by the phone is too low?

just an idea from the peanut gallery

:rolleyes:
[Verizon Samsung Galaxy S III] mastamoon:
I actually had my bluetooth get stuck today when in my car. Had to stop all the bluetooth services to get it to work again.
[Verizon Samsung Galaxy S III] RED ZMAN:
^^^

Sucks doesn't it? I haven't had to do that but maybe once in the past few weeks, the build I'm on has decent bluetooth.

Hearing about this getting worse again has kept me from updating. Thanks for keeping up the good work man.
[Verizon Samsung Galaxy S III] juancaperez2000:
Maybe just me but new RIL loocks like working really good
[Verizon Samsung Galaxy S III] goldsmitht:
Was the new ril incorporated in cm10.1 base, or something you built in
[Verizon Samsung Galaxy S III] mastamoon:
Hasn't been merged yet - http://review.cyanogenmod.org/#/c/43476/
[Verizon Samsung Galaxy S III] mastamoon:
Today's build is even better. Really coming along nicely.
[Verizon Samsung Galaxy S III] jdubau55:
So I should wait for the 6/6 build or go ahead and flash the 6/5 build?

Been away for a while too....how is photosphere coming along? I downloaded a modified version that is supposed to work well with recent builds.
[Verizon Samsung Galaxy S III] juancaperez2000:
Niiiiice!!! thanks Masta
[Verizon Samsung Galaxy S III] mastamoon:
I'm holding off till my usual build time to see if anything else gets merged or if the RIL gets updated further. 6/5 works fine.
[Verizon Samsung Galaxy S III] V3TTOO:
I had the same issue. I restarted since it is quick and doesn't hurt to reset all the stuff that was in cache and ram.
[Verizon Samsung Galaxy S III] goldsmitht:
as usual, you are ahead of your time; well, of the official time.

:cool:
[Verizon Samsung Galaxy S III] bobby janow:
Except if you use your phone for business and family and can't afford to miss a call. Other than that, yeah. It shouldn't happen and won't once it's fixed.
[Verizon Samsung Galaxy S III] RED ZMAN:
"At the freezing of the bluetooth, the Official Time is 1:35"
[Verizon Samsung Galaxy S III] mastamoon:
06/06 build in the OP

-- Repo Sync @ 3:10 PM EST

There was another RIL patchset commited since the 6/5 build further cleaning it up. Reduced the time it takes for the radio to come up after a reboot.
[Verizon Samsung Galaxy S III] AdMire:
You still recommend using the MB1 aio zip?
[Verizon Samsung Galaxy S III] mastamoon:
So far yeah. Until we get source for D3 or samsung/Verizon push another update like they should since lots have issues even stock with d3.
[Verizon Samsung Galaxy S III] PerCompLLC:
Not sure what changed with today's build, but my custom image on my lockscreen went away. So I tried to put one back and it won't take. Maybe a bad download?
[Verizon Samsung Galaxy S III] mastamoon:
Could check the merges between yesterday and today. I skim through them and don't remember anything about this topic but never know.
[Verizon Samsung Galaxy S III] mastamoon:
Maybe http://review.cyanogenmod.org/#/c/43630/ ? But mine didn't disappear.
[Verizon Samsung Galaxy S III] PerCompLLC:
I should add that my custom image on the lockscreen was different from my wallpaper on my homescreens.
[Verizon Samsung Galaxy S III] julesism:
I wiped/clean flashed 6/6 and have also lost the ability to set a custom lockscreen wallpaper. I can choose/set a custom image but at the end of the day it only shows my default wallpaper. no biggie.
[Verizon Samsung Galaxy S III] senorbuck:
Experiencing the same thing. Homescreen and lockscreen are the same no matter what I set the lockscreen to.
[Verizon Samsung Galaxy S III] mastamoon:
Ok, same thing here. Someone logcat and report to jira. :sly:
[Verizon Samsung Galaxy S III] PerCompLLC:
I feel better knowing that it wasn't just me... :eek:
[Verizon Samsung Galaxy S III] goldsmitht:
Can do a solid color, guess just not a custom image
[Verizon Samsung Galaxy S III] Reborn627:
I finally received a text while in my car today. I can confirm that the MAP function is now working on the gen 1 v 4.0.3 ford sync system. Not sure about other systems but after repairing my phone it is now working.

Peace,

Ray
[Verizon Samsung Galaxy S III] locozildjiangodx:
Does this mean AVRCP 1.3 is now active? For example, is the phone pushing artist/song info via bluetooth? (I know Google Play has this feature, but it hasn't worked on 10.1 yet).
[Verizon Samsung Galaxy S III] Reborn627:
This functionality, as far as I know, is unrelated to AVRCP. I believe there is a team working on AVRCP but I'm not sure where they are at with it. I did load up Play Music to see if any of the info you've mentioned is displayed on my bluetooth system and it was not. That doesn't mean it doesn't work, it just means that it doesn't on my stock 2011 ford system. Only way to find out is try it.

Ray
[Verizon Samsung Galaxy S III] mastamoon:
That commit broke it... ill revert for my built today. Which will be an early one cuz I have a half day at work today! :good: :victory: :cyclops:
[Verizon Samsung Galaxy S III] terpsarlington:
it was already reverted this morning

http://review.cyanogenmod.org/#/c/43918/
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I reverted it lol.. but not merged so the revert needs to be cherry-picked. But the author wants another commit tested that should fix.
[Verizon Samsung Galaxy S III] jguns112:
Not sure if this is rom related or not but on 5/29 data usage is reporting that Google Play Store has used upwards of 2 GB of background data. I'm hoping this is just an error in the reporting.. anyone know anything about this?

I flashed the 6/6 build earlier today so hopefully that fixes this.
[Verizon Samsung Galaxy S III] mastamoon:
Known issue.. but thought it was cleaned up. Its a false report, you can safely ignore.
[Verizon Samsung Galaxy S III] mastamoon:
Build is running now, with http://review.cyanogenmod.org/#/c/43919/ which should clean up the lockscreen wallpaper issue. (hopefully)
[Verizon Samsung Galaxy S III] senorbuck:
Hooooooray! :good::good::good:
[Verizon Samsung Galaxy S III] locozildjiangodx:
Gotcha....oh well....one can hope, right? I'll test it anyways.
[Verizon Samsung Galaxy S III] mastamoon:
6/07 build in OP

-- cherry-pick to fix custom lockscreen backgrounds - works!

-- bluetooth reverts/fix was merged -- removed from my list

-- repo sync @ 11:00AM EST
[Verizon Samsung Galaxy S III] Reborn627:
Thank you...It may just be me, but it seems that there were some stability issues with this one after flashing. I did reboot and things seem to be closer to normal. Has anybody else experienced some quirkiness after flashing this recent build?

Ray
[Verizon Samsung Galaxy S III] mastamoon:
I flashed around 11:20am and haven't seen anything wrong yet. What were you doing when things went.. quirky?
[Verizon Samsung Galaxy S III] Reborn627:
It was right after flashing. It did the "android has been upgraded optimizing apps". Once it finished, the lockscreen loaded. I didn't get right to the phone so it went to sleep. At that point I was unable to get it out of sleep. After pressing the home button then the power button a couple of times it did a soft reboot. Once it reloaded I rebooted and things have been Ok since. Probably wasn't worth mentioning now that things are working properly. I was just curious if anyone else had seen anything similar.

Peace,

Ray
[Verizon Samsung Galaxy S III] titanshadow:
Bluetooth works beautifully in RC5. Thanks. :)
[Verizon Samsung Galaxy S III] xHoLyx:
Bluetooth working as it should. Thanks Masta!
[Verizon Samsung Galaxy S III] icedmayhem:
I am now getting the infamous rpc:s-5:aec-0 play store error. Tried everything I found online. Removing account, adding second account, force closing clearing data, fixing permissions, factory reset.. It's on every device I own too. If I add my account to another device, same issue of that device. I can't believe this is happening. I hope no one gets this issue. It just happened two days ago. Great building btw, needed to vent for a hot second

Sent from my Galaxy
[Verizon Samsung Galaxy S III] funnyperson1:
So do the new ril changes seem to make a difference in data handoffs?
[Verizon Samsung Galaxy S III] sivarticus85:
It's better than it was, but still not as strong as TW. It's very close though, but I still find that my battery takes a heavy hit when I'm in a low signal area, because it's not able to sustain a consistent connection.
[Verizon Samsung Galaxy S III] jguns112:
Alright well that's good to know. It seems to be fixed on 6/6.. Must have been an issue from dirty flashing.
[Verizon Samsung Galaxy S III] Div033:
This might be placebo but I've been noticing less 0dbm instances... It still happens though. I think TW still has a leg up on AOSP still when it comes to signal.
[Verizon Samsung Galaxy S III] funnyperson1:
Thanks for the info guys, I'm on touchwiz right now after a couple really inconvenient data drops while traveling on RC2. Touchwiz really does an amazing job of switching between Wifi and 4G or 4G and 3G when necessary. It almost seems like they maintain a backup connection and switch as soon as the faster connection is dropped whereas AOSP waits until the connection is dropped to look for something else. I wonder if there is some sort of daemon in the touchwiz roms that handle this separately from the RIL.
[Verizon Samsung Galaxy S III] senorbuck:
Latest and greatest is running fantastic! Thanks Masta :)
[Verizon Samsung Galaxy S III] mastamoon:
6/10 build in the OP

-- custom lockscreen background got fixed-- removed cherrypick

-- new RIL got merged -- removed cherrypick

-- repo sync at 3:10pm EST
[Verizon Samsung Galaxy S III] MWFD:
On 6/7 build, I'm still having trouble with Bluetooth audio/volume. When using Bluetooth in my car on a phone call, the audio is very low. I have to move the slide volume win my fingers on-screen back-and-forth to get the volume to go back to normal levels (using volume rocker does no good even though the levels appear to be moving) anyone else experiencing this or know of a fix?
[Verizon Samsung Galaxy S III] jalewis:
On the 6/10 build, the cLock weather text color will not change to another color. I can select another color, but the text stays white.

Also, I'm not getting any contact photos from Facebook. I've experienced this on earlier builds as well. Anyone else?

Otherwise an excellent rom. The signal definitely looks better with the new RIL patches. Thanks.
[Verizon Samsung Galaxy S III] WhammyDroid:
All,

I have submitted a new fault report on JIRA for CM10.1 RC5. This issue has been happening for a really long time on CM10 and CM10.1. Thought I would take the time to write up a fault report.

DSP Manager Overamplifies Sound on Headphones

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

Check it out and vote for it.
[Verizon Samsung Galaxy S III] mybook4:
MHL HDMI

I just switched to the 6/10 build from the 2/20 build (I know, I know, I should flash more often). I love how the kernel uses more RAM!

MHL (HDMI) was working previously in the 3.0 kernel before the switch to the 3.4 kernel. I searched the thread and saw that the last time we've talked about it was a month back. There was a request for logs and then it kind of trailed off (that I saw, I could be wrong or missing something). I bring it up not to complain, but to help complete the ROM. Almost everything seems to work great. I'd like to help get HDMI working again.

I performed a logcat of while plugging in and then unplugging my MHL adapter (by running "logcat > hdmiLog" in terminal emulator). I utilize the Monoprice adapter (has worked well previously). Full pastebin here. A quick search for HDMI yields the following results:

D/qdhwcomposer( 318): handle_uevent sending hotplug: connected = 1
D/qdhwcomposer( 318): hwc_getDisplayAttributes disp = 1, width = 1920
D/qdhwcomposer( 318): hwc_getDisplayAttributes disp = 1, height = 1080
I/DisplayManagerService( 8813): Display device added: DisplayDeviceInfo{"HDMI Screen": 1920 x 1080, 60.000004 fps, density 320, 320.0 x 320.0 dpi, touch EXTERNAL, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, rotation 0, type HDMI, address null}

and

D/qdhwcomposer( 318): handle_uevent sending hotplug: connected = 0 and dpy:1
I/DisplayManagerService( 8813): Display device removed: DisplayDeviceInfo{"HDMI Screen": 1920 x 1080, 60.000004 fps, density 320, 320.0 x 320.0 dpi, touch EXTERNAL, FLAG_SECURE, FLAG_SUPPORTS_PROTECTED_BUFFERS, rotation 0, type HDMI, address null}

I hope this helps.

P.S. Saw this on jira. At first glance, it seems related.
[Verizon Samsung Galaxy S III] stearic:
I've been having this issue over bluetooth myself. Finally figured out it was dsp manager that was doing it. I could tell things were off when i tried other programs that didn't use/go through dsp manager. Now if we could figure out what exactly is causing it. I'm glad to have figured out it was dsp manager, now i can use the phone in my car again finally.
[Verizon Samsung Galaxy S III] MadWicket:
This is absolutely true. I even encountered this while plugged into the Samsung dock, with the headphones plugged into the back of the dock. When I went to turn the volume down it wouldn't let me with the volume rocker or with the touch Screen. Neither would going to the volume settings during play would it let me reduce the volume. Again this was with headphones plugged into the back of the Samsung dock.
[Verizon Samsung Galaxy S III] sivarticus85:
Facebook contact pictures don't sync. Use Haxsync or Ubersync to to do this. It's never worked and I don't know if Google/FB will ever fix it.
[Verizon Samsung Galaxy S III] stearic:
Not only does haxsync (not sure about ubersync) sync the pics, the pictures are also higher res pics then what you would get by default with how facebook sync used to do. I say it's well worth the purchase price if you (like most people) prefer to have pics attached to their contacts.
[Verizon Samsung Galaxy S III] V3TTOO:
FB sync has been out since Google introduced Google+ and maybe some time before that. Usually it is allowed through MFG UI, like SenseUI and TouchWiz, but not sure if they still do. I started using HaxSync a while back and I love it. It saves high res pics for profiles, uploads them to the Google contact itself, so it doesn't matter if they delete their FB because it is saved to their Google contact. It also saves some "metadata" to the note of the Google contact so if you get a new phone or change the info, it still links it to the correct FB account. It syncs the FB events with your calendar, adds their updates to their Google contact on your phone, and a few other things. Sorry if it seems I am selling it, but it is the best thing I have purchased on Google Play.
[Verizon Samsung Galaxy S III] WhammyDroid:
Please go and post these comments in the official thread. It would really help the cause. I made the same post in that thread a page or two back.

Thanks!
[Verizon Samsung Galaxy S III] senorbuck:
Ubersync works great! Can sync a few options regarding your contacts. Can even pic the res of the contact pic. Been using it for months now.
[Verizon Samsung Galaxy S III] jalewis:
It's currently working on the Liquid Smooth roms, but I'll take a look at Haxsync and Ubersync.
[Verizon Samsung Galaxy S III] Ty07allstar:
I mentioned this a while back and nobody really said anything about it so I gave up and just continued to use TW. This is the only reason I'm not using CM10.1. Hopefully somebody can get this fixed. I am more then willing to test for anybody willing to try to fix hdmi out.
[Verizon Samsung Galaxy S III] mybook4:
Yeah, if I had to guess, I'd say its something in the 3.4 kernel (since it worked in the 3.0 kernel). I'm not sure how hard it would be to fix/revert.
[Verizon Samsung Galaxy S III] funnyperson1:
The proper way to submit bug reports is to submit them to jira after verifying that they exist in the official rc builds.
[Verizon Samsung Galaxy S III] MWFD:
Can anyone give a quick list of advantages that the 3.4 kernel has over 3.0? Seems to me that right now that the last nightly w/3.0 kernel (I think 3/13) would be more stable/better than the newest nightly?
[Verizon Samsung Galaxy S III] Stupifier:
I recently converted to the 3.4 kernel over 3.0. My opinion so far is that 3.0 kernel is much more battery efficient. I was having an easier time getting into deep sleep and holding charge overnight with 3.0 kernel. I remember only dropping like 2-3% while I slept overnight.

I might have to just tweak the 3.4 kernel more to get back to what I had before. It is hard to tell.
[Verizon Samsung Galaxy S III] mastamoon:
6/11 build in the OP

-- repo sync at 10:10AM EST
[Verizon Samsung Galaxy S III] dpaine88:
Anyone know why Android System usage would be 45‰ in battery stats?
[Verizon Samsung Galaxy S III] stearic:
Not something specific with the 3.4 kernels. I had this issue back with the 3.0 kernels. It might be something specific to the chipset i'd say.
[Verizon Samsung Galaxy S III] V3TTOO:
Maybe cause that is all you did for 21 hours on your phone? If you don't use it, the phone is still acting like a phone, which happens to be running on the Android System.

**That is my opinion and not to be taken as a solution or remedy for headaches. Please see a physician before taking any opinions from the guy posting this as it can be detrimental to your health.**

---------- Post added at 02:45 PM ---------- Previous post was at 02:45 PM ----------

Oh, any chance we might be seeing this in a build, Masta?

http://www.androidcentral.com/paranoid-android-team-open-sources-its-halo-multitasking-feature
[Verizon Samsung Galaxy S III] jalewis:
I'm at 14.5 hours on battery with only 5% being android system. 19% cell standby and 30% screen...
[Verizon Samsung Galaxy S III] dpaine88:
See that's the thing, I was using a ton of apps and over 2 hours screen time, just isn't showing any apps on the battery page
[Verizon Samsung Galaxy S III] dpaine88:
Anyone else getting 0dbm 99asu fairly often?
[Verizon Samsung Galaxy S III] juancaperez2000:
Im like that in this moment
[Verizon Samsung Galaxy S III] mastamoon:
Its been looked into.. apparently it is an oddity that comes from the modem that the phone doesn't know how to display. I still have data when it is in this state so I think the only cosmetic. I dont think it will be 'fixed', but you never know. It just needs to annoy the right dev for long enough usually :P
[Verizon Samsung Galaxy S III] funnyperson1:
Is this commit related?

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

I know Shareef abandoned it, I for one wouldn't mind playing around with it because I wonder if the remaining data drop/handoff issues are related to a poor representation of signal strength. I just wonder if there's any reference on what needs to be done, or if the devs are forced to reverse engineer the information the modem is trying to present.

The odd thing I guess is that the 0dBm issue never occured on CM10 that I can remember.

I could have sworn that there was an IRC channel just for d2vzw devs, but I can't find it anymore.
[Verizon Samsung Galaxy S III] Gordon Ramsay:
Do you guys think that the gap between aosp and tw in regards to data reception/performance/handoffs has shrunk or become non existant?
[Verizon Samsung Galaxy S III] MG386:
Yes. The bars might look different, but comparing db levels with several un rooted stock i535 phones, they r the same.
[Verizon Samsung Galaxy S III] mastamoon:
It was probably something that changed when the jump from 4.1.1 and 4.1.2 radios happened (or whatever the jump was. At some point I thought we had to upgrade our modems to have data on CM. (I think).. As Shareef/Noobnl has explained to me is the 0dbm is happening when the modem sends a value that he called 'max init' which our RIL or hardware cant display. Ive seen as high as -116dbm I think.. the cut off might be when the modem is sending something 'higher' than that.. meaning -120dbm or higher. TW ril knows what to do with this value.. AOSP/CM doesnt. But like I said before, I think it is mostly cosmetic as when I have 0dbm 99asu, I still have a data connection.
[Verizon Samsung Galaxy S III] goldsmitht:
There was a big discussion in Synergy forum on XDA regarding how TW was reporting higher than actual bars. I can't find it and i don't want to go into what it was cuz the memory just isn't there, but if someone is really interested, thats a starting point.

:confused: