yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] one7dchevy:
Ok, just reflashed without DAGr8s kernel (KKO.V) and have not seen any flicker like I was. With his Kernel I saw some when clicking menu from the homescreen and when opening the settings app.
[AT&T Samsung Galaxy Note I717] Radukk:
Nightly 0914 several things have changed and now no flickering without disabling HW overlay. YAY!
[AT&T Samsung Galaxy Note I717] MadHatter83:
Lucky! I'm still getting flicker no matter what kernel I try. Just wish the HW Overlay box would stay checked the phone restarted and I wouldn't even notice.
[AT&T Samsung Galaxy Note I717] rohankb:
On none of the developer ROMs since I've been on cm9 or cm10 have I ever had that stick on reboot. Don't think it was ever intended to.
[AT&T Samsung Galaxy Note I717] Ltilt2:
You will see flicker
[AT&T Samsung Galaxy Note I717] Radukk:
Guys just don't flash any other kernel and use stock CM kernel. It is perfect as it is.
[AT&T Samsung Galaxy Note I717] dvdivx:
Occational hard freeze on 9/14 w stock kernel. Installed after a complete wipe.
[AT&T Samsung Galaxy Note I717] Ltilt2:
With stock kernel you will get occasional freezes and reboots. With oc kernel you will get minimal flicker so its your choise. Choose your poison
[AT&T Samsung Galaxy Note I717] dvdivx:
Can confirm hard freezes go away with KKO.V kernel.
[AT&T Samsung Galaxy Note I717] spectredeath:
I am also freezing but I would say it is definitely more frequently than occasionally. I noticed a few things that trigger freezing using the hw menu button in the stock browser and several other applications mx player is another one. I set the interface to add the sw menu button and it is a little bit less frequently it also freezes when I put stress on the memory ie multiple applications running maybe some tweaking in the performance settings will help... Or possibly melt my phone and give me cancer.
[AT&T Samsung Galaxy Note I717] Web-head:
Check the disable hw overlay option and it will not only improve performance but it will eliminate hard freezes.
[AT&T Samsung Galaxy Note I717] :
Using 09/15 nightly (today) and KKO.7 kernel, I have no flicker!

Sweet! This rom is ready for an RC :good:
[AT&T Samsung Galaxy Note I717] one7dchevy:
Awesome good to hear!
[AT&T Samsung Galaxy Note I717] :
I remain unconvinced. I would like to hope...
[AT&T Samsung Galaxy Note I717] bradmont:
Yeah, still pretty crash in certain situations, like task switching and the menu in the stock browser . It's definitely getting better, but not there yet.
[AT&T Samsung Galaxy Note I717] thair7391:
Holy **** you're right!! Now I can enjoy the smooth tipple buffering of Project Butter without that badgering flicker. JB is finally smoothing out like it was made to. :) :) Chrome seems to be running smoother than in previous builds as well.

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

Actually that option decreases performance although it does get rid of flicker. But we no longer have to use that option anymore! Just clean-flash the latest 9/15 build along with DaGr8's latest KKO v7 kernel and you can leave triple buffering enabled without getting flicker!
[AT&T Samsung Galaxy Note I717] ipprof:
BT

Is there no fix for the BT audio?
[AT&T Samsung Galaxy Note I717] ipprof:
Skype doesnt work
[AT&T Samsung Galaxy Note I717] cityhunterxyz:
Still getting freezes with the hardware menu button in some apps but the lack of flickering and general improvements make it liveable.

Also I seem to be noticing improved battery life on the stock kernel, could be that my previous flashes were a bit flakey but I just finished a shift at work and when I got my phone out of my locker had about 10% more battery than normal and was still at 87%.
[AT&T Samsung Galaxy Note I717] ipprof:
I'm getting a lot of freezes especially and predictably when I menu almost any app or use anything that drops down Ialso list phone signal every few hours and have to reboot (that causes a freeze too if you try to reboot from the power stop down ). Anyone have a good cm10 compatible Tmo radio/modem
[AT&T Samsung Galaxy Note I717] Web-head:
It actually does not decrease performance any longer. It improves performance. There is no frame rate drop and the transition animations are much smoother with the hw overlay setting checked. It also prevents freezes like when task switching or opening the settings menu in portrait.

This is on the stock kernel. What ever you believe that setting does is probably wrong. I used to think so too but the performance is improved with the setting checked.

---------- Post added at 09:39 PM ---------- Previous post was at 09:36 PM ----------

Use the stock kernel and check the disable hw overlay button and you will get the best performance and it will eliminate the freezes. Try it.

I think that the disabled hw overlay button is mislabled or we just didn't understand what it was because it does not decrease performance anymore.
[AT&T Samsung Galaxy Note I717] cphancock1:
I had lots of problems with the leaked modem. Like you said cutting out phone rebooting ect. I switched back to blaze ics and it seems to be much better. Haven't lost signal in two days. Only major problems I have is the menu button in the stock browser and trying to switch apps with task manager everything is is pretty good for a nightly
[AT&T Samsung Galaxy Note I717] ipprof:
I really like this Rom. I assume the bugs will be worked out. one problem that probably isn't a bug though is how to get a full photo as wallpaper try as I might, cropping squares appear and I can not get the full photo. any help?
[AT&T Samsung Galaxy Note I717] Killemalll:
The new 0916 nightly that goo manger is showing has CM9 in the title. Is that just a typo?
[AT&T Samsung Galaxy Note I717] rohankb:
CM9 is still being released. Not to be confused with CM10.
[AT&T Samsung Galaxy Note I717] Web-head:
No, it isn't. It is actual a CM9 Nightly.

I do wish they would fix Goomanager to not alert me to a ROM update for CM9 when I'm on 10 though lol. Guess it just goes on the date.
[AT&T Samsung Galaxy Note I717] tbae2:
9-15 has been the smoothest yet! Just the freezes were annoying but the check box seemed to fix that. I think I'm getting sleep of death though. Will see if check box also fixed that . No flicker either
[AT&T Samsung Galaxy Note I717] cityhunterxyz:
Yeah, I love goomanager except for that part.
[AT&T Samsung Galaxy Note I717] jlpatte2:
9/15 has been great for me also so far, only one force close so far and definitely much smoother. running kko v7 with sio and lulzactive at 1720mhz top and 192 bottom.

Have not really worked it hard though.

Update... so Bluetooth is almost completely broken, oddly, it will control (I.e. pause play, next) successfully, but can't seem to get music out of it for anything...had worked on at least some previous nightlies.

Josh
[AT&T Samsung Galaxy Note I717] ipprof:
yeah I would think fixing BT would be a priority.
[AT&T Samsung Galaxy Note I717] hololight:
There is actually audio problems all over the place... I have weird issues with a few apps like audiobook apps I use, intermittent issues with google play, couple other...
[AT&T Samsung Galaxy Note I717] rohankb:
Looks like they are implementing BT fixes from CM9 into this next release. Looks like a lot of fixes in the next release.

http://cm10log.appspot.com/?device=quincyatt
[AT&T Samsung Galaxy Note I717] ipprof:
That is in fact a huge list of files including half a dozen for BT alone. Talk about ambitious. Nice work!
[AT&T Samsung Galaxy Note I717] thair7391:
Yeah. Not only are they fixing A2DP playback but they are adding message access functionality so that my SYNC system in my Ford vehicle can finally read messages back to me! I'll have to make sure I turn that off if my mother is ever in the car with me. Either that, or tell the ladies to take it easy :highfive:
[AT&T Samsung Galaxy Note I717] :
We shall see. I'm not budging from 9/5, yet.
[AT&T Samsung Galaxy Note I717] Sicarius128:
You can at fix A2DP right now. Just edit /system/etc/audio_policy.conf. In the a2dp section near the bottom of the file, change "sampling_rates 48000" to "sampling_rates 44100". Save and reboot.
[AT&T Samsung Galaxy Note I717] ipprof:
That was a simple fix! Thanks! A lot!
[AT&T Samsung Galaxy Note I717] Ltilt2:
Why wait till tomorrow. In dev section, Natewiebe13 added all CM's fixes to his CM10. Check it out
[AT&T Samsung Galaxy Note I717] ipprof:
I don't see it at all.can you tell me exactly where I can grab it?

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

I can't find it at all.can you tell me where it is so u can grab it too?
[AT&T Samsung Galaxy Note I717] ndmoh1:
Here you go!

http://xdaforums.com/showthread.php?t=1871010
[AT&T Samsung Galaxy Note I717] rajendra82:
The 9/19 nightly makes the capacitive buttons stop working for me a short time after boot. I wonder if anyone else is seeing this as well.
[AT&T Samsung Galaxy Note I717] closeshave2:
I just installed the 09/19 nightly. I didn't notice any flicker, but every time I locked/unlocked the screen the buttons at the bottom (menu, home, back and search) stopped working! I had to flash back to my previous rom. As always, YMMV.
[AT&T Samsung Galaxy Note I717] bradmont:
I'm having the same problem with soft keys. Back to 9/15.
[AT&T Samsung Galaxy Note I717] rohankb:
There's a second download. Check the md5
[AT&T Samsung Galaxy Note I717] MadHatter83:
It seems if you use a different launcher it doesn't seem to have an issue with it (I use Nova). Even though it didn't have any flicker, I had issues with the stock kernel freezing and rebooting if I didn't have HW Overlay checked.
[AT&T Samsung Galaxy Note I717] Web-head:
Grabbed the second release of 0919. The capacitative buttons seemed to be working, but I didn't stay on it long enough to say if they wig out again after awhile like the earlier release.

Went back to 0915 though because I didn't notice any real changes on the new Nightly other than that the transition animations are all jacked up, regardless of whether you check Disable HW Overlays or not. Not the end of the world, and I would live with it if there were some meaningful fixes, but in my limited walk through, I didn't see any.
[AT&T Samsung Galaxy Note I717] :
I sort of remember that the CM team stating the transition from ICS to JB would be less work than GB to ICS and everything woulb be much smoother. Seems to be the opposite. I feel bad for them. Everything they try to fix seems to create new problems.
[AT&T Samsung Galaxy Note I717] rohankb:
Be careful as it doesn't see that the update is not on Goo.im yet. For those looking for it:

http://get.cm/get/jenkins/8380/cm-10-20120919-NIGHTLY-quincyatt.zip
[AT&T Samsung Galaxy Note I717] Ltilt2:
Which CM is this you posted?
[AT&T Samsung Galaxy Note I717] kurtolson:
I also noticed that the buttons aren't working on boot/resume from suspend.

I'll try the 2nd build but I'm not holding my breath.

My failsafe, is as with others in the 9/15 build for now.

UPDATE: the 2nd daily build today corrects the button issue!
[AT&T Samsung Galaxy Note I717] Web-head:
He means that there were 2 builds of CM10 0919 released today. You can see them both on get.cm but Goomanager Beta only has the first 0919 release. Presumably, the second release corrected issues with the first, but I can't confirm that as I went back to 0915 after trying out 0919 for only about 10mins. That goes for both 0919 builds.
[AT&T Samsung Galaxy Note I717] rajendra82:
The second build does not have the disabled buttons issue. I am noticing some new artifacts with the 9/17 nightly with "Disable HW overlays" checked that were not present before. With the new build, and having that option checked, the swirling pencil animation in Draw Something has a ghost version playing underneath. Unchecking the option fixes the issue.
[AT&T Samsung Galaxy Note I717] Ltilt2:
OOOOh I see. I couldn't make sense of what he was saying.

Thanks for your reply
[AT&T Samsung Galaxy Note I717] rohankb:
I'm reading some of you jumped back to 9/15. I have been running this 9/19 so far. Only issues I did have was some "glitching" it seemed. Had to go back into the build.prop and make the previous changes and that resolved it as in previous versions of the rom. I have been running it fine since early morning. No glitches, flickering or anything. Could be in my head, but battery life seems a lot better to me, not draining as quickly.

Now for my set up, just as a reference: I am using 9/19 CM10, DaGr8 v8 @ 192/1836, Apex beta launcher (designed for JB)

Not doing any undervolting. Governor is OnDemand, I/O Scheduler is SIO with 3072 SD cache size, memory management zRam is 26% and the other two boxes are checked in there for Allow purging of assets and Kernel samepage merging.

All animation scales in Dev options are off and Disable HW is unchecked, BUT, I did make those changes in the build prop as earlier posted to the

debug.compostition.type from dyn to gpu

debug.mdpcomp.maxlayer from 3 to 2

Thanks to Thair7391 for pointing that out in the past...

Let me know if you guys think a better governor and I/O combination work for you guys that have a similar set up.

Also to note, I did get Youtube to crash multiple times when trying to adjust the volume during playing a video, but havent tried to identify where the setting is that I think they added to make video or music skip ahead on pressing volume buttons, I am assuming that may be the issue with it.
[AT&T Samsung Galaxy Note I717] ipprof:
So I installed the unofficial and there is no flicker and NO FREEZE. But there is no bt which I had fixed by inserting the right speed in the audio package. But I checked and this already has that fix. So.. what to do?
[AT&T Samsung Galaxy Note I717] ipprof:
And now I've flashed the latest cm10 and still no bt. I was able to install it in the last version but not this one. Anybody?

---------- Post added at 07:35 PM ---------- Previous post was at 07:13 PM ----------

Also with 9/19, no sound on apps(for instance but not limited to YouTube) sound is fine on phone and speakerphone but nothing else. I think the bt problem may be more of an audio problem and not a bt problem
[AT&T Samsung Galaxy Note I717] ChronoReverse:
Does the browser instantly crash when pressing the Menu button for anyone else?
[AT&T Samsung Galaxy Note I717] ipprof:
Crashing may not be the right word. I would say everything freezes as soon as you press menu and the pop up menu appears. Nothing to do but reboot. It's replicable and consistent
[AT&T Samsung Galaxy Note I717] ChronoReverse:
I've fixed it somehow. Wiped the data clean in Titanium, disabled HW overlays and set Forced GPU Rendering. Don't know which made it work.
[AT&T Samsung Galaxy Note I717] cityhunterxyz:
Yeah that's been an issue for the past several builds, you can did it by disabling HW acceleration in dev options or using an alternative kernel
[AT&T Samsung Galaxy Note I717] nique0201:
Does anyone know why with the latest build my A2DP works but not my in call Bluetooth.... it works on my phone but not on my dads .. is there a fix?
[AT&T Samsung Galaxy Note I717] ipprof:
my bt basically doesn't work so talk of a2dp isway beyond my stage right now. this Rom needs seriouswork on audio and blue tooth

---------- Post added at 10:02 PM ---------- Previous post was at 09:49 PM ----------

So by basically fooling around with volume on you tube but first Dractivating the option to use volume to advance tracks, I now have full bt. Is it supposed to be this hard? By the way the rocker choice is the very last choice under volume. It worked for me. Turn it off.
[AT&T Samsung Galaxy Note I717] rajendra82:
The underlined part.
[AT&T Samsung Galaxy Note I717] Web-head:
Disable HW Overlay is what made it work. It has been stopping freezes for the past few Nightlies.
[AT&T Samsung Galaxy Note I717] rohankb:
You never tried the build prop settings? That way you don't have to keep setting it on reboot. Also there's a new 9/20 nightly up that says on the change log that it addresses the quincyatt hardware definition?
[AT&T Samsung Galaxy Note I717] ChronoReverse:
Which build.prop settings? I have tried the dyn->gpu one but is there another?

Sent from my Galaxy Note!
[AT&T Samsung Galaxy Note I717] rohankb:
Scroll up to my post earlier, #335
[AT&T Samsung Galaxy Note I717] McNoob:
I'm back on the 9/12 nightly. Anything newer, calls over BT don't work for me...it connects, but no audio is piped thru BT - the audio still comes out the earpiece.

shame too, because it seems that the 9/19 nightly seems less power hungry. here's hoping the BT gets resolved soon! :good: :victory: :highfive:
[AT&T Samsung Galaxy Note I717] ipprof:
have you tried to turn off the volume control music toggle function? Iturneditoff and all my bt returned. it'stheverybottom volume function.
[AT&T Samsung Galaxy Note I717] Web-head:
I'm hesitant to do it because i don't think that we really have an understanding of what those settings actually do, and/or the Disable HW Overlay setting is actually mislabled. As I stated in earlier posts, every thing posters have written about what the setting is supposed to do, it actually does the opposite, at least on the past few builds.

Checking the setting actually IMPROVES performance. It doesn't decrease it at all like it used to, and like many still believe that it does. It also eliminates known freezing issues as far as task switching, opening settings in portrait mode in many apps, etc.

I'll give the gpu build.prop setting a try, as that is what i think the disable HW Overlay actually does now, but who knows anymore. I'm gonna steer away from the maxlayer to 2 setting as I believe, we want it at 3 for better performance, but again, who the hell knows anymore lol.

As for the latest 0920 Nightly, the transition animations are still all jacked up, whether you check Disable HW Overlay or not, so I can't see how it could be for our hardware, but maybe it is and it just needs a lot of smoothing out. One thing is for sure, the graphical performance on 0915 is much better than 0919 and 0920. The transition animations are perfect in 0915.

I'll stick with 0920 for a bit just to see if the random reboot issues are solved. I can tell you that the freezing issues as far as task switching and opening settings menus in portrait in apps is NOT fixed in 0920. You still need to check the Disable HW Overlay button to prevent them. I'll try the gpu over dyn build.prop setting to see if that also will prevent the freezes, so that I don't have to check the HW Overlay setting on every reboot.

I'll report back.
[AT&T Samsung Galaxy Note I717] rohankb:
@web-head, I think the number is associated with how many passes it does to draw or buffer. Something like that. I'll look for it later and post it. But think it does the same as checking the disable hw, thair posted the reasoning behind it in the past.
[AT&T Samsung Galaxy Note I717] Web-head:
That's what I've heard as well. Not sure it's accurate though. Even still, if it is, we want 3 then and not 2. Jellybean uses 3 buffers. ICS 2. That's part of how JB improves performance. If the prop works how we think, why would we want it to be set to 2?

Furthermore, I don't think that's what the Disable HW overlay setting does. If it did, why would performance improve with only 2 buffers? Again, who the hell knows lol?

Just tried the gpu setting on the build.prop from dyn and I can confirm, it does not prevent freezing. First thing I did after reboot was open the stock mail app and attempt to change email accounts in portrait. Froze on the very first attempt. Had to hard reset.

I'll try it with the maxlayer at 2 for ****s and giggles. Most likely, though I'll end up having to check the HW Overlay setting to prevent freezes.

I'll report back.

Update:

Well, I can confirm two things.

1- Changing the maxlayer to 2 from 3, AND setting the composition type to gpu, not only prevents the known aforementioned freezing issues, but it also makes the transition animations smooth again, like on the 0915 build with the disable hw overlay setting checked. If you only change the composition to gpu, it neither prevents freezes, nor smooths transition animations. If you only set the maxlayer to 2, it prevents freezes, but the transition animations are still jacked up. You need to enable both to get the best results.

2- Those two build.prop settings are obviously not the same as what checking HW Overlay does. If it was, then simply checking HW Overlay would have gotten the same results, but it doesn't.

Based on deduction, I'd be inclined to say that the HW Overlay setting is closely related to the composition prop being set to gpu. It isn't exactly the same though because checking Disable HW Overlay stops the known freezes while having jacked up transition animations. Just setting the composition type to gpu, has the jacked up transitions, but does not prevent the known freezes.

Make of this what you will, but for now I'm going to rock these 2 tweaks. We'll see what happens on future Nightlies.

Update 2:

Full disclosure, this is all on the stock CM10 kernel.
[AT&T Samsung Galaxy Note I717] McNoob:
I re-flashed the 9/19 build to test this - sorry to report that it makes no difference whether the music control setting is toggled or not. :(
[AT&T Samsung Galaxy Note I717] rohankb:
Can you try deleting Apollo in Titanium Backup and see if it works then? I know some of my music apps wont work with this installed on my phone when I am not in Wifi range.
[AT&T Samsung Galaxy Note I717] ChronoReverse:
Thanks for doing the testing. I had the gpu part but not maxlayers which is why it didn't work for me until I set both.
[AT&T Samsung Galaxy Note I717] ipprof:
My mistake
[AT&T Samsung Galaxy Note I717] borgib:
Download RomToolbox from the market. It makes it super simple for noobs ;)
[AT&T Samsung Galaxy Note I717] rohankb:
System Tuner seems to be way easier to me to use. There is a Build tab and in there you can make the changes.
[AT&T Samsung Galaxy Note I717] ipprof:
I finally found it with just my file manager and used a text manager to make the two changes. The problem is I got a freeze trying to refresh an xda page on the browswer. I thought this would prevent the freezes. Maybe just some freezes? Too bad... But good work.
[AT&T Samsung Galaxy Note I717] Web-head:
Maybe it was just a one off thing. I haven't gotten a single freeze with these tweaks and I tried to make the phone freeze by repeatedly doing all the things that I know makes the phone freeze consistently.

I've task switched in portrait, opened settings in portrait in the stock browser as well as Chrome, and I've changed accounts in the stock mail app in portrait. All these things I tried repeatedly, in succession, a few dozen times, and no freezes. Haven't gotten one in the course of using them as I normally would throughout the day either.

I'd still use ROM Toolbox Lite. It's free and it is pretty useful for making these kinds of tweaks and also changing the dpi. If you're into that Tablet/Phablet thing.
[AT&T Samsung Galaxy Note I717] ipprof:
Thanks very much. I AM into that phablet/tablet thing because getting the new Yorker app requires tablet specs. Can you tell me how u would go about making that change?

By the way no more freezes all day. This is so COMFORTABLE to use. Thanks again.
[AT&T Samsung Galaxy Note I717] Web-head:
Look for ro.sf.LCD_density. Should say 320. That's default. You would have to ask someone else what number gives you tablet mode on this ROM. I believe its anything below 177 or 170.

I don't change DPI so I don't remember exactly.
[AT&T Samsung Galaxy Note I717] rajendra82:
The value at which the switch occurs is 215 or below. At that point, the OS thinks the device is larger than 7”, and switches to the tablet UI. This is because our resolution is 1280X800, giving us a diagonal pixel count of 1509, and 1509 divided by 215 or less is greater than 7.

Edit:

The value of 215 for the lcd density used to trigger tablet UI in CM9, but it seems that it needs to be dropped to 170, before CM10 switches UI. This makes some sense, because the Nexus 7 has JB running with the phone UI.