yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rs3freak:
Is there a fix for the YouTube? I cleared the chache and data but that only fixed it for a little while
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Anyone having issues with snapchat?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rhealeyogden:
8/6 seems to be running fine. No issues so far. All apps compatible so far. Running stock kernel FYI.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drivel2787:
I'll give that a shot just wanted to report I see it on the 8/6 build. Didn't on the 8/5

Sent from my sexy Android 4.3 thanks PWNCAKES
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
So SELinux. Settings>About Phone....... tap SELinux three times and it's ''Enforcing''. Bout to do some reading up on it. Figured I'd ask in here too, who has messed with it and what does it do for ya?

EDIT: Set SELinux back to permissive. Couldn't change my dpi and Nova started giving me FC's. Like I said, I need to go read up on it. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
8.6 Release

Hey guys to try and be more organized I have switched to another naming structure, seeing as how now I can put out multiple builds a day. I've been testing the latest build for the last few hours and it's been sipping battery so far. I fixed the speakerphone echo as well as made it so a few drivers are a little bit more accessible resulting in a nice and smooth experience. Remember to download the new GApps

8.6-d2att

All donations are appreciated you guys, I've started to even call out of work just to twiddle with the ROM!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rhealeyogden:
Thanks for another update. Will flash shortly and test out the new changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
http://www.androidauthority.com/selinux-cyanogenmod-243988/

SELinux has been planned to come to CM for quite awhile. Basically, it's the way *nix operating system should be run rather than under a full, blown root account (which is essentially what we do when we root our devices).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Thank you sir. Wonder why a new security feature like this would give me FC's on Nova and would not let me change my DPI with Rom Toolbox or Density Changer.

Maybe something to do with permissions?

After I set SELinux back to permissive things are now fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] assaf.bm:
This is a good article onSELinux

http://www.cyanogenmod.org/blog/this-week-in-cm-july-19-13
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dotnetguyaz:
Most likely. I don't think a lot of apps are able to take advantage of the SELinux implementation as of yet (considering it's new to 4.3). Apps that utilize root or workarounds for hiding notifications (which is what every launcher has had to do before 4.3) are going to be very problematic for the next few weeks as devs learn how to live with SELinux.

Basically, with SELinux, apps are initially denied a broad set of permissions and then the app in question needs to be given the more granular permission(s).

"Permission Revocation

This mechanism, based on a similar mechanism in CyanogenMod, supports revocation of permissions from installed apps. A revoked permission list is maintained for each package and checked at runtime on permission checks. A revoked permissions configuration (found in external/mac-policy/revoke_permissions.xml in the source tree and as etc/security/revoke_permissions.xml on the system image) can specify revocation lists that are applied automatically on each boot. An updated revoke_permissions.xml configuration can be pushed to /data/system/revoke_permissions.xml to override the configuration on the system image on the next boot. This support is available from the revoke-perms branch."

http://selinuxproject.org/page/SEAndroid
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Exactly the info I needed guys.

Thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ratdog07067:
WiFi?

Been loving this ROM so far.

I flashed the newest 8/6 over the first 8/6 and now my WiFi won't turn on. I'll try do a full wipe and see if that fixes it but wanted to see if anyone else is experiencing this.

Thanks,
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liebowa:
Installed the very latest release and the latest gapps, and I have no WIFI. Cannot even enable is settings,

I completely wiped before install, including Dalvik.

I reflashed and same results.

Anyone else having this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] assaf.bm:
i got the same result.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I did a clean wipe of it when I first installed and I had no Wi-Fi issues. Can't even tell what'd be wrong with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
WIFI is good here. Dirty from 8/6 to later 8/6. Wiped cache/dalvik and booted.

Still had 7/29 GAPPS from first 8/6 flash.

Guys try flashing Bionicsheep kernel and see if that helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] trh1341:
What do you mean by sipping? I would think you mean slow battery drain? But other developers would use sipping to say there is moderate drain. Just a question:)

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

Thanks for the work by the way! I'm out of work at the moment. But will donate when I get a job:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
The only difference between BionicSheep and the packaged kernel is the toolchain used. It won't fix any issues, other than just offering features and speed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liebowa:
Hmmm. Interesting. Three bad WIFI installs and one success.

So, that rules out a bad upload of zip file..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] caspersfi:
Yep, my bad. :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
There honestly shouldn't be any issue. Try reflashing again, not sure what could've went wrong. Full clean install for me from stock 4.1.2 was fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
Viper for me doesn't work. I've installed busy box and viper doesn't acknowledge a busy box being installed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Got this error when checking ROMdB Dev Tool app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rob_z11:
Note2 version if possible?

Hello OPS,

Any chance to build ROM for us version of Note2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Tried out Task's AOKP for a day. Bad decision, I got like 20% battery drain in about 45 minutes from idle. SO glad to come back to this! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbrian27:
You have to use SuperSU
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
Yeah I used task650 aokp for quite awhile. I never got even close to the battery life and also the speed wasn't noticeably better. I don't know if that's a issue with aokp as a whole or just with the version he's cooking... :-/

This is what im seeing now on QUANTUM! At 7% ****27+ hours! Wow****
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Yup, but its also the little stuff like that Quantum is for just d2att, so the support is a lot better
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] c47v3779:
Care to share your kernel settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Sorry if this has been answered before, but where can I find the setting anymore for screen temperature?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
Bone stock settings. :) greenify and I keep the screen off as much as possible. (When playing music etc). Mainly the battery life is due to pwn and cyanogen mod devs. :) Quantum v1.9 and QuantumKernel! !! Woot!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Are you susing SuperSU? The default superuser binary is not compatible. EVERYONE should be using SuperSU anyways!

Could you post your specific error or problem? Just saying it doesn't work doesn't give me any advice other than pointing you to the FAQ and troubleshooting part of the Viper OP
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Do you need to remove superuser or can you just install supersu over top of it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gvsukids:
The problem was fixed with installing supersu. the problem was that viper was saying my phone wasn't rooted/busy box wasn't installed.

You can install it over
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ps3kev:
On 1.4c and 1.9 I still get rwboits pwncakes. I hate to break it to you.. first time on youtube and bam froze abd rebooted. I did all nesscessary wipes.. sad to sau I went back no non aosp 4.1.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Just install it over. I'm going to recompile the settings apk to remove the superuser shortcut and replace it with supersu. Its 1pm here I'll probably have it out by midnight unless I run into problems.

Is there any demand for this? I was going to make it include CPU spy, wakelock detector and better betterbatterystats as well for my personal use. I can release both separate apks if there is any demand for either.

What do you guys say?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Hopefully someone posted help for this, but whenever I wake my device, it goes into a reboot. Unless I start to use my phone before the screen times out, it'll keep rebooting.

Kernel Settings 384-1242 Interactive

1024 Read Ahead buffer -ROW

MP - Decision Off
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
That would be great! I use all those apps also!

---------- Post added at 04:14 PM ---------- Previous post was at 04:09 PM ----------

I think I've had this problem since 4.3 came out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Would there be any way to get rid of this? This is he first time this has happened to me and i'm on 1.9 with clean wipe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
No solutions that I know of.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
This may be a 4.3 problem but I've never experienced it. I'd suggest a clean wipe including system and flashing the rom, gapps and supersu only. Have you wiped system? Maybe you're undervolted too much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
Anyone use Songza? I use it at the gym and about 95% of the time I'm using it, it won't automatically skip to the next song at the end of the previous one. It used to. And, I can instantly make it skip by literally touching any button on the phone. (screen is off at this point).

I have a feeling the phone is going into deep sleep and Songza isn't triggering it to wake in order to advance to the next song.

I don't know when it started but probably back around Quantum 1.2 or even earlier.

Any help for this problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I actually flashed it clean with wipe of system, but I underclock to 1242 MHZ, so I'll try upping my voltages by 50.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Yeah, I suggest you try that. If that doesn't help then try raising your minimum voltage or try using another gov like ondemand and scheduler like deadline. Also maybe change rear ahead size to the default 256.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Raise minimum voltage, I'll go and actually probably revert the OC steps if everyone is having so many issues. It seems as though removal of OC is what fixes most issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Woot my suggestion to him was actually supported!!

Okay guys, I'm on mobile right now so i can't make this until I get home but I'm going to mod the settings file and this is what will be done:

Settings mod 1:

Remove superuser menu

Replace with link to SuperSU menu

Settings mod 2:

Remove superuser menu

Replace with link to SuperSU menu

Remove performance menu

Replace with link to Trickster Mod

Add link to BetterBatteryStats

Add link to Wakelock Detector

Both of these will be made into separate flashable .zip files.

Its important that your configuration is the same as mine; SuperSU is a SYSTEM app and Trickster Mod, BetterBatteryStats and Wakelock Detector are installed as regular USER apps.

Quantum, maybe you could add the first mod as a stock part of the ROM as well as including SuperSU (or a link to it if the dev doesn't allow it to be bundled)? Not everyone uses the apps in mod 2 so that's why i suggested the first and am making different versions. Its universally better than the included superuser, I'm sure you know that. I'd love to be able to contribute to this ROM in some way, I've been very active on this thread but mostly just to ask questions...it's clear that this is my favorite ROM but I'd love to give back if I could. :)

If you don't want to include it as stock then maybe include both mods as options in the OP and a link to my post? Or at least just the link? I'm sure a lot of people would find use with it so it's better than being buried hundreds of pages in.

What I'm not sure of is if my mod will work the same with the pro version of SuperSU and Trickster Mod as it would with free, it would need to have the same com.blabla name which I'm unsure of. If not then I'll make alternative versions for free and pro.

Stay tuned guys! And thanks Pwn for reading this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
It could also be the table and the underclockimg. I'll try removing the UC first as I'd like to keep OC if possible. I'll work on more later tonight.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'm not underclocking but I UV'ed -50 with no problems. I don't OC either, kills battery.

---------- Post added at 12:43 AM ---------- Previous post was at 12:29 AM ----------

Here's how I installed it.

First make sure you have SuperSU and the latest BusyBox installed

1. Install v2.3.x V4A as a USER app and choose 'Yes' to the 'Install/Update' prompt when you start it.

2. REBOOT.

3. Select V4A in Settings>Sound>Music Effects.

4. Make sure in V4A menu FX Compatible Mode is set to Normal Mode.

5. Extract the .IRS starter pack and copy the files (no folders in this directory, take all .IRS files out of their folders once you extract the archive) <storage>/ViPER4Android/Kernel/xxxx.irs - this can be either on your internal or external card. Make the folders if they aren't there.

6. Start V4A and load up an effects profile.

If you have driver errors (I didn't need to do this):

1.Open up /system/build.prop in text editor.
2.Change the line
Ipa.decode=true to lpa.decode=false
tunnel.decode=true to tunnel.decode=false
lpa.use-stagefright=true to lpa.use-stagefright=false
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ShinyBuddha:
Everything is looking great. Here's my battery stats (full stock) which includes 2.5 hours of call time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
My battery is pretty meh again...gonna try dkp kernel. Right now I'm using ondemand/deadline all stock/reccomended settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
What theme is that?

Also get off ondemand! Use interactive!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayRokk:
Looks like Gem Flat or Simplex Blue.

Both amazing themes.

I'm currently using Gem Flat
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Gem flat is correct. Switched to interactive, gonna give it a shot for a few days before any switch :)

I'm home now so I'm starting work on the mod
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I have a new kernel I'm gonna post soon. Over 63 commits :) Should fix a lot of issues and I reverted UC, as well as a lot of other things. Things should be a LOT more stable now, including youtube!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] XxSTEROIDxX:
Total respect for the dedication and time you give to this rom and listening to and working with us users!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Wee new stuff!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Maybe it was a bad zip or something but the 9/20 stable zip gave my that weird reboot loop maybe it was the freelunch governer or because I was at 1.2 ghz. Hopefully it was just me... Otherwise, battery life is pretty phenomenal :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Wrong thread dude! I think this belongs in the thread you made not Quantum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
From what I'm hearing 1.9 and QuantumKernel v1.45 seem to be the go to combo.

Int/row 256 read ahead, seeder- light/ extend read ahead
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Does anyone's phone keep waking up for no reason? Mine keeps waking up since 1.4c.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
I'm not experiencing this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Realorasz:
I haven't had that myself, but I did flash QKernel 1.45 and I only got one boot out of it. Then it started to freeze at the bootanimation and reboot-loop. I've been doing lots of reboots because I'm working on a theme based off of Betterbean Purple, and sometimes not everything applies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
Previously running 1.9 with v1.4c kernel, Int/row 1024, OC 1620000 and no issues.

Updated to v1.45 kernel with the same settings and I've had one random reboot and experienced an SOD this morning. I'm reverting back to v1.4c for now. My phone doesn't appear to like the new kernel but it flies on the previous version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
While I've always had issues with bluetooth audio skipping, it was happening few and far between (maybe every other song). I flashed v1.45 kernel this morning and when the screen was off, it would stutter every few seconds, but with the screen on it would work as before. I'm guessing it has to do with voltages, but I've left them all at stock and always used PwnCakes' recommended settings (int/row 384-1620).

I'm back on 1.4c and the skipping is happening much less (like before).

I'm fairly certain this will all get sorted out once official 4.3 drops with proper bluetooth drivers, but just wanted to get this on the books.

Thanks PwnCakes for your ROM, still the best out there for battery life and speed. Everyone I'v shown my phone to, can't believe how killer it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alkiter:
On 1.9 with 1.45 kernel get constant SOD, reverting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
1.9 with 1.45 got stuck booting twice but runs smooth as butter now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
I've been running 1.9 and 1.4c so far its been pretty killer. I get amazing battery life. I using on demand and row. And I'm oc to 1.6 only thing I've noticed is sometimes audio wasn't working after a reboot... Another reboot fixes it. But I'm enjoying this ROM after being on TouchWiz for so long. So far I'm not having any issues. Great ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Just so you all know I'm currently running 1.95 with 1.45 and it's working fine. No SOD, but booting can be finnicky sometimes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Running 1.9 with kernel 1.45. 384/1620, asswax governor, deadline scheduler. No boot hang after initial install, but several since and one SOD.

(Correction: make that several SODs, and boot hangs almost every single time. Going to back down to 1512 to see if that helps, as everything else is stock settings.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] procco13:
Testing 1.95 with v1.45 kernel now. Booted up fine (only tried once mind you). No OC, int/row 256, MP decision off.

I'll report back after a day's worth of use.

So far, so good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I'll build when I get back from class to try and fix everything. Seems I may have to remove OC for a while :( boot hanging is an issue I can't even figure out yet but it doesn't affect anything else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Going back down to 1512 seems to have helped. I won't miss OC, personally, as my SGS3 is zippy enough as it is.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
1.45

Installed the new test kernel.........wiped my apn file. No data. Tried to re-install the ROM with the new test kernel.......boot loop city......would not boot. Re-install ROM, as is, no problems.

Not gonna try the new one again!!:laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RampageRR:
Yup, mine was going the same yesterday on the 1.95 beta version. It'd wake up and sit on the lock screen probably once every 10-15 mins. Weird.

I just went back to 1.9 for now, no issues whatsoever. Not sure what's causing the random waking up, all settings were the same on both versions. Not complaining at all, just letting you know what I saw on the test version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
Kernel 1.45

ROM v1.9 (-1... so is that 1.95?)

Had a random reboot while using FB messenger. First problem I've had with this combo.

Kernel settings in Trickster are 256 read ahead ROW, Interactive governor, not OC'd or UC'd, stock voltages. Fast-charge ON, MP-Decision ON (default... I believe no boost).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Try this out and I'll see if I can actually release this one!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tallsilver:
Okay so far! Booted......apn's stick.......setting stick......will run for awhile and see how battery does.

Thanks for all you do!! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] curls00:
Had a reboot while booting for the first time after flashing the kernel. Otherwise seems fine so far (5 minutes in LOL).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LostByte:
Ditto.. 1.95 and 'wakes up' every 10-ish minutes. I'll try the new kernel on 1.9 and see if i get the same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
I experienced it the first time when the user mentioned it. Other than that I haven't found that at all, I used to have the problem on 1.5-1.7 though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jasonv31:
No random wakes for me/us on the three gs3's I have running quantum. Just moved the second one to v1.9 will have the third on it by this evening. Runs smooth with amazing battery life! Couldn't ask for more... thanks pwn!

P.s. The no sound bug is still present on all of our gs3s running quantum. Seems that it has been more frequent lately... a reboot fixes it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LostByte:
I went back to 1.9 and the problem went away... I'll just wait for the next (non-testing) build and try again :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
Has anyone recorded HD video successfully? I'm on 1.9 and HD 720 video won't record. Well, technically it records but won't play. I can record in SD 480 though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
How goes the script berryman? Any thought of including this in the ROM pwn? I think it would make this ROM the complete package with everything built in.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingpongg:
I had an issue playing back recorded video- gallery or the player app would crash. dropping the clock speed to 1512 fixed it for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Try out 1.45b. Raised ION size should help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Things have been far too stable w 1.9 time to install 1.95 &. 4c

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
Been rocking kernel 1.45b since this afternoon. Stable for me. No SOD, no boot lockups (and I've rebooted the phone quite a few times today while testing themes), running at 384/1512, asswax governor, deadline scheduler, MP-decision off. Me likey. :D