yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] dingermtb:
No problem...Hope it works for ya

Sent from Outside the 9 using my Zombiefied Exodus OnyX
[Sprint Samsung Galaxy S III] techdog:
Anyone else having Bluetooth issues with the latest nightly, 06182016?

I flashed it and started having music drop out issues with Bluetooth when the screen was off - never had that before. Flashed back to 06112016 and no more drop outs.
[Sprint Samsung Galaxy S III] FLDataTeK:
I have this issue with my nVidia Shield K1 tablet with 6.x on it. Seems that it only occurs when you turn the screen off.. But with the screen on its fine.
[Sprint Samsung Galaxy S III] FLDataTeK:
Thank You very much.. This has solved all my issues with connecting to data.
[Sprint Samsung Galaxy S III] dingermtb:
No problem. REALLY glad it worked for ya:good:
[Sprint Samsung Galaxy S III] akira6968:
Do you use BT for media AND phone, by chance? With recent CM builds, a dual-use BT won't work for phone, you gotta disable media lol. For media, gotta disable phone....and it's choppy at best.
[Sprint Samsung Galaxy S III] techdog:
Yes, thanks. :good:

That's a known problem with these phones and there are a couple of bug reports open with CM to try and get this problem fixed. It's been going on for months with no resolution.

I did some more testing and it was only happening with streaming of SiriusXM, otherwise it was fine. However, I did finally resolve the issue by changing some of the governor parameters, the i/o governor, and TCP contention algorithm. This improved the performance of the phone overall. I had gotten lazy since everything previously was working fine. So, the issue with Sirius and BT forced me to change some of these parameters to make everything else work better.

BTW, there is an app called SoundAbout in the app store which, if you are mostly a phone user, might be a help until this issue is resolved. Using SA, you can re-route your bluetooth to the physical wired interface for media and the phone will function as a BT phone without having to change the BT settings. My experience is that it isn't so great at re-routing the phone, at least with the BT for this CM build. However, for using the phone and re-routing the media to the wired/speaker interface, it works like a charm.

More evidence, it seems to me, that the CM BT issue is with the phone interface code.

Edit: Here is the link for the CM Nightlies regression bug report https://jira.cyanogenmod.org/browse/NIGHTLIES-2986
[Sprint Samsung Galaxy S III] MellonHed:
Not a bad build

Been using this for about 5 days so far .... NO problems found.

Have been using Wicked X and the only thing I miss is the Reject List in the received phone calls ... was nice to add the spammers to the reject list. Trying out a call blacklister in Xposed so I guess I can live with my one "Complaint".

Overall a very solid build .... Good Job.
[Sprint Samsung Galaxy S III] akira6968:
[MENTION=2597290]techdog[/MENTION]

Thx for that link-

"Just to be clear. Nobody's working on this issue. As a workaround, you can go into Bluetooth settings and click the gear next to the name of your car's stereo system and then deselect using it for phone.

All of the people who could be working on this are either busy with real life (me) or have moved onto other phones and aren't really interested in d2 anymore."

At least I know now.

Any chance you'd have a moment to detail a little what you did with the kernel?
[Sprint Samsung Galaxy S III] KernelCorn:
Thanks for taking the time developing this. I just downloaded along with gapps and plan to flash when I get home tomorrow evening. It looks amazing!! From reading all the posts, it looks like this will be the only ROM I'll ever need. I'll report back after flash and use it for a bit. Thanks again!! :)
[Sprint Samsung Galaxy S III] techdog:
I have been having a lot of trouble with the last few builds. I have currently down-flashed back to the 7/2 build and that is working ok for me.

I'm not sure exactly what the trouble is but it manifests itself as stuttering and hanging in the UI. If music is playing, the music starts stuttering and stops playing. Bluetooth disconnects. I can re-create this fairly straightforwardly by: 1) connecting to a bluetooth speaker, 2) connecting to wi-fi (this actually sometimes causes bluetooth to disconnect), 3) running the sirius XM app (this app in particular seems to be a resource hog).

I down-flashed to 7/9 which had the same problems.

As earlier reported, I first noticed this issue with the first nightly after the 6/11 nightly with bluetooth. The 6/11 nightly worked well but the next nightly, can't remember the date, caused stuttering with bluetooth. I was able to get past that with some kernel and I/O governor tweaks.

Everything seems to work ok with the 7/2 nightly but I'm having trouble with the builds of 7/9 and after.

Is anyone else noticing this or is it just my phone? (Which is always possible...)

Thanks.
[Sprint Samsung Galaxy S III] Max Frost:
Do you mean playing music on the phone or using bluetooth to play it ? Mine is fine playing music on the phone but I don't have any BT device to hook up to try it . I've had a couple of occasions where my phone just started messing up after several delta updates but when I clean flashed everything was perfect again . Have you tried a clean flash lately ?
[Sprint Samsung Galaxy S III] techdog:
Sorry. I should have been more clear. Playing music over a bluetooth speaker. I haven't had any issues playing music over the phone speaker.

I have done a number of clean flashes.
[Sprint Samsung Galaxy S III] neondev:
Wow, this looks like a really great rom!

Just one question before I consider jumping on board. Does it matter what custom recovery you have? I'm on clockworkmod 6.0.5.0 right now.

Thanks!
[Sprint Samsung Galaxy S III] Max Frost:
Changes

Exodus users , in case your unaware Exodus is moving from Layers to the new Substratum theme engine . This should prove to be a much better and easier system to work with . As I understand it reboots will no longer be required after changing themes . I'd advise you to visit the Exodus G+ community to find whats different and what to do on the new builds . Here is the link to a pinned post telling you what you need to do to make the change . I think substratum has already been merged . https://plus.google.com/112199061099928069499/posts/8nhf4mSWp26 . Also here is a link to another must read https://plus.google.com/+SykoPompos/posts/9MTuCdVafna . This is a good introductory video that's very informative .

https://plus.google.com/+CharG/posts/XX2zAXKdbfi

https://plus.google.com/communities/106801227383087889476
[Sprint Samsung Galaxy S III] wayne-of3:
Wow! 27088. Best I could get was 23000 once using same settings as you. This is what I usually get
[Sprint Samsung Galaxy S III] idontknowhow:
camera app crash

Camera app crashes when rotating phone
[Sprint Samsung Galaxy S III] Max Frost:
On dkp or stock ?
[Sprint Samsung Galaxy S III] wayne-of3:
Stock. I also tried dkp and had to over clock to 1675 to get similar scores
[Sprint Samsung Galaxy S III] wayne-of3:
This was dkp
[Sprint Samsung Galaxy S III] Max Frost:
Yeah same here , I had to way overclock dkp to even get close . I haven't ran antutu since that post . I installed it just now and first run got 26936 with all kinds of crap installed and running . All stock settings . I haven't tried the new dkp kernal to see if it's changed any . Here's s a shot of the other bench and todays . [MENTION=3337806]wayne-of3[/MENTION]
[Sprint Samsung Galaxy S III] wayne-of3:
Well whatever you're doing is working. Lol:)
[Sprint Samsung Galaxy S III] Max Frost:
If I could overclock this kernal , no telling what I could get , maybe someone could modify it for us so we can flash it and O/C ? Exodus is the fastest smoothest rom I've ever ran on this phone .

---------- Post added at 11:09 PM ---------- Previous post was at 11:00 PM ----------

---------- Post added at 11:17 PM ---------- Previous post was at 11:09 PM ----------

I tried to dupe your issue but mine is working perfect . Any more details ? Try installing open camera to see if it stills does it . I like snap camera but open cam does work pretty good too . Anyone else having this problem ?
[Sprint Samsung Galaxy S III] idontknowhow:
It seems to happen only with the front facing camera

---------- Post added at 10:21 PM ---------- Previous post was at 10:17 PM ----------

and I just tried open camera and it totally froze on me while using it and even restarted my phone
[Sprint Samsung Galaxy S III] wayne-of3:
I've been using snap camera HDR with no issues
[Sprint Samsung Galaxy S III] techdog:
I've been using the last few nightly builds and the changes from the July nightly builds are dramatic - to the positive. The stuttering on bluetooth when playing music is significantly less. I had stuttering on bluetooth everytime I turned the screen back on. That is completely gone, now. I have been able to go back to more battery-favorable governor settings when streaming sirius XM over Wi-Fi through my bluetooth speaker.

Thanks for all those fixes. The ROM is working better than ever!
[Sprint Samsung Galaxy S III] idontknowhow:
Should I mention I am using the NJ2 baseband and the cwm rom manager does that make any difference?
[Sprint Samsung Galaxy S III] wayne-of3:
I'm on NDC. Have you wiped everything and clean flashed?
[Sprint Samsung Galaxy S III] idontknowhow:
It has been a while, is NDC a later one?
[Sprint Samsung Galaxy S III] wayne-of3:
Virgin mobile previous. Same as Sprint ND8

---------- Post added at 06:49 PM ---------- Previous post was at 06:47 PM ----------

Don't think that has anything to do with camera not working
[Sprint Samsung Galaxy S III] techdog:
I'm running some more tests, but I am having similar issues with the snap camera.

Edit: Ran some more tests and it is definitely only when using the user-facing camera. Open camera seems to work ok.
[Sprint Samsung Galaxy S III] techdog:
Does anyone else have a problem with having to re-install the SuperSU app after every update?

I don't know if I am doing something wrong or not but after every update when I go to Settings->Exodus menu->SuperSU, nothing happens unless I install SuperSU from the App store. Once I install SuperSU and I go to Settings->Exodus->SuperSu, the Exodus SuperSU screen shows up.

Any suggestions?
[Sprint Samsung Galaxy S III] dingermtb:
Same here on both, my S3 and OnePlusX. First thing I do now is install SuperSU app from PlayStore

Sent from Outside the 9 using my A.R.I.S.E. Exodus Zombiefied OnyX
[Sprint Samsung Galaxy S III] KernelCorn:
I forgot I posted this. Well I've had plenty of time on this ROM and I must say its the best one ever!! Coming from SlimKat 4.4.4 9.0, this ROM is king! Flashing with TWRP was a breeze. Battery lasts much longer. Anything I do on my old S3 is zippy. Haven't had any lockups or freezes. The developers did a fantastic job!! If you're looking for a ROM that makes your old S3 run better than the day you bought it. Look no further!
[Sprint Samsung Galaxy S III] KernelCorn:
I just ran that benchmark and scored 23158 on NDC.
[Sprint Samsung Galaxy S III] Max Frost:
Glad it's working well for you ! Have you visited the google+ community and downloaded any Exodus wallpapers etc ? Substratum theme installed ? Yes your right , definitely the king ! :) What I love most about it is it's different from CM based roms and snappy as hell . I'm pretty sure we'll have Nougat too .
[Sprint Samsung Galaxy S III] KernelCorn:
I had to re-flash Exodus last night (user error screw up hehe) and didn't include gapps this time just to see how Exodus runs. Is there a safe non play store APK download for Biohazard? It looks killer!!

Exodus runs even faster without gapps by the way. Battery life even better. I'm just having fun playing around with this ROM since my S3 is WiFi only and no service provider.

My girlfriend gave me her old d2spr S3 and I'm thinking about making that phone exclusively for experimental purposes. I'm gonna flash the DKP kernel and push the limits with the OC just to see what it can do.
[Sprint Samsung Galaxy S III] mustaph12:
please help, its not detecting my sim

saying NO SIM CARD
[Sprint Samsung Galaxy S III] KernelCorn:
Deleted by user
[Sprint Samsung Galaxy S III] KernelCorn:
I think you may have a hardware issue. I saw you posted the same thing on the Lollipop forum. The only Exodus ROM I've flashed is Marshmallow on my S3 and audio works just fine.

Are you wiping cache and dalvik between ROM flashes? Are you using TWRP for recovery?
[Sprint Samsung Galaxy S III] Gthunders:
yes in advanced i wipe data system cache and dalvik/art cache. Is Twrp 3.0.2-0 a issue with flashing the rom? And should the all the file system sizes remain on ext4?
[Sprint Samsung Galaxy S III] KernelCorn:
That's the latest and same version of TWRP I have. No issues that I know of. Ext4 is the norm as far as I know. F2FS is fairly new and now supported. This shouldn't matter with your audio issue.

Have you changed kernels? I'm on NDC. Is this strictly Bluetooth, ring tone or using headphones audio issue? Or no audio output all together? I'm no expert at this stuff, but I'm pretty good at figuring out Android issues. Hopefully someone will chime in that has the answer, but I'll do my best to help you out.
[Sprint Samsung Galaxy S III] Gthunders:
Hello yeah everything from the rom is stock no adjustments. What i just realized is that i am using d2bst based s3. L710t boost model. Could this be the reason for no audio compatibility? I also couldn't get YouTube to work via playing videos. The audiofx app that comes with the rom won't work either.
[Sprint Samsung Galaxy S III] KueDAWG:
HotSpot Issue

Greetings. My s5 recently tanked and I had to go back to my old s3. WOW. thatnks to this ROM I almost don't miss my s5. this thing is awesome. Great work DEVS! Thank U. One quick question. I am on build 20160906 and theres an issue with hotspot. I can set it up and clients can connect but no internet. I saw the post back on page 8 and it fixed the issue, but I couldn't find anything on whether or not this will have to be done on every nightly update. also, is there any chance the fix will get baked into the ROM?
[Sprint Samsung Galaxy S III] techdog:
Which version did you flash? I have not had to make any of the hotspot changes since I had done that. I thought it was baked into the latest Nightlies, but I could be wrong...
[Sprint Samsung Galaxy S III] KueDAWG:
I downloaded and clean installed "exodus-6.0-20160906-NIGHTLY-d2spr.zip" from the link in OP. I am running opengapps. everything is working great. just that one hotspot glitch.
[Sprint Samsung Galaxy S III] KernelCorn:
Absolutely. This is particular ROM is specifically for d2spr.

---------- Post added at 09:25 PM ---------- Previous post was at 09:07 PM ----------

Check this ROM out. Read carefully.

http://xdaforums.com/galaxy-s3-spri...ctos-oct-l-t3156861/post61851628#post61851628
[Sprint Samsung Galaxy S III] Gthunders:
Thanks i really appreciated that. I will be trying this out. Are there any more marshmallow roms compatible with my model? Also the sound works as soon as i flash back to stock OH which was the last release for the original stock for the model.
[Sprint Samsung Galaxy S III] mydian:
I have the same problem but haven't tried the fix on page 8 yet.
[Sprint Samsung Galaxy S III] RingPlus:
KueDAWG, mydian

Problem: Android 6.0 hotspot activates but there is no internet access for wifi clients. Internet still works on phone.

The hotspot fix for me was as simple as this:

1. On your Windows computer open up a terminal and type: adb shell

2. In the terminal window, type: " su - " (check your phone to approve)

3. Run this command: settings put global tether_dun_required 0

4. Reboot

That's a little shorter than the fix on page 8, but it's all I needed. Run that command as root on the phone via any method (Terminal app, adb, via SSH, etc).

Fixed the issue for me on RingPlus after first using ChangeOfJinzoData-APNFix-V1.2.zip to get functioning phone and data service.

Note: You can also verify that it was set properly by using this command: settings get global tether_dun_required and verifying the output is 0.
[Sprint Samsung Galaxy S III] KernelCorn:
Just wondering about something. According to Exodus updater we have relatively recent security updates with this ROM. On average what are the gaps in between once an exploit is found and when a patch is pushed through the updates?

The reason I'm asking is I was watching a mp4 (on a site I probably shouldn't have been on *grin*) a few days ago and my browser locked up and forced closed. Phone locked up and I had to pull the battery to restart. After the restart my s3 all seems normal again, but you never know.

Then I found out about this below.

https://source.android.com/security/bulletin/2016-09-01.html

Processing media files part caught my attention. Luckily, I just use this phone strictly for browsing and using the XDA Labs app. No personal info at all other than my password for this forum is saved.

I just thought this was strange because I've not once had single issue since I flashed this ROM. I'm probably just being paranoid huh? :)

Will we eventually get a security patch for this exploit? Just wondering how this works on a custom ROM.

Thanks for reading.
[Sprint Samsung Galaxy S III] mydian:
Thanks this worked.
[Sprint Samsung Galaxy S III] boneskid1:
I flashed build 20160908 and 20160908 tonight and cannot get past the welcome screen

I cleared the cache, data and such.

Not really sure what else to do
[Sprint Samsung Galaxy S III] hilla_killa:
You can use any d2spr rom on l710t after flashing rom youll need to flash the symlink zip then all will be fine.
[Sprint Samsung Galaxy S III] rootinchase:
I have a 64GB SdCard formatted with f2fs and when i flashed this ROM, it said it was corrupted. When I searched this thread, I found in this thread that there is f2fs support... Any ideas what's going on?
[Sprint Samsung Galaxy S III] SimLynks:
Installed this Rom on my D2Spr after running an OctOS-MM build for a while (and thinking that was one of the best Roms I've ever used) , but was totally blown away by the quality your release. I've been lurking XDA for years, this Rom was good enough that I finally created an account! With the latest Nightly the build even passes the Zimperium Stagefright testing 100% for the first time since I can't even remember, so thanks Exodus Team.

My only question for the Exodus-Devs (besides whether you check these threads on XDA or your Google+ Page more for bug reports) is about Magisk and whether or not it's possible to modify your Delta Update process so that SuperSU wont get reinstalled during every nightly flash?

Currently after every Nightly I have to:

1) Flash Nightly & wait for the cache to rebuild/reboot -> 2) Full-Uninstall SuperSU -> 3) Reboot to Recovery -> 4) Reinstall Magisk/PhhSuperuser/Systemless Xposed, 5) Wait for Xposed to do it's thing, 6) Reinstall Phh-Superuser apk as it gets wiped out by SuperSU in Step 1

I did some digging into this and found the "Secondary Flash" folders but since your update process seems to reflash SuperSU no matter what Ive tried (Deleting the UPDATE-SuperSU.zip, Creating a Symbolic Link from UPDATE-SuperSU.zip to redirect to Phh-Magisk-Superuser.zip, chmod 000 UPDATE-SuperSU.zip) but no matter what, SuperSU always seems to gets through...I'd appreciate any help with this, but know that you guys are probably not exactly focusing on Magisk at the moment with everything else that's going on in DroidLand right now. Thanks a bunch for this flat-out amazing Rom regardless!
[Sprint Samsung Galaxy S III] Max Frost:
[MENTION=7767738]SimLynks[/MENTION] Glad your enjoying the Rom . What might be a quick workaround would just be to open the rom zip and delete the su zip . When the rom flashes using the updater script it won't find the su file to flash and skip it . I've done that before while testing something else . Might be a little extra trouble each time vs what you described above . Just delete the supersu.zip from inside the rom zip and see if that works . You could also edit the updater script to remove what you don't want it to do such as flash supersu , wipe catch etc . Then just replace the script in the rom zip each time with your edited version .Holler back and let us know .
[Sprint Samsung Galaxy S III] SimLynks:
Thanks for the tip Max, that did the trick! Once I unpacked the latest Nightly ZIP, deleted SuperSU, Quickly read through the Updater scripts to finally figure out that SuperSU was getting flashed after being copied to addon.d from /tmp in the ROM update data, and finally renaming the addon.d/UPDATE-SuperSU_zip so it wouldn't be detected by the updater scripts, I was finally able to flash a nightly without having SuperSU flash through as well.

However just my luck, I did all this today just as a brand new version of Magisk/PhhSuperuser Magisk-Binary/Systemless Xposed was released, so I got the satisfaction of finally updating how I wanted, to immediately going back to exactly what I was trying to avoid, removing everything in recovery and starting all over again haha

Anyway even if just for my own sanity im probably going to throw together somesort of wonky Magisk-Updater script that automatically takes care of Unpacking the Nightly ROMs, removing SuperSU, repacking the Nightly ZIP, and finally placing the necessary Magisk updater ZIPs in the Secondary Flash folders as I continue testing this and figuring out a way to make updates a bit more seemless. Would the Exodus team have any interest in this script if/when I actually finish it, and if so would just posting here be enough for the team to evaluate it, or would pushing a commit on Github be more effective? Alternatively its also totally cool if the DevTeam prefers I STFU about Magisk so you can focus on other things like this ROM. Anyway Ill be updating this thread eventually once I finish my script and/or give-up on it and Magisk.

Thanks again for the pointer Max, always the most obvious things I eliminate as possibilities...
[Sprint Samsung Galaxy S III] salman986:
great work:good::good::good:
[Sprint Samsung Galaxy S III] techdog:
I have an easy question to answer. I have been flashing the nightly builds as they come out because I assumed that even if there were no specific Exodus team changes that the nightlies would pull in the latest CM nightly builds, etc.

Is that a correct assumption? Or, have I just been flashing the same code when there are no Exodus changes?

Thanks.
[Sprint Samsung Galaxy S III] SimLynks:
Bug Report: In Multiuser Mode I cannot enable Bluetooth when logged into any User except the "main" Owner user account.

Seems to be a common issue, out of three CM based ROMs on two different devices, only CM 13 on a Droid Bionic has Bluetooth function correctly in Multiuser mode.
[Sprint Samsung Galaxy S III] Max Frost:
Your very welcome , Glad it worked . Just removing the supersu file should do the trick alone without having to change the script . Might be less complicated . As for a script maybe after Nougat gets released and things settle down Dave can look at your script .

[MENTION=2597290]techdog[/MENTION] , it's hard to say how much change any given nightly would have but any changes that come down the pike that Exodus uses from CM or anyone else would be included through merges .
[Sprint Samsung Galaxy S III] Seattleweather:
Well, have tried all the files, but I still do not have LTE. 3G is all I got. Please let me know which file you have used. I have seen the apns-conf.xml is located in /etc. Is that right?

Thanks.
[Sprint Samsung Galaxy S III] Max Frost:
Your gonna need to give more info like exact model number or is this a triband ? What carrier such as sprint , ringplus , boost etc . LTE should be working fine but we need more info to help . You have exodus rom installed ?
[Sprint Samsung Galaxy S III] Seattleweather:
Hi Max,

It's RingPlus on SPH-L710 with Exodus 6.0.1 I have used ChangeOfJinzoData and other Apn change files to fix it, but nothing happened except changed Carrier name to Ringplus.

Thanks a lot.!