yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Fenix2002:
What motion sensor type is the correct type? I thought it just used an aggregate of several types of sensors, but especially the accelerometer and gyroscope, and if you have "gestures" enabled, the proximity sensor. I think I remember reading that if the proximity sensor is enabled, it won't go into doze at all, and that the other sensors are polled for activity for a default of 30 minutes before Doze starts taking effect, meaning you can't even bump the table that the phone is on.

But that still could be dependent on the correct type of motion sensors.

Looking at your screenshot, I'm wondering a few things:

Is Deep-sleep a descriptive name for Doze?

Is Doze that's referred to there the Samsung Doze? (If you look in the system apps, I see one listed as Samsung Doze.. so I'm wondering if maybe that's showing up on that app, but isn't enabled because of stock Doze?)

If you feel froggy, maybe you two could try to see what the results are after using the app "Naptime".. it lets you tweak the settings for Doze and enable an 'aggressive mode' that will go into Doze the second you turn off the screen.. supposedly.
[Verizon Samsung Galaxy S III] YabbyYou:
Word of warning, the 3/22 build is not booting on my phone. I'm not sure what's up. After I flash, go to reboot, Samsung flashes on the screen, then nothing. I'm going to restore my backup now.

EDIT: Looks like it was just a bad download. I downloaded it again on a PC, verified the MD5 ("Captain Ramius: Verify our range to the target, 1 ping only") then transferred to my phone, re-verified the MD5 ("Captain Ramius: Re-verify our range to target, one ping only Capt. Vasili Borodin: Captain, I - I - I just... Captain Ramius: Give me a ping, Vasili. One ping only, please."). Flashed, cleared cache, phone booted up. Running it through the paces now. Sorry for the confusion above.
[Verizon Samsung Galaxy S III] beckx020:
03/22 bluetooth with music still doesn't work. Otherwise it's ok for me so far.
[Verizon Samsung Galaxy S III] YabbyYou:
beckx020 - same here with me. No bluetooth audio using the a2dp profile. Front facing camera is still wonky.
[Verizon Samsung Galaxy S III] beckx020:
YabbyYou, are you using the same camera as I am? How do you tell what camera it is?
[Verizon Samsung Galaxy S III] YabbyYou:
I have been testing with three different camera apps. The CM Snap camera, the Google camera and Camerazoom FX. None work properly with my front facing cam.

You can find out which you are using by going into the Settings, Apps menu and look at the details of the camera or cameras you have installed. The detailed name is near the top.
[Verizon Samsung Galaxy S III] beckx020:
I'm using the cm camera. I finally got it to crash with video then pics. Tried it again and it just works switching back and forth. How weird.
[Verizon Samsung Galaxy S III] Fenix2002:
Leading up to it working for you, what steps did you take? Dirty/clean flash? From what ROM & build to what ROM & build? Any other steps? What GApps? Are you on the Verizon S3 (i535) or the MVNO S3 (S968C)?

Also, anyone who didn't know (which included me), apparently they released TWRP3 for our device.
[Verizon Samsung Galaxy S III] YabbyYou:
Yes, all of this info would be helpful!

I knew about TWRP3 but I was not sure if it was stable and working on our phone. Are you using it?

---------- Post added at 11:13 PM ---------- Previous post was at 11:12 PM ----------

Are you taking pics in low light? What resolution? I can take pictures in low light with the front facing cam, but it's gotta be pretty dark.
[Verizon Samsung Galaxy S III] Fenix2002:
Getting ready to flash it over, so we'll see. haha. I haven't seen anyone in the TWRP forum freaking out and saying not to ever flash it. Gotta be a good sign, yeah?
[Verizon Samsung Galaxy S III] Jaws4God:
I took [MENTION=6342402]Fenix2002[/MENTION] advice.. got Retrica camera.. a few test pics seemed to work..

AICP stock front camera FCs for me..

via Tapatalk

Samsung Galaxy S3 (AICP 6.0.1)
[Verizon Samsung Galaxy S III] Fenix2002:
Seems like the issue comes from the way it focuses due to light in the picture. Best I can tell, Retrica doesn't do that. Therefore, no issue. Lol
[Verizon Samsung Galaxy S III] Roger W:
I've been on it for several weeks, works fine for flashes and also backup/restore.

Only quirk (and I think the old one did this too?) is that backup apparently doesn't cover /data/media which is the user-facing home directory, so when I reformatted after trying encryption again unsuccessfully, I had to move all my personal files back from other sources, the TWRP backup didn't have them. (or a pic I'd taken the day before)
[Verizon Samsung Galaxy S III] Fenix2002:
2.8.7 did that too. It had options to backup boot, System, Data, and cache. Unless you need to wipe everything with factory reset, really no need to do the /data/media partition in most cases. And it would make a HUGE backup that in some cases probably wouldn't fit on the internal storage. Lol

Edit: I'm on TWRP3 now and it seems nice. Got a bit of a facelift. Not really many new features that I noticed, except I saw that it can read internally formatted extSD now.
[Verizon Samsung Galaxy S III] Jaws4God:
It has been awhile since I put TWRP on my phone... can you let us know the best process to update? Do you have link to the correct version?

** EDIT **

I was able to search and find the TWRP Homepage, found the link and flashed it via TWRP... However on reboot to recovery.. it asked this:

"TWRP has detected an unmodified partition. TWRP can leave your partition unmodified to make it easier for you to take official updates. TWRP will be unable to prevent the stock ROM from replacing from replacing TWRP and will not offer to root your device. installing zips or performing adb operations may still modify the system partition.

Never show this screen during boot again."

What did you all select?

Thanks!
[Verizon Samsung Galaxy S III] Fenix2002:
I flash recovery through Flashify, and that's the same TWRP I got (d2vzw TWRP 3.0 from their website).

I got the same message, except it specifically mentioned the system partition, I thought? I can't remember what I chose, but it shouldn't matter since we're not going to be getting any official updates from now until eternity. Lol. I just let it modify system.
[Verizon Samsung Galaxy S III] beckx020:
Went in bight light and the camera does fc when I exit out. But takes as many pics as I want. Using I535. This phone was on cleanrom 8.2 when I installed TWRP 3.0 Then went back to 2.8.7 and back to 3.0. I was trying to get it installed properly. I started I think with the 03/11 or 03/12 build. I formatted everything I could. Flashed rom, loaded the new modem and whatever file, gapps, wiped, flashed rom and gapps. However, I needed the gapps mini because the nano version seemed to send the phone into a bootloop.

Now I just wipe the cache and Dalvik before and after the flash. Then boot.
[Verizon Samsung Galaxy S III] Fenix2002:
03/23 build

Front camera crashes repeatedly, no photos even in low light.

Device reboots when I get a call (doesn't even ring, just goes back to boot animation) but I can call out fine.

Going back to 03/22 (the last stable build for me)
[Verizon Samsung Galaxy S III] Jaws4God:
wonder of that means they are trying some fixes [emoji106]

via Tapatalk

Samsung Galaxy S3 (AICP 6.0.1)
[Verizon Samsung Galaxy S III] malik mohammed:
I want make root to my phone s4(5.0.1) please....
[Verizon Samsung Galaxy S III] YabbyYou:
Malik, sorry man, wrong forum, this is for the Verizon S3 only.

---------- Post added at 12:19 AM ---------- Previous post was at 12:14 AM ----------

Fenix, as always, thanks for trying the build out and reporting back to us. I've been watching the change log, nothing seemed to compelling so I'm sitting on the 3/22 build for now. I also haven't seen any movement on the gerrit log for the Bluetooth code that I hope will start to fix our Bluetooth issues.
[Verizon Samsung Galaxy S III] YabbyYou:
Anyone know anything about all those FM tuner commits that are being pulled into our nightly build? Do we actually have a working FM tuner in our Verizon S3?

Also, I noticed one of the commits is about enabling the output of the FM tuner to be sent over Bluetooth... If only we had a working Bluetooth audio profile ?
[Verizon Samsung Galaxy S III] XdrummerXboy:
In pretty sure I remember (at launch) speculation that our phone did, or at least that the chipset supported it or something. I did try some sort of FM Tuner app at some point, pretty sure still on stock, and I never got it working.
[Verizon Samsung Galaxy S III] Fenix2002:
Not positive. I remember reading that it was supposed to have one. Most new-ish have them, especially high-end. But the manufacturers and carriers usually leave them disabled, which probably means the firmware never supported it. There's been a big push in recent years to enable it in all smartphones (FCC and FEMA have made it a disaster safety issue).
[Verizon Samsung Galaxy S III] YabbyYou:
I've been running the 3/22 build for a few days. Yesterday, I lost LTE data and I still have not been able to get it to connect again. I've rebooted and cleared the cache a few times, nothing seems to help. 3G seems to connect, although even that seems a little unstable. Anyone else experiencing this on the 3/22 build?
[Verizon Samsung Galaxy S III] Fenix2002:
Have you tried making sure it's set to connect to LTE by dialing *#*#4636#*#* and going to phone info? I've seen that sometimes it sets itself between LTE/CDMA and CDMA auto
[Verizon Samsung Galaxy S III] raisins:
Just tried to clean flash the 3/26 nightly. I just downgraded from 4.3 to 4.1.2 and rooted / unlocked bootloader. I flashed the firmware posted in the OP, then the 3/26 nightly, and finally Gapps for MM. Now my phone will not boot up at all, and there is no response plugging it in. I am concerned I just bricked my phone. Anyone have ideas? Thanks
[Verizon Samsung Galaxy S III] iwearthebelt:
If you can manually go into download mode I would ODIN back to a stock ROM and start over again. This may be the only option you have if you can't get it to boot.
[Verizon Samsung Galaxy S III] raisins:
Thanks for the reply. By manually going into download mode, do you mean pressing Home, Volume down, and Power? Or is there another way?
[Verizon Samsung Galaxy S III] iwearthebelt:
Yup, home volume down & power. Are you able to boot into download!
[Verizon Samsung Galaxy S III] YabbyYou:
Fenix, good idea. I checked it out and it looks like it was set correctly. Strange that I lost LTE even though it was working good for a few days. I guess maybe I can make a jump to a newer build and hope it works. Not sure what else to try at the moment.
[Verizon Samsung Galaxy S III] Fenix2002:
That's so odd. Well, which build did you try and how is it?
[Verizon Samsung Galaxy S III] YabbyYou:
I haven't made a move yet, still running 3/22. I will definitely give an update when I install a newer build.
[Verizon Samsung Galaxy S III] XdrummerXboy:
I am by no means as knowledgeable as the others here, but I was under the impression that once you took 4.3 OTA you were hosed (minus maybe safestrap?):

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

A while back I came across a flashable 4.3 stock ROM with an unlocked bootloader from scottsroms.com though. I don't know if that means people got around the 4.3 OTA locked bootloader or if the flashable ROM was the only way to get 4.3 unlocked (and it had to be done prior to the OTA)

At any rate, good luck!
[Verizon Samsung Galaxy S III] Master Cylinder:
Ooooooooh!

If you took the 4.3 OTA with the locked bootloader, then used that hybrid "Downgrade 4.3 to 4.1.2★Unlock bootloader★Root " method and THEN flashed the firmware in the OP, you screwed the pooch! That method avoids downgrading one part of the firmware which is overwritten by flashing the firmware zip in the OP. At least that's the way I'm remembering it. You can unpack the zip in the OP and look at the 'updater-script' and see exactly what partitions are written to to be sure. There is an unbricking thread in that same d2vzw subforum - don't know if someone has come up with any magic to overcome this, but the main thing they should explain carefully in that "Downgrade" thread (maybe they do?) is that you can't flash any other firmware.

I've only known of one other person who did what you did and he ended up with a unresponsive brick. If you can get into download mode, you can Odin I expect, but that's the part of the firmware that is left untouched if I remember correctly. They do explain what you're changing out in the flash zip, and if you look in the Official CM12.1 d2vzw OP (in this subforum) "d2vzw ROM Extras" link you'll find partition tables that tell you what those partitions that are and aren't flashed do.
[Verizon Samsung Galaxy S III] YabbyYou:
I just installed the 3/26 build and my LTE has not returned. I still only get 3G. Any ideas?
[Verizon Samsung Galaxy S III] Fenix2002:
I only ever have 3G at best, so I'm not entirely positive. Have you tried messing with SIM, booting without it and then booting with it, see if something "resets"? Maybe LTE is down for service in your area? Idk. Spitballing here.

Is 3/26 stable otherwise? Except camera and Bluetooth I guess. Lol
[Verizon Samsung Galaxy S III] YabbyYou:
So I reviewed my build notes (yes I'm taking notes on each build) and found the last build that I had consistent LTE was 3/12. So I just dirty flashed back to that, booted up and BAZINGA, LTE returned. So I rebooted and flashed right up to 3/26. Booted up a little while ago and I have LTE. So strange. Anyway I'll see how long this lasts. I'll also run this build through the usual tests and see how it goes.
[Verizon Samsung Galaxy S III] YabbyYou:
3/26 build still can not use Bluetooth audio. Front facing cam takes low light pics but crashes as soon as the light level goes up. I'll see how stability and battery life are today.

Edit: I tried to get the FM tuner to work but I've had no luck yet. If anyone gets it working let me know.
[Verizon Samsung Galaxy S III] YabbyYou:
3/26 stability is good. No crashes or random reboots. LTE worked for me all day when I was in an area with LTE signal. Battery life doesn't seem that good. I haven't found any new problems yet.
[Verizon Samsung Galaxy S III] Juni10:
Plz tell me which is the best rom for s3 e210L???
[Verizon Samsung Galaxy S III] Fenix2002:
That's the Korean S3 model isn't it? I have never come across anyone else here who had that type. Since this is the forum for the Verizon Wireless S3, I do not think you'll find what you are looking for here. Sorry.
[Verizon Samsung Galaxy S III] wadhwaa:
Yes I did flashed this combo but no luck still same issue, please note I am using a non verizon sim in this phone i.e. I got it unlocked in India using Vodafone sim phone was running fine on stock rom after unlock but after I decided to go for custom ROM i started facing this issue of no incoming calls last I have tested now CM13-20160321 but no luck again

---------- Post added at 12:25 PM ---------- Previous post was at 12:19 PM ----------

Hi,

Yes this was first time I installed a custom ROM, please note I bought this phone from US and got it unlocked in India using Vodafone Sim phone was working fine on stock ROM then I decided to upgrade as I never got updates on this model in India so I installed CM13 20160217 to start with, Yes I did a clean flash using CWM recovery app before installing, I did cleared delvik/cache again after installing apps but no luck, since then I have been trying other releases hoping that probably some release will have solution to my problem, last I tried CM13-20160321 but again no luck everything works fine except incoming calls don't come in

Thanks in advance
[Verizon Samsung Galaxy S III] Fenix2002:
I'm not terribly familiar with Vodafone and mobile devices in India, so forgive me if I am mistaken on any of the following, I am only trying to help.

A quick search via Google shows that Vodafone is a GSM network, whereas Verizon is CDMA/LTE. That would make your device incompatible to Vodafone IF you really have the SCH-I535.

Are you certain you have the SCH-I535, also known as d2vzw? If that's the case, it almost definitely won't work on Vodafone India. Apparently TATA Indicom is CDMA/LTE though.

If you have the i9300, which is GSM, it will work on Vodafone India, but you are in the wrong forums and flashing the wrong files. If your device was working with Vodafone on stock ROM, this is most likely.

I could be wrong, and probably am. We don't get many people using our device internationally. The more specific information you can give us, the better we'll hopefully be able to help you.

On a side note: gotta get rid of CWM. It doesn't play nice with newer ROMs. You should look into TWRP.
[Verizon Samsung Galaxy S III] YabbyYou:
I have to second this post by Fenix. Summed up everything I wanted to say before I had a chance to write it! I hope that gives you some answers wadhwaa.
[Verizon Samsung Galaxy S III] Master Cylinder:
I would like to put a potentially positive 2 cents in here: On CM12, one was able to use this phone and ROM on a GSM network IF they flashed the d2gsm_rilblobs.zip and it could work! I don't know of the status of CM13 for this. You could flash this file and see if it helps? You could flash the latest CM12.1 or the AICP Lolly for our phone and these blobs as well and may get a working custom ROM that still kicks a lot of butt and has none of the bugs MM still has for us.

Also I would use TWRP without question, rather than CWM. Go to the official CM12.1 thread OP in this sub-forum and find the details there, as well as the files you'll need.

:good:

EDIT: There is an official "release" CM12 build that is still available from the CM download site, dated 11/17/15.
[Verizon Samsung Galaxy S III] wadhwaa:
Appreciate your efforts Sir!

I have sch-i535 also known as d2vzw, I got phone unlocked in India from a local market and used it on vodafone sim for 3 years, I just love the hardware this phone has samsung's custom UI makes it lag but surfing through net I found there are custom ROMs available which could improve performance and I installed CM13 using CWM, faced incoming call issue then I started hunting for solutions

I have tried using TWRP as well currently I am on TWRP, I have removed CWM

I have tried flashing latest modem available on invisiblek

I searched for older stable version and tried CM10.2 on which my phone works fine there are no issues with incoming calls but on this one I can't send outgoing messages

I read of AICP ROM to be a stable one, I tried flashing their stable version I guess AICP-10.1 or so but again no incoming calls

I contacted admins of CM forums they routed me to log a ticket on JIRA

JIRA guys told they won't accept my ticket I should post same on forums so I again posted to forum

CM team asked for my catlogs I shared same and they told me logs have been shared with developers now it's upto them if they would like to fix it in next nightly or not

Currently I try to flash new CM nightly hoping probably any of it would have fix for me

So that's a long story :) I don't know what's left for me to try further I guess I will have to live with CM10.2 with no outgoing messages

I really appreciate your help sir, initially no one responded to my post so I just stopped checking my posts here hence apologies for delay in replying back

Regards,

Atul

---------- Post added at 05:48 AM ---------- Previous post was at 05:21 AM ----------

Thanks for replying back, I have downloaded the release CM12 build but what I can't find is d2gsm_riblobs.zip all the links to this file are not working if you can help me with this file i wll try flashing this one and check if this works for me

Regards,

Atul Wadhwa
[Verizon Samsung Galaxy S III] Master Cylinder:
If you just scroll to the bottom (or the top) of this page, you'll see the links that indicate where we are in the structural hierarchy of the xda-developers site. There's a house and to the right are the names of the sub-forums which are live links and that is what I was referring to to get you to the Official CM12.1 OP where all info and files are. This is just one of a few ways that you can understand and navigate around on this site. It would be beneficial to you, and everyone messing with their d2vzw, to see what sub forums and threads there are in the d2vzw section of xda-developers.com,.

However, just for you ;) I'll paste the link here to the extra file stuff that I referred to, where you will also find some later nightly builds of CM12.1, which is in the official CM12.1 OP: d2vzw ROM Extras It's on Google Drive so after you select the file you want to dload, it actually opens the file for some reason, and then you have to select the arrow above to activate dloading.

Also, you can try cm11 - you don't have to be stuck on cm10.x. There are cm11 release links below the cm12 release links on the official dload site.
[Verizon Samsung Galaxy S III] wadhwaa:
Got the file will try flashing it

Thanks Again!
[Verizon Samsung Galaxy S III] YabbyYou:
Ok, I created an account on the CM JIRA Issue tracker. I put my name on one of the open Bluetooth issues to see if I can help push this issue forward and try to get some resolution for us. If anyone is interested, I'm starting with this open issue: https://jira.cyanogenmod.org/browse/NIGHTLIES-2680

If they want me to create a new issue specifically for our d2vzw then I'll do that and attach some logcats or anything else. We'll see what happens.
[Verizon Samsung Galaxy S III] Master Cylinder:
Awesome!

You could also go to that Official CM12.1 thread and in the search field for the thread search on "gsm" because there was a bit of action about that.

There is a d2vzw thread on the cyanogenmod.org forum, you could check over there. There are other android forums but I haven't visited them in awhile.

Good luck, and tell us what happens! :good:
[Verizon Samsung Galaxy S III] beckx020:
Should more of us post/add to that so they know there are more of us?
[Verizon Samsung Galaxy S III] YabbyYou:
That's a great question. I would defer to the others in here for an answer though. I'm still kind of new to the whole CM contribution scene so I wouldn't want to upset anyone by giving the wrong advice. There are a lot of open issues on the cm jira site and there are a lot of people who can't follow directions on how to create an issue. I wouldn't want to step on the mods toes in there. I'm trying to wade into it slowly. However, if some of the long time members here feel it would be a good idea, I would be happy to hear from them. I of course will pass along any info I get to this group.
[Verizon Samsung Galaxy S III] wadhwaa:
Thank You So much I some how managed getting to Rom extras and yes I downloaded from G-drive and guest what this RILBLOB file did the magic, incoming calls works for me on CM13 itself it was just converting cdma to world phone that's it.

NOW this phone works BANG BANG smooth and so fast like never before ;):good::good:

THankyou [MENTION=5519140]Master Cylinder[/MENTION] YoU RocK

Thankyou Eeveryone [MENTION=7295238]YabbyYou[/MENTION], [MENTION=6342402]Fenix2002[/MENTION]
[Verizon Samsung Galaxy S III] Fenix2002:
You're welcome! I'm so glad we were able to help you. Please feel free to be part of the community here. CM13 is continuing to get updates with fixes and there are rumors that an "Android N" version may make it onto this device! Either way, you're always welcome here with any questions you have.
[Verizon Samsung Galaxy S III] Master Cylinder:
That's awesome! :good::good: Glad to know that still works even with cm13!

I bet yer phone is slicker than snot now if you were coming from 4.3 or whatever.

EDIT: by the way, props to [MENTION=2963287]mastamoon[/MENTION] for hooking us up with this way back when. He was blazing the trail for us for quite awhile.
[Verizon Samsung Galaxy S III] Fenix2002:
lol did anyone give the 4/1 build a shot?
[Verizon Samsung Galaxy S III] iwearthebelt:
Lol . I almost forgot what today is. Good one! No issues here.
[Verizon Samsung Galaxy S III] YabbyYou:
I was going to give it a try, is the "No issues here" comment mean you are running the 4/1 build?