yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
here is a build to fix the 0/99 bug:

http://jenkins.cyanogenmod.com/job/...-EXPERIMENTAL-d2att-SIGNALSTRENGTHTESTNEW.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mranonymous333:
Is there anyway to under clock on the stock kernel for 10.1.2 stable? I've tried changing from 1512mhz to 1026mhz in the performance settings but the change doesn't happen. Also is there anyway to under volt stock cm kernel? Voltage Control doesn't seem to work. Other kernels seem to make games (like minion rush) lag even when over clocked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayDream:
Subway Surfer fix

This was the only way I could get subway surfers to work on the newer nightlies and the stable releases http://xdaforums.com/showthread.php?p=43668006#post43668006
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
Thanks. I am starting to think that the wild fluctuations in data strength are simply a network issue. I am in a big city, too (LA), and get great speeds most places, but there are just some black holes (i.e., my office...). I might flash back to touchwiz and see what happens.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rock7632:
Hi, I was wondering how stable for everyday use the latest cm10 nightly is? On the get.cm site the latest one says its experimental so are there any major bugs in it? Is that why its labeled experimental. I wanted to flash it on my friend's s3 which is still stock touchwiz 4.0.4.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stonewallmike:
In my (limited) experience, and the greater experience of the guys who got me into flashing, CM builds are high quality, and reasonably reliable. If any serious breaks show up after it ships, they are usually fixed straight away.

FWIW, I decline requests to flash other people's phones. I'm happy to teach people how to research and learn how to do things, but anyone who can't root and flash their own phone probably shouldn't be running a custom ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
another test build is here

http://jenkins.cyanogenmod.com/job/...EXPERIMENTAL-d2att-SIGNALSTRENGTHTESTNEW2.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I have read the the d2att and d2tmo are the same except for radio. That would explain this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Shouldn't our DPI match our PPI? Like.. Shouldn't the build.prop have this value at 306 instead of 320?

lalala boom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Danvdh:
I would not flash a test build, they are pushed for a select few to use and test a commit or two,

well I'm sure you know but other's might not :)

cheers

only flash a stable build on a friends phone, or a touchwiz rom. see my sig for a complete stable touchwiz rom that's themed to look exactly like cm 10 with everything working. Nightlies and such are for development purpose. I'm sure the stable build will be a massive upgrade over 4.0.4 but you will need to odin the bootloader. search this thread for more info
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalchef:
Curious...since TWRP isn't supported, I flashed CWM-touch. But CyanogenMod won't flash (error). However, Liquid Smooth and Slim Bean flashed fine. Is this strictly related to CWM-touch vs CWM?

I have an i747m, not that that should matter....:confused: I came from stock (samsung) 4.1.2 ... anyway. other AOSP-based ROMs flash fine. Why not CM?

edit/update: flashed CWM (non-touch) -- doesn't like my build-prop ID ? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Flash TWRP, CWM or CWM touch for d2att, not for d2can. Ignore d2can recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
this is exactly what I was going to say...

I first flashed for d2can... and I wasn't able to flash a d2att rom...

Is there a reason why they still have a d2can recovery if there is not use for this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalchef:
I'm not using d2can recovery. it's directly from CWM website. in fact, this reply seems silly to me (no offense). there is no "d2can" recovery on CWM website -- only AT&T.

still not getting it. :silly:

edit: also, I used terminal (dd) to flash my recovery. not rom manager, or goo or s3 toolbox...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
While TWRP isn't officially supported it still works fine and is better (imo) than CWM, touch or not
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
there is a d2can recovery on TWRP... I'm wondering why it's there if no one has to use it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
To be compliant. You know, because they are technically different devices.

Realistically though, there's never gonna be any dev scene specifically for d2can and apart from the radio, d2att and d2can are identical.

Metalchef, what is the exact error you are getting? You say it's a build.prop error, but it can be 2 things: Whining about model (d2can/d2att) or bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustangtyson:
Why was the "Random Reboot on Galaxy S3 d2att" bug closed today by "Shareef Ali"? I don't see any commits that fixed anything? :eek:

https://jira.cyanogenmod.org/browse/CYAN-1167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

I don't agree with this being fixed. But i can't edit the bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Are there any problems with this ROM and games such as Tapped Out (Simpsons) or other games with the new stable releases?

I searched for some game names and didn't find anything...

Thanks guys,

Elliott
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I haven't had one random reboot in months and months. Issue is closed on cm side of things. It's possible your modem or kernel is rebooting your phone. There aren't many out there who have random reboots anymore. Sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Same here. Reboots are usually my fault. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustangtyson:
Thanks! Checked into that. I am running "I747UCDLK3" baseband and bootloader. See attachment. Are these incorrect?

PS: I use "Bootlog Uptime" to save the logs of my random reboots. It notifies you when one happens and saves the logs for debug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Everything is good on both the bootloader and modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I too am on the correct bootloader and run stock everything. I'm still experiencing random reboots while streaming A2DP. It happens pretty consistently every morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
​

There is a guy who frequents the KT747 thread who is pretty good at deciphering kernel debug logs. He can usually pinpoint why your phone is rebooting by looking at that log or if it's even kernel related. Some phones just don't play nice with certain setups. This is due to different hardware tolerances within your phones circuitry.

Shane87 is his name. It might not hurt to ask him for some help.

http://xdaforums.com/member.php?u=3482571
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Are you still testing those signal strength experimental builds flexfulton?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I just flipped to the latest nightly. Ran the latest experimental the morning. It does show correct signal strength now but unfortunately has no affect on network hand-off as I was hoping. It also didn't clear up the no network connection that we sometimes see during a 3G to 4G switch.

So I'm still likely going to turn LTE off most of the time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Same - random reboots have gotten very rare. About the only way I can still consistently cause my device to crash & reboot is when attempting to edit 1080p video using the "Movie Studio" app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
That sounds to me like if you upped your voltages you might have better luck. Editing HD video is pretty labor intensive on the GPU and CPU and they likely crash because they become unstable under such heavy load. Try upping the voltages 25 or 50mv across the board and see what happen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
There was 2 experimental builds this morning, tried both? :/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
The guy derped the first one resulting in 3g cell signals being wrong. So he compiled it again after he corrected the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Aye ok. That sucks though. Kind of a killer bug when you're at the wrong place heh!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanD911Phx:
New problem on d2att builds: WiFi 5g type N fails to attempt authentication.

Introduced in the 7/16 nightly, not fixed in 7/17 nightly.

Backing down to 7/15 nightly fixes problem with no other changes. (Confirmed broken then fixed 3 times)

Most tests were with warm installs from CMUpdater but one test was from CWM where I could be sure cache was wiped.

Time to start looking at code, but BBQLog doesn't show any culprit that leaps out at me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Confirmed? Your set of circumstances are probably unique as I've had zero problems with 802.11n on 5G on my dual band netgear w/ ddwrt.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I only use 5ghz at home on a dual band n router without issue as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
or it's over-heating because of too much voltage. So if upping voltages doesn't work perhaps lowering the highest frequency voltage will? I assume this to be a heavy load, flat-out CPU scenario.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Isolated problem maybe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Flex,

Just to update the LTE toggle thing I and a couple others mentioned, I'm on my phone right now on the 7/15 nightly build (same as last time I posted) and, while the LTE button is greyed out, my device is reporting I'm on LTE in the mobile network type and by listing 4G in the status bar. Toggling the button has no effect whatsoever. It's a shame, too, since the extra battery draw is quite apparent.

Dunno if this helps, but I figured I'd mention it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Ever since 7/17 my battery sucks and cell stand by is the culprit even after a full wipe on straight talk wireless service
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Anyone else having issues with lte being super slow lately?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanD911Phx:
Further isolation. I had been using channel 157. This failed on latest builds; none of the high channels work. What works is setting the router to use a low channel like 44.

BTW I get 150Mbps using 40mhz channel setting.

---------- Post added at 07:08 PM ---------- Previous post was at 07:05 PM ----------

Please tell me you are not using a high channel but one 48 or below. See my update to my original post
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
I've tested it on my router and device too...

I have the same problem on the 5GHz band with my Linksys EA6500 router.

Channels 48 or below are fine... but all channel higher than 48 are not connecting.

I've confirmed that all my other devices (2 laptops and 1 iPad) are working fine with all channels.

I don't really know when it stopped working since I was always using a channel below 48.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Confirming that it doesn't work over channel 48. Either way, unless specifically requires due to lots of noise, channels over 48 shouldn't really be used to maximize compatibility (and ironically also to prevent noise from other 5GHz band devices).

See this table for further information:

http://en.wikipedia.org/wiki/List_of_WLAN_channels

I don't know if it's a thought out change in CM10.1 to limit people to connect to channels 48 and under for some obscure reason, but if it is I don't believe it should be enforced anywhere else than from the AP... Hopefully just a bug.

I myself live in a not too crowded area so I can hang around the 2.4GHz band without any problem. Covers a greater distance and isn't too prone to interference, so I'm all good. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ddiehl:
Running latest stable and having issued with bluetooth hanging at turning off.. Did a clean install. Is this still a known issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Yep
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SomethingAwesome:
I'm running 7/18 and my battery life has been decent, (I thought so anyway). Maybe I'm just using my phone less the last few days. I've been seeing only about 1% drain per hour standby, which is pretty good?

Sent from my magical SGS3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Hey guys

Is there any way to change the brightness of the soft keys? I find them to be very bright and I don't need them to be like that...

Thanks,

Elliott
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Haven't followed this thread in a couple of months. So stable has a bluetooth bug, but does it also have an LTE bug?

---------- Post added at 11:50 PM ---------- Previous post was at 11:49 PM ----------

Is there a Jira issue to track this "no network connection during a 3G to 4G switch"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Thr33Seed:
Haven't checked in a while, has the MMS issue been fixed yet in 10.1?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kryptonite_2448:
Read.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phoenix2217:
So I am aware of the network drop outs that were occurring on CM10. The July 17th nightly was supposed to fix this?

The issue I have is, if I leave CM10 on the stock kernel, the network does not drop out.

Once I flash a different kernel, it drops out almost every 10 minutes.

The kernel I am using is from 7/20 which means it should be synced with the newest CM10. Is any one else still experiencing the drop outs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nikhilppatel:
Been trying this for a week. This is the best battery stat I got:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
which nightly are you running?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Is anyone else having problems with the phone not locking? I'm on 07/17 and the phone does not lock by itself most of the time...I hit the power button or home button and the phone is already unlocked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krad:
I ran 7/20 build and could not access my 5ghz network with my ac access point. 2.4ghz worked fine. Just flashed back to stable and all is well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Looks like to be a bug with the nightly... Change the channel to 48 or lower... Should work fine after that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
Please help me to display development menu

Envoyé depuis mon SAMSUNG-SGH-I747 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
go to settings, about.

click a few times on the last entry (build number)

developer menu will be enabled after that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
Think you it's work:):thumbup:

Envoyé depuis mon SAMSUNG-SGH-I747 avec Tapatalk
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nikhilppatel:
The latest stable version, not nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You should try the 7/20 nightly. It is very stable and has great battery... although I used the BMS kernel with it and under-volted a bit and ran it from 189 to 1350. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ahagersr:
7/21 is running very smooth as well. The last few have for me, actually.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krad:
anyway to load privacy guard on latest stable version? is there a flashable zip? do you need root to do it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
privacy guard is only available in nightlies....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I've seen this MMS pic resizing bug in some of the last nightlies, though it is intermittent. Sometimes it appears, sometimes it doesn't, even on the same pic. The workaround mentioned above does not seem to fix it for me. It's pretty frustrating. Any idea on how to fix it permanently?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krad:
Anyone know of a way to block gps for an app? I am running this Rom with good technology and want to block tracking.. not rooted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
How about turning GPS off? ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
If you're running this ROM, you're a bit more than rooted.;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
Has anyone else experienced the 0db/99asu bug after installing 22nd nightly? They supposedly fixed it in

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

I'm still having the issue though. Not as frequently but it's still happening. Just thought I'd ask around.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krad:
There is a script and package I load called gfe. That hides root and basically unroots. My phone needs to be unrooted for good foe enterprise to work without locking me out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I haven't seen it but I've only looked a couple times.

In the end I believe the fix was only cosmetic anyway and didn't actually change the way your phone does things which is what I was hoping for. I was hoping that with such a poor signal it was supposed to switch over to 3G but that it wasn't doing that due to a bogus value but now that the value is true, it still hangs onto that poor signal.

It has appeared to perhaps have fixed the time my phone reports as time without signal when not signal loss has occurred. I still see some time reported but I believe this small amount of time is due to the network dropping all together sometimes when switching from 3G to 4G. I haven't had time to debug further at this point in time and sort it all out again.

So I guess it wasn't all cosmetic but it didn't help the network hand-off which is what I was really hoping for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bazald:
msm_otg

I seem to be experiencing an issue with the latest stable and the nightlies. If I ever connect my phone to my computer (for example, to charge it), BetterBatteryStats reports kernel wakelocks from msm_otg from that point onward. This keeps the phone from sleeping properly, resulting in battery drain. Rebooting the phone seems to be the only solution I've found. Any thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Used to be an old old bug where if you rebooted while your phone was connected then disconnected it, it would hang. Maybe it's reared it's ugly head. Try rebooting it disconnected, then connect it, and disconnect it and see if the msm_otg wakelock is still adding time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bazald:
That seems to be sufficient to produce the bug. The Awake Ratio is at 100.0%, and I haven't been using my phone or keeping the screen on constantly. The Kernel Wakelock for msm_otg is already above 70%.

This also might be relevant: It reliably keeps the notification that it's "Connected as a media device; Touch for other USB options." after it has been connected once, even after disconnection. Perhaps the root cause is the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
You can turn root on and off in settings. Have you tried that before flashing the mod? I'm just curious.

If you are running one of the newer nightlies then the privacy guard feature should take care of your GPS problem. Outside of that GPS is pretty dang hard to control. Apps installed to system can turn it on and off but that's about as far as that goes. Blocking location access per app is going to need root at least

~L.T.

Sent from my Galaxy S3 [AT&T][CM10.1]

Galaxy S Captivate [CM10.1]

Nexus 7 [CM10.1]

OUYA [Stock Rom...for now]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
The past few nightlies(22-23-24) cause phone to reboot when trying to run game killer. I have 7-4 save and loaded that and game killer runs perfect in that. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Are you on stock kernel? I haven't had any reboots in game or out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krad:
The latest stable release works really well. Just need privacy guard via cwmod flammable zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
o_o that's strange. I don't have this notification. Turn your phone off and use a toothpick to clean your phone micro USB port and try another cable if possible. It might be that it's simply dirty.

---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------

Also for those interested who still have the MMS not sending bug, ganjah and I have found a workaround which involves using an older MMS.apk from M3 release since it used different values for the resizing of pictures.

Here's a link to MMS.apk, you can replace the one found in /system/app by this one and set permissions accordingly.

https://app.box.com/s/ch5h29neu1vmazj5sqb3

I might end up making a flashable ZIP if there's enough interest.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bazald:
Hrmm.... I tried cleaning the port to no effect. And I've encountered the issue with multiple cables, so that's no solution. But you may be onto something. I've had difficulty maintaining reliable data transfers over the cable in the past. My computer can navigate the directories on the phone, but when I try to transfer files over, the transfers usually fail very quickly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bruce Lee:
+1 for the flashable zip. I think you should make it so the really new users can use it. I personally could do the manual way. But you should make it. just my recommendation though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I would look into that. The bug was squished a while ago, but if the notification doesn't go away something is definitely wrong. It's difficult cleaning the port thoroughly though.

It's not really super long, but unless some people require it, I'd rather not invest my time in this. I've spent enough time working around a bug that I've never experienced myself. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bazald:
No way. Using cleaning advice from this thread, the message actually disappears now. It looks like your advice was right on the nose. Thanks a bunch.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Happy you fixed your problem and good technique to remember. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Made a flashable zip for the MMS fix. So for those unable to send MMS at times because it gets stuck, this shall fix it.

1) Flash nightly/stable/whatever

2) Flash MMS fix

3) ????

4) PROFIT!!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fallon:
Actually I'm not rooted either. Good for Enterprise (GFE), corporate secure E-mail client has root checking & disables itself if it finds root.

The best resource on enabling/disabling root for this situation is located at http://xdaforums.com/showthread.php?t=2040163 . Pretty easy to toggle root on or off with the right scripts.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
I'm a curious person. Can you explain what the fix entails? As in, what's wrong with the stock MMS, what does this change, and if you happen to have any insight... why hasn't it been fixed in the CM code?

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Is that a server side setting? I'm rooted and been running Good just fine?