yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
There's no need to flash a modem newer than JB or a bootloader newer than G2. Knox poisoned the Android well and is best avoided. The JB bootloader isn't as bad as NE4, but I'd still avoid it. I should have made that clear.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
this is very aggravating [emoji53]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tepeee:
Is the Jb modem good for CM11 kit Kat?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tanker Bob:
Works fine for me. I did not encounter any phone or data issues installing M11 clean with the JB modem I already had on the phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Yes, Bluetooth is working as well.

This is on a October 09th nightly. Though I believe I have some leftovers from a working August 18 nightly.

During my several data wipes there was a point where I couldn't wipe data at all within CWM. Ended up installing Oct 09th dirty on top of a corrupted data wipe on August 18 and that's how I ended up with a working GPS and BLUETOOTH.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
https://play.google.com/store/apps/details?id=com.jphilli85.deviceinfo

Use that to find your current baseband and bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
phew! got a GPS lock at last guys and on the latest nightie lol just a normal clean flash

and the trick is...let it settle

take your time restoring your tibu, do a couple of reboots , I also wiped dalvik/cache once and 30 to 40 mins later GPS will kick in and start locking fast

that's all there is to it, just patience [emoji6]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I've noticed a problem with the nightly builds ever since 9/25 or so, and now I'm getting the same thing with M11. The in-call volume is always LOUD AS HELL, even with the volume turned all the way down. Has anyone else encountered this or found a solution?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
Does anyone have any idea if and when a stable KitKat version will be released?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
The CyanogenMod team doesn't do "stable" releases anymore, they do M releases every month now which are snapshots taken a week earlier and are supposed to be stable because they spend a week squashing bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krazywrath:
On the topic of bootloaders and modems, these shouldn't impact whether GPS works on an S3, should they?

My understanding is that modems should only impact mobile network connections.. Not sure what bootloaders affect.

Edit: I miss my GPS. Dirty flashed Oct 9 on top of a clean M11 and still nothing...

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imcol:
Yes I been noticing this and its a huge problem! They need to fix this asap.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
W

I'm highly skeptical myself of updating latest nightly now since the gps has been a hit and a miss for lot of us.

It was a nightmare trying to to get mine to work.

BTW M11 is a rock solid release provided that you can get gps/BT working on it.

You might want to try clean Oct 9th for gps.

---------- Post added at 08:36 PM ---------- Previous post was at 08:36 PM ----------

Which nightly exactly?

Is your BT working?

Did you format system from recovery?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
@ blasterrr

-10/11 nightly

-BT working

-yes, I always format system when doing a clean wipe

I also tried the same procedure with the previous nightly and worked the same

just let it settle for more than 40 mins and GPS will eventually kick in, I use it daily, and its been working flawlessly in real world situations
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krazywrath:
When you let it 'settle' for 40 mins, do you mean leaving the GPS on in a GPS test app (for example)?

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
I tried letting it settle. All I get in GPS test is no fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
these are the things that I do

-clean flash on twrp(wipe data/cache/dalvic/system)

-reboot phone a couple times(give it some time in between reboots)

-bring up all the apps that use gps(gps test, google maps, runstastic etc)

-clear cache and dalvic once

- turn on and off gps option from the settings menu a few times

I have repeated the process with 2 nightlys and it worked both times

maybe let it settle for a longer time?

I was using quantum 5.2 as my daily driver,since I need GPS daily, but now I can use CM since everything works

I know this is sort of a crap shoot throwing mud to a wall to see if anything sticks, but it works [emoji51]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
For what it's worth, a complete clean flash with format of system, cache, data didn't get my GPS in working order either with the latest nightly. I wouldn't fret it, something is definitely broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
Try this as I posted in the carbonrom thread. http://xdaforums.com/showthread.php?p=56000954
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Thanks, that did it. Whatever one of the CM nightlies did to AGPS, it would be wise if people didn't have to jump through hoops to get it back to working state. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
I just got back. As far as I can tell the current status is that the ticket is still closed and that people are still having problems. Does that sound right?

I'm fried from the long ride but tomorrow or the next day I can wipe and try things again and grab some more logs to see if I can get the ticket re-opened.

Do you think this is still necessary? I mean, if things are OK I'm not going to bother (I don't mind doing the work but it's time consuming so if it isn't needed I won't bother).

Thoughts?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elcocolo50:
I dirty flash all resent nightlies to my wife phone with no issue on data and gps all run good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
just want to verify this is the recommended launcher? https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes. Apex launcher is also very similar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
Just try them out and decide for yourself...there isn't really a "recommended launcher".

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Hiquin:
I highly recommend Action Launcher.

https://play.google.com/store/apps/details?id=com.actionlauncher.playstore

There's a pro version as well which is well worth the money.

I like everything that Chris Lacy builds. Tweet Lanes is my fav twitter client, and his new app Link Bubble is just an awesome browser that solves a lot of problems I didn't even know I had.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] v1nsai:
I'm not understanding the difference between the regular gapps and the link there. That thread looks like it just provides a more complete set of gapps. Was that the point?

Anyway, I've come crawling back to CM after seeing how slow, ugly and uncustomizable even modified stock ROMs are. It's either CM or I put my SIM back in my iPhone. Is there any reason for AOSP ROMs to be more stable than CM?

+1 for Action Launcher, even though I'm using Smart Launcher now. Kind of like Action launcher in that it emphasizes using the sidebar to get around, but Smart Launcher lets you categorize the sidebar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sugarkryptonite:
That thread provides different levels of GApps, depending on what you want/use...read through the descriptions of each full modular, mini modular, micro modular, etc, and you'll see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] v1nsai:
So I just flashed the 3/27 nightly and a process called sim toolkit using 35 - 50 percent of my processor at all times. Google has very little information about it and I haven't seen anyone else having problems with it running wild. Anyone else seeing this? It's been going for at least an hour now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
3/29 stuck at boot
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Just booted it with Quantum 3/26 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Same here.

Edit: Nevermind. It just started, after displaying the boot screen for a loooong while.

Edit #2: No touchscreen. Stay away from 3/29.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mts3:
I've been hesitant to switch back to CM after the LTE and camera issues. Are those resolved?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
LTE yes, camera it's on and off. Fine for most parts, sometimes front camera broken, sometimes camera won't connect upon certain manipulation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Drunk. Flashing 2/29. Will report back.

Edit: Back. Running 2/29. Running fine w/ KT's latest kernel. Something is wrong on your guys' end. Goodnight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
So if user prefer stock cm kernel, then we should avoid flashing todays nightly..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
If a user prefers having their phone boot they should avoid 3/29 for now. The Touch Screen commits are causing a no-boot for some people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Here you go guys. (And y'all thought I was crazy!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Who do you think committed that back? :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Some random guy. :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Woooahhh... They pulled the 3/29 nightly? So it's like I'm running a super limited edition exclusive nightly... Badass.

Edit: Just realized I referred to 3/29 as 2/29 last night. Not bad too bad a mistake for my state of inebriation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Dude why the f@#$ don't we have a custom wallpaper setting for the lock screen yet? I need to look into that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I'm for trying to reopen the ticket, obviously GPS is not working properly

we shouldn't have to go through all this hoops to get it to work, should we?

is kind of sad seeing development on this device stall, but I guess is the nature of technology

if the android gods are willing, I'll be picking up the upcoming shamu as soon as it launches, but d2lte has served me well after all I have put it through [emoji52]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Up to you. Personally, I clean flashed Carbon 8-24 nightly, instantly locked. Clean flashed CM 10-13 nightly, no GPS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
I'll see how busy work is when I get back tomorrow. I'm OK with things breaking periodically, that's what nightlies are for. But if the ticket is closed no one is even aware of or working on the issue. That's not good.

I'll see what I come up with.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I believe we do need the ticket re-opened. You shouldn't have to submit new logs though.

Appreciate the hard work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
I clean flashed M11 and I haven't been able to get GPS to lock, I've rebooted several times, wiped cache/dalvik, to no avail. It doesn't seem like I'm the only one either... this seems to me like a massive issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AddictedToB3er:
The consistency to this issue seems strange as I have gps on a clean m11 flash yet so many others don't. Is this the nature(issue) with unified builds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
There's a chance the gps.conf could have gotten corrupted, or something along those lines. Try downloading FasterGPS from the Play Store and rebuild accordingly!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Yes it is a big issue for lot of us. Sad part is last several nightlies have no mentioning of gps in change log. I really wonder if someone is really looking into it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Good idea, but nope, got a custom gps.conf going and first lock still takes > a minute. It's inconsistent at best, whereas I would get a lock under 5 seconds with ~20 sats when GPS "worked right".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] monkeysez:
I agree, GPS is having some major issues right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crandy2:
The method outlined in this post:

http://forum.cyanogenmod.org/index.php?/topic/99965-Gps-Issues-With-Latest-Nightlies#entry487191

Worked for me as well as others. It is a pain, but my GPS now works as well with M11 as it did with stock.

If you read the next post after the one I linked, a theory is offered as to why the GPS is broken. If that theory is correct, there won't be a fix in the rom, the fix will be to upgrade your bootloader, modem, and rebuild nvram.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
NVrebuild is always "the way" to fix it, problem being that one shouldn't have to go through these steps to get it back to working state methinks. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
So what's the best way to get the GPS working for someone like myself who is using the MK5 bootloader on a I747M. I've read posts about people hard bricking by flashing different bootloaders.. is it even a bootloader issue at that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I updated a long time ago to NE4 firmware but the gps woes are fairly recent( last month) , so idk if the nvrebuild thing will permanently fix the issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Krazywrath:
Same situation here. Running MK5 bootloader and modem at the moment. I've asked on the CM forums for advice too [emoji28]

http://forum.cyanogenmod.org/topic...est-nightlies/page__gopid__487797#entry487797

Sent from my S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
No nightlies in the last two days, whats happening?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
All devices, not d2lte related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Yes I know, just wondering what happened? CM purchased by Microsoft and no longer supporting other devices? Lol

I have not seen this in the last 2 years that cm has not released nightly in two days for all devices
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
This worked for me, too. Now on the 10/13 nightly. It was not too much trouble at all. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Did this wipe your SD card?

Did you loose custom recovery?

Did your Nandroid recover easily?

Did you install stock or a touch wiz Rom like Dandroid in order for the code to work?

Thanks for feedback.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
For the record, you don't need to ODIN back to stock unrooted etc etc.

You can flash any rom based on TW 4.4.2.

Personally, for the sake of saving bandwidth, time and so forth, I'd go with a smallish one such as TMS3KK (~500mb)

Cheers

Edit: And if you do flash that, it won't delete your recovery or anything of that sort.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
I recently installed PA GApps full "Google Stock Package", which also uninstalls a bunch of CM apps. I am now wanting to delete the PA GApps, and go back to the CM apps.

I think I know how to remove the PA GApps using PA GApps Remover, but how do I reinstall the CM apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
No

No

I didn't do Nandroid; I restored from Titanium Backup.

I installed the stock, rooted ROM (Touchwiz -- yuk). This is necessary to run the *#....# code to get the Utility (?) menu to restore the NV RAM. The original post says it's optional to install the stock recovery and I didn't do it. It worked fine keeping my original TWRP recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
does the above method works by restoring a TW nandroid, or you need to install/flash a TW rom from the scratch? after all what is needed is the stock dialer to access the NVbuild, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Not sure if this would work properly with a pre-4.4.2 TW (most likely though, you can nvrebuild using a prior rom but something else might be needed such as KK TW rom vs JB TW rom).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm not actively flashing my s3, but I think I had to flash back to stock a few times to get GPS back. For those with GPS issues, have you tried a stock derivative?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I tried the Nvrebuild thing, it didn't work for me, I used the latest nightly and the TW stock rom

gps was working, but when I restored the cm nandroid, I lost it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
A little confused here. You wiped and installed TW ROM. GPS was working. But after restoring Nandroid it didn't work?

Perhaps try installing a clean nightly after the stock install, NV rebuild Instead of Nandroid.

Since pixbuf above restored using TB, meaning no system or cache was restored. He got his working like many others in CM forum.

---------- Post added at 10:59 PM ---------- Previous post was at 10:52 PM ----------

Nice. Glad yours is working.

And you went to stock using ODIN?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
haha I have no idea how to restore what would be the equivalent to a nandroid but in Titanium Backup?

what sort of wizardry is this? [emoji1]

no srsly can anyone explain? I always thought restoring system data on Tibu is a nono

---------- Post added 16th October 2014 at 12:00 AM ---------- Previous post was 15th October 2014 at 11:53 PM ----------

I followed the instructions to a T, after doing the nvrebuild, I rebooted the phone on TW and gps was an instant lock, when restored the cm11 nandroid, gps was gone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Sorry if I confused you. If you read pixbuf's post above he did not perform a nandroid restore. Which copy pastes the entire data/ system image back on the phone including 'system'.

I am suggesting that you only 'restore your apps using TB' and avoid Nandroid restore.

Ps: I know the CM post suggests that nandroid restore will work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
For that matters, spent around an hour last night flashing TMS3KK 2.3.2, nvrebuild and everything, couldn't get a lock. Disassembled the phone to bit, checked the GPS antenna, checked the contact points, everything is fine. Screwed everything back together, still no GPS. Restored to CM nightly, waited like 10 minutes and got a lock eventually.

Will try tonight if I get time with actual stock rom rather than offspin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
guys this is crazy, well last night I didn't had a lock after doing the NVrebuild, and restoring a CM nandroid

good thing I just let it settle overnight,(didnt do anything else) and this morning bam instant lock

now, the question is, are we gonna have to be flashing a gargantuan TW stock rom and doing the NVrebuild thing every time we are flashing a new nightly? [emoji1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I wonder, how long before team cyanogen start cranking up builds four our device on android L, that would be sweet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ¿Will-it-Blend?:
Man I'm glad I left CM for likewise ROM. There just seems to be too many bugs.

However, back when I was on CM, if I ever had issues with GPS flashing a TouchWiz ROM, performing a factory reset, then going outside to make sure my GPS locked and the clean flashing back to CM always seemed to fix the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's the thing with nightlies though, one day everything is near perfect and the day and for the next month everything is broken. Bleeding edge kills!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ¿Will-it-Blend?:
Yeah, but I see that people using monthlies are suffering issues such as no data or GPS as well. Monthlies on this phone from CM used to be so solid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Monthlies have always been a "week old nightly". No matter how often I say it, there's some sort of general knowledge myth where some assume it's a more stable release.

It's less experimental and bleeding edge because it's a week old, but it doesn't pack special unicorn horn powder to make it somehow better. :P

I was on heavily modded stock TW w/ some Xposed modules a while ago while CM had some issues and it's definitely usable and relaxing to know that your things will work even before trying it. Camera, bluetooth, phone calls, volume, gps etc etc, it just works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
I gave my best to the last crop of 4.4.2 TW ROMS and couldn't handle it mentally, my eyes were bleeding [emoji1], had to go back to AOSP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cryceratops:
So I ended up doing a clean flash of a TW 4.4.2 ROM and doing the NVREBUILD, then I clean flashed back to CM M11 and all is working well again, GPS locks on as it should, no problems at all... it's just ridiculous that one should have to jump through such hoops to get it to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
So who here is brave enough to try latest Oct 16 after doing Nvrebuild? See if gps works...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kmarc33:
s/brave/dopey/p

I hope to get to it tomorrow or saturday. Actually, I'm still looking for which TW rom to grab. But I'm planning on following the TW/nvrebuild instructions and then clean installing the latest nightly. Rough week, though. Poodle is causing problems for some of my L4 switches. <sigh>

I'm wondering, after reading a few articles saying CM had some vulnerabilities, and after not seeing nightlies for 2 days (I can't remember that happening in years, if at all), if the CM guys were being cautious and doing a nice audit. Seems like a good time to do it. I'm finding all sorts of odd things in my world doing poodle/shellshock/heartbleed damage control over the last few months.

Most interesting to me about 16Oct: I use bluetooth on 5-6 things and there seemed to be a lot of BT commits. Could be curious...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Sounds good.

I have a Canadian variant of s3 i.e. 747 M. I have been browsing and reading on few roms myself. Even though my GPS is working right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] droidgeek99:
Hi, I'm experiencing a interesting problem.

When I turn off the screen power remains to the LCD. At night in the dark you can still see it glow with the screen off.

I'm using M11 Snapshot release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
My GPS doesn't lock on any TW rom I've tried, clean flash obviously. Nvrebuild does nothing to help. It locks on CM after 10+ minutes though. woop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgloki77:
11/16 and 11/17 links are down on CM page, only 11/13 and below working*taping fingers*

---------- Post added at 11:41 AM ---------- Previous post was at 11:38 AM ----------

did you tried this ?

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

I had no problem locking gps when I flashed this one

I also format system when clean wiping on TWRP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No, this is an AT&T stock rom, I have a Canadian i747M. I tried stock Canadian rom (which didn't boot, others also had issues with it though) and like 3 different NE4 based roms to no avail. Can't say "I'm stumped" because I could always ODIN to stock rather than recovery flashable, but I'd rather not, it's painfully long to get back up and running.