yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Ibuprophen:
I don't believe your flashing had done that. It may be the power button...

Try turning it off, remove the battery then just gently tap the top right portion of the device (where the power button is). Then put the battery back in and try turning it on.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise

---------- Post added at 04:53 PM ---------- Previous post was at 04:44 PM ----------

Also, the Tracfone S3 is SCH-S968C and further information is located in these 3 links.

https://xdaforums.com/showthread.php?t=2539018

http://www.samsung.com/us/support/owners/product/galaxy-s-iii-tracfone

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[Verizon Samsung Galaxy S III] rjuds82:
Didn't work. Upon searching I saw a post in another thread

So maybe the modem fw flash was the cause, although not sure what he meant by "wrongly", but mine did say successful. I had a feeling I shouldn't have flashed it.
[Verizon Samsung Galaxy S III] Ibuprophen:
I've had a device die like that before and it was linked to the power button. It had just died all of a sudden. I had to use a skill i hadn't used in many years called Micro Soldering to replace it.

I'm not stating that that's 100% of what your issue is but, based upon what you stated, it looks like the same issue.

If you had, in fact, flashed the wrong Firmware, your device should have still booted but, would have reflected some type of error like being stuck in a boot screen or similar.

I've found, personally, that when i had the same model as yours, i was able to flash the CyanogenMod for the d2vzw as well as the d2lte with them both working fine.

I ultimately feel (of course as an opinion) that your power button may have suddenly gone bad.

Please feel free to research this as i always encourage members to do.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[Verizon Samsung Galaxy S III] rjuds82:
Idk. Haven't noticed or had an issue with the power button before. And used it minutes before to reboot into recovery. I suppose anything's possible. Although, I did have to boot into recovery again at the time from powered off status, and it took like 5-10 min of trying before I finally got recovery because no combination of buttons would work. It just kept trying to boot straight up. Maybe the power button was failing right then. But it did power on with each attempt, just seemed to skip recovery, so idk. Thinkin of trying the microSD debrick trick but I only have an 8gb card. If not I'll just see if a family member has an unused phone.
[Verizon Samsung Galaxy S III] rjuds82:
I used an actual Samsung usb cord (I think) and now the red charge light turns on for a minute and then back off, but stays showing up in device manager as QHSUB_DLOAD. Even without the battery in. So pretty sure I need to do the SD card debrick trick. Unfortunately I don't have one and can't afford one as I'm disabled at the moment and broke as a joke.
[Verizon Samsung Galaxy S III] Fenix2002:
Absolutely. Almost everything regarding clean vs. dirty is a myth. You should be fine to dirty flash, although I still recommend a nandroid backup first just in case. lol. And I usually still clear dalvik and cache because it seems to help with stability (IMO).

The only time you need a clean flash is going between two different ROMs or when you're going backwards to an older nightly, or version, etc.

Read more here from invisiblek's G+ on the topic!
[Verizon Samsung Galaxy S III] Roger W:
Am I missing something obvious with nandroid backups these days? I had to wipe over the weekend and both of my CM12.1 backups from November with encryption had problems after restore (to the same encrypted data partition), but also a brand new CM13 one without encryption, had the same after I reformatted data. They restore and boot all the way, but go into a crash loop of core processes like com.android.phone. The OS is loaded and I can (barely) use the power menu to reboot between popups, but can't get past there.

I'm using the current online nandroid app, default settings for TWRP, TWRP 2.8.7.1 , and it's worked before. I've done a full wipe of everything in TWRP including formatting data because it used to be encrypted. Same result.

I've also tried flashing the same build before the restore; I've tried flashing after, before boot, no luck.

My backup files are:

system.ext4.win

boot.emmc.win

cache.ext4.win

data.ext4.win

efs.ext4.win

recovery.emmc.win

thanks for any tips!
[Verizon Samsung Galaxy S III] Fenix2002:
I'm not sure, but spitballing I'd say encrypted file systems can't be backed-up and restored. The encryption key is probably lost or changed. It makes sense.. Android is a modified Linux system and if you lose the integrity of your installation, you lose your encryption key, AFAIK anyway. I've never attempted nandroid with encryption, so I could be way off base, but I'd say you're losing the integrity of your encryption key.
[Verizon Samsung Galaxy S III] pogeymanz:
That's not correct. I've restored nandroids of encrypted systems. I don't know what the issue is with this person's system.
[Verizon Samsung Galaxy S III] LegoFarmer:
What kind battery life are you guys getting?
[Verizon Samsung Galaxy S III] pogeymanz:
It appears that the nightlies are still not working for encrypted data partitions. Still getting the No Sim message on 12/23.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Much better than 12/12.1 for me it seems.
[Verizon Samsung Galaxy S III] LegoFarmer:
Interesting... What gapps package did you use? I ran two different nightlies and had bad battery life. Could be due to some apps. Should I use the nano package?
[Verizon Samsung Galaxy S III] XdrummerXboy:
I'm using open gapps from the OP, and I choose "stock", which is close to the middle of the options I think.

I still get bad battery life, it just seems to be a lot better than 12/12.1. Part of that is because I use cheap amazon batteries though.
[Verizon Samsung Galaxy S III] Fenix2002:
Last time I tested it for more than a couple hours, I got like 12 hours on a charge with moderate use. Mostly calls, messenger, and internet on WiFi with cell on in background. No games or heavy apps other than FB messenger. Nano GApps with other apps downloaded.
[Verizon Samsung Galaxy S III] LegoFarmer:
I use an extended battery, so how would you rate that in comparison to AICP or CM12 battery life?
[Verizon Samsung Galaxy S III] Master Cylinder:
So you've got no nandroid that will boot? I'm not sure what online nandroid app you're using but the one I used before worked, then it didn't, meaning after awhile, I never could figure out why, I would have data restore issues. I've seen this com.android.phone issue lately quite a bit as well.

Not sure if that helps but if you could get something loaded and booted then you could try without the online nandroid which in the end, and I even paid for it, I gave up because it became useless. It worked great, then it didn't. ಠ_ಠ
[Verizon Samsung Galaxy S III] Jaws4God:
any major fixes with the 12/25 release?

Merry Christmas!
[Verizon Samsung Galaxy S III] LegoFarmer:
For those coming from AICP Lollipop, how does the CM13 battery life compare?
[Verizon Samsung Galaxy S III] AndyYan:
Strange, I can add hotspot tile in notification pulldown, but when I quit edit mode, the tile disappears. This doesn't happen on my other devices with CM13. Makes turning on hotspot quite a bit more complicated.
[Verizon Samsung Galaxy S III] Fenix2002:
I don't think the 12/25 build had much of a diff.

I can't even add the hotspot tile to mine. It comes and goes. Managing quick settings tiles is really wonky still. Editing it earlier caused a systemUI crash for me. Lost status bar. Lol.

From reading changelog entries though, it seems like they're working on it pretty heavily.

Sorry I left you hanging when you asked me that question the other day. On CM12.1 I got like 10 hours (I think) last time I actually paid attention and didn't charge it until necessary. On today's build of CM13, I checked the 'projected battery life' based on a few hours worth of use and it estimated about 16 more hours? So, not actual battery life and not AICP comparison, but it might be helpful.

Merry Christmas and Happy Holidays, all!

Sent from my SCH-S968C
[Verizon Samsung Galaxy S III] stevet86:
I noticed the same thing. It turns out once I activated the hotspot from the settings menu the hot spot tile appeared and stayed in the notification pulldown. Thought it was just something I was being too picky about.
[Verizon Samsung Galaxy S III] AyUaxe:
Dirty flashed 12/24 over 12/10 cm12.1, delta gapps 601 base 12/09, & nuke-it. Worked for calls, lte, and wifi. Gapps updated and worked. ExtSD not seen in stock apps, threw corrupted error in ES, though pretty sure it wasn't corrupt, since loaded all flashed zips from it. Couldn't update super SU. Themes didn't load properly. No settings pulldown from status bar. Tried 10/04 dkp, before restoring back up of 12/10 & it seemed to work fine. Since this is my daily driver, I'll stick with 12/10 for now. No problem with extSD access after restoring. Happiest Holidays to all and thanks uber much to [MENTION=2385005]invisiblek[/MENTION], [MENTION=2044079]Nardholio[/MENTION] and [MENTION=4932679]decimalman[/MENTION] for all they've done for us and our little D2s that could (I think I can, I think I can, I think I can!)

P.S., howzabout opening up the cm kernel to tweaking with Adiutor etc, like dkp. Stock kernel settings seem crazy locked down.
[Verizon Samsung Galaxy S III] AndyYan:
Wow, can't believe that actually worked.

Long pressing on the hotspot tile will have a dialog ask you if you want to hide the tile, so I guess this is done intentionally. I can't for the heck of me figure out what's the meaning of this idea of hiding the tile after using it, when the sole purpose of tiles is for turning them on/off anywhere anytime.
[Verizon Samsung Galaxy S III] AndyYan:
Is adaptive brightness (and the light sensor altogether) working for anybody? I can see that it works under other ROMs, yet with CM13 I got no brightness change and the app Lux shows a constant reading of 0.
[Verizon Samsung Galaxy S III] Ibuprophen:
I had seen this before and had, successfully, helped another member but, it was quite some time ago.

I had just found the following thread from the Android Forums that just might help you with your specific issue:

[Verizon] May have hard bricked device. Please help - Android Forums

Though, the title does refer to a Bricked device, the information does also address the "QHSUB_DLOAD" as well.

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[Verizon Samsung Galaxy S III] Ibuprophen:
I was just wondering if anyone had bumped into Invisiblek's personal LineageOS mockup of the Official LineageOS website solely for his Unofficial releases?

Here's the link for Invisiblek's Unofficial d2vzw releases:

LineageOS Unofficial Builds for the d2vzw by Invisiblek

Just a friendly FYI... :)

"Live Long and Prosper..."

~Ambassador S'chn T'gai Spock

Sent via Communicator [D2VZW] from the Bridge of the U.S.S. Enterprise
[Verizon Samsung Galaxy S III] madmatt5510:
I'm brand new to doing anything like this. I downloaded the Archidroid v3 rom to put on my Verizon Galaxy S3 from stock and I need to know how to boot into recovery because everytime I try i get that stupid message from Verizon saying it detects the rom and locks the phone. Please help!
[Verizon Samsung Galaxy S III] Ibuprophen:
I believe that the following, device specific, thread may be helpful for what you are looking for.

https://xdaforums.com/showthread.php?t=2199042

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
[Verizon Samsung Galaxy S III] jerryspring:
Did you ever get any ROMs post kk for the locked bootloader?
[Verizon Samsung Galaxy S III] J-Lindo:
No one did, and no one will.

But for what it's worth, afaneh92's SuperLiteROM is the absolute best for a locked bootloader S3.
[Verizon Samsung Galaxy S III] afaneh92:
No rom only stock, and cm11 but its buggy and need some work to boot.
[Verizon Samsung Galaxy S III] jerryspring:
No rom only stock? Huh?

---------- Post added at 05:33 AM ---------- Previous post was at 05:28 AM ----------

Too bad we couldn't flash the 4.1 bootloader to get to be able to unlock bootloader.
[Verizon Samsung Galaxy S III] J-Lindo:
I suspect he means no AOSP ROMs.
[Verizon Samsung Galaxy S III] AndyYan:
Also, camera often refuse to take shots - pressing the camera button will have it become gray, and then swiping right to the camera roll will show you a blank picture with a progress bar that never proceeds. Is nobody encountering this?

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Verizon Samsung Galaxy S III] Fenix2002:
Everybody is encountering that, to varying extents. On different builds, I'm seeing "can't connect to camera" and the in-progress bar for others (especially video). I have a lot of bad freezing issues.

Quick work-around that helps about 75% of the time: in developer options, enable back button to kill app at the very bottom. When you exit the camera or it freezes, hold the back button until it kills the app. It will usually let you use it when you go back.

To answer your last post, I've seen issues with brightness sensor, also. LogCat showed an error.
[Verizon Samsung Galaxy S III] static.chaos73:
I've had some issues with brightness/color settings. I tried out the live display and that works great. But when you opt out of it, you have to go in and manually change the color settings to normal before disabling it, otherwise I ended up with the "night" mode all the time...sort of a yellow tint to everything. But it did change the color between day/night just like flux does.
[Verizon Samsung Galaxy S III] AndyYan:
Yeah, force stopping the camera app did the trick. This isn't my primary phone so I don't have to set the back button kill, just occasionally snapping won't be much trouble. Hope the brightness issue gets addressed soon.

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Verizon Samsung Galaxy S III] Master Cylinder:
"Unknown" in Call History?

Is anyone getting "Unknown" in the call history after a call that's not in your contacts? I'm seeing the number and location of a call when it comes in but in the call log there is no record of the number even under "details." (I'm having the same problem on AICP MM.)﻿ I'm not seeing anyone else with this problem. I even did a test clean flash and had it.

But, my cm12 nandroids, or any other lollipop ROM works fine! Logcat attached.
[Verizon Samsung Galaxy S III] matt_man:
I'm seeing this on CM13 also. I haven't done any investigating yet because is not that big of a deal for me.
[Verizon Samsung Galaxy S III] Master Cylinder:
Ok. At least there is one other person. I know it works on some other devices. What about anybody else? :confused:
[Verizon Samsung Galaxy S III] yorkwar:
I have this problem too even on 2016-01-03 nightly. Cannot find anyway to figure out the calling number.
[Verizon Samsung Galaxy S III] Master Cylinder:
According to [MENTION=1782878]Stealth111[/MENTION], the latest nightly should fix this.:highfive:

---------- Post added at 12:59 PM ---------- Previous post was at 12:57 PM ----------

Anyone having bluetooth issues?

My earpieces pair and connect normally but the sound does not route to the earpiece, but stays with the phone. Selector on the in-call page doesn't effect it. (I did forget to try external speaker maybe?)

EDIT: Will try the 1/4 and report back on these issues.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well Zip-a-Dee-Doo-Dah! (EDIT: I'm not being sarcastice!) An unknown caller's number is now stored in the call log on 1/4! Yipee!

Bluetooth is a scrambled mess. On 1/4, I was getting "Unfortunately, Bluetooth Share has stopped." and no function at all. However, when I pressed back button long to kill a message showing "AudioFX Killed" would show up, even multiple times in a row! So, I froze AudioFX and could get Bluetooth to pair and connect with my devices, but same problem as before - no sound routed to the earpiece. But, I activated bluetooth and my earpiece mid-call once and the sound came to the earpiece. Next call not, though. Also the call cannot be really released while bluetooth is active and it's not functioning right, the dialer gets hung up. I'll get a logcat before the day is over. (Uh, ..., I am running Xposed. :o I'll give it a try without it, too.)
[Verizon Samsung Galaxy S III] Master Cylinder:
Here's a logcat for the Bluetooth sound misdirection :

http://dl.dropboxusercontent.com/1/view/l9s9br96wajdfb4/Public/Bluetooth_sound.txt
[Verizon Samsung Galaxy S III] Fenix2002:
haha, you're a machine, Master Cylinder.

Is anyone actually having any luck with the front camera? As of today's build (1/6), the front camera is still screwed for me. The back camera is flawless, but if I try to use the front camera at all, it freezes, and it's a toss-up whether it forces a hard reboot or not. If it doesn't force a reboot, it jacks up the entire phone and everything lags. Usable, but miserable.
[Verizon Samsung Galaxy S III] Master Cylinder:
LOL! Yeah, well my namesake is in fact a machine.

I have the same thing with the front camera. Seems like it worked at one point. Do you have the same problem with bluetooth I've described?
[Verizon Samsung Galaxy S III] Fenix2002:
Haha, makes sense. I wasn't thinking Felix the Cat, but master and slave hydraulic cylinders. Engineer brain, ya know? Lol.

I don't use Bluetooth. I've tested it for file transfers with my laptop, but that's it. Don't even own an earpiece or I would give it a shot next time I flash a nightly. Sorry!
[Verizon Samsung Galaxy S III] Master Cylinder:
Yeah, it's a pretty obscure reference. Probably not too many would get it. Maybe no one has!
[Verizon Samsung Galaxy S III] stevet86:
I'm on 1-4 at the moment. Just got done using Bluetooth streaming xm and making phone calls. Listened for several hours and didn't seem to have any problems using ford sync.
[Verizon Samsung Galaxy S III] Master Cylinder:
Well :p

EDIT: Sounds like that was all in your car? Mine was all earpieces. Funny - in the past on LP it was the car stuff that was a problem but earpieces worked!
[Verizon Samsung Galaxy S III] stevet86:
I have used my ear piece also without any major problems. Once in a while I could not disconnect the call with the ear piece.
[Verizon Samsung Galaxy S III] Fenix2002:
tl;dr:

Probably will not work. Try going back to a build you know it worked on, connecting, then flashing current build.

Full:

Even though I fully recognize that this is bull and pseudo-science, I'm going to bring it up anyway. Awhile back, I was having problems with my GPS on 12.1 builds. It would start, I could reset it and download AGPS data, all the typical troubleshooting, but it would never get a loc.-lock. Would rarely connect to more than one satellite, even on a clear and sunny day. Tried everything. Then came across a post somewhere here on XDA about the issue that said some weird settings come through even between ROM flashes that can affect hardware. Dubious as I was, I tried it, and it worked. Went back to stock, turned on GPS, downloaded AGPS info, got a good lock, then re-flashed the new ROM. Even though I recognize it makes very little sense, I've seen that settings can carry over between builds on telephony/data, GPS, BT, WiFi. Give it a shot if you have a chance. The post actually said you really only have to go back to the last build you know it worked on, connect, and then re-flash. Will it work? Who knows. Just a thought. It (seemed to have) helped with my GPS, may help with Bluetooth?
[Verizon Samsung Galaxy S III] XdrummerXboy:
Are you guys having any luck getting TiBu to work on 6.0? It's been sorta working when I backup and restore from the same install, but when I backup, clean install, and try to restore TiBu won't even recognize my backups, I've even adjusted the folder where it looks...

Backups are from 1/4 ish and restoring to 1/8 clean install
[Verizon Samsung Galaxy S III] dltccf:
I have CM13 loaded, but several apps that need root, namely wifi recovery and TWRP manager say I need root to run. How are these apps not seeing root?
[Verizon Samsung Galaxy S III] Fenix2002:
Have your enabled root for apps in developer settings menu?
[Verizon Samsung Galaxy S III] dltccf:
Forgot, Thanks.
[Verizon Samsung Galaxy S III] Master Cylinder:
I was having 10 different kinds of problems with TiBu on these cm13 builds. Couldn't backup an app, would only backup data and leave the description of the app missing; all of my app backups were "protected" and I couldn't unprotect them or delete them. All labels and schedules were gone (still working on this one, though I think I'll be able to fix that so I won't have to create new schedules and labels.)

My problem showed up as "This folder is not writable" in the dialogue that selects the folder to backup to, the one I've always used. I found a solution from [MENTION=2035300]gregferns[/MENTION] on a seemingly unrelated thread. The answer is on the Titanium Backup website knowledge base, like I guess the answer to everything really is. However, you have to use the current mapping of the external sd card instead of the one listed here, which seems to be for Samsung TouchWiz Jelly Bean or KitKat.

http://xdaforums.com/showpost.php?p=64184400&postcount=901

:good:
[Verizon Samsung Galaxy S III] Fenix2002:
Is anyone having lucky with the front camera yet?
[Verizon Samsung Galaxy S III] static.chaos73:
Nevermind, wifi scanning was on. :/
[Verizon Samsung Galaxy S III] Roger W:
Whose bug is it if Settings is indexed wrong? CM or the device branch?

I used the search feature of settings to pull up Smart Lock, which took me to the Security menu, but the setting wasn't there. I found it instead on the Lock Screen menu.

Separately, has anyone tried device encryption in the past couple weeks' builds? Last we checked on this thread, it resulted in a no-SIM error.
[Verizon Samsung Galaxy S III] XdrummerXboy:
Thanks MasterCylinder!

Also, I've noticed a lot of WiFi disconnects on 1/7 and 1/8... Could be my router, but it was fine up until I tried 1/8, gave me issues, tried 1/7, gave me issues, and sometime tonight or tomorrow I'll revert back further. I was on either 1/4 or 1/6, can't remember...

Edit:

Switching to the 2.4Ghz band seems to have solved the WiFi dropping issues.
[Verizon Samsung Galaxy S III] Fenix2002:
I'm pleased to announce that the front camera finally worked on the new 1/11 build for me. (I'm only occasionally seeing "can't connect to camera" and it's not freezing my phone when I attempt to use the front camera.)

I've had it flashed less than 30 minutes at this point, but so far I'm not seeing any other issues!
[Verizon Samsung Galaxy S III] Shakes The AssClown:
Are we at the point where this could be a daily driver? Thoughts?
[Verizon Samsung Galaxy S III] Fenix2002:
I've jumped the gun on that one before.. But I think I'd actually feel comfortable using it as a daily, based on this build (1/11/16).

It's not perfect.. But it seems like all the necessities are working, at least well enough, for my likes. The camera is still slightly buggy, but it works, and will only get better over time. Using the camera in a video chat worked, and then caused "can't connect to camera." But I managed to get it resolved without a reboot. [emoji1]

Not sure about Bluetooth or Smart Lock or any of that, not something I typically use.
[Verizon Samsung Galaxy S III] Jaws4God:
i do use smart lock so curious if that works . :)

does it allow on screen nav buttons?

Editable Nav Ring Targets?

does google tap work?

thanks.