yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note I717] ipprof:
I don't know how useful it is but to test gestures I checked a couple off (it won't work if you don't choose a corresponding action) and the two I chose seem to work flawlessly. My left gesture makes it move to the previous screen and my right brings it home. Seems to work. The only problem is getting the stylus out of its testing place!

---------- Post added at 08:36 AM ---------- Previous post was at 08:30 AM ----------

I understood it was fixed. I got two units to pair and exchange code numbers and APPEAR tethered (they said they were) but there was no useful signal on the tethered phone. I figured I must have done something wrong .
[AT&T Samsung Galaxy Note I717] khaytsus:
Nah, the devices have always connected, turned blue to indicate paired, etc. But the Note side doesn't set up a route or something. I don't know what all is done for BT Tether, I looked into a little once to see if there was anything I could do to "fix" it or kludge it but I gave up.

I'll certainly try it, but sounds like how it's behaved since moving to CM10.1.
[AT&T Samsung Galaxy Note I717] ipprof:
It's blurry when I shoot it and blurry when I play it. Actually it's just raster trails.
[AT&T Samsung Galaxy Note I717] stgeorge88:
battery life is actually much better than cm10 for me. 50% can get me thru 12+ hrs light use (1hr screen time), which used to end up with less than 20% when i was on cm10.
[AT&T Samsung Galaxy Note I717] happy2000hk:
I agree. Battery life for me has been quite good too.
[AT&T Samsung Galaxy Note I717] Ouroboross:
Widget laid out is cut off on the sides

Widget laid out w/ offset incorrect. It's cut off.https://www.dropbox.com/s/ny6ggbe0nnogfkd/Sketch133205918.png

There's another bug w/ launcher layout that layout a widget but it floats above the desktop. It hangs there w/O finishing the drop onto desktop.
[AT&T Samsung Galaxy Note I717] Ltilt2:
What launcher are you using?
[AT&T Samsung Galaxy Note I717] Ouroboross:
The one that came w/ CM10.1.
[AT&T Samsung Galaxy Note I717] Jmelendez1:
If I recall, there is a setting in launcher to stretch to fit. I'm sure that's what fixes that.
[AT&T Samsung Galaxy Note I717] DARKCHYLDX101:
Battery life looking good on 2/13. Going on 9 hours at 74%.
[AT&T Samsung Galaxy Note I717] Ltilt2:
Switch to Nova Launcher
[AT&T Samsung Galaxy Note I717] Ltilt2:
This is the Launcher Im using. Very smooth
[AT&T Samsung Galaxy Note I717] rohankb:
+1 that
[AT&T Samsung Galaxy Note I717] C0BRA01:
The battery issue is because the phone is not going to sleep. The default lower speed is 384 MHz, and so thats as low as it goes, manually drag it down to 192 MHz will help a little, but if you install CPU Spy from the Play Store, you will see it is not going into sleep mode.

It does freeze once in a while, I did a full wipe, right down to full reset, formatting System, and internal storage, both caches, and Android Secure. I didn't like the camera, so I used Camera JB from the Play Store. I also use Nova Launcher.

I will say that it is extremely fast, and smooth though.
[AT&T Samsung Galaxy Note I717] android4545:
My mms wont work for some reason. Also does anyone know where changelogs for this is?
[AT&T Samsung Galaxy Note I717] ipprof:
Battery life is good--about the same as stock--but nothing spectacular. Started the day at 7:30 with 100% and the phone turned itself off at 5:30. So 10 hours is what I get on a charge with average use, meaning BT to music for a while, several photos, emailing the photos, and receiving about 100 emails and responding to 20 or 30 of them, and about a half hour of phone calls.
[AT&T Samsung Galaxy Note I717] Ouroboross:
Oh gee, why would they do such a thing! Thanks for pointing this out.

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

You are lucky. I think GPS is eating the battery quite a bit. It could be the screen too. I gotta turn off the sliding status bar to change brightness to test further. My battery is down 50% by 11a when using GPS for an hour. I unplug my phone at 9am.
[AT&T Samsung Galaxy Note I717] ipprof:
If you want a bit of diversion, tap several times on android version. Then if you tap and fool around with that big red object even more unexpected things happen...
[AT&T Samsung Galaxy Note I717] Ouroboross:
Thanks! That fixes it.
[AT&T Samsung Galaxy Note I717] Jmelendez1:
Holy cow, major nightly update on the way! Fingers crossed for this motherload!

Edit: To the Cyanogen team... Thank you
[AT&T Samsung Galaxy Note I717] ramharder:
Was wondering where you get your info looked around and couldn't find any on a nightly tonight
[AT&T Samsung Galaxy Note I717] Jmelendez1:
Nightly is still in the kitchen.

http://review.cyanogenmod.org
[AT&T Samsung Galaxy Note I717] LuckyStrike88:
Does anyone know anything about editing vold.fstab in order to swap memories basically where the real ext sd card shows up as internal storage?

I'm very interested in this.
[AT&T Samsung Galaxy Note I717] andersco:
google music issue?

Do people still have the issue with google music that you have to start it, kill it, then start it again to make it work? Or is there some manual fix for that?
[AT&T Samsung Galaxy Note I717] paleh0rse:
Change these two lines in build.prop to match the following:

lpa.decode=false

lpa.use-stagefright=false

save, reboot.
[AT&T Samsung Galaxy Note I717] andersco:
That fixed it thanks!
[AT&T Samsung Galaxy Note I717] MechaGen:
Better yet, make a file called "local.prop" with the same things you would put in or edit in build.prop, and put that in "data/". That way you don't have to edit build.prop every time you flash.
[AT&T Samsung Galaxy Note I717] jlpatte2:
Audio dock still broken in RC1

Josh
[AT&T Samsung Galaxy Note I717] ipprof:
BT toggle STILL broken. I was wrong about 5/7. It worked until today. I don't know what they're doing with this build.
[AT&T Samsung Galaxy Note I717] khaytsus:
Hmff, screens are still broken on the RC, just flashed it today. Apps which don't show full screen (expanded? I forget the term..) are all screwy. GScript is one. I'll look in Jira.

And BT Tether is still broken. Wifi Tether seems okay so far.
[AT&T Samsung Galaxy Note I717] srpanadero:
Went back to M3 after trying with RC1 for a couple of days. Instability with some camera apps (Evernote, MD scanner) and VOIP (Csipsimple).
[AT&T Samsung Galaxy Note I717] jwhitney83:
I am having the same problem, on the lock screen. and some apps, going back to build 420 < works great for me.
[AT&T Samsung Galaxy Note I717] briand.mooreg:
Random reboots after a couple of days of use. Uninstalling until next build.
[AT&T Samsung Galaxy Note I717] khaytsus:
Anyone that cares about BT Tether, can you vote on this issue? It seems to cover various devices, so seems like an overall CM10.1 issue. No need to comment, just create an account and vote on it. https://jira.cyanogenmod.org/browse/CYAN-96

And I think this should cover our screen corruption issues, but not sure at this point, might eventually need to log a new bug. This one I would suggest adding more information to, and of course, vote on. https://jira.cyanogenmod.org/browse/CYAN-1057

EDIT: Updated URL, I (like the reporter) thought if you didn't click "I read" they'd ignore the thing and she logged a new one, but they closed the second one.
[AT&T Samsung Galaxy Note I717] TheHamPimp:
Remember to submit your bugs to Jira. CM Google+ page is practically begging for them, since users are simply submitting them on forums and not logging in Jira with log attachments.
[AT&T Samsung Galaxy Note I717] Frankenbiker:
Indeed. I got the serious impression that they released the RC level for the specific reason to get good logs, not because it was considered stable enough for a true RC build level.

-blaine
[AT&T Samsung Galaxy Note I717] khaytsus:
I updated the URL for the graphics bug guys, if you haven't, vote/comment on the graphics bug.

https://jira.cyanogenmod.org/browse/CYAN-1057

If you guys have any new information to add especially, apps that reproduce it 100% etc, that'd great. Probably no need to comment on just a "me too", just vote.

Hopefully they'll figure the issue out and resolve it soon. I'd have to suspect it's kernel, but I dunno. Anyone else using a CM10.1 of the last week or so and a third party kernel that can comment?

I've only seen it myself on GScript, which is not full screen, I saw it on another app but I can't remember which it was. I just grunted and restored back to 0422 when I saw it happening on the second app.

WallSwitch, another older app, is doing it. So I wonder if older apps that didn't support GPU rendering are the problem? Piano Perfect is making my screen flicker like crazy, but that's a different issue I think.

Interesting, Speed Test isn't full screen, and it looks okay.
[AT&T Samsung Galaxy Note I717] ipprof:
I had the problem with several apps and decided to live with it (for me the broken BT toggle was more annoying) but then I saw the post a few above yours, checked off the overlays, and it solved the problem completely. I'm sure I must lose something by checking that off but it's not apparent exactly what.
[AT&T Samsung Galaxy Note I717] khaytsus:
Yeah, it's a workaround. I think I've read it slows some things down, and it'll reset itself every reboot.

Basically Android, like most OSes really, maintain several layers of screens to speed up transitions between them, backgrounds so they don't have to be redrawn, etc. I think that option disables it.

So far there's no app that's really critical to me. I use GScript to toggle root rw sometimes, but I can type it about as fast as I can go into gscript, so not too big a deal.
[AT&T Samsung Galaxy Note I717] ipprof:
I also don't know how to submit a bug report. Any advice?
[AT&T Samsung Galaxy Note I717] khaytsus:
Hmm? Not sure how you wouldn't know how to submit a bug report. But..

The wiki has info, which of course I found after I typed all of the below, so I'm leaving it...

http://wiki.cyanogenmod.org/w/Howto:_Use_the_Issue_Tracker

Search for issues... go to URL, under the Issues tab (click the down arrow) select Search for Issues top-right corner type in a seach query, like "bluetooth"

https://jira.cyanogenmod.org/secure/Dashboard.jspa

Look through the issues. If you find one that matches yours close enough, vote on it, and if your device isn't listed, add a comment that describes your behavior. Don't do this if the bug is "sorta close", only if you're really sure it's the same issue.

If you can't find an existing issue..

Same URL above, click the down-arrow besides Issues, click Create an Issue. Follow the instructions to the T. If you don't, your issue might just be closed/ignored. Part of those instructions are ensuring you're using an official M, RC, or Stable build and can reproduce the issue after a factory reset. So nandroid and verify that first. And pay attention to all of the fields. Add logcats, etc. Feel free to redact GPS coordinates etc in the logcat, but otherwise don't truncate it or anything.
[AT&T Samsung Galaxy Note I717] nstuber3956:
I'm using the rc1. Build and it seems to be fine with the exception of one of the games I have. It only has problems intermittently so idk if it's the same issue or just an issue with the app itself.
[AT&T Samsung Galaxy Note I717] khaytsus:
Hmm, some guy named "Steve" seems to be looking into the graphics glitchy bugs. Cool.
[AT&T Samsung Galaxy Note I717] marcelomanzo:
RC2 is available.
[AT&T Samsung Galaxy Note I717] nstuber3956:
Screen issue is still present though.
[AT&T Samsung Galaxy Note I717] ipprof:
"Ethan" is looking into the BT toggle issue.
[AT&T Samsung Galaxy Note I717] dezrik:
I updated to RC2 last night and my screen is very glitchy, looks like a GPU issue. Only happens when I push the power button to wake up the phone.

Edit: Oops I see its being worked on. Should of read the last few pages!
[AT&T Samsung Galaxy Note I717] nstuber3956:
Also the captive buttons do not light up on notifications anymore. I know this is minor but I really liked that since we don't have a notification light.
[AT&T Samsung Galaxy Note I717] ZacksBuilds:
How is the RC1 Build?
[AT&T Samsung Galaxy Note I717] rohankb:
It's been gone since probably the start of May, thought it was only me. I tried turning off and on in settings like in the past but no difference...
[AT&T Samsung Galaxy Note I717] nstuber3956:
Yeah I guess when I updated to the rc1 build I didn't notice that they didn't light up anymore. I hope they bring it back or someone can do something to get it working again.
[AT&T Samsung Galaxy Note I717] khaytsus:
I don't use BLN because of the awful wakelocks, but I bet the new kernel dropped the support. Accidentally or no.
[AT&T Samsung Galaxy Note I717] rohankb:
That was months ago, as far as I can remember.
[AT&T Samsung Galaxy Note I717] khaytsus:
Recent comment by Steve about the graphics glitches..

:cool:
[AT&T Samsung Galaxy Note I717] TheHamPimp:
If it's Steve Kondik, we're in good shape....
[AT&T Samsung Galaxy Note I717] khaytsus:
Of course it is ;)
[AT&T Samsung Galaxy Note I717] andersco:
I tried this but it isn't working. Do you mean the data directory in root? The file should just have those two lines it right?

Referring to the fix for google music
[AT&T Samsung Galaxy Note I717] MechaGen:
Yes, root/data/local.prop

This technique has been working on several different devices of mine. The tablet I'm on right now has the screen density changed with "qemu.sf.lcd_density=300". You might want to check your code, typos kill.
[AT&T Samsung Galaxy Note I717] ipprof:
Would something added to that permanently disable hw overlays?
[AT&T Samsung Galaxy Note I717] jlpatte2:
Despite a very promising sounding change log commit, dock audio is still broken on 5/13 nightly :(

Josh
[AT&T Samsung Galaxy Note I717] ipprof:
Would something like this work to permanently disable HW overlays?
[AT&T Samsung Galaxy Note I717] TheHamPimp:
Snag some logs and report it:)
[AT&T Samsung Galaxy Note I717] jlpatte2:
Good point, done! If anyone is interested, it is a long standing issue, CYAN-40 in the Jira bug tracker.

Josh
[AT&T Samsung Galaxy Note I717] ipprof:
IT PAYS TO SUBMIT LOGS

On Thursday I sent a cat log to JIRA about the BT toggle. The guy in charge (Ethan) immediately changed the description from something like BT doesn't enable once first enabled to something completely different having to do with wakelocks not releasing. Without the log I guess it wasn't apparent. By the next day, Friday, Cyanogen(Steve Kondik) had chimed in, and by today's build, the issue has been fixed. And probably BT will function better, but that's only a guess. So use those catlogs!
[AT&T Samsung Galaxy Note I717] ipprof:
Well, enough for optimism. It lasted through 5/14's fix but 5/15 broke it. BT toggle doesn't work any more and I assume it's because of some wakelock malfunction that had been repaired but no longer.
[AT&T Samsung Galaxy Note I717] TheHamPimp:
My screen artifacts like crazy on 5/15. Not sure if that was happening in prior versions, but I just upgraded from 4/16. I think I'll roll back, as I think my issue is the same as CYAN-1057.
[AT&T Samsung Galaxy Note I717] ipprof:
It's possible BT toggle isn't broken.It may have been an artifact....
[AT&T Samsung Galaxy Note I717] smo1970:
BT toggle works in the 5-16 release. No BT tethering, but otherwise things seem pretty solid so far. Will know more after using it for a bit of course.
[AT&T Samsung Galaxy Note I717] ipprof:
I find that only partially true. I find that the toggle in the pull down notifications breaks BT when used more than once or twice. But if you stick to the system setting it seems to work consistently
[AT&T Samsung Galaxy Note I717] ipprof:
The latest nightly has a lot of PIE stuff including a "New way of activation"and a"pie delivery service." Does anybody know what the hell is going on? I put it on my power menu so I can get another percent or so of screen area but there's got to be more to it than that. If it's only for gamers, ignore this.
[AT&T Samsung Galaxy Note I717] nethead72:
I confirmed that using most third party or non built in bluetooth toggles breaks the toggle in the 5/16 nightly. Any recommend a good logcat app? The switches in the HD Widgets app seem to function normally...
[AT&T Samsung Galaxy Note I717] khaytsus:
CatLog works in ICS/JB, alogcat doesn't seem to.

https://play.google.com/store/apps/details?id=com.nolanlawson.logcat
[AT&T Samsung Galaxy Note I717] ipprof:
I just use the terminal emulator and enter the following string :

su

logcat -d -f /sd card/logcat.log *:V

I think I've parsed that right.
[AT&T Samsung Galaxy Note I717] TheHamPimp:
Good info, but remember: You can only submit bugs based on RC and official releases. If you submit one for the nightly, it will instantly be closed as 'invalid'.
[AT&T Samsung Galaxy Note I717] GRIM.657:
Has the feature to flash HW button lights upon notification been removed? It still turns the lights on when I press a button/use the screen, but not when I get a notification, and for the life of me I can't find the option in settings anywhere.

edit: I just found the option in Advanced Settings (what's it doing in there?) and it was already enabled. Toggling it makes no difference.
[AT&T Samsung Galaxy Note I717] rohankb:
BLN has been off since the start of May it seems. Brought this up earlier in the thread. They think it was turned off because it was causing crashes upon wakeup. Who knows...
[AT&T Samsung Galaxy Note I717] ImSteevin:
I'm still hanging out on RC2, have any of the lag issues been resolved on the current nightlies?
[AT&T Samsung Galaxy Note I717] ipprof:
Today's nightly must rank with the very worst builds in cm history. Crashes, spontaneous reboots, freezes, sluggish. For the first time in my cm experience I'm going back to the previous build. I'm kinda shocked.
[AT&T Samsung Galaxy Note I717] jlpatte2:
Are you talking the 19th or 20th?
[AT&T Samsung Galaxy Note I717] ipprof:
19th. I just loaded 20th and so far it seems more friendly.
[AT&T Samsung Galaxy Note I717] nethead72:
testing on several versions including N-4/19,4/22,5/02,5/12,5/16 has shown that reformatting my dalvik fixes all bluetooth problems, including broken connectivity and toggles, both system and third party, such as widgets, which i encounter every couple of days. what cause the problem is unknown, but at least i know where it is located now. anyone else done this?
[AT&T Samsung Galaxy Note I717] ipprof:
Reformatting is different from wiping. I have no idea how to reformat Dalvik. I do wipe Dalvik and reformat cache but I have had BT problems (although far less with recent builds)
[AT&T Samsung Galaxy Note I717] xda1zero:
You guys notice the commit for the 21st build, random reboots might be fixed :)
[AT&T Samsung Galaxy Note I717] INeFFeCTiVE:
I'm pretty sure that TWRP reformats by default when you do a wipe, in fact you have to choose to do a rm -f of a partition instead of a format in settings. :D
[AT&T Samsung Galaxy Note I717] ipprof:
Well in that case I've been doing it with every build with no obvious improvement (although if I use BT only from settings it usually, not always, toggle nicely)
[AT&T Samsung Galaxy Note I717] nethead72:
Use TWRP 2.5 to wipe dalvik with rm - rf (i believe this is the right tag, there is an option to set this mode in advanced settings) to rebuild file tree and formatting. normally this is used to repair issues with internal sd. apparently it did sometime to my dalvik partition, sorry, i cannot be more precise than that, as i am not completely familiar with how the android system arts up is partitions and how twrp interacts within it. i stumbled upon this effect inadvertently while trying to get internal sd to mount.
[AT&T Samsung Galaxy Note I717] jlpatte2:
Pie controls? So I disabled my capacitive keys, enabled the soft navigation keys, enabled pie and the switched to expanded desktop, but no pie menus... Am I doing something wrong, or is something necessary for pie just not compiled in for our device?
[AT&T Samsung Galaxy Note I717] ipprof:
Des
[AT&T Samsung Galaxy Note I717] nethead72:
it does not remove the problem only corrects the symptoms. you still must not use the bluetooth toggles on the pull down menu. use the system settings or use HD Widgets.
[AT&T Samsung Galaxy Note I717] esokolov:
USB Mass Storage is gone???

Folks,

When I tried early nightlies, there was USB mass storage access to both emmc and SD card.

Then I was with SoA, then tried stock JB (ugh), then flashed 10.1 RC2... Same random reboots, BT is going off, and in addition NO USB MASS STORAGE!!! It's only giving me the choice of MTP and PTP.

I've just applied the last nightly, just in case, nothing.

I've honestly googled the Internet and searched this thread... nothing. Any idea?
[AT&T Samsung Galaxy Note I717] VannMann:
What is the last nightly that doesn't have the reboot problem?
[AT&T Samsung Galaxy Note I717] Shagerty:
I want this info as well. Please share community.
[AT&T Samsung Galaxy Note I717] srpanadero:
USB Mass Storage was removed in, I believe RC1. I can't see that changelog now, it has dropped off of the nightly logs page, but I recall reading it. A comment said something like "...After the new kernel, we can revisit it..." Here is a link also that mentions that it is deprecated.
[AT&T Samsung Galaxy Note I717] khaytsus:
Graphical problem must run deep, they've been working on it for over a week now.
[AT&T Samsung Galaxy Note I717] ipprof:
It seems to be deeper than those trying to solve it. I've never seen a nightly problem like this. It seems they're understaffed on this project.
[AT&T Samsung Galaxy Note I717] imb951:
What OC kernels are you guys using now with the latest nightlies?

I was using Flapjaxxx's kernel (h0tcakez-JB-4.2.2-Kernel-v3.0.9) for a while but on the latest nightly it wont boot after flashing that kernel.
[AT&T Samsung Galaxy Note I717] jlpatte2:
I'm pretty sure there are no oc kernels available at the moment for cm.

Also noticed something weird I think there is almost always a new superuser binary ready for install after my random reboots...

Josh
[AT&T Samsung Galaxy Note I717] ipprof:
I wish I knew what that means!
[AT&T Samsung Galaxy Note I717] khaytsus:
....what? how is there a new superuser binary, it's built into the ROM now?
[AT&T Samsung Galaxy Note I717] xda1zero:
for a couple of months at least

[/COLOR]

just curious but did you do a format of the internal sdcard+ data + cache?
[AT&T Samsung Galaxy Note I717] ipprof:
I'm really not sure. Usually I just wipe cache and Dalvik cache multiple times. What is it exactly you are suggesting and won't I lose my data if I do that?
[AT&T Samsung Galaxy Note I717] xda1zero:
yes that will empty out all your data.

if mine starts acting goofy when flashing a new nightly ive noticed clearing all residual information from previous installs will sometimes stabilize it.
[AT&T Samsung Galaxy Note I717] imb951:
Major bummer!
[AT&T Samsung Galaxy Note I717] :
Flappjaxx kernels are OC'able AFAIK.
[AT&T Samsung Galaxy Note I717] jlpatte2:
Unless I missed something he hasn't updated since the kernel change in early may so his older work is incompatible and he claimed he is done developing for at least note if not Android period..

Josh
[AT&T Samsung Galaxy Note I717] imb951:
That's correct. Flapjaxxx's OC kernels up through the 3.1.2 no longer work, won't boot.
[AT&T Samsung Galaxy Note I717] srpanadero:
Possibly so is Samsung. https://jira.cyanogenmod.org/plugins/servlet/mobile#issue/CYAN-1057

That is the link to the bug. Steve Kondik is the one working on it. If you read the thread, you can see that it is happening on all Qualcomm devices, including on the S4 with the stock rom. Also is mentioned that it is completely fixed by disabling hardware overlays.

Since it is fixable, that doesn't trouble me as much as random reboots and general instability. There are bug reports for those, but no progress so far. Might need more votes from users. So maybe sign up and vote for an open issue?
[AT&T Samsung Galaxy Note I717] imb951:
getting random reboots on the 5/21 nightly. going back to my old build with working Flapjaxxx OC kernel...:(
[AT&T Samsung Galaxy Note I717] marcelomanzo:
We need more votes!!!

https://jira.cyanogenmod.org/browse/CYAN-1057