yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] dlongb13:
I hate bringing this up, but what is the SD card deal. Was on a TW Rom, flashed this, none of my files are on my SD card now. I have no "0" folder in there either. I have scoured my phone using root explorer and they are nowhere to be found. So I restore back to TW, and they are all there again, so they aren't being deleted. I am using the latest TWRP recovery. This has happened to me a few times now. Not sure what others are doing when this happens. Even my photos aren't showing up in the gallery and when I connect to my pc there is nothing their as well. Any help would be greatly appreciated.
[Verizon Samsung Galaxy S III] Recon0212:
Cool man, everything works, even BT in my car! I'm getting 0dBm sometimes in my house. But I can still make calls and texts so I don't know.

Otherwise 1/18 is running great!
[Verizon Samsung Galaxy S III] ddggttff3:
Thats a feature of CM10.1 due to the new jellybean and the multi user system. This is NOT a glitch or error.

EDIT: there is a thread in Q&A for questions like this, don't post here without a logcat.
[Verizon Samsung Galaxy S III] dlongb13:
Yes I understand it is not a glitch. I was just looking for some quick info as to how I retrieve my data easily. No need to get bossy boss. It is just the internet.
[Verizon Samsung Galaxy S III] Restola:
mnt/shell/emulated/0

I can find it using es file explorer

Tapatalk via CM10.1 Galaxy S3
[Verizon Samsung Galaxy S III] mpetruzz:
I just noticed that when I stop playing a game my phone is super slow. Screen transitions, opening apps etc are all cf crawling. A reboot fixed it. Anyone else noticing this??

sent from my blue police box flying through time!!!
[Verizon Samsung Galaxy S III] mastamoon:
Yes well known issue without resolve.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah if you have no bars and check out your signal in about phone you will see 0dbm.
[Verizon Samsung Galaxy S III] tducote:
So it seems like receiving and sending MMS does indeed work with the stock Messaging app on your 1-17 build. It does not work in Handcent. Just wanted to give my experience.
[Verizon Samsung Galaxy S III] Amphibliam:
I get this issue sometimes, but it never actually drops. The interwebs, calling, and texting all work.
[Verizon Samsung Galaxy S III] mastamoon:
I use bluetooth daily and haven't seen anything like that. I would force close the bluetooth apk and reboot.

Yeah disable HW Overlays in developers settings for now. I may add the build prop to the next build that usually clears this up until it's figured out.
[Verizon Samsung Galaxy S III] NegativeOne:
Thanks, I know the workaround, just wanted to report it as I hadn't had such problems until recent builds (not for a while)
[Verizon Samsung Galaxy S III] airmaxx23:
I had the same problem showing the same times even though bluetooth is off and has been off the whole time. It happens on the official and unofficial builds, even on the 5/25 build. I've tried stopping BT and clearing data but it doesn't help. The 5/22 Official nightly is fine.
[Verizon Samsung Galaxy S III] jguns112:
I had this issue right after I flashed 5/23 but it went away after I recharged the phone. I haven't had any noticeable battery drain either, so I think it's just an error with the battery report.
[Verizon Samsung Galaxy S III] xHoLyx:
Reverted back to RC2 for a time being.
[Verizon Samsung Galaxy S III] titanshadow:
I just loaded it and while it makes my Bluetooth work, I will happily post on whether or not my bluetooth eats my battery tomorrow, after some testing.
[Verizon Samsung Galaxy S III] Div033:
So while I was driving I had turntable playing music through AUX output and used navigation while the screen was off.. I got a phone call and the screen didn't turn on automatically, but did when I pressed power. Caller ID showed Unknown as the caller, but when I answered it was my friend who I have as a contact.

Has anyone else experienced this? I'm using leankernel 6.0 and flashed the new ril build.
[Verizon Samsung Galaxy S III] cesium:
I experienced similar today while playing music in the car, although for me I didn't even get a ringer and music kept on playing. Although I didn't wipe system so I'm going to do that and see if it fixes my issues.
[Verizon Samsung Galaxy S III] Div033:
Mine was a clean wipe. Bummer. Wonder what's causing it.
[Verizon Samsung Galaxy S III] cesium:
I can confirm that wiping system fixed the phone issue for me. Not sure what's causing it for you then :confused:
[Verizon Samsung Galaxy S III] Div033:
I haven't experienced it since then, and I've had my phone plugged in and playing music during a drive (without navigation). The caller showed up correctly when I got a call. I literally changed nothing.

I came from a TW ROM so I had no choice but to do a full complete wipe (data and system). I have reservations that wiping system will fix it. I'm thinking this issue occurs sporadically and will be difficult to reproduce. Let us know if it happens to you again in the future.
[Verizon Samsung Galaxy S III] titanshadow:
I can also say that I am getting a lot of screen flickering, almost every time I go to unlock the phone the screen looks garbled and flickers.

---------- Post added at 01:45 PM ---------- Previous post was at 01:28 PM ----------

@mastamoon just FYI, when I updated to the 5/24 ROM on my tablet it shows the same bluetooth problems and uses a different Kernel version than the SGS3.
[Verizon Samsung Galaxy S III] RED ZMAN:
Just go ahead wipe system guys. All you have to do is reflash G apps afterwards. It fixed my longstanding Bluetooth problem.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] Restola:
hey mastamoon, were you ever able to figure anything out with the recording volume? The topic has popped up once in a while over the last 6 months but it seems to be 'good enough' to not warrant dev time. It's like 80% ok as it is (if you max out volume in youtube and on my computer)...heh...but when I compare it to my wife's stock TW it's like night and day.
[Verizon Samsung Galaxy S III] Obaterista93:
I think the verdict was given that it was a fault with AOSP in general, not just with our phones. I know a few users said that the volume was on par with their nexus, so it might be some sort of post processing that Samsung does with TW.
[Verizon Samsung Galaxy S III] Masterfisto:
Has anyone else noticed really low vibrate intensity for notifications in the latest build? I just came from Beans 15 which had what i would call a normal level of intensity. Any way to change that?
[Verizon Samsung Galaxy S III] btonetbone:
That is from a setting that got merged in April.

http://xdaforums.com/showpost.php?p=40546034&postcount=2423

Go to Settings -> Advanced -> Haptic

I put mine back to 100%.
[Verizon Samsung Galaxy S III] RED ZMAN:
I'm on the May 14 build and having issues with USB tethering. I have the option to turn it on when I plug it in, but the other device doesn't seem to get data. It's also not showing up correctly in the Log View on that device.

Anyone having similar issues with USB Tether?

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] MWFD:
anyone else receiving text/email notifications & ringtone coming through the speaker AND the wired headset when plugged in? I want it to go just to the wired headset and not the speaker
[Verizon Samsung Galaxy S III] RED ZMAN:
Masta, to give you some info on what I'm talking about for USB Tether issues...

https://developer.android.com/refer...bConstants.html#USB_CLASS_WIRELESS_CONTROLLER

My S3 isn't being shown as a 244 class device, it comes up as class 0.

http://rootzwiki.com/topic/37755-ti...ost-power-management-usb-audio/page__st__2870

Hope this helps some.
[Verizon Samsung Galaxy S III] mastamoon:
5/28 build in OP

-- Dalvik, SKIA and Kernel patches (hopefully fixes the need for disabling hw overlays and gives you some moar ram)

-- some kernel reverts to hopefully fix up BT issues that were introduced a few weeks ago

-- if you couldnt launch your lockscreen camera in landscape, try it now :)

-- repo sync @ 12:30PM EST

Let me know if you have any thing get fixed or broke.. thanks!
[Verizon Samsung Galaxy S III] mastamoon:
Has this ever worked?

If you plug your phone into your PC, does it by any chance not connect and only charge?
[Verizon Samsung Galaxy S III] RED ZMAN:
I don't know if it has ever worked, I just recently started trying it because of the latency with Wi-Fi tethering. And charging benefits with both my s3 and nexus 7 (in dash).

No, I get my s3 as a drive on my PC if I plug it in.

Blasted from my Samsung Galaxy SIII (CM10.1 Masta Mix).
[Verizon Samsung Galaxy S III] ddggttff3:
Um, wow... I gained a lot of RAM! (now shows 1820MB) Thanks man, so far its running great and smooth!
[Verizon Samsung Galaxy S III] mastamoon:
Ok, just checking because sometimes the USB port on these phones acts weird so thought maybe it was in one of those moods/modes :P

Has anybody else used USB tethering on CM10.1 at all? Let us know.
[Verizon Samsung Galaxy S III] GideonX:
Just a FYI, the kernel reverts will fix the BT problems. I have a bunch of confirmations from a BMS test build I did this morning.
[Verizon Samsung Galaxy S III] RED ZMAN:
I can confirm that it partially works. For example, I get the ability to activate it on my phone, and after doing that.SOME apps on the Nexus 7 will receive SOME data.

For example...

1. Google Maps didn't work at all - Says "No data connection"

2. Waze, partial data connection, allows reports but no viewing of traffic conditions, other Waze members, or scoreboard. Occasionally says no data connection.

3. Play Store - Usually allows me to open and view, view installed apps.

Same on my wife's CM10.1 Note II.

The developer of USB ROM is extremely supportive and responsive. He told me he has several phones on CM10 and it is working on his. In the thread I linked, it seems some folks are working others aren't.

His phones were the Nexus S and the Galaxy Nexus.

He stated...

Nothing that I know of.
[Verizon Samsung Galaxy S III] mastamoon:
Honestly I don't know about any of that. If we were able to know that it did work in the past and around what date, I could look into what broke it. Without that, I would say try and collect as much info as possible by flashing Official CM10.1 RC2 and getting some logcats of the various situations you posted. Then take that info and make a bug report on Cyanogenmod's JIRA bug tracker.. https://jira.cyanogenmod.org/issues/?jql=
[Verizon Samsung Galaxy S III] titanshadow:
Do the changes you have reverted ever make it back into the main build? Like for the RC or final stable release?
[Verizon Samsung Galaxy S III] mastamoon:
Yep
[Verizon Samsung Galaxy S III] titanshadow:
Thanks for all your help!
[Verizon Samsung Galaxy S III] mastamoon:
Camcorder might be a bit wonky after taking a video. Use at your own risk till its worked out.
[Verizon Samsung Galaxy S III] titanshadow:
Works perfectly for my Bluetooth AND no screen flickers so far. :)
[Verizon Samsung Galaxy S III] ugachris:
Holy code drop, Batman. Looks like quite a bit added for d2 in the latest official nightly.
[Verizon Samsung Galaxy S III] Div033:
No kidding. Maybe the camcorder will work after these commits. Eagerly awaiting Masta's daily!
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I believe it was fixed and why the stuff got merged. :)
[Verizon Samsung Galaxy S III] V3TTOO:
Yeah, I found that out yesterday. :p
[Verizon Samsung Galaxy S III] goldsmitht:
define "wonky"? haven't been able to test yet (at work, they frown on video taking here).

:cyclops:
[Verizon Samsung Galaxy S III] mastamoon:
Doesn't matter now, should be fixed in today's build. Should be up by 3pm EST or so. :)
[Verizon Samsung Galaxy S III] mastamoon:
5/29 build in OP

-- camcorder bug is fixed.. everything else is good. BT should be working also. Narrowed it down a bit, hopefully gets fixed in official soon.

-- repo sync @ 2:30pm EST
[Verizon Samsung Galaxy S III] fromthesticks:
Downloaded yesterday's build and flashed with a cache/dalvik wipe.. Used alot of data today on a roadtrip but the mobile data counter is screwed up or something funny is going on...

Edit: looking at my Verizon looks like I've used just over a half a gb in the past 4 days. The Google play music was showing over 1/2 GB and I played only 3 songs on it today.
[Verizon Samsung Galaxy S III] nbaj2k:
I apologize for the stupid question. I know the GPS reverts have been removed and it is recommended that we flash a TW ROM, get GPS lock and then flash the latest nightly. After getting lock, is it recommended that I should first wiping data and cache, and then install the nightly, or should I just be dirty flashing it without wiping?

Thanks in advance,

~J
[Verizon Samsung Galaxy S III] mastamoon:
Yeah full wipe or if you just do a backup of your current rom it is fine to just restore that after getting a lock in Touchwiz.

If that doesn't work, or even before doing that, check the screws on the back of the phone. Specifically the one left of the battery when looking at the back of the phone. Make sure that one is tight.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah there is something going on with Google services using lots of data recently I believe, specifically Google music.
[Verizon Samsung Galaxy S III] fromthesticks:
Even dogcatcher, I looked at all of the shows I downloaded today, and they were around 200mb. The data usage is showing almost 6 times that. Got me real worried as I lost my unlimited and am only paying for 4gb now. The data usage shows I've already gone over that this month. But Verizon hasn't sent me a data alert yet. They usually do when I hit %50 percent.
[Verizon Samsung Galaxy S III] goldsmitht:
FYI: New modem / firmware out (http://rootzwiki.com/topic/34053-firmware-vrbmd3-modemrpmtzsbl-verizon-sgs3-sch-i535/) but is breaking the camera for some reason. seems to work on "some" TW based ROMs, but is definitely wiping out the camera on CM10.1 / AOSP ROMs; something about using a different camera system

:rolleyes:
[Verizon Samsung Galaxy S III] Reborn627:
I noticed the same thing with the Chrome Beta browser. A total of 1.8GB since May 21st with the bulk of it yesterday. Yeah, I've since uninstalled chrome.

Ray
[Verizon Samsung Galaxy S III] titanshadow:
How do you mean, wipes out the camera? Does flashing back to the last firmware restore the camera?
[Verizon Samsung Galaxy S III] goldsmitht:
screen stays black, and get message, "cannot contact camera" or something like that. no picture, and nothing works.

:cyclops:
[Verizon Samsung Galaxy S III] titanshadow:
I wonder which bit of the update package does it. Could the modem and RPM be flashed without the TZ or perhaps parted out in other ways? I mean, I'm sure someone will figure it out soon, but just kind of curious what breaks it.
[Verizon Samsung Galaxy S III] airmaxx23:
I can confirm this issue.
[Verizon Samsung Galaxy S III] Desterly:
Problem is in the new TZ when trying to download the camera firmware...

A couple work arounds have been found but nothing I'd say is a fix.

Easiest thing to do is either stay on MB1 or flash back to MB1
[Verizon Samsung Galaxy S III] V3TTOO:
Doubt we will get some of the features from the VZW update, correct?
[Verizon Samsung Galaxy S III] mastamoon:
I modded the zip file for myself so it flashes MB1 Tz instead of the new one. Camera works and the rest of the firmware is up to date.

Download - http://bit.ly/18Btjwc

Once they figure out the issue with the camera can just flash over with invisiblek's full zip.
[Verizon Samsung Galaxy S III] goldsmitht:
so i'm taking that this is just the radio and rpm?
[Verizon Samsung Galaxy S III] mastamoon:
No, its Radio, RPM, SBL2, SBL3 from D3.. and Tz from MB1

So its all the latest firmware that keeps us working... if they figure out how to get camera working with D3's Tz.. we can just flash invisiblek's zip that has the full firmware package from D3.
[Verizon Samsung Galaxy S III] PerCompLLC:
Trying it now...
[Verizon Samsung Galaxy S III] goldsmitht:
works so far, no issues with camera, and i didn't see anything else that was broken on first one other than camera.

will keep digging

:cyclops:
[Verizon Samsung Galaxy S III] PerCompLLC:
No issues here either... :good:
[Verizon Samsung Galaxy S III] goldsmitht:
has anyone tried to send an MMS with the new setup? Not sure if it is working; i tried, and it seemed to sit quite a while. deleted message, went back to MB1, same picture to same number seemed to take a while to send, but eventually did go through

:confused:
[Verizon Samsung Galaxy S III] PerCompLLC:
Trying it now... I'll report back in a few after I get confirmation.

Edit: MMS worked perfectly!
[Verizon Samsung Galaxy S III] mastamoon:
Same here..
[Verizon Samsung Galaxy S III] goldsmitht:
and here the second time i tried; i have wonky service here, so while it is great most of the time, i can have full bars, and SMS / MMS will just sit there like they are not going out.

once again, thanks for all the good work, your version works great!
[Verizon Samsung Galaxy S III] mtw204:
Looked for the answer to this for a while but no luck. I'm still getting screen flicker, actually getting worse and worse, running LK 5.9. Is it the kernel or a known bug?
[Verizon Samsung Galaxy S III] goldsmitht:
Would suggest going to the kernel page, where its been dissected, and for the most part, fixed with updates
[Verizon Samsung Galaxy S III] mastamoon:
Use stock kernel.. 404 no flicker found.
[Verizon Samsung Galaxy S III] V3TTOO:
Cool, it is on the OP as well. Thanks. No new build today?
[Verizon Samsung Galaxy S III] mastamoon:
No, nothing worth building for got merged. Maybe tomorrow! :D
[Verizon Samsung Galaxy S III] V3TTOO:
Alright. Thanks for the update and the ZIP file.
[Verizon Samsung Galaxy S III] speedingcheetah:
I know what the radio and rpm is....but is the rest of that stuff?,,,,never had to flash any of that stuff before
[Verizon Samsung Galaxy S III] titanshadow:
Testing RC3 for Bluetooth issues now...
[Verizon Samsung Galaxy S III] speedingcheetah:
so i flashed the modded modem zip....ran speed test before and after...i see an improvement...but those speed tests vary due to network conditions etc....

bottom one listed is me on MB1, top one MD3.

I am on Synergy Rom.
[Verizon Samsung Galaxy S III] stearic:
On the 5/29 build and i'm glad that bluetooth seems to be working much better. No more sound distortion on the low frequencies (like the gain was turned up to much on the low end). There was some.... pauses? though while playing it though. Not sure if it was because my phone was doing to much (started to listen right after a reboot) or if that's the one issue left.
[Verizon Samsung Galaxy S III] NegativeOne:
I'm still getting silly battery drain. 5-10% per hour due to Cell Standby. I'm in Boston and I'm on 3G. 0% time without signal. IIRC i've been getting this ever since the 3.4 kernels hit. I'm pretty tempted to go back to the March builds hehe.

Seriously though - anyone else having this ? Any idea how I can determine what's causing it ? I don't think it could be an app - could it?
[Verizon Samsung Galaxy S III] fromthesticks:
I have the same battery drain.. Havent tried a full wipe in a few weeks. Was thinking about doing that this weekend

Edit : I did a full phone wipe system/data. I'm setup again with no program restores. Everything manual. Will try that out to are how it goes.
[Verizon Samsung Galaxy S III] NegativeOne:
I've done full wipes - but that didn't help. Granted, I immediately restored my apps...

To be honest, aside from the recurring issues of reboots/hw overlay artifacts/and BT being broken once in a while (then fixed, and broken again), this is probably the biggest issue in the rom right now on this device. I would really like to get some more visibility on it.

Thanks to the hard work of masta and the maintainers, the rom is actually really solid and freaking FLIES! But the battery... God forbid I break out of my daily routine of taking a train to work and leaving it charging all day.
[Verizon Samsung Galaxy S III] Div033:
Hey masta, about the recent RIL changes in the official... You've already have these cherry picked right? As long as we chose the 'new' RIL build.
[Verizon Samsung Galaxy S III] mastamoon:
Yeah the ril stuff I was cherry-picking for a week or 2 was merged last night.
[Verizon Samsung Galaxy S III] dmginc:
Any idea what's causing the battery drain?
[Verizon Samsung Galaxy S III] NegativeOne:
5% over 3 hours with screen off. Cell Standby 42%; Phone Idle 28%.

Asleep 2.5h; awake 22m;

Kernel wakelocks: PowerManagerService 7m19s

bam_dmux_wakelock: 6m48s

sec-battery-monitor: 4m53s (is this better battery stats)?

radio-interface: 3m26s

Partial Wakelocks:

ostly google maps...

signalcollector.scannerthread 1m49s

Signalcollector.scanner 1m45s

Sill seems kind of high - no ?
[Verizon Samsung Galaxy S III] Reborn627:
Some of the latest google apps updates have shown some data increases which would in turn cause some battery drain. I noticed a significant data drain from chrome earlier this week with some crummy battery usage as well. I'd take a look at your data usage and see if anything looks a bit out of the ordinary. You may find it to be an app issue rather than a ROM or kernel issue. Just my $.02 and with inflation that ain't worth much.

Ray
[Verizon Samsung Galaxy S III] mastamoon:
5/31 build up in OP

-- removed wifi driver stuff, i think the D3 OTA will bring us some correct for our phones soon.

-- RIL patches got merged.

-- Repo Sync @ 3:20PM EST
[Verizon Samsung Galaxy S III] NegativeOne:
Top 3 for last 7 days:

Play store 223mb

gReader (Rss) 70.23mb -- (high, but not huge)

Google Voice 39.36mb

164MB background today on play store, but i don't think that was during the window I was monitoring
[Verizon Samsung Galaxy S III] SymbioticGenius:
Would it even make sense to flash RC4, with all the reverts you have in your build currently, isn't the RC4 a few days behind your unofficial?
[Verizon Samsung Galaxy S III] mastamoon:
Rc4 will be just like mine, minus the Mms tweak and working bluetooth. If those don't matter to you rc4 would be fine.
[Verizon Samsung Galaxy S III] npro1464:
Does yours fix the in-call volume? I know I'm not the only person who has this problem with the Official (I'm on RC2). It's driving me nuts!!
[Verizon Samsung Galaxy S III] fromthesticks:
My battery usage after the wipe has been positive so far. Been on battery with fair use for 8 hours with 50% battery drain. Yesterday morning I had %15 drain per hour with light use. Not scientific but I'll keep tabs on battery life the next few days.
[Verizon Samsung Galaxy S III] Div033:
It's still there.

A decent workaround:

1. During a call, set volume all the way down, then all the way up.

2. Then set it to the 3rd volume level. That's the 3rd from the lowest.

1 2 3 <- that's where you want the volume marker to stick.

After doing this, when you answer a call it won't be blasting loud. For some odd reason if you have the volume set to level 1 or 2, it will jump to max when you get another call regardless of the volume setting (1 or 2 specifically). If you have it set to anything higher than 1 or 2 it won't trigger this behavior. I find the volume of level 3 to be acceptable; not too loud, not too quiet.

They had it fixed for a while but it seems the 3.4 kernel brought it back.
[Verizon Samsung Galaxy S III] AdMire:
disregard
[Verizon Samsung Galaxy S III] damnyouwaffles:
Is the microphone volume fixed in this or is it still really soft? Its kinda a deal breaker for aosp ROMs for me.
[Verizon Samsung Galaxy S III] mastamoon:
6/03 build in the OP

-- repo sync @ 9:30 AM EST
[Verizon Samsung Galaxy S III] mastamoon:
Microphone volume for the camcorder or voice calls or what?
[Verizon Samsung Galaxy S III] damnyouwaffles:
I guess for all three. When I was using any AOSP ROM, I had problems with Google now, camera, and a few other things.

-------------------------------------------

Galaxy S3 running Bonestock 1.5 with KT kernel