yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] J-Lindo:
Anyone else having trouble connecting it to a PC? I've tried two different cables (using ports directly on the motherboard), both of which always start charging, but nothing else. Sometimes Windows (10) will pop up something about a USB device malfunction. Going into Dev Settings and manually switching "Select USB Configuration" to MTP has no noticeable effect.

I'm updated to build 11/08, and the problem persists. Default kernel, Xposed not yet reflashed.

It's entirely possible that for some reason neither cable wants to transfer data, but I remember having both of them work in the past. So, any ideas past finding another cable?

Update: If ever someone travels down these old forums again, I'll at least share the solution I eventually found, if someone else encounters this strange issue. With the phone plugged into my PC, I just went to Dev Settings, disabled and re-enabled USB Debugging, restarted the phone (still plugged in), and that's all there was to it. I was able to select whether I wanted to just charge, transfer files, import photos, etc., and Windows 10 sees my phone just fine. All is well! Worked on my ol' S3 (Nougat) as well as my sister's S7 Edge (still on Marshmallow).
[Verizon Samsung Galaxy S III] Master Cylinder:
No. I just tried it on my 11/8 and it works normally. It initiates 2 notifications in the notification pull-down shade, 1 of which, if selected, gives one the chance to select to transfer file (MTP)
[Verizon Samsung Galaxy S III] Master Cylinder:
Phone works? I don't think it did on mine when I flashed 14.1. How's your battery?
[Verizon Samsung Galaxy S III] Stealth111:
Camera seems to be worked out on the latest cm14.1 build!!! Hoping to post a new build later tonight! Stay Tuned!

damn, invisiblek, damn is all I can say..... Make it so! gps, CHECK, bluetooth, CHECK, phone and data, CHECK, camera, CHECK, fast and smooth, lighning quick, CHECKKKKK! :)

COME AND GET IT!!!

http://download.invisiblek.org/roms/cm-14.1/d2vzw/

Stealth111
[Verizon Samsung Galaxy S III] Master Cylinder:
Bloody hell! It's too good to be true. :fingers-crossed::highfive:
[Verizon Samsung Galaxy S III] mamarcac:
14.1 Daily Driver worthy?

Holy...this is fantastic news. How's the stability so far - any random reboots or cell signal drops? Man I'm tempted to flash it this weekend.

[MENTION=2385005]invisiblek[/MENTION] is a gift we don't deserve!! :cyclops:
[Verizon Samsung Galaxy S III] Stealth111:
Daily Driver? YOU KIDDING ME? LOL :) I shall NEVER go back to cm13 again!!! :D This thing is SOLID! No reboots at all, and signal drops are nowhere in sight! I have thrown the kitchen sink at this thing all day long, and have only found 3 small issues, which 2 of them have fixes in place for next build by invisiblek. I seriously can't begin to tell you how well this thing runs. Camcorder is all that is borked right now, but small beans IMO. It is smooth, crisp, fast, and the battery life has been fantastic all day. Invisiblek seriously is flat out unbelievable for taking the time out to give "One of the best selling phones of all time" another breath of life!

d2 has gone from: cm-9.0, cm-10.[0-1], cm-11.0, cm-12.[0,1], cm-13.0, to cm-14.1!!

Stealth111
[Verizon Samsung Galaxy S III] J-Lindo:
In that case, what the hell. I'm gonna give it a go. I'll report back here when I get it going! Not gonna lie. I'm kind of excited now :D :fingers-crossed:

Edit: First off, WHOA. This is FAST. It runs amazingly well. A million thanks to you, [MENTION=2385005]invisiblek[/MENTION]! For everyone's information, as can be guessed, it's still a little buggy. Some apps (notably apps Gmail and Pixel Wallpapers installed via 7.1 openGapps aroma) are having issues recognizing that there is, in fact, any sort of internet connection. I'll uninstall them and try reinstalling from the Play Store and see if that makes any difference, as Play Store apps (like Snapchat, save for the ever-persistent camera video recording issue) are working perfectly fine. Call, text, data, and wifi all working. Haven't tested bluetooth or GPS yet, but I'm sure I'll have a chance for that soon. The most interesting bug happens when I boot up the phone: it boots up fine, but first shows an error message saying "Settings has stopped", with options "Open app again" (which solves the problem every time so far) and "Mute until device restarts".

Also, small issue: I like my battery icon to be the circle, but selecting it keeps it at the normal battery-shaped icon. The other formats and options work fine. Not a huge issue, but eh. It's there.

Edit 2: Gmail still doesn't sync properly and the Pixel Wallpapers app doesn't want to download those daily rotating wallpapers. Not sure what the deal is, but I imagine they'll be fixed in future builds. Also, I managed to accidentally reproduce that weird Settings error; when in Wireless and Networks, there's a button a the bottom labelled "Tap & pay". I was curious, so I tapped it, and I got the same error I get when I boot up. Anyone have any idea what that is?

Also, dkp for 7.0 works on this build :)
[Verizon Samsung Galaxy S III] canodroid15:
Running great here! I completely agree [MENTION=1782878]Stealth111[/MENTION], not ever going back. I have the build running on my d2att as well & it works just as good. All I did was delete the getprop lines & flash the d2gsm ril blobs. Had LTE on first boot ? both d2vzw & d2att running tops! Thanks a milli [MENTION=2385005]invisiblek[/MENTION] & all who have worked on this device for soooo many years! You guys are BEASTS! ??
[Verizon Samsung Galaxy S III] Stealth111:
Glad to hear it went well for you! As mentioned in my post, the setting crash on first boot (same as the tap and pay crash) should be fixed in the next build. The statusbar not allowing clock position changes to stick for some choices, as well as the battery icon choice is also known and being worked on. I will say that I installed this build, and installed the opengapps 7.1 Pico arm build right after I flashed the rom zip, but before it was ever booted, and then proceeded to install gmail from the Play store after setting up the basics on the phone, and it is working perfectly. No syncing issues after 2 days running still. There may be a few more bugs crawling about waiting to be discovered, but, hey, you must admit it is pretty damn polished for the second 14.1 build! LOL! :)
[Verizon Samsung Galaxy S III] canodroid15:
word! ?
[Verizon Samsung Galaxy S III] Master Cylinder:
Joy! Rapture!

CM14 is landing

It’s been a long wait, but tonight we will kick off the first CM14.1 nightly builds (based on Android 7.1) for a handful of devices. It’s still very early on for this release and a number of features (like Themes) aren’t available yet, but development is progressing.

The devices which are part of the first push:

angler (Nexus 6P)

bullhead (Nexus 5X)

cancro (Xiaomi Mi3w/Mi4)

d855 (LG G3)

falcon/peregrine/thea/titan (Moto G variants)

h811/h815 (LG G4)

klte/kltedv/kltespr/klteusc/kltevzw (Samsung Galaxy S5)

oneplus3 (OnePlus 3)

Z00L/Z00T (Zenphone 2)

from: http://www.cyanogenmod.org/blog/cm14-is-landing

Also, AICP has already pushed out nightlies for about 50 devices! Not ours, though.

Dirty flashing over 7.0 created a gully-washin' storm in my phone. Also had trouble getting Aroma GApps in the first couple of times, though I might have been distracted by something. I can't believe this thing DOES NOT NEED TO OPTIMIZE THE APPS? That sure makes flashing very pain free.

Still putting it through it's paces but phone, wifi and data all working! Looking REAL good.:silly::good::D:victory::highfive::cowboy:

All Hail [MENTION=2385005]invisiblek[/MENTION]!
[Verizon Samsung Galaxy S III] gcounts:
My daughter dropped her s4 mini for the millionth time and it finally died. I loaded up the latest 7.1 on my s3 and popped her sim in and everything is working. She's coming from old old old tw, so you can only imagine the shock of smooth, slick, snappy cm14 [MENTION=2385005]invisiblek[/MENTION] has put together. Really amazing. Calls, SMS, mms, all working.
[Verizon Samsung Galaxy S III] Master Cylinder:
Thats awesome!

I'm noticing that my Spotify works 10 times better so far. It had become a nightmare on 13 - took 60 seconds to start, and I had to start and close it multiple times just to get it up and running frequently. Love the Heads Up. I'm thinking about taking steps to protect this phone now (I was starting to browse Pixel/fi) Might even put one of my covers on it! Same screen protector from day 1 to day 1305. Not a scratch on my screen: a miracle of modern science!
[Verizon Samsung Galaxy S III] thelangosta:
FYI battery settings is doing the same thing on my m8. Percentage works but not circle. 14.1 is so fast and smooth I need it on all my devices!
[Verizon Samsung Galaxy S III] Stealth111:
New build is up! Camcorder seems to be good to go. One thing I did notice after a dirty flash over last build is that it threw a fit thinking it could not see my external sdcard. Knowing how things can be in the early phases from using CyanogenMod nightlies for the last 5 years, I decided to give it a good 5 minutes to settle in. Patience paid off, message went away and all is well. Rebooted for safe measure, no message, and works perfect like last build. A few of the small bugs that I experienced are also gone now as well. I will do a clean install later and report back anything out of the ordinary I might experience, otherwise this is another great build with additional progress made..

Stealth111
[Verizon Samsung Galaxy S III] jtnc:
FWIW I've found the 11/13 build less stable than 11/10. The main issue is my home key didn't function to go to the launcher nor bring up the task switcher. It just sat there like you had not pressed it. The other issue was setting advanced reboot did not bring up the secondary menu regardless of the toggling I did.

The caveat is this was a dirty flash to 11/13, so perhaps a clean flash would fix it. Dirty flashing back to 11/10 fixed the above issues. When I get time I'll try a clean flash and see. If it does reproduce on a clean flash, I am not sure if a logcat would show anything.

That said, Bluetooth is amazing for me so far. Seems at least as reliable as it was on CM 12, much much better than I ever had CM13 behaved. Not sure yet vs TW 4.3 was. No issues with phone calls either.

11/10 is very much a daily driver which amazes me given how early it is! Much less 7.1 on an S3! - john
[Verizon Samsung Galaxy S III] canodroid15:
[MENTION=4989583]jtnc[/MENTION], definitely clean flash! I don't have any of the issues you mentioned & the 11/13 build is much better than the previous. I haven't had the "settings has stopped" pop up on reboot either.
[Verizon Samsung Galaxy S III] Stealth111:
Agreed! I am also not experiencing any of the mentioned issues. When in doubt, wipe and flash! I would say that to be especially true with such early builds...

Stealth111
[Verizon Samsung Galaxy S III] jtnc:
Yep, didn't have time to clean flash until late Monday night, got greedy when tossing the new version on Sunday and things started fine so figured worth a risk. As you say, those issues disappear with the clean flash to 11/13. I haven't seen much difference between the two images for my use yet. But after more Bluetooth testing with my Toyota radio today, CM14.1 is interacting better than Touchwiz/4.x or Cm12. It still can't reconnect to the radio/receiver after switching BT off then on(or changing between two BT devices). But it does reconnect after power cycling the car! Whereas the other OS revs did not. No such issue with the jawbone headset, so I'm assuming it's a poor BT implementation by Toyota. Shocking I know.
[Verizon Samsung Galaxy S III] AyUaxe:
Clean flashed 11/13 N with latest dkp and she ran beautifully, but battery drain was more like a flush. Didn't see this on the earlier N builds. Are others seeing the battery drain (was pulling more mah than the charger could supply, just sitting idle)? Back on 13.x, 10/29 for now.
[Verizon Samsung Galaxy S III] canodroid15:
Strange, my battery life has been great latest N build. However, I just bought a brand new OEM battery & new charge block & cable. I have seen that happen "pulling more mAh than the charger could supply" when either the cord or block, possibly both start to go bad. I'm also running latest dkp as I wait for my home to kick out a new skatter kernel for 7.1! ???
[Verizon Samsung Galaxy S III] AyUaxe:
I suspect the battery, as it's still the original. No matter how well they're treated, eventually, they go bad. However, it's doing better with my 13.1 backup and same results with different chargers that work with my Quark, so....? I did restore data from my prior N backup, so that may have contributed. I want to update my 13.1 build and backup, then I'll get back on the N train with a complete clean install and new gapps.

BTW, been using Delta Gapps base for a while with good success. They seem to be kept well up to date.

I need to retry ScatterKernel--looks to be a great project. My first try was a little glitchy, but there was a lot going on, so I didn't get to work with it as much as I would've liked. How dare work and family interfere with 'droid tweakin'!
[Verizon Samsung Galaxy S III] canodroid15:
[MENTION=3056030]AyUaxe[/MENTION], I'd bet its the battery as well. I think you'll like skatter ;) he puts a lot in it & works with only the best code as well as fixing a lot so its compatible with our d2's. He had a lot of inspiration from decimalman as well as others & he is an awesome dude!

I usually go with Opengapps nano & TBO theme-ready gapps so I can theme properly (love my dark ui) lol. Delta is still a good choice tho. I'll be sure to let you guys know when a skatter 7.x build is close! ;)
[Verizon Samsung Galaxy S III] mamarcac:
Just wanted to jump in here and say I'm checking in on this thread daily and wanted to say Thank You to you all for posting your progress and results. It really helps the rest of us to see how the experienced folks are doing!

The progress with N on our d2's only months after it was even released is just mind boggling and incredibly exciting to see. :D
[Verizon Samsung Galaxy S III] J-Lindo:
Woohoo! New 11/17 build is up! I'm gonna clean flash it and report back. [MENTION=1782878]Stealth111[/MENTION], I'll flash it and Pico GApps as you suggested and see whether my issues are resolved.

The fact that these builds seem to be coming at regular three-day intervals is exciting!

Edit: 11/17's good. Sadly, no amount of clean-flashing so far is getting rid of my Gmail and Wallpaper issues. But otherwise, it's doing fantastic. Great to hear that, [MENTION=2385005]invisiblek[/MENTION]! Thanks for your work.
[Verizon Samsung Galaxy S III] invisiblek:
Finally got around to fixing my build script, they should upload daily now (assuming the build itself doesn't fail).
[Verizon Samsung Galaxy S III] canodroid15:
Woot! [MENTION=2385005]invisiblek[/MENTION], greatly appreciated! You are awesome ??
[Verizon Samsung Galaxy S III] lepa71:
Which gapps you guys are using with 14.1? I'm on TW4.3. Do I need to update TWRP? I'm on 3.0.2

Thanks
[Verizon Samsung Galaxy S III] gcounts:
3.0.2 is good..... Use open gapps ARM 7.1..... I chose nano.
[Verizon Samsung Galaxy S III] lepa71:
Did anybody try microg gapps? Is 14.1 a daily driver or at least close.

I don't expect camera/camcorder to work, but ... Is it?

Thanks
[Verizon Samsung Galaxy S III] gcounts:
Camera works, not sure about recording or playing video. My daughter is using the phone as a temporary because hers broke. But calls, SMS, mms, all work. So as far as daily driver goes, it is for her.
[Verizon Samsung Galaxy S III] Master Cylinder:
I'm on 11/17 and everything seems to work! Dirty flashed. It's pretty awesome! Used the camera (have been using it all along) took a selfie and a video just now.

I used OpenGApps aroma installer when I got going on 14.1(which is a humongous dload!)

:good:
[Verizon Samsung Galaxy S III] Ibuprophen:
I stick with Open GApps as recommended by Cyanogen for their ROM's.

I use the Pico (with Play Store and those that make the Play Store work).

I feel that if Open GApps work, then why change something that's not broken.

Peace and Love!

Peace and Love!
[Verizon Samsung Galaxy S III] Pierre2324:
Extreme battery drain on cm14.1 dont know why help?
[Verizon Samsung Galaxy S III] canodroid15:
Maybe you need a new battery, mine has been better than it has since kit kat lol.
[Verizon Samsung Galaxy S III] Pierre2324:
What is your screen on time? Will maybe get a new battery I get 2 and a half hour of screen on time max
[Verizon Samsung Galaxy S III] canodroid15:
Its not likely that you'll get more than 3hrs SOT on an OEM battery. I've had 3&½ hrs SOT but I had to set it up to get there. Custom kernel etc.. Also running a black theme helps too. On my brand new OEM battery I get between 2&½ to 3hrs SOT. I don't have a boat load of apps installed either. Just a few.
[Verizon Samsung Galaxy S III] AyUaxe:
Clean flashed 11/18 14.1 with a pico or base Gapps (Delta), plain and later with DKP. Pretty awful batter drain. Tried restoring data from prior backup, used Rom Tool Box to freeze every optional app, also throttled back dkp and activated more battery saving options in HEBF (look on XDA for it). Drain was still very rapid and continued even when plugged in. After almost 24 hours of leaving the phone on charge (comfirmed good charger/cable), checked stats in 3C Battery Monitor, which showed that CM System was 100% waked the entire time the phone had been on 14.1. Specifically, a light sensor, I think it said 33365, was keeping the system awake, even with everything else, including screen off/idle.

Switched to 11/17 13.1 build with my usual dkp etc. and immediately phone would charge normally. Of course, 13.1 is great and getting incrementally better, so it's no bad thing to fall back to it.

If anyone can advise how I can pull a log that will document the wakes in 14.1, I'd be glad to switch back and provide that. 14.1 has dramatically better wifi range and faster startup in direct comparison with the latest 13.1, so I imagine that as 14.1 builds mature, we'll once again see our lil D2s that could thinking they can, thinking they can and actually performing like a current generation device, thanks to [MENTION=2385005]invisiblek[/MENTION], the rest of the CM team, [MENTION=4932679]decimalman[/MENTION], and the whole D2 community!
[Verizon Samsung Galaxy S III] Master Cylinder:
I dirty flashed 11/18 but am seeing great battery life. I did have a problem with one of the previous ones but I can't remember which. I tracked down the offending app/service at the time. I'll keep looking around to see if I made a record of it, which I seem to remember doing.

---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------

PS - Flashing without optimizing apps is an advance that makes me want to cry with joy and relief! And, I always had to optimize twice because the first time it only got about 2/3s of the apps, so pull the battery and do it again. Quite a labor of love I guess., but now I wanna have a parade for Nougat and [MENTION=2385005]invisiblek[/MENTION]!
[Verizon Samsung Galaxy S III] canodroid15:
[MENTION=5519140]Master Cylinder[/MENTION], any noticeable changes in the 11/18 build? I'm still on 11/17 & its running good. I just noticed the 11/18 zip was a good bit smaller in size compared to the previous zips. Anyway, just curious lol. Ttyl ✌
[Verizon Samsung Galaxy S III] J-Lindo:
Well, I decided to go whole-shabang and wiped the whole phone (advanced wipe in TWRP, selected everything), and clean flashed the 11/18 build with GApps. While flashing CM, I do get two red lines of generic-looking errors (can't remember exact wording, but I can reproduce it and get it if anyone wants), and Gmail still. Won't. Work.

And it seems that, according to [MENTION=1782878]Stealth111[/MENTION], I'm the only one facing this issue. Any ideas? Any logs to make and show?

Also, I haven't noticed any horrific battery drain on 11/18.
[Verizon Samsung Galaxy S III] mamarcac:
I got 2 red lines when I flashed as well, it went by fast but it said something about "Error not able to write log to sdcard" or something along those lines.

Regarding Gmail, I think it was on CM 12 maybe where if you had a certain combination of items checked under your Google account that it was trying to sync, that it would cause problems. An easy possible fix is to de-select all the items in your Google account from Settings (Music, Photos, Gmail, Google Fit, Apps, etc.), then re-check only Gmail, Clear Cache & Data for Gmail under Applications, and see if she syncs up.
[Verizon Samsung Galaxy S III] Master Cylinder:
Also had the can't create a log lines. No prob. Never had any problems with Gmail, so whatever you got goin' I hope I don't catch it! ;)

I can't say that 11/18 is an improvement because I don't remember if there was anything wrong with 11/17 - that was so long ago I can't remember. (NOT kidding.) Had a couple of needs to reboot because of apps not able to access the microphone. Otherwise, everything is A-Kay.
[Verizon Samsung Galaxy S III] J-Lindo:
Thanks for the suggestion! Sadly, that didn't do the trick, though I may have found a potential clue. When I toggled off, then toggled back on syncing Gmail (only), I noticed that People Details attempted to toggle itself on, then instantly back off with an equally instant error message. Curious, I toggled it on, and the error message appeared. I've attached a screenshot. Think this might be related?
[Verizon Samsung Galaxy S III] lepa71:
Just FYI. I'm still on TW4.3 and I had big battery drain. It was related to people detail sync. I disabled it and battery life is back to normal.
[Verizon Samsung Galaxy S III] Stealth111:
New build posted, COME AND GET IT!! :)

File size difference was due to some dex preopt things! Back to normal now!

Enjoy!

Stealth111
[Verizon Samsung Galaxy S III] mamarcac:
Ah yes that was it! People details. Maybe try lepa71's suggestion. I recall over time I was able to re-sync people details but if you don't need it and can keep it off then go for it.
[Verizon Samsung Galaxy S III] J-Lindo:
Let there be rejoicing! After discovering that TWRP has a function to Format Data, I gave it a shot, uber clean installed the 11/23 build with 7.1 Aroma GApps, and the issue still persisted. But, in the Aroma installer, I saw that there was an option to install Google Exchange Services, and block the stock version. I didn't imagine there'd be much difference between the two, but I decided to give it a shot, as it was the last idea I had. Well, in sending myself emails (with and without attachments, between PC and phone), there seems to be a delay in sync, but it does now work! Hopefully this issue won't rear its ugly head again.

In other news, the Pixel Wallpapers app is now half-functioning, as I can use all the pretty wallpapers it has (after one error message per photo, it works), but the option for downloading new wallpapers to change every day over wifi still insists there's no connection to do so. And, of course, the issue with Snapchat recording video fine, but only uploading black with audio still persists (and, of course, stock camera and Snap Camera HDR record and save video just fine).

Oh! I just remembered something I wanted to ask. Speaking of cameras recording video, both stock and Snap only have options for recording in 720p at highest, but couldn't the ol' TouchWiz record in 1080p? What's up with that?

I appreciate the help and suggestions from you guys. This community is a big part of why I love Android :D
[Verizon Samsung Galaxy S III] mamarcac:
I misunderstood, when you said you clean flashed I thought you wiped (in TWRP):

Dalvik Cache

Cache

System

Data

Internal Storage (Data\media)

If you didn't do all of those I can see why there may have been "ghosts" hanging out that were wreaking havoc with your Gmail. Glad you got it sorted!