yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] hololight:
Still no BT a2dp (media) in 9/8. It's funny, when you disconnect the BT device the media stops as if it was working correctly all along.... but for whatever reason, when connected to bt, media is always routed to speaker or headphones (if plugged in).

Note: BT for calls works just fine.
[AT&T Samsung Galaxy Note I717] lenng:
Can you post a link for that kernel 1.5 never mind I found it what is the best settings for the l/0 scheduler
[AT&T Samsung Galaxy Note I717] Web-head:
Tried Flap's new 1.5 kernel. Screen flicker came back after having no flicker on the cm kernel.

Wiped cache and dalvik and flashed the 0908 nightly and job gapps again and flicker was gone.

Maybe someone else would have better results but I'll stick with the stock kernel for now.
[AT&T Samsung Galaxy Note I717] rohankb:
I'm using SIO, I remember h0tw1r3 older cm9 builds, he suggested that, but I am not sure which is best on these. I would have to do some benchmarks. Currently on SIO and running at 1836, I am getting 3600's on my Quadrant score.

I see no evident flickering, I am using Apex launcher, not sure if that helps it or not, and am overclocked.

EDIT: I see the flickering a bit when I switched to a still background, I normally have WP-Clock as my background and it's a live wallpaper type background.
[AT&T Samsung Galaxy Note I717] thair7391:
I just wanted to propose a solution to the issues that have arisen in the most recent three builds, namely audio issues and Bluetooth functionality.

The past three nightly builds have had significant increases in performance as well as reductions in flicker but they seemed to have disabled previously operational functionality so my first recommendation to get the vest of both worlds is to first flash the latest nightly (9-8) and then after flash the 9-5 build (the last stable release with known working Bluetooth) over it, clearing cache and Dalvik before rebooting.

The next step to get Google Play Music streaming working is simply to use Titanium Backup to remove Apollo. (Idk why but it works!) This has fixed the "unable to stream music" error for me.

Then finally, to improve graphical AND system performance (as mentioned in my Jelly Bean Smoothness forum), change the "debug.compositing.type" value in build.prop from "dyn" to "gpu". This will force Android to always offload graphical operations to the GPU instead of dynamically switching between CPU and GPU based on resource consumption.

By the way, I've done all of the above just recently (about 4 hours ago) and have had nothing but success so everyone let me known if this provides you with any luck!
[AT&T Samsung Galaxy Note I717] Web-head:
Yes. I'm using a static wallpaper and there is no flicker with the cm kernel but it flickers a lot with Flap's kernel. I'm also using the stock trebuchet launcher.
[AT&T Samsung Galaxy Note I717] rohankb:
I'm gonna try it without the flap kernel
[AT&T Samsung Galaxy Note I717] ipprof:
Will this also allow BT audio (to headphones, speakers, etc.)?
[AT&T Samsung Galaxy Note I717] thair7391:
By "this" do you mean the proposal I suggested until everything is fixed in the next nightly? Yes, it will allow full Bluetooth functionality, both headset and A2DP stereo output. I use it just fine in my Ford vehicle equipped with Microsoft Sync.
[AT&T Samsung Galaxy Note I717] ukguy115:
Anyone's gallery bringing in picasa albums mine do not show up? Just curious. Thanks.
[AT&T Samsung Galaxy Note I717] rahsaanabdul:
CM10 EXPERIMENTAL is live. I've already flashed it but I'm headed out to work...
[AT&T Samsung Galaxy Note I717] :
I have no idea what "Experimental" means. Based on the performance on the current Nightlies experimental is the word I'd use to describe them. What does this one do? Add a death ray?

(Either way I'm still using 9/5 as my DD. It's actually remarkably stable if you work around the quirks and inconsistencies.)
[AT&T Samsung Galaxy Note I717] NYConex:
http://www.cyanogenmod.com/blog/cyanogenmod-10-m1
[AT&T Samsung Galaxy Note I717] BoOsT:
LMFAO!!!
[AT&T Samsung Galaxy Note I717] EvoXOhio:
Flashing the ROM is a full replacement of the /system partition. If you flash 9/8 and then 9/5, you have completely overwritten the 9/8 build. So all you've done is flash the 9/5 build.
[AT&T Samsung Galaxy Note I717] thair7391:
OK so the only location/partition in which ALL components of the ROM (OS) are stored is in the /system partition? There aren't other elements that can reside in other places?
[AT&T Samsung Galaxy Note I717] nlghtcrawler:
I want able to change the dpi on the m1 build. Anyone else having that problem? Other than that it ran very smooth and no flicker.

I want on it long enough to test audio but I'm back on cm9.1 since i can't go without tablet mode.
[AT&T Samsung Galaxy Note I717] Web-head:
I'm pretty sure that CM10 has tablet mode. I think it just engages at a lower dpi than CM9. 170 or something like that. Not a tablet guy so I don't know the exact number.

---------- Post added at 11:39 AM ---------- Previous post was at 10:59 AM ----------

Not exactly sure what the Experimental was supposed to accomplish based on the link that a poster provided, but I went back to the 0910 Nightly. The Experimental brought back random reboots and loss of data issues that I hadn't had in a few nightlies.

Others may have better luck.

Full disclosure, I didn't factory wipe before installing the Experiemnetal. Just wiped System, Cache, and Dalvik, then flashed Experiental, then gapps, then wiped cache and dalvik, then fixed permissions and rebooted.
[AT&T Samsung Galaxy Note I717] jyazzie110:
For future reference there is no need to reflash gapps when u update. Just wipe both caches and flash the nightly or experimental update
[AT&T Samsung Galaxy Note I717] Gater2011:
How is the experimental Cm-10..any issues as of yet?
[AT&T Samsung Galaxy Note I717] yohojones:
I still can't play to the bluetooth in my truck and the screen was flashing occasionally.
[AT&T Samsung Galaxy Note I717] Web-head:
Can't speak for anyone else, but I did.

Got 3 random reboots. One while I was typing in What's App. One while phone was idle, and the other while I was surfing with the JB Browser.

I lost connection once and had to reboot my phone to get it back. Toggling Airplane didn't work.

Those were all issues that I had on previous Nightlies but hadn't seen on the last few, so I flashed back to the 0910 Nightly. Maybe others had better luck, but my experience with the M1 was not good. And those issues all came up in the course of about 2hrs on M1.

Side note. Anyone else seeing this issue? I can recreate it at will. If you click on the button to switch mail accounts in the stock mail app while in portrait mode, the phone freezes. Do it in landscape and it's fine. If I open the settings menu in the stock browser while in portrait, the phone freezes. Do it in landscape and it's fine.

Also, it doesn't happen all the time, but when I switch tasks in portrait, it sometimes freezes the phone. I don't think it has ever happened while the phone was in landscape.

This has happened on every Nightly since 0907 or 0908, can't remember which, and happens on M1 as well. Now that I know of it, I work around it, but I want to know if everyone else has this, because I've never seen it mentioned, and it isn't random. It can be done at will. Weird that a bug like that isn't mentioned, and also hasn't been fixed yet.
[AT&T Samsung Galaxy Note I717] NYConex:
I was having issues with m1 as well. I flashed dagr8's kernel and all is right in the world.
[AT&T Samsung Galaxy Note I717] Gater2011:
I'm Pretty sure this has beem mentioned in an earlier post...but sometimes when I'm making a phone call I would get a random reboot...then aftwards won't be able to hear the person whom I'm speaking with...How do you guys deal with this issue..if you've ever encountered it..I don't like re-flashing the entire Rom
[AT&T Samsung Galaxy Note I717] laxjones:
Install

Sorry for being a noob but what should we wipe before flashing a new nightly and/or the m1? Ive just been wiping the Dalvik between each.
[AT&T Samsung Galaxy Note I717] rohankb:
Wipe cache then the dalvik in between nightlies.
[AT&T Samsung Galaxy Note I717] troyolson92:
U have to flash gapps as it wipes system/app on a new ROM flash. That is where your gapps are.

---------- Post added at 06:29 PM ---------- Previous post was at 06:26 PM ----------

Wipe cache, wipe dalvik, flash ROM, flash gapps. Boot, wait, wipe caches again and reboot. Seems to settle in faster this way. I wipe caches dalvik and cache often anyway as i am constantly removing adding changing apps
[AT&T Samsung Galaxy Note I717] jyazzie110:
Idk but I always just wipe both caches and flash the rom and never had my gapps disappear.....don't believe me? Try it out next time u flash a nightly
[AT&T Samsung Galaxy Note I717] laxjones:
You dont have to flash gapps. Im pretty sure you did with the first few nightlies but i forgot one day and they were there still. I just wasnt sure if wiping cache made a difference or factory reseting and all that. I flashed one nightly without clearing anything and it seemed to work but it might have been buggier than it should be
[AT&T Samsung Galaxy Note I717] Err0xx:
System/app is backed up by your recovery (cwm/twrp basically all of em now) when you wipe and restored when you flash a new nightly.

Flashing gapps every time is NOT required and increases chances for screw ups.

Wipes cache and davlik but ditch flashing gapps every time.
[AT&T Samsung Galaxy Note I717] MadHatter83:
Thanks for the tip. :good: I flashed the latest versio (KKO.IV.ZIP) and it completely solved my random reboots and freezes. Still get some flicker but I can live with that.

http://xdaforums.com/showthread.php?t=1870835
[AT&T Samsung Galaxy Note I717] :
got lockups with the Sept 12 nightly when pulling apps up from the task switcher. back to m1 with dagr8 kernel and everything is good for me except flicker.

so far the m1 has been the most kind to me
[AT&T Samsung Galaxy Note I717] Web-head:
Try task switching in landscape mode. It never freezes in landscape for what ever reason.
[AT&T Samsung Galaxy Note I717] rohankb:
I have no lockups on task switching. Am on 9/12 and running dagr8 kernel at 1836
[AT&T Samsung Galaxy Note I717] diamantericos:
Is it safe to flash these nightlies of the new m builds
[AT&T Samsung Galaxy Note I717] Web-head:
Yes it is.

---------- Post added at 10:56 AM ---------- Previous post was at 10:53 AM ----------

1- Do you get flicker with DAgr8's kernel like with flapjaxxx'? And...

2- Did you ever get lockups on the stock kernel when task switching in portrait to begin with? Ditto for opening settings menu's in portrait in the stock browser and SMS apps, as well as switching accounts in portrait in the stock mail app?
[AT&T Samsung Galaxy Note I717] rohankb:
Flicker is slight. Like while typing like right now the screen blinks black. Nothing really noticeable.

Never got lockups on stock. Only use my phone on portrait. I never have my phone on auto rotate either. Settings menu is with no issues.

I don't use stock email. Using gmail with 7 accts with no issues.

....................

Update: I just took off "show touches" in developer options and now I see no flicker at all even as typing this.
[AT&T Samsung Galaxy Note I717] ipprof:
Kind of a noob question, but those are the kind I always have. Do you flash a kernel just as you would a ROM or is there something distinctively different about it requiring different procedures?
[AT&T Samsung Galaxy Note I717] Web-head:
I was in the settings menu under developer options cause rohan mentioned the show touches settings, and I glanced at the HW Overlays setting and saw that it says underneath "Always use GPU for screen composting."

I'd seen the HW Overlay option before, but I don't remember it saying this underneath, though it very well may have all along. The thing is though, I'd been conditioned to think that this setting should stay unchecked as it would disable the HW acceleration and NOT use the GPU, but after reading it, it seems like that's the opposite of what it does. Maybe it's worded incorrectly, or I don't fully understand what it's really saying, but I wan't sure. So I checked it to see what happens, as I haven't tried checking it in many, many builds of Nightlies and other custom ROMs, and when I had back then, it always made the framerate drop noticeably, though it stopped the flickering.

Thing is, when I try it now, not only does it stop what little flicker was left over, like when switching or opening apps and such, but it also did NOT decrease the framerate at all. In addition, it totally eliminated the freezes that occurred when task switching in portrait, changing mail accounts in portrait in the stock mail app, and opening settings in portrait in both the stock browser and Chrome. The phone runs perfectly with the setting checked. I unchecked it just to test, and, just as before, the phone froze while changing accounts in the stock mail app, in portrait.

Now I'm confused, based on not only the wording of the description of the HW Overlay option, but also by the results that I now get while its checked, as to what it actually does.

Let me know if anyone else sees the same thing, because the framerate is just as smooth as with it unchecked, but with absolutely no flicker, smoother transitions of opening, closing, and switching apps, and it rectified freezing issues that happen, EVERY SINGLE TIME when it is not checked.

What the F lol?
[AT&T Samsung Galaxy Note I717] rajendra82:
<strike>Read the link below. Post 3 and 4 has the answers.

http://rootzwiki.com/topic/28977-disable-hardware-overlays/

I am not so sure that the answer there is right.
[AT&T Samsung Galaxy Note I717] Web-head:
Not sure that it doesn't confuse the issue more lol.

From their explanations, it sounds as if performance should go down when you disable HW Overlays, which is what USED to happen, but not what happens now. Furthermore, one of the posters says that using the GPU for drawing should be fine. The thing is, the setting says Disable HW overlays, which was said to be bad, but says underneath it Always use GPU for screen composting, which is supposed to be good.

My question is, is the setting mislabled? Is the setting doing something other than what it should? Are we not understanding what they are actually trying to say with that setting?

Right now, the performance with the setting checked, is much better than with it not checked. From framerate perspective, as well as to a stability of the OS (no more freezes during the actions I listed before) perspective.
[AT&T Samsung Galaxy Note I717] rajendra82:
I agree with you, except my eyes are not good enough to see any performance difference due to enabling our disabling that setting, which needs to be done on every boot for some reason. I would rather trade a small performance loss, if any, for the increased stability. Before checking the box, bringing up the settings in Chrome menu an instant freeze for me. Now it doesn't do it any more.
[AT&T Samsung Galaxy Note I717] rohankb:
Glad this worked out for you guys. I have "disable HW" unchecked and the one beneath it for 2d checked.

I found that I got better Quadrant scores when I left it checked, but no noticeable difference otherwise using the device.

I've had scores of 3600+ with that setting.
[AT&T Samsung Galaxy Note I717] laxjones:
kernal

Does anyone know a good kernel that has OC and works with the nightlies? All i need is OC and UV would be nice
[AT&T Samsung Galaxy Note I717] Web-head:
Mine are lol, and I could easily see a framerate drop when the HW setting was checked back on early Nightlies and unofficial CM10 ROMs before there even were Nightlies. Now though, that isn't the case. It runs better with the setting checked from every standpoint.

The settings menu freezes in browsers, switching accounts in the stock mail app, and task switching, all in portrait mode, were freezes that I could recreate EVERY SINGLE TIME. They weren't random at all. They never happended in landscape though. With the HW Overlay setting checked, now the freezes can not be triggered even once, ALL flickering is gone, not some, not most, but all, the framerate is just as smooth with it unchecked, AND the transitions for opening, closing, switching, and rotating apps, looks MUCH smoother and complete.

Don't want to make it like I'm complaining, because I'm not, but I'm just curious what this setting actually is intended to do, and want to know why it has both a description with a negative connotation (Disable HW Overlays) as well as a description with a positive one (Always use GPU for screen composting) on the same setting?

From my limited understanding of what each of those two things means, I don't see how the setting could be doing both at the same time, which makes me wonder if one of those two things is listed incorrectly, or if I, and probably just about everyone else on here, have had the wrong idea of what the setting did all along.

---------- Post added at 05:42 PM ---------- Previous post was at 05:39 PM ----------

I too, have the Force 2D GPU setting checked. That one I do understand lol and would not uncheck it. The other though, I'm confused about, because it used to yield poor performance, but now it yields much better performance in every way.

You said that you never get the freezes that many of us mentioned, so I dont expect you to be able to test that, but try checking the Disable HW button, and tell me if you see any drop in framerate when scrolling, or if you see how much better EVERY transition animation looks, along with the complete elimination of flicker.
[AT&T Samsung Galaxy Note I717] rohankb:
Also forgot to mention, the 3 settings for scaling, I have them all disabled. Never used that .5x or 1x settings. Screw that to make the phone look nice switching thru menus or screens. Always seemed like a waste to me. Idk...

................

Just tried enabling disable hw and it made no difference. Got no problems switching tasks from long hold on home button, nor in settings of the default browser, chrome or dolphin.

Just to tell you, checking it helped on other kernels like on ICS because they addressed the issues of the OS talking to the hardware better. JB still has kernel issues that need to be ironed out is my assumption. I remember on h0tw1r3 ROMs of ICS, you enable that and you got much better 3d performance.
[AT&T Samsung Galaxy Note I717] rohankb:
delete
[AT&T Samsung Galaxy Note I717] :
This is everything you want and more

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

Checking in that I am having great luck with the thursday 09/13 nightly with DAGr8's kernel
[AT&T Samsung Galaxy Note I717] karmanator:
bug list for cm10 i717 rom nightly 2012 09 13

Bug list 2012 09 13

1) gmail attachment in email freezes upon second attachment. Always freezes and requires a reboot.

2) camera video flickers when recording on ocassional bright light.

3) dead freeze when trying to add a webpage address
[AT&T Samsung Galaxy Note I717] rajendra82:
These are precisely the issues that get fixed by checking the "Disable HW Overlays" box in Developer Options.
[AT&T Samsung Galaxy Note I717] rohankb:
A lot of nice lil goodies on 9/14 like burst mode on camera and finally stopwatch and timer are back on the clock app, nice new JB version...
[AT&T Samsung Galaxy Note I717] bigwayne3902:
No flicker with new nightly
[AT&T Samsung Galaxy Note I717] ipprof:
Can anyone...ANYONE...tell me whether flashing a kernel is done the same as a ROM or are there important differences and if so what? I want to flash cm10 but also want the most effective kernel for it.Thanks.
[AT&T Samsung Galaxy Note I717] borijess:
Same

Sent from the TermiNOTEr! ;)
[AT&T Samsung Galaxy Note I717] Web-head:
Flashed the 0914 Nightly.

Immediately tried the things that I know freeze the phone consistently. Opened an app and then went to the homescreen. Opened recents and then opened the app again from the task switcher while in portrait. App opened fine. Went to homescreen and tried it again. Froze the phone. Nothing new. There have always been rare occasions where it would actually work. The thing that was different this time though was that when it did work, the transition animation of opening the app from recents was perfect like when you do it with The HW Overlay option checked, only I didn't have it checked. Usually the animation looks incredibly choppy, there is screen tearing, and the animation plays more than once like a ghost in an Asian horror film. The fact that the animation is as it should be now, without checking HW Overlay, gives me hope that they are closer to getting things ironed out.

On the subject of the animation. It just occurred to me that when the transition animations played out on previous builds, without HW Overlay checked, that there were visual issues, from flicker, to choppiness, to animations repeating, to screen tearing. VSync fixes screen tearing. From the link that a previous poster posted explaining what Jellybean is doing in terms of animation, VSync played a role in that. From what some have posted about what the mdcomp maxlayer option does, it controls the number of frame buffers. They have also said that setting it to 2 is the same as checking HW overlay.

My question is, if HW overlay/ maxlayer controls the number of buffers, and setting it to 2 should yield better performance, then why do the transition animations play out worse, or even worse still, freeze the phone, when it should be performing better? The fact that the animations tear, tells me that VSync isn't on, but seems to be on when you check the HW Overlay option, even though we've been told this is bad.

Again, I wonder if the option is labeled wrong, or if what we have been told the option actually does has been wrong all along, because the ROM works like a stable release with it checked, and is an alpha build with it unchecked...
[AT&T Samsung Galaxy Note I717] MadHatter83:
Most kernel zips you find in the posts are flash-able. I can't say they all are, but the "King Kang One" and flapjaxx's kernels you find at the bottom of the first post in the below thread are. Just download to your your phone and flash over your current rom. I always wipe cache and dalvik cache first, don't know if you need to but I do. I've had the best results with h0tcakez v1.5, but for some KKO V works the best. You just have to play with them both to see how your phone and nightly build handle them.

http://xdaforums.com/showthread.php?t=1740367 (wrong thread, but still a lot of good info)

This is the thread I was talking about.

http://xdaforums.com/showthread.php?t=1863291
[AT&T Samsung Galaxy Note I717] Killemalll:
I'm on nightly 9/14 as well. Everything is working smoothly and the screen flicker is gone!
[AT&T Samsung Galaxy Note I717] one7dchevy:
Do you get any flicker when pressing the menu button while on the homescreen? Or when opening the settings app? I was getting a slight flicker when doing either..
[AT&T Samsung Galaxy Note I717] rajendra82:
I am going to pretend that the magical check box in Developer options is called Enable HW overlays (or Disable SW overlays), because the description, Always use GPU for screen compositing, is more consistent with the revised title, and the effects of checking the box also seem more consistent with the description than the current title of the box.
[AT&T Samsung Galaxy Note I717] ipprof:
Which kernel?
[AT&T Samsung Galaxy Note I717] :
I'm using DAGr8s kernel with the 9/14 and I've still got flicker.

other than that is a solid build!
[AT&T Samsung Galaxy Note I717] one7dchevy:
I was using DAGr8s kernel also (had flicker), maybe the CM10 kernel is the way to go for now. I might re-flash and see.
[AT&T Samsung Galaxy Note I717] :
if you do let us know your results!
[AT&T Samsung Galaxy Note I717] Web-head:
Based on the results, I would have to reluctantly agree with you.

Would be nice, if we are right about what the setting does, that they would make it stick after a reboot on the upcoming builds.

We have to be missing something lol.
[AT&T Samsung Galaxy Note I717] Killemalll:
Stock kernel. I see zero flicker going into settings or back to home screen.

I'll try one of the OC/UV kernels.