yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
The d2att developers thread has a sticky post with links to tools. There's a galaxy s3 version of Odin there

http://xdaforums.com/showthread.php?t=2150268

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Asmegin123:
Wondering if anyone can help me out with a problem I'm having...

About two months ago, I lost my IMEI so had to do a full restore to stock. Since then, I've lost my screen rotation ability (except in stock). I update nightly with CMUpdater, figuring it would get fixed, but it didn't.

I then did a full wipe and re-installed RC1, along with older versions I know worked in the past. Now the screen only rotates 270 degrees (ie upside down). It also gets stuck there, and I have to turn the screen off/back on to go back to 0 degrees. If I enable just 90 degrees, nothing happens.

I've tried all the fixes I've found (removing memory card, full wipe, back to stock and re-flash, recalibrating gyro) but nothing seems to work.

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
The last of the bootloaders was added in the 5/18 nightly.

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

If you're getting a bootloader assert on 5/18 then idkwtf.

Are you possibly getting a different assert? Like maybe you flashed an international rom or a t-mo rom and your phone props are buggered?

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
I'm on the DLK4 bootloader (using Rogers Galaxy S3) by default, is that enough to flash the latest nightly? I believe some posts a few pages back did say it would, just wanted to confirm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Yeah, DLK4 is confirmed working as far as I know. Have you confirmed that you have the DLK4 bootloader and not just the DLK4 baseband(modem)?

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ethere:
Quick question. Last time I was on Cyanogen the only issue I had was when I would go to answer a call the ring tone would bleed into the ear speaker for a second or two. Does this still happen?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeahmann:
Updating bootloader cured the constant reboots completely. Some advice: Backup everything including the internal sdcard and save to your computer. Somewhere along the way, everything got wiped including the sdcard.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayRolla:
You did something wrong. If you flash just the bootloader you don't lose anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] r3dd09:
Still having issues with random service drops. Phone has been on for almost 2 hours and has 10% without signal. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SirFunk:
Anyone having trouble with bluetooth in the most recently nightly 5/19? I have been having good luck lately but as of this one it just won't connect to my headset (LG HBS730) It pairs fine but then just says Connecting...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I've been seeing that sort of behavior since CM9. If I turn Bluetooth off and then on again, it connects fine. Not sure what's going on there. This has persisted with the stock kernel and ktoonzes kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
It paired to my car but later wouldn't connect. I went back to RC2 and all is well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] swtnix:
Thanks a million. worked slick....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
Broke for me a day ago. Turning BT on and off doesn't seem to fix it. It stays stuck attempting to pair.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Just got a random reboot on the latest nightly while watching a video on YouTube.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Do a force stop on Bluetooth Share, clear data and cache for it, then reboot before turning BT back on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
Worked like a charm, thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thelakeshow:
Since I'm still SIM locked to Telus, if I used this method: http://xdaforums.com/showthread.php?t=2176719 to unlock my device between flashing TWRP (or CWM) in Odin and restoring my nandroid, would the SIM unlock still hold upon restoring my nandroid?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] voldomart13:
The only way to update is through updating the bootloaders? crap -_-. For the bootloader packages posted a couple pages back, do we have to go back to stock for it to work?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No. That's the point of them, not having to go back to stock.

---------- Post added at 02:52 AM ---------- Previous post was at 02:52 AM ----------

Yes. They're unrelated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bzow:
Is there a /sdcard/0/ directory? The contents of your internal sdcard should be there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitardude87:
Anyone else getting really bad battery life on RC2? Google Services is draining my battery life. Not sure what data I can include in this to make this issue more detailed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
It's the broken camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I suggest flashing the latest nightly. The battery seems to have improved a bit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I'm not running RC2 but what worked for me to fix google services draining the battery is reboot into recovery and flash gapps again (don't clear cache) and reboot.

it has something to do with location services and possibly latitude in maps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nrod0784:
Is there a way to activate pie controls on cm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Stock CM on the S3 doesn't have PIE controls because it has physical buttons. PIE controls are only available (without modification) on devices that only have onscreen buttons and no physical buttons, such as the Galaxy Nexus, Nexus 4, and Nexus 7. There might be some zips that enable it, but I don't know of any specifically.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Anyone getting bad battery life on latest nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Anyone have an issue when turning off Bluetooth it hangs at "turning off bluetooth" and pings cpu at 100%? Reboot is the only fox for me. On cm10.1 with ktoonz kernal
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitardude87:
That seems to have worked out pretty well. I'll also update to the latest nightly build since klin1344 says the battery life has improved. Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The LPT:
I've been having bad battery life ever since the 3.4 kernel jump. But its not Google services. Its cell standby for me. I go from 100% to about 70% overnight (roughly 7 hours). Where as before that same time period I would still be above 90%

I keep going back to 3/17 nightly because of this.

I have great cellular coverage in my area so its not that issue.

Also note that I alwayd do a clean wipe first.

Sent from my SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
yw :) glad it worked!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
This app will allow you to use pie control:

http://xdaforums.com/showthread.php?t=1330150
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Please don't post issues here when not using stock CM10.1 ROM; that being said, I've been seeing this behavior too and either a reboot or force stopping the bluetooth share app are the only 2 solutions...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
I thought this was for CM10.1 not the stock rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The LPT:
Ignore. I was quoting the wrong context
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Sorry, I meant stock CM10.1 ROM, not modified with other kernels, etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
You're using ktoonsez kernel, not the CM10.1 kernel, so you are not "stock CM10.1."
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Best work around: If you disconnect from the connected device BEFORE turning off Bluetooth on the phone, this will not happen. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Is this a known issue with the CM team? I want to report it if it has not been.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daniel1306:
I need update the bootloader for install RC2? i cant install it in my i747M (Mexico)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheCynick:
I'm on the May 18 nightly and had one solid day up followed by two reboots yesterday. Where should I post my last_kmsg for analysis?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewmiranda:
Absolutely terrible. Drain to about 60% with basically no use today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tarphoun:
Exactly the same for me. I use to be able to go on 2 days before charging on M2 depending on usage of course . Since 3.4 battery drain while idle has been pretty bad.

I haven't figure out exactly why yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Same issue here with my device...I'm almost tempted to flash a touchjizz ROM because of the idle battery drains. Even with airplane mode on, I still get drain of about 1% an hour, which is still bad compared to my (now sold) one s, which drained a total of 0% overnight with airplane mode enabled. And that was with the first few cm10 nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phirewire110:
I used this mod to disable my hardware navigation buttons and switched on the software navigation button's.

I'm enjoying the software navigation so far.

http://xdaforums.com/showthread.php?p=32328345
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
4G Cell Signal Not Reporting Correctly

I've been noticing for quite a while on CM10.1 that my phone was not switching back to the 3G (UTMS) network when a poor 4G signal was present. I've tried flashing all the 'M' modems and playing with the APN's and preferred network modes both through the ROM settings and the dial code menus but nothing seemed to correct this issue. I flash the latest nightly every morning and have been for months. I've noticed an issue from as long as I can remember.

I've noticed tonight however after trying a little more to figure this issue out and I've discovered what I believe to be an incorrect reporting of signal strength in the settings/about phone/status page.

First, a little bit of a signal strength lesson for those who might not be familiar with it. Signal strength is measured in dBm which is a negative number. The closer the number is to 0 the better the signal strength. So a -120 dBm is a very poor signal -90 dBm is getting better while -60 dBm is a very good signal. A 0 dBm is impossible to achieve as a cell signal as it's the standard signal strength for blue tooth at 1 meter.

This is what I believe is wrong and I may completely out to lunch but I'd like to share my theory anyway.

You will see in my first screenshot that with one bar signal it's reporting a correct -115 dBm. Everything looks normal, there is a poor 4G (LTE) signal and it looks like everything is good.

In my second screenshot, I've got no bars but it is reporting a 0 dBm reading. The phone at this point should be switching over to the 3G (UTMS) network but instead will hang around here as it thinks everything is still good with the LTE network connection.

So my issue is that I believe the phone is lingering on the 4G network a lot longer than it should because it still thinks it has a signal and a strong one at that. I believe this is possibly why people are complaining about cell standby draining huge amounts of battery. Something just doesn't seem right.

So my question is does CM10.1 just show 0 dBm when there is no signal or does the phone actually believe there is a super strong signal? Perhaps switching it to something like -99999 would be better and help the phone switch to the 3G network a little better.

I went back to a stock ROM tonight just to confirm and as I walked down to my basement my phone switched seamlessly from 1 bar LTE to 3 or 4 bars 3G. On the CM10.1 ROM, my signal would would drop to no bars and 0 dBm as I went to the basement and I had to be down there for about 20 or 30 seconds for it to switch from that to 3G. It's just not switching between the 2 networks correctly while on CM10.1.

Any input is welcome in regards too this potential issue and possible bug. I'm not sure a logcat would be valuable in this matter.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I've noticed this as well, and it drives me nuts sometimes when I get into an area where 4G is weak, but an H+ signal would be full bars.

Could you report this on JIRA for the CM Devs to see? They won't see it here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I know they won't see it here but I don't know how to use JIRA or how to submit a bug report or the first thing about letting the devs know.

First I wanted to get some input here to see if I was onto anything or if I was just wasting my time. I don't want to waste there time if I'm wrong on my theory.

Second of all, I don't have logcats as this issue won't appear in them so they likely won't even listen to me.

Maybe someone who agrees with me on this problem but who has a bit more pull with the devs can share this with them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
check pm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
This is a great, thorough description of your problem, which I bet others are experiencing, too. I know you said you don't know how to submit the issue report, but please try to submit this somehow to the CM team, because this is great info that I'm sure they'll appreciate hearing. Thanks for the good write-up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
All AOSP ROMs do this at times. They say it is an upstream issue that will eventually be fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
On the 05/11 release, all working beautifully. Latest Google hangouts update causes by mic to not function. i can hear/see the other person, they can see me but they cannot hear me.

mic works fine everywhere else and prior to the google update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Try the latest nightly before reporting issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fpshah:
Has anyone tried video call through hangout... The microphone is not working for me.. Can anyone else confirm it.?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
Please reference the 2 posts directly before yours.... Cmon!

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
So I've done a bit more reading and and I'm still not sure what's up.

According to Wiki......

________________________________________________________________

In GSM networks, ASU is equal to the RSSI (received signal strength indicator, see TS 27.007 sub clause 8.5).

dBm = 2 × ASU - 113, ASU in the range of 0..31 and 99 (for not known or not detectable)

In UMTS networks, ASU is equal the RSCP level (received signal code power, see TS 27.007 sub clause 8.69 and TS 27.133 sub clause 9.1.1.3)

dBm = ASU - 116, ASU in the range of -5..91 and 255 (for not known or not detectable)

________________________________________________________________

So according to that a 99 ASU should be shown when you have no signal on the GSM network and should show 255 on the UMTS network when you have no signal. Now it doesn't say anything about the LTE network but it's likely 255 or higher for a not known or not detectable signal. So why is it showing a 99 when I'm not on a GSM network.

Anyway, my major question is why am I even seeing a 0dBm 99ASU for any amount of time. The network should have switched over to 3G long before I had a chance to see and take a screen capture of no signal.

I've found some interesting android based code posted on the net talking about signal strength and network handover.

http://mirror.yongbok.net/linux/and...ny/java/android/telephony/SignalStrength.java

If you read through that you will see IF and ELSE commands that should be switching over the networks during daily operation of your phone. I know this isn't CM10.1 code but they have to have something that does this type of work in their code.

I'm interested in checking out the telephony-common.jar but likely won't get around to it until tonight unless someone can point me to a text based version of the code on the web somewhere similar to the link I shared above. I'd like to see what's contained there and see if there are any mistakes in what it thinks poor LTE signal is.

Perhaps the lower limit allowed can be upped a bit to help switch over to 3G before the signal is completely gone or maybe there is a mistake in the code that prevents a seamless handoff. No signal should ever linger on no bars when there is another network for it to jump on. It should make the switch as soon as the signal strength is gone. And if there isn't another network to jump on, it should show the empty triangle indicating you aren't even connected to your carrier's network at all.

Anyone else have an input on this or see something I'm missing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I also had this problem way back when, and it actually persisted a lot since last fall. I live on the edge of LTE service in a desert metro area. Inside my house, it's HSPA+ full bars and signal (-87dBm at the moment), never switching to LTE. However, when I step out my front door, the phone decides to switch to the -113dBm LTE signal. Why it would prefer a signal that is so much weaker, I don't know.

When it does so, it gives me the triangle of no service, then switches in somewhere around 10 seconds. However, when going back inside, it does the same thing in reverse, but often either takes 20-30sec to reconnect to HSPA+, or it just doesn't reconnect at all. This means that I lose cellular data connection, texts don't send or receive, and all sorts of wackiness happens. This happens on campus, too. Better LTE signal there, but it's lost as soon as I go inside buildings.

Also, LTE represents a terrible battery drain and, because it's so spotty here, the network switching is a real hassle. Thus, I wanted a way to completely eliminate LTE altogether, as the difference between 10mbps HSPA+ and 15mbps LTE is completely immaterial in my world.

Though not really a solution, trying the preferred network workaround helped me a lot to avoid this annoyance, when coupled with a stable rom. In settings-->wireless & networks-->more-->mobile network settings, click Network operators. Let it sit there for a while to find networks - mine often takes 2-3min to find operators. If you have to, press volume up or down to keep the screen awake.

Once it lists the operators, choose the top AT&T one (assuming you're on AT&T), then it will back you out to settings-->wireless&networks-->more-->mobile network settings. Click Network Mode, and now you'll be able to set it to GSM/WCDMA preferred, which will keep it on HSPA+ forever until you next have to reboot.

Not a super great deal, but something to eliminate a lot of the headache you're experiencing. This, actually, is the biggest reason I'm still on 3/17 and haven't rebooted for 1382hrs straight. Since it's so stable, I don't need to **** around with the hassle of doing this lengthy process every time a 3.4 ROM glitches/bugs out, reboots, or locks up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
What you are seeing is not what I am seeing. I never see an empty triangle. I never have a period where my phone actually indicates no service. And an LTE of -115 is still a signal that's acceptable and will give you the same speeds as full bars of LTE. My issue is that it drops to 0dBm while still connected for a while before switching over to 3G or going back up to -115 4G. It doesn't loose connection to my carrier completely like you are saying.

I know I can turn off LTE (it's as easy as toggling the quick settings option) but that's not what I'm out to do. I am trying to resolve the issue not turn off or hide what my phone should do correctly. I pay for LTE, I want it to work correctly. I can get upwards of 30Mbps which is worth it for me.

I appreciate your input but living with the issue or using an old outdated nightly isn't an option for me. And for the record if you are hung up on the 3.4 linux update after the 3/17 nightly, it has nothing to do with cell signal and network handoffs. I'm trying to be proactive and fix something that isn't right here. I honestly think you are referring to a different issue.

On a side note, WCDMA preferred should stick even after a reboot. It does for me.

Thanks for your time and input.

EDIT - I've thought about it some more and I think I have seen your problem happen on my phone before way back in the day and I found that it was directly related to the network mode not sticking. For example I set it to LTE/GSM/WCDMA. When using my phone it would drop signal from my provider all together when trying to switch from 3G to 4G and I'd go back in to check my network mode and it would have set itself back to WCDMA preferred or something like that. Something just doesn't sound quite right with your phone and your settings. I'd look into it a bit more. Likely not a CM issue but rather a set up issue on your end. I'm not trying to be a prick here. Just trying to help you out. Maybe a revert back to stock to make sure all your LTE is running smooth there and then reflashing back on a fresh CM would help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
I wonder if you could make a Tasker profile to do that process upon each boot-up, so you don't have to deal with it yourself every single time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
So I have taken a radio logcat of what my phone is doing while lingering on the LTE network at 0 bars and 0 dBm 99ASU. It is a rather lengthy log and I don't know if it shows anything useful but I thought I'd post it incase someone can see something wrong within it.

Basically it shows the phone lingering around for quite a while at 0dBm 99ASU on the LTE network before FINALLY switching over to a strong 3G signal and full bars. Perhaps someone smarter than me can make sense of it or mine out some useful information as to what it's doing.

I've posted it in dropbox at http://db.tt/AhBjNtxA as it's too big to attach to this post.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Death&co:
Do you guys recommend going with the RC2 build or the latest nighly? I'm coming from Liquid Smooth and just want something to try out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
the latest nightlies have been pretty smooth. i went from the 3/17 nightly to RC2 to the 5/19 nightly and it's been pretty golden.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Death&co:
Thanks :good:

Will try the latest nighly and worst case scenario I'll just go to RC2. I'm pretty excited, this will be my 2nd ROM ever (1st was liquid smooth) :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Just got a text message from my carrier (Rogers) that Jelly Bean 4.2 is offically out for my S3 and I can update OTA from them. So be on the look out for a newer bootloader that will likely be released with this update and need to be added to the assert at some point in time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
:o!

That's great! If we get officially supported 4.2, it can only mean good things for the dev community.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Makoers:
4.1.2 ? Or 4.2.2?!? Because there's no way its 4.2.2 haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Looking on Google real quick will reveal it's the real deal! Party hard.