yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy Note II] MrMuzik:
is it the iphone? it's a joke. shhhhhh :P

i've attached pictures of the menu. from the picture you can clearly tell that there is a grey filter over the screen. if you look at the status bar icons that's where you'll notice it easiest. it's just very annoying on the n2 because it doesn't have a super bright screen to begin with.

so even if you uncheck the adaptive display box. it doesn't actually turn off as it should.
[Verizon Samsung Galaxy Note II] TEK112:
I see what you mean, but you can always theme and increase brightness to compensate. It won't be white, but it will be a much brighter gray.
[Verizon Samsung Galaxy Note II] MrMuzik:
Theming won't do jack because it's not the icons specifically it's the ENTIRE SCREEN! Also as I mentioned the N2 brightness isn't very good to begin with compared to other phones! Turning is all the way up (as I have to anyway) doesn't help at all because it still filters the screen. I just want a workaround to disable the feature without me having to strip it out of the source code. #MyWeekOff
[Verizon Samsung Galaxy Note II] TEK112:
I think this will work for: http://goo.gl/ULlxJO
[Verizon Samsung Galaxy Note II] MrMuzik:
LOL. Lemme get one and walk around outside in the sunshine with it. People won't think I'm nuts. Nope. Not at all. #Portlandia

:good::good::good::good:
[Verizon Samsung Galaxy Note II] TEK112:
I am doing a bit of research. I am wondering the version of superuser that comes with Cyanogen mod. Kernel settings should override rom settings when it comes to screen control and gamma. However, non Koush superuser apps have been known to allow the rom to override the kernel. I'm playing with that now, but I am getting an error updating my supersu binary.
[Verizon Samsung Galaxy Note II] fordmanck:
What about supersu?
[Verizon Samsung Galaxy Note II] TEK112:
Supersu is chainsdd. I am trying koush superuser now.

---------- Post added at 04:24 PM ---------- Previous post was at 04:15 PM ----------

I think I got it. Install superuser from koush. Then open and install binaries. Then open settings and change display from cyanogen to ui and then change from dynamic to auto. The screen should brighten up plenty.
[Verizon Samsung Galaxy Note II] MrMuzik:
It doesn't really have anything to do with SuperSu.

This is what it has to do with. It's this feature. Or acts like it. I remember this on the other CM ROMs. Usually unchecking the option works.

Also I got off my butt and removed all these commits. Didn't fix the problem. So I'm wondering what is actually causing this filter?

http://review.cyanogenmod.org/#/c/48465/

https://github.com/CyanogenMod/andr...mmit/c24bf526251aec4a84cf83d7273fc78f774dfe3c
[Verizon Samsung Galaxy Note II] TEK112:
It has everything to do with it. Like rock, paper, scissors. Kernel is rock and rom is scissors. Without superuser behaving the rom becomes paper.

Chainsdd supersu has a known issue with certain kernel settings.

I just did it and it worked.
[Verizon Samsung Galaxy Note II] MrMuzik:
it requires CWM recovery as it won't update with TWRP. i don't wanna touch CWM, so maybe i can find a flashable one around.

guess i'll be installing cwm for the first time in a year. then i'll see if this works. thanks.
[Verizon Samsung Galaxy Note II] TEK112:
Twrp has been having a ton of issues lately. Cwm and sometimes philz are the preferred recoveries for most of the Roms especially 4.4.
[Verizon Samsung Galaxy Note II] MrMuzik:
indeed. anyways. i knew about this method i just overlooked it. but it's not what i'm looking for cause it makes the screen look like crap on these settings. i just want the stock look without this bug. but overall it absolutely brightens up as it should but i guess it's back to cm10.1 for now!
[Verizon Samsung Galaxy Note II] DanDaGuitarMan:
Is anyone else having graphics issues in today's release (2/2)? It seems as if everything is responding at half speed. Scrolling long websites produces graphics tearing and nothing smooth. I reverted back to 2/1 and it behaved normally. Strange.
[Verizon Samsung Galaxy Note II] tdrussell:
Yep. Its all wonky. We'll see what happens with tomorrows build. I think its a hardware acceleration issue because video playback, animations, and touch detection are all screwed up.
[Verizon Samsung Galaxy Note II] DreamFX:
Gonna disagree latest build running smooth and graphics working great. I use Devil kernel, f2fs and art.
[Verizon Samsung Galaxy Note II] bigmike35:
Tried devil and angi, between scrolling thro homescreen, web pages, pulling up apps/settings slight jutters everywhere. Tried with 1200-1900MHZ and nothing really resolved the issues. Tried a wipe of cache/dalvik and still not help with resolving the slowness/jitters.
[Verizon Samsung Galaxy Note II] WisdomWolf:
I have the graphics issues everyone else was complaining about and the only thing different from what you mentioned is that I don't use ART (too attached to Xposed).
[Verizon Samsung Galaxy Note II] MrMuzik:
I'm running a build I made late today and it's fine with devil kernel. Stock kernel is okay too.
[Verizon Samsung Galaxy Note II] mcweinert:
On newest nightly 02/02 I was having graphic issues and lag, fc of launcher and trebuchet not being uninstalled correctly by gapps. I tried with new 02/01 gapps, older gapps, devil kernel, stock, stock with ART, TWRP and Philz CWM. Also tried clean and dirty flashing on top of each other. All to no avail. I noticed in the change log they redid Trebuchet and so I went to the build before that (01/29) and all is working fine. Just wanted to let you guys know. I did not however try another launcher but the graphical issues seemed to affect apps as well.
[Verizon Samsung Galaxy Note II] tdrussell:
Graphics issue appears to be resolved on 2/3 build.
[Verizon Samsung Galaxy Note II] CallerHoller:
Cracka-lackin!

I was on 2/2, this morning I downloaded 2/3. However when I see the post about 2/2 I jump back to 1/29. Then I read your post when I got to work so I've crack-flasher 2/3.

Kinda numb now. Think I'll chill on this one for a week. :eek:
[Verizon Samsung Galaxy Note II] WisdomWolf:
Yeah from the commits I'm guessing that the change to API 1.1 was the issue since they reverted that today.
[Verizon Samsung Galaxy Note II] krash:
Camera taking blurry pictures when photographing "text"

Hey guys i was wondering if anyone else has this problem when taking a picture of something like printed text. I can focus the camera by clicking on the screen and the text looks great, but as soon as i hit the "snap" button it goes blurry and snaps the photo. I attached an example.

I tried all different focus modes they all do the same thing. I am using the standard camera that comes with cm11. Is there another alternative i should be looking into?

Thank you.
[Verizon Samsung Galaxy Note II] fordmanck:
It's a known issue.

Flash this file to fix it for now.

https://www.dropbox.com/s/no5sowrt3cu5jhh/Fixed_Cam_for_CM_10.2_CM11_V2.3.zip
[Verizon Samsung Galaxy Note II] krash:
Thank you i will do that right now!
[Verizon Samsung Galaxy Note II] WisdomWolf:
The camera issue is also fixed in the most recent nightly.
[Verizon Samsung Galaxy Note II] CallerHoller:
2/4? Is the focus as good as stock now?

**Looked at the change log. The only change I saw was on 2/3 a crash issue was addressed.
[Verizon Samsung Galaxy Note II] John Kotches:
On the 0203 nightly I am seeing stock keyboard lockups that can only be cured with closing the application.

I have not loaded the 0204 nightly... Is anyone else seeing this behavior?
[Verizon Samsung Galaxy Note II] rippedwarrior69:
The new nightly for me in camera the video transition lags the video. Anyone else having this problem?
[Verizon Samsung Galaxy Note II] TEK112:
2/4 change log says they fixed the camera focus.
[Verizon Samsung Galaxy Note II] WeThePeople13:
Still looks horrible to me. Also I tried to flash the .zip that is floating around that is intended to fix the focus problem and keep getting a fail...... Any help? Running newest twrp and newest nightly with devil kernel.
[Verizon Samsung Galaxy Note II] fordmanck:
https://www.dropbox.com/s/no5sowrt3cu5jhh/Fixed_Cam_for_CM_10.2_CM11_V2.3.zip

That file? I believe DreamFX mentioned somewhere that not everyone could get it to flash.
[Verizon Samsung Galaxy Note II] krash:
I had to download the file a couple times.. the first few times it was only downloading like 61k, after a few times it got the 3.99mb. I don't know what was causing it I was downloading it directly from my note2 with "es downloader".
[Verizon Samsung Galaxy Note II] bigmike35:
On the pull down for quick settings I see settings switch/tab was remove and replaced with a + to go into adding/setting up the quick toggles. Anyway to get back the settings key and or take off the +....
[Verizon Samsung Galaxy Note II] tdrussell:
Just add a settings tile?
[Verizon Samsung Galaxy Note II] bigmike35:
Yea I got a settings tile, was just use to clicking settings right there and now when I hit it, brings me to edit tiles. Just need to stop hitting it lol
[Verizon Samsung Galaxy Note II] CallerHoller:
Unable to attach files in Android Browser. 2/5

I use a 4.4.2 gapps with Android Browser and Messenger. I got today's build all set up then found I couldn't attach anything to an email. I went to a forum and couldn't upload anything. I downloaded Chrome and it attached files. I reflashed, didn't fix it. I Flashed an older gapps, didn't fix it.

So today I'm stuck with PA-gapps with Chrome and Hangouts. :(
[Verizon Samsung Galaxy Note II] DreamFX:
Tapped Out is working on latest nightly and latest Tapped out build.
[Verizon Samsung Galaxy Note II] MrMuzik:
Same here. Kinda sucks.
[Verizon Samsung Galaxy Note II] sbergman27:
This is a real problem. I've had this issue going all the way back to at least CM10.1. Youtube is quite stable on wifi. Browsing, sftp, etc. are quite stable on LTE. But Youtube locks up every few minutes on LTE. And once that happens, even rebooting doesn't help. Sometimes toggling mobile data off/on will get it to work for a few minutes before it locks up again.

I'm running Alliance Rom now, and Youtube performs flawlessly on LTE. It's a night and day difference.
[Verizon Samsung Galaxy Note II] DreamFX:
I use youtube all day long on LTE on this rom. Never a single lock up. So it's definitely not the rom. There is always the rare one or two people that stop by on this thread every now and then and blame the rom on their youtube issues. If it was the rom we all would have horrible youtube on LTE.
[Verizon Samsung Galaxy Note II] sbergman27:
Look. It doesn't work anywhere near reliably on my device with any CM ROM. And it never has. I registered a bug about it a year ago. However, under exactly the same conditions, I can switch to CleanRom or Alliance Rom and it works perfectly, and rock solid reliably. In fact, I've been back and forth between CleanRom, Alliance, and CM11 several times over the course of today. Youtube is unusably unreliable on CM, locking up every few minutes. And the same version of YouTube on exactly the same device under exactly the same conditions, at within a few minutes of the same time operates rock solid reliably under CleanRom and Alliance ROM. If you want to go into denial mode about it, fine. But it doesn't change the facts.
[Verizon Samsung Galaxy Note II] sbergman27:
AOSP kernel and sensors?

I've been meaning to ask for a while if others have issues with the magnetometer. Using GPS Toolbox, I've never had a reliable compass. At first, it and the orientation sensor seem completely locked. The compass and level display doesn't move. Sometimes it does sort of work, but fluctuates a lot for no apparent reason. After using CM exclusively for the last year or so, I've finally gotten around to trying out TW based roms. And I've noticed a number of things that "just work" in those that have never really worked well for me in CM. Among those are sensor issues. Any recommendations? I'd really prefer to stick with CM. But I'd like the device to work properly.
[Verizon Samsung Galaxy Note II] MrMuzik:
Your issues are mainly to you. So it may be fact for your device but not for the rest of us. Because there are a few people around who complain the same thing about LTE. And far more that say there's no issue. So placing the blame on a ROM when sometimes it's the actual device won't help you :P
[Verizon Samsung Galaxy Note II] sbergman27:
The device works perfectly with other ROMs. "Works for Me" is not a valid QA policy. However, the responses I'm getting to having simply confirmed a problem that someone else reported makes me feel better about having moved on to a ROM that actually works properly.

There's a reason that Samsung takes a while to get a ROM out. It takes time and care to get everything right. With CM on the i605, it's a never ending treadmill of half-working nightlies. 10.2 doesn't even have an RC out, and we've already been railroaded into CM11 nightlies. (CM 10.1.3 doesn't work any better, btw.) After over a year of living with a phone that doesn't really work... and even though I actually prefer the cleaner CM interface... I've had enough of the ROM. And I think I've now had about enough of the community, too.

Enjoy your Green Acres ROM, and your over-sensitivities.
[Verizon Samsung Galaxy Note II] thatdudebutch:
What's that
[Verizon Samsung Galaxy Note II] MrMuzik:
You make me chuckle. Come back more often. I like you :)
[Verizon Samsung Galaxy Note II] synapsesboob:
Lol railroaded into CM11? I didn't realize we were forced to use these ROMs.
[Verizon Samsung Galaxy Note II] fordmanck:
I have ZERO issues with YouTube over LTE. I have a S3 running CM11 with zero issues as well. My G2 is coming today, I'm sure it'll run flawless as well.
[Verizon Samsung Galaxy Note II] DreamFX:
It's a free Simpsons game. I couldn't get into it. But it wasn't working for awhile on cm11 but now it is.

---------- Post added at 09:40 AM ---------- Previous post was at 09:36 AM ----------

I know I hate complainers. They come in here complaining stuff doesn't work and telling us what rom it does work on. The devs work for free and your offered a free rom. You have a choice to flash or not flash. Respect the work that is done here. Also remember the note 2 is basically a legacy device. I'm super thankful to be able to run the latest and greatest Android version on an older device. Thanks again cm team.

---------- Post added at 09:41 AM ---------- Previous post was at 09:40 AM ----------

+1
[Verizon Samsung Galaxy Note II] TEK112:
If you still have your receipt they will probably refund your...oh wait, nevermind.
[Verizon Samsung Galaxy Note II] sbergman27:
Well, I did get some educational experience out of my year on CM. So I'm not really interested in a refund on all the *time* that CM cost me. Or really even the year of reduced functionality of my phone. I'm on fully stock VRUEMJ9 now and loving it. I ran a suite of baseline tests before flashing stock, so I can now compare actual numbers rather than perceptions. Here's what I'm finding:

1. Youtube works flawlessly (of course)

2. Wifi range is improved by ~15% - ~20%.

3. Wifi transfer speed at 1/2 range distance is improved by around 15%

4. LTE transfer speeds are up 15%.

5. Audio Bluetooth range is a little better. (5% - 8%)

6. A VOIP benchmark shows excellent (low) jitter in the LTE connection speed on stock, but very poor jitter (long maximum latency) on CM11. (Perhaps this relates to the YT lockups.)

7. Battery life on stock at default settings is ~10% better than with CM11 at default settings.

8. 3D video is ~20% faster.

9. Nothing in the AOSP world even comes *close* to the capabilities of SNote.

10. My S-Pen is *useful* again! (Yea!)

11. Air Command is cool.

12. If anything happens to my phone (hardware-wise) to the point that I can't flash back to stock at that time, my warranty is still good. With CM it would have been void. (And rightfully so. It's not reasonable to expect Samsung/Verizon to take responsibility for phones not running their properly QA'd firmware.)

13. TW is actually quite a bit slicker than AOSP once you get used to it.

14. The Galaxy Gear is starting to look nice.

15. Compass works.

16. GPS locks almost instantly outside. And will get a lock inside, in areas of the house where I was never able to get a lock before.

17. True multi-app/multi-tasking!

Sure, I've been able to get by with CM. But needless to say, I'm happy with stock now and not looking back. That said, I figured I'd post the comparison results to perhaps help posterity come to a decision as to what firmware might be best for them. Certainly, if I'd known 9 months ago what I know now, I'd have been running stock all along.

And BTW, regarding your implication that if you don't pay money you can't expect quality... well... I've been in the Linux community since 1996 and the UNIX community since 1988. And I've always used quality distros like Debian, CentOS, Scientific Linux, etc. These are distros that are both free and Free, but take the time to get their distros *right* before moving on to shiny new stuff. You can do OSS right... or you can do it hurriedly. You *can* expect excellent QA from an OSS project sometimes. But that depends entirely on the project and how it's run.

Of course, I *have* actually paid for CM via multiple donations made to people in the CM community, including Scott. And of course, I've bought apps to *try* to fill in for the gaps in AOSP relative to stock Samsung. No. Problem. I'm still glad I did. But I'm moving on from CM to something that actually works. A year is enough.

HTH

Steve Bergman
[Verizon Samsung Galaxy Note II] MrMuzik:
TLDR
[Verizon Samsung Galaxy Note II] TEK112:
A nightly is the equivalent of an alpha build. This thread is for support of a nightly build with constructive feedback. They release these nightlies for testing after working their regular 9-5. You are entitled to your opinion, but a modicum of decorum is appreciated. As a developer myself, with my own development website and ROMs I can't help but take offense.
[Verizon Samsung Galaxy Note II] sbergman27:
"TLDR"

Oh, come on. Sure you did.

---------- Post added at 02:52 PM ---------- Previous post was at 02:39 PM ----------

Well, CM does have 10.1.3, based upon Android 4.2, which is one Android release older than Samsung's/Verizon's current offering. But all the issues I reference apply the same way to it. I didn't actually benchmark it. But I do know that Youtube and the compass are screwy for CM 10.1.3 on my device. (No one has come forward to share their experiences, positive of negative, regarding the compass.) Other than that, the device is over halfway through its lifecycle (about 2 years for a phone). Will there be something that really works before the Galaxy Note II is obsolete?

Anyway, it seems to me that as a developer you would welcome comparisons between your own offerings and the stock standard experience had by people who stick with the default. But I get the impression from the responses I've seem in this forum that many would rather just not know where CM falls short. Bug reports just don't seem to be well accepted. (Must be your device. Must be the area you live in. Must be something you did wrong.)

Sure, it's difficult to match vendor quality in an environment of proprietary drivers. But the successful open source communities I've dealt with over the last 17 years (e.g. the Debian project) have taken user feedback and bug reports seriously, rather than taking the "ostrich" strategy for QA

.
[Verizon Samsung Galaxy Note II] fordmanck:
But this is a CM11 thread. A thread for an Alpha which it is widely known in this community you don't give bug reports about alpha builds. Being a developer, you should know this. This thread has been a select few of us helping each other with getting our legacy devices the latest and greatest Android. The fact is CM just isn't for you. There are good and bad with every type of ROM. Just like programming, which I do as well, there are a million ways to do the same thing. My way is no better than your way, I just prefer mine. Move along, no one will be upset, I promise.
[Verizon Samsung Galaxy Note II] sbergman27:
What a brain-dead QA strategy. No, I would never adopt that policy for any of my projects. If you buy that as a valid QA strategy, then it's hard for me to believe that you are a programmer.

On the contrary. Review the thread. (And I do recommend that people go back and review it.) On Jan 23 user quepaso reported that YouTube was unstable over LTE but worked fine on wifi, and was dismissed with the usual "Works for me. Must be your __________" excuses. (User DreamFX was one of those wanting to dismiss quepaso's report.) This happens far too often in this forum.

I noticed quepaso's posts, recognized the problem as something I've been experiencing since 10.1 alpha2 (and had reported before, but got the brush off then, too) and posted that it was a real problem and not just quepaso's imagination. This made user DreamFX *very* upset. And now, since I didn't back down like a good boy, lot's of people (notably, MrMuzik) seem to be upset. Note that not one person has come forward to suggest any possible reasons or remedies. Seems like if there were concern about CM quality, someone might have asked something like, say, what radio version I was running. But nobody thought to do that. It's been 100% denial and defensiveness from the start.

If you're happy with a ROM that has all the issues I've outlined in a recent post (i.e. if CM is for you) then that's fine with me. But I certainly don't apologize for publishing the results of a few direct comparison benchmarks for the benefit of users who may be trying to decide whether to switch from stock to an AOSP ROM. People should have access to the facts before making the decision.
[Verizon Samsung Galaxy Note II] fordmanck:
You're right, I made it up. I program equipment. The difference in me releasing a machine to the floor without testing it and a ROM for a phone are clearly on the same level. Again, it is widely known that nightlies are not for the average user. Apparently you missed that memo along the way. You were probably busy bullying people in the irc channels.
[Verizon Samsung Galaxy Note II] TEK112:
That's what you are missing. This is a thread for us to support each other with fixes and work arounds. The real cm bug threads are on their site. This is a thread for us to play with and break stuff. Feedback is read by any cm devs who look on their own, but they are not looking for bug reports knowing this is an unstable build.

After alpha comes beta or rc. Then after the rc comes the release version which is a stable build. Cm may never get that far but at least they give us the opportunity to play and integrate parts that are useful. That is the beauty of open source.
[Verizon Samsung Galaxy Note II] sbergman27:
Please point to a post in this thread in which someone tried to do that for user quepaso. (Or for that matter, for me.) Not that I care about getting help at this point. Still, it seems like someone might care enough to at least be a little bit curious as to why Youtube doesn't work over LTE for some people while it does work for others. I know I'd be curious as to the reason, even though it doesn't really affect me anymore.
[Verizon Samsung Galaxy Note II] fordmanck:
Not that it matters, but I'll bite. I can't tell you how many people over the years I've helped out off of the thread as to not clutter it. I'm sure a few will chime in as they're still active posters. I'm by no means on your level. I just know android devices well and how to get out of jams. So just because you don't see the help here, doesn't mean we aren't. It's tough to help the condescending, never wrongs though.

Being a programmer as you are, number one you should be aware that no two devices are identical, even if physically they are. Geographic locations are different as well as what someone has loaded on their phone. He stated he was having an issue, multiple people posted they weren't. Did you want us to lie to make him feel better? Enlighten me as to what your tact would have been.