yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Master Cylinder:
Like you cLock with Yahoo is bonkers. but, there is another choice now! OpenWeatherMap. IF you dump your cLock widg and put it back, you can choose a weather source and get rid of the mindless Yahoo thing. I restored a 12.1 nandroid a couple of days ago and couldn't get it to give me any weather other than last December.

Dang! Sorry you had to revert, though CM12.1 is still an awesome ROM. [MENTION=3056030]AyUaxe[/MENTION] mentioned that his 4/2 was stable. I was stable on a 4/1 build of AICP. Just flashed a 4/9 build before I went to bed. Might be having some lockscreen issues but I may just need a reboot, or to get some apps to optimize. I usually can't get AICP to optimize all the apps in one go - usually pulling the battery will start a second round.

Hey dude, thanks for all the info! Awesome! If I ever found you without dkp I might wonder if someone put mushrooms in my Cheerios.:p

(EDIT: LOL I liked that last line, it seemed to match my signature picture, so I put it in there.)
[Verizon Samsung Galaxy S III] YabbyYou:
AyUaxe, I may give the dkp kernel another shot when I try the next nightly. I don't know if I want to go the nuclear route though, so I may just dirty flash (is that even a thing with kernels?) it on after I get the next nightly stabilized. I'll see how adventurous I'm feeling. Thanks for the good info though.
[Verizon Samsung Galaxy S III] YabbyYou:
Derp, I think auto rotate is broke again on 4/8. Anyone else having this problem?

Edit: Oh maybe not. Cleared the cache and rebooted. Seems OK. Sorry for jumping the gun on this.
[Verizon Samsung Galaxy S III] YabbyYou:
I flashed the 4/12 nightly and there is some bluetooth audio now. It's stutters like crazy, but it does play something. One step forward I think! I'll continue testing.

EDIT: The stuttering seems to be app related. I can't figure out exactly which app, but if I start killing apps that are running, the stuttering decreases. Maybe it's apps that have access to BT that are causing some issue, not sure. For instance, I starting playing a song, stuttering, when into settings and killed WeatherBug (which has access to view bt settings and also attempt bt connections) and the stuttering stopped. Three songs in and still no stuttering. Open WeatherBug, stuttering starts again. Now, I won't just say it's a WeatherBug problem because it seems to work the same way with other apps. That's why I'm leaning toward the idea that it's apps that have access to bluetooth that are causing high CPU usage when a2dp audio is in use and they want to scan for BT devices. Jeez this is a long edit, maybe I should have just made this my post. Sorry, I'm babbling, I'll go back to work now.
[Verizon Samsung Galaxy S III] Fenix2002:
Interesting. Keep up the line of thinking and maybe it can point the devs in the right direction. [emoji106]

A bit OffTopic here, but I'm considering retiring my little d2 that can from DD life, possibly making it a dedicated GPS/media unit for my car. Not sure if or when I will, but does anyone have ideas about good upgrades? I like the Samsung family, but I've read that newer models are a pain to root/ROM, and the S7 may not be able to be ROMed because of bootloader issues. Thought about Nexus off and on. Thoughts anyone?
[Verizon Samsung Galaxy S III] YabbyYou:
You should get a Blackberry :p:p:p

I'm just kidding!!!! I really do like the new S7, my coworker has it, the hardware is downright amazing. Beautiful screen, insanely fast, MicroSD card! Samsung Pay is really cool, he's using it everywhere and always texting me about it. Now, the Touchwiz interface, ugh, I can't deal with it. Also, I believe it's not going to get rooted, at least, not the Verizon one. So, with that in mind, I don't think I would go with it. I've also been considering my options as the S3 gets older each day. I really think I might make the jump to Project Fi and go with a 6P. I'd have to spend the big bucks and get the 64GB or 128GB version though due to all the music I have. Since I don't think I'm ready to jump ship yet, I'm hoping to see a new Nexus phone sometime this year with even better specs then the current gen. I don't feel like there are any other top of the line choices out there right now. I mean the new HTC 10 came out today but that's unproven. LG has the G5, which is also pretty nice. Then you've got the iPhone, if that's your thing. Everything else out there is not quite top tier and you'll probably be disappointed. On the upside, just about anything out there is going to feel like a huge upgrade from the S3 spec-wise. I had a really hard time leaving my OG Droid for the S3 and I have a feeling I'm going to have just as hard a time leaving the S3 for something else. Hope that helps.

Back on topic - I've been using the crap outta my bluetooth all day and night and it's working relatively well. As long as I keep other apps not running, I get very minimal amount of stuttering. I might install the dkp kernel tomorrow and see if I can get it stable on my phone. If I can, I'll try overclocking a bit and then seeing if that has any effect on other apps running in the background and bluetooth performance.

[MENTION=3082999]Deliquified[/MENTION] I was asking around today to see if anyone I knew had an old S3 that I could borrow and root to install the "stable" release of CM13 on so I could try and log a bug report on the ffc. Unfortunately, of the 3 people I talked to that have old S3's, all of them took the updates and have locked bootloaders, so the phones are useless to me. If I come across one, I'll let you know. For now I just keep hoping to see a new bug report on the ffc from someone else that I can piggyback on.
[Verizon Samsung Galaxy S III] phonetool:
I am also interested in hearing what phone the Verizon rommers are looking at.

I took 2 OG Droids as far as they would go and then went to HTC Dinc2 (good rom crowd, but small) and was on a Galaxy Nexus just prior to the S3.

I love running vanilla Android and being able to pop in a massive battery. Those are my minimum requirements. That and a good rom support crew! Like all of you guys!
[Verizon Samsung Galaxy S III] YabbyYou:
From the CM bug tracker it seems a lot of people are running the 1+1 (aka bacon) and the various nexii (nexues?), so that seems to be where there is a lot of active rom support. Of course, those are easy phones since they aren't locked down. I think htc still lets you unlock, so there might be some rom support there, but I'm not sure. Obviously, the new Galaxy phones are knox'd up, so rom support is super limited.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Could be a rumor, but I read the HTC M10 or whatever the new one will be will basically have uh oh protection, where you can return it even if you brick through ROMing

I'm still holding out for a Nexus if possible (another rumor said the new Nexus would be based off the HTC, wouldn't be opposed to that)
[Verizon Samsung Galaxy S III] YabbyYou:
I think I read somewhere that if you unlock an HTC phone via the htcdev site, your warranty is still valid, so I think that's the "uh oh" protection you're talking about. I don't think it's know yet if the HTC 10 will be supported on the htcdev site.

A new Nexus with better specs then the current one would be great!
[Verizon Samsung Galaxy S III] Fenix2002:
That's what's stopping me from getting another Galaxy. The S7 is supposed to be amazing, but unless they guarantee regular OS updates (which they don't and won't), I won't get it. ESPECIALLY if they don't update AND have it locked down. :( android may be more "free" than Apple, but that's dissipating, and the other benefits are waning, IMO.

That's what has stopped me on the Nexii... Pretty much outdated specs, and I don't want a 6" screen. I don't really want anything bigger than the S3's. Hopefully they announce something spectacular soon, or an iPhone sounds better and better
[Verizon Samsung Galaxy S III] YabbyYou:
BLASPHEMY! BOO HISS! FETCH MY PITCHFORK.

ok, no more caps. Haha!
[Verizon Samsung Galaxy S III] YabbyYou:
It looks like there may be some camera related fixes in the next nightly build, so maybe we'll see some improvement with the ffc. Fingers crossed.

[MENTION=3056030]AyUaxe[/MENTION], I flashed the dkp kernel yesterday. The phone just doesn't feel as stable to me. I started with just one kernel change, the gov to tierservative. In the few hours I had that set, I had a bunch of random reboots. I switched back to the interactive gov and stability was a little better. Now I'm just trying the max CPU freq at 1566, which is 1 notch up from standard. I'll see how this works the next few hours and then try to increase further. I wonder if part of the reason you're seeing more stability is because you factory reset. I don't know what kind of effect that has on kernel stability, but maybe it's something. I don't think I want to go through that hassle at the moment though. I'll see how it performs today with incremental changes. Do you (or anyone else) know if there are any other kernels available? I remember there used to be one called ktoonz I think?
[Verizon Samsung Galaxy S III] Master Cylinder:
Oh man! Someone really here old enough (or as old as me anyway) to remember the "Outer Limits" ! That's sooo coool!

If you Google "outer limits original television series" and select images, you'll see some awesome/hilarious images from that show. What a trip!
[Verizon Samsung Galaxy S III] AyUaxe:
What could be more outer limits than d2 on MM? N will be twilight zone. Meanwhile, the apple crowd are stuck in The Prisoner (I am not a number, I am a free man!).
[Verizon Samsung Galaxy S III] YabbyYou:
Hey AyUaxe, thanks for the tip about the voltage and the info about the, how did you say it, "unusualness" of our d2. I have been messing with the kernel parameters all day. I think the phone is a little more stable with a min 800 voltage setting. It still randomly reboots, but I'm trying to find the magic combo of settings. I just laugh every time I try a gov/frequency combo and I'm just surfing the Web or listening to music and the phone just up and reboots.
[Verizon Samsung Galaxy S III] Fenix2002:
Lol, struck a nerve with that iPhone comment, eh? Had to make sure you guys were awake.

Idk, I've always been in the android corner, but iPhone offers stability and guaranteed updates (plus a few nicely integrated features). So far that I've seen, only Nexii get regular updates, and they're not always entirely reliable anyway. Almost all of the newest and best out there, feature-wise, seem to be locked down.

Locked down S7 or locked down iPhone? Which one gets guaranteed updates? Better features, better assistant (Siri hands-down), better integration?

Like I said, I'm still in the android corner, but recognizing that iPhone has some merit isn't beyond reason. That being said, has anyone had hands on with a 1+1?

---------- Post added at 10:12 PM ---------- Previous post was at 09:59 PM ----------

Oh, and just a quick mention since kernels is a frequent discussion topic and a recent one ...

OctOS Oct-M has a built in custom kernel (Kraken) and comes with Kernel Adiutor as a system app. I'm on it now and while it's flavored more like AOSP, it feels much more fluid and stable in most ways. A good alternative to CM if you ask me.
[Verizon Samsung Galaxy S III] phonetool:
LOL at iPhone users being stuck in The Village.
[Verizon Samsung Galaxy S III] AyUaxe:
Dat blob be coming to get 'em!

Thanks, [MENTION=6342402]Fenix2002[/MENTION] for the octos info. Something to check out over the weekend perhaps. Happy Friday to all!
[Verizon Samsung Galaxy S III] Master Cylinder:
1984​

---------- Post added at 10:17 AM ---------- Previous post was at 10:15 AM ----------

Hey Fenix: I put that OctOS on mine but haven't spent too much time with it. AICP has built in features that I love. What's cool about it? (I actually asked this question on that thread but just realized I forgot to subscribe - maybe others have also answered.)

EDIT: Nope! Nobody answered my post! Nobody wants to brag on that ROM?
[Verizon Samsung Galaxy S III] canodroid15:
[MENTION=5519140]Master Cylinder[/MENTION], we have our settings hidden in "tentacles". 3 ways to access, QS tile, tap build date once in about phone page, or the tentacles icon in app drawer ?
[Verizon Samsung Galaxy S III] Master Cylinder:
Deleted - off topic:o
[Verizon Samsung Galaxy S III] canodroid15:
[MENTION=5519140]Master Cylinder[/MENTION], sent you a PM ?

? d2att Oct-M KrAkEn Kernel ?
[Verizon Samsung Galaxy S III] Roger W:
Just tried 4/15 coming from 3/14 -

Encryption works! I was able to encrypt and still get the SIM to be recognized. I'm really happy to see this!

Bluetooth media audio is back to how it was before it totally broke last month - I can play music without it stuttering,. But, the previous (January-ish) problem still exists where having both the phone and media profiles active, and using the phone, will cause problems. The workaround is to only enable one or the other profile per BT device. So, my car is set to phone profile so I can use the hands-free, and I live with not having the voice navigation come through the car speakers. And, for my portable music speaker I disable phone.

ffc same as usual.
[Verizon Samsung Galaxy S III] beckx020:
Using 4/15 build. It's a keeper for me so far. Although getting a call while listening to bt music will crash the phone. But it's a step in the right direction. I'll make a nandroid of the phone so it's easy to restore if needed.

Whoever got the bt working, thank you!!!!!
[Verizon Samsung Galaxy S III] Fenix2002:
Don't ever make hasty decisions.. The boss lady (wife) decided she wanted to get the new iPhone yesterday, so that's what we did. Long story short, I ended up with a Droid Turbo 2(xt1585/kinzie).

It's beautiful and damn near indestructible. The salesman beat it on the wall, threw it as hard as he could at the ground... Nothing.

The booboo comes when I found out that it doesn't have root, probably never will. Lots of laughs were had all around, and I'm taking it back to the store to trade it out. Lol (and pay the ridiculous "restock fee")
[Verizon Samsung Galaxy S III] Master Cylinder:
That'll learn ya! Women LOVE those iPhones.

Don't forget to test it's indestructibility by running it over with your car ...
[Verizon Samsung Galaxy S III] Fenix2002:
I thought about it. Seriously, the DT2 is a really nice phone. But it shipped with LP and probably won't get anything else. Without root, that's a huge PITA. But as far as the phone goes, I benchmarked it better than the S7, the camera is slick, and it's fluid as heck. It also came with 20 bloatware apps, but that's Verizon for you. [emoji23]
[Verizon Samsung Galaxy S III] AyUaxe:
Don't be to hasty, [MENTION=760734]fenix2[/MENTION]000. Similar things were said about quark, but a root exploit was developed. Check this thread for 411 on kinzies, before giving up:

http://xdaforums.com/droid-turbo-2/general/root-discussionthink-tank-t3239979/page31
[Verizon Samsung Galaxy S III] Fenix2002:
Appreciate the effort, but so far all the forums are pointing to no. There's a possibility of root through a potential exploit, but it's temporary if they get it to work. I read they had a hard time getting it to stick. The bootloader is the big issue, though. They can't get past it and haven't been able to figure out a workaround to unlock it.. So no custom ROMs, even if root is achieved. At least none any time soon.

Seems like this is the case on most new flagships on VZW. S7 is knox'd up, LG G5 is running a modified bootloader that they haven't managed to get around, and the DT2 seems to be having the same issue. :(

HTCs do have the HTCDev portal to unlock bootloaders.. Maybe that's the way to go? But Verizon will probably find a way to block that. The new HTC10 qualifies for HTCDev
[Verizon Samsung Galaxy S III] Jaws4God:
sorry for late responses..

for me.. I LOVE nexus.. had a Nexus 5 when on TMobile.. never looked back.... I wanted to go to the 5x but cant with total wireless. Would love to go back to one though.

[MENTION=6342402]Fenix2002[/MENTION] Congrats on phone. u still gonna be here and flashing the S3?

Im hooked on AICP.. LOVE their features and fairly stable.

just discovered OmniSwitch. so sweet!!

Anyone see a CM13 front camera fix yet?
[Verizon Samsung Galaxy S III] canodroid15:
[MENTION=6342402]Fenix2002[/MENTION], if you can afford to go Nexus. I'm moving to Nexus & I'll never own anything else again. Carriers are ruining the new devices.

FFC, is close to being fixed. Its working on d2att test builds but nothing has been merged yet. Matrixzone over in the d2att thread has been working hard on it & he's got it working 98%. Won't be long!
[Verizon Samsung Galaxy S III] Jaws4God:
i feel so giddy. lol
[Verizon Samsung Galaxy S III] canodroid15:
Hahahah, gigidy gigidy ?

? d2att Oct-M KrAkEn Kernel ?
[Verizon Samsung Galaxy S III] AyUaxe:
Canodroid, did you find a flashable zip of just the kraken kernel? Looked some on oct-os threads, but didn't find it separately.

Now running 4/15 build w/ dkp, cpu 54-1836, tierservative. Stable, quick. Haven't had the chance to try BT yet. OTmusic tip-Monsieur Perine. Django Rheinhart-ish. Happy Sunday Compadre's.
[Verizon Samsung Galaxy S III] YabbyYou:
So I've been playing with the DKP kernel on my 4/12 build since I flashed it. Wow... lots of work, trail and error, reboots, researching, etc. Long story short, I get a decent level of stability with this profile, min CPU freq set to 54, max to 1782, tierservative gov and +50mV Global Offset. By decent stability I mean I can run for a bunch of hours, doing all the usual stuff and be fine. I may get a random reboot in there. However, I seem to get a consistent random reboot on my commute home while listening to music via bluetooth. I feel like it might be heat related, phone seems to get hot just before it reboots. Maybe something is hanging in the background and sucking up all the CPU (at 1782mhz too), running the temp up and then rebooting. I don't know. In any case, I'm going to try and stick with DKP and this profile going forward. I hope to get a new CM nightly flashed soon now that I've found a decent DKP profile to work with.
[Verizon Samsung Galaxy S III] Roger W:
Compass - I guess I never really used it to notice, but did the compass ever work better than it does now? Mine's not just miscalibrated, it's like the sensor data is being interpreted entirely incorrectly; in apps that use it, (GPS Status Pro is handy, but Google Maps seems to repro), as I turn the device, the needle swings the wrong way entirely, then bounces 180 degrees away discontinuously.

I don't personally care about compass itself, but I wonder if this hasn't been what caused Google Maps Navigation to get confused at intersections lately, when I wasn't moving fast enough for GPS to set the vector, and the compass told it I was going a different direction than I was facing so it kept rerouting me erroneously? (I don't even know if maps works that way, since there's no guarantee which way the phone is facing in a car)

I looked an found that the OPO phone had a CM13 compass bug that was fix a few months ago, I don't know if other devices could have the same problem.
[Verizon Samsung Galaxy S III] Fenix2002:
I gave up on navigation with the S3 a long time ago for exactly those reasons, and a few more. I still use it for directions, but after it losing lock in broad daylight with no clouds or buildings, showing me going the wrong direction, showing me in a field or river... But yeah, I always saw similar behavior in maps and with the compass. At one point it read exactly backwards of what I was actually facing.
[Verizon Samsung Galaxy S III] adobeman:
Interesting. My S3 has always been pretty solid with respect to the compass, sat locks, and navigation on every ROM I've tried (currently on AICP LP). Sometimes the compass needs calibration (turn device on all axis) but that's about it. One thing that will mess up the compass is having my S3 near the dashboard of my car. This is due to the magnetic fields created by the electronics/wiring in the dashboard. So when you aren't moving GPS can't calculate a point-to-point bearing and will sometimes rely on the compass...which is messed up by proximity to the dashboard.
[Verizon Samsung Galaxy S III] AyUaxe:
Those of us with crappy GPS function probably need to do the hardware fixes that are shown in many youtube videos, instructables, etc. on the net. From cleaning/tightening screws and chassis mounting points, to adding an additional wire to enhance antenna function. Mine has long been hit or miss--I've tried the compass recalibration procedure multiple times and it has never worked at all on any ROM. My general recollection is that it was better on the stock ROM, but that's reaching back almost 2 years at this point, so could be "good ole days" syndrome.
[Verizon Samsung Galaxy S III] Fenix2002:
Heh, I've done all the hardware fixes except the extra wire. It would help a little for awhile, but not long. And when I say it helped, it would go from not getting a fix at all to getting one at about 5 minutes. And it drops randomly en route. My personal favorite was rush hour Washington D.C. traffic, when it kept saying I was driving in the Potomac, and had to reroute. I drove around the Lincoln Memorial four times before it told me which turn to take.
[Verizon Samsung Galaxy S III] Roger W:
Hmm, my compass problem isn't interference/deviation. It seems to be misinterpreting the signal. Let's say I look at the compass laying flat, and it points a certain way. When I rotate the phone in its plane 30 degrees clockwise, the needle should rotate 30 degrees CCW to compensate. Instead, it rotates 30 degrees clockwise, so the needles is moving through space two turns for every one of the phone, rather than always 0 turns! (Actually, at some point it does a 180 and moves backwards or something. Like a flipped sign in a rotation matrix or something.
[Verizon Samsung Galaxy S III] mastamoon:
Oh hi!

Any of you fine gents know if MHL is working on CM13? Nothing came up on a search.

Thanks Ya'll!
[Verizon Samsung Galaxy S III] Master Cylinder:
Dang!! Ain't YOU a blast from the past! Glad to see you around! Your legend is kept alive around here ... :)
[Verizon Samsung Galaxy S III] mastamoon:
:D

Hey man!

Im still using my d2 for desktop duties, playing music n such while at work.. but was thinking about getting a MHL adapter and turning into more of a garage PC for watching Youtube How-To's an such. Im guessing it doesnt work but just thought i'd stop by and ask before I spent 20 bucks on amazon lol.

Glad to see this thread still kicking a bit. Cant believe people still use this phone as a daily. D2VZW was released 3 years, 9 months, and 9 days ago haha. That's like forever in phone time.
[Verizon Samsung Galaxy S III] AyUaxe:
All hail legendary [MENTION=2963287]mastamoon[/MENTION], d2vzw's blast from the past bridge to the future!

According to http://www.mhltech.org/devices.aspx?tid=1 , SCH-I535PP, i535 has MHL capability, but requires 5-pin to 11-pin adapter tip. I guess that only partially answers the question, since we don't know if the functionality is maintained in CM13. I haven't tried wifi screen casting with CM13, but it worked well with a Roku stick last time I tried it (like in December, so on CM12.1).
[Verizon Samsung Galaxy S III] Roger W:
Welcome back!

I just tried my MHL dock and it doesn't do anything, sorry. I know the dock works because I once tested it on someone's stock d2, but mine's been on CM since I got the dock (and, yes, the 5-11 pin cable tip), so I've never seen it work on my phone. I don't think there's any particular setting needed to turn it on; I cant find one and prior threads elsewhere said that (older) CM didn't support it on this device at least.
[Verizon Samsung Galaxy S III] AyUaxe:
Yeah, I randomly appear in the middle of Lake Pontchartrain when I should be home in bed. Wife and I are developing a comedy routine about it (mermaids may play a part).
[Verizon Samsung Galaxy S III] mastamoon:
Awesome but not awesome! Thanks for testing it out!

So I either put it back to stock or see if another rom out there works. Or find another older phone where CM and MHL do play nice together.