Search results

So....it looks like all the d2 branches just lost their maintainer for LOS. Has the S3 finally reach its end? https://www.lineageoslog.com/14.1/d2vzw

Kind of need more info, but just by the way you're posting...i'm guessing you're on android 4.4.2 (kitkat) with a locked bootloader....then you're stuck. No possible way to downgrade without killing the phone. This will never change. That's why majority of development for this phone has...

Good call mamarcac. I remember the FFC being fixed upstream and but I thought that was limited to only CM13. But in the process I totally forgot about Open Camera. I just downloaded and tried open camera and front camera works fine so my guess is something is up with stock camera. Not sure...

So I finally jumped over to LOS 14.1, from CM13. I've tried 2 builds so far 4/24 and 5/01 and am quite impressed with it. I've put it through its paces and the biggest surprise for me is the GPS. I haven't had the GPS working this fast since I was on a stock ROM. CM12 had a none existent...

Oh I'm use to downloading from the cmxlog site, and that completely removed d2vzw. I didn't dig as much on the official lineage site.

Good to see people still DD the S3. I'm still DD on CM13, and haven't made the switch because I'm still holding out for xposed to support it. Nice that people are giving quick reviews of it too...makes it more enticing for me to jump. Quick question, are you guys running the last official...

That sounds about right. GPS is a finicky thing on the S3. I could never get GPS to lock on CM12.1. I got GPS to lock on CM 13, except for the last few releases (I would say the ones around august & september, I was able to get GPS to lock). I'm still waiting for CM 14.1 to mature a bit...

Doesn't matter. Safestrap is only for 4.4.2 based roms. If you have 4.4.2, you're stuck on 4.4.2. That means no CM based roms and defintely no Lineage based roms. Since you're new to dvzw version of the S3, verizon locked the bootloader for good when it updated to 4.4.2. If you try putting...

No, you need to download the d2att specific version....which is out now. Check the Lineage OS download page.

Thanks as always invisblek. What a milestone for d2vzw to reach cm14.1 nightlies. My S3 is still chugging along as my daily driver, especially since the 6p didn't go on sale as I hoped during Black Friday/Cyber monday.

Yeah, I forgot about that until I read your post. I tried AyUaxe's settings...no dice. The best I can go is 384-1620Mhz, global -10mV with tierservative. And that gets a little unstable sometimes too. I'm sticking to stock freq. and voltages for now. I use kernel adiutor as my kernel...

I haven't ran into that problem. Something is pegging your cpu to max when your location is on. The CPU and battery are roughly located 2/3 of the way down the phone. Does it get really hot with location services is on but you're not using an app like Maps? Have you looked under settings...

Thanks AyUaxe. I'll give these a try. I tried to mess with the voltages randomly, but my phone was not having it. I hadn't messed with the CPU voltages and freq since I was on 4.3.

Just out of curiosity, what is your CPU freq/voltage list?

I'll also chime in. If OP is looking to update his phone, there are 2 paths. The stock path, which will be up to KitKat based roms (android 4.4) because that was the last update the S3 ever received. You could install something like superliterom (found in our android developement thread)...

Awesome. Glad it's working out. I think for most people, it's been working either straight up since 621 or those that set their selinux permissive themselves.

Yeah, I get the connectivity problem too, but I think it has more to do with the code than the phone. Mine typically happens on crashes that forces a self reboot which I think half the time is really a soft reboot, and since cm12.1...soft reboots have always caused a connectivity problem for...

I'm not sure, but you can probably make it work yourself by temporarily setting your selinux to permissive (see my post on the official cm13 thread... Second to last page). The whole problem is that selinux doesn't allow the camera to create a log file. If you temporarily set selinux to...

One more comment....I actually looked through that commit...wow, can't believe the limiting factor was that selinux wouldn't let the camera create a specific log file...a freaking log file...and then the whole FFC would just die from that...it just seems so trivial.

Awesome...there's the clean solution. I knew you guys would get it through soon...just didn't expect it to happen 1 day after I figured out what you guys were trying to do, and took the nuclear option of just opening up SELinux. Nice work!

Haha, I had a hunch that you probably used something like VIPER and had SELinux set to permissive because of it. Makes a lot of sense now why you had consistent luck with the camera now.

I got my FFC to work consistently now! I've tested the results with build 6/11 with DKP kernel, and it also works with build 6/18 with stock kernel. But I'm not completely sure about 6/18 because I dirty flashed from 6/11. So before I get into the further detail, what I did was set SELinux...

Just wanted to report back, 6/11 with dkp kernel still has problems with ffc. It works indoors with open camera, but is very jittery. Outdoors, open camera is way too sensitive with the light sensor and basically everything is white. If I mess with white balance, then the app freezes up. Any...

12/27 is the "latest" dkp right? Just want to make sure I'm grabbing the right file.

Just put 6/11 on my S3 last night after reading through the page. FFC is still borked for me when using stock camera, open camera, and instagram. I have a rev 0 processor which is what most of the early adopters have, but just wanted to report my results. Also, I'm running stock CM kernal...

You should give Naptime a try. I have greenify too, but I disable greenify's agressive doze and let naptime control that. Before I wrote this, I also made sure doze was activated and registered in GSAM (just because I had never used GSAM before), and doze seems to kick in quite readily. The...

Boo. But I may have jumped the gun a bit...seems like 531 is giving people over at d2att some trouble too with FFC FC....the wait continues

Anybody tried the 5-30 nightly? From looking at the changelog and also whats been said over at the d2att forum, some of matrixzones camera edits have made it into CM13 official nightlies.

Sorry Jaws to stalk you on this thread and CM13 official thread, but I really hope your conversation over on the d2att thread gets shown to the maintainers of either AICP or official official cm13 for d2vzw: d2att especially this guys response seemed promising...

Hey Jaws, saw you poking around over on the AT&T S3 thread. Looks like they finally fixed the ffc problem on the d2att. Now from the last guy that responded to you, I wonder how hard it would be to push the fix upstream to official CM13 so that it fixes all d2 variants (which I would assume to...

I've been lurking over on the AT&T S3 forum, and like someone else stated a few pages back, it looks like matrixzone over there has a lead on the problem and he was pushing out test builds over there. But then the VM (Virtual Machine) that he does his testing or compiling (he didn't state)...

Thanks, for the edit. Still waiting for the front camera to be completely fixed before I hop into this. Waiting patiently on CM12.1

I was quite surprised too, and that's why I had to post a general request for the last cm12.1 build. I'm very grateful that XdrummerXboy hooked me up with the download off his personal google drive. I know a ton of progress has been made on CM13 and I'm excited about it, but the remaining work...

Thanks XdrummerXboy, I just downloaded it, so you can free up your drive now.

does anyone have a mirror to the last cm12.1 release (12/10)? The link to it on the CM repository is dead since CM13, is now official. When I try to click the link for the 12/10 release, all I get is a "404" error.

I just started cyandelta after reading about it on this thread. Man...it's like crack...the ease with which you can flash nightlies. I use to dirty flash maybe once every 2 weeks, or when there's a major bug fix...but now, its like the old glory days of rom flashing. I just wish cyandelta...

I agree. I'm on 6/01...and I'm just so pleasantly surprised how quick development for CM12.1 has gone. It's probably the smoothest and snappiest ROM that i've had on the SG3, especially for a phone that's soon to be 3 years old. For me everything works...the only thing I don't use much of is...

Got a new update to google+ today...fixed my connectivity issues, on version 5.3.0.91034052

From what I've read on not just here, but for other phones...the usual culprit is location services via google now. The best way to test this is to turn off google now (which will just give you the standard pre jb google search) and see if that calms things down. If you want google now...try...

ISIS mobile wallet

Has anyone tried getting ISIS working on AOSP roms? Is it as simple as moving the nfc libs off of stock TW, and copy over the AOSP ones?

I had this happen sometimes when I move from rom to rom or a new build. I read somewhere its because the GPS cache gets corrupted. The way I fixed it was to download something like GPS Status and go into settings of GPS status, tools, Manage A-GPS state, and do a reset. Then go into the App...

I'm loving this build and everything is perfect except has anyone run into an issue with the stock gallery app? Mine is really laggy. When I'm scrolling through some of my camera roll, it would hang up and then think I selected a picture when all I'm doing is scrolling through. I've tried...

Are you sure you wiped data and data/media aka the internal sd. This happened to me when I used Philz recovery and tried the wipe option for installing new roms (its suppose to wipe everything) but it didn't wipe the internal sd because all my folders were still there after the build 23 was...

Just for clarification sake, is it okay to install build 23 with Philz? I know Beanz was having some trouble right before this release, and was checking out that bug with TWRP, but there wasn't and conclusions after that. I'm about to switch from 22 to 23, and I want to make sure my clean...

Post #2

I'm a little late to the party, but good to see you back on here Scott. Much appreciated for everything you've done to the S3...always liked your work.

I also attempted to make a patch with auto patcher, but failed. I read through pretty much every page of this thread and I have a few questions: I know edits need to be made to autopatcher...I edited the script so that it would work with any setup not just emmc. But since i'm trying to patch...

I've ran into a problem with Zinio magazine reader on CM10.1. It worked on stock ...but in CM10...it says i'm not connected to wifi (when I am) and every other app has no issues getting internet...very weird.

Nope...each are only compatible with its files. Why are you moving to TWRP...just curious?