yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] dbolivar:
Hmm really strange it's not happening on your N8013; AFAIK the devices should be the same, but perhaps there's a hidden hardware difference we are finding now? Anyway, what I did:

Using PhilZ Touch 6.00.8, made a full wipe twice, installed normally, before reboot also flashed latest PA Gapps 4.4 (20131215). Rooted flashing UPDATE-SuperSu-1.86.zip directly from Chainfire's website (latest). That's it, I messed a little bit with the DSP Manager but only after the problem had already happened.

Do you think the Gapps could be the reason? It's the only thing that might be different from your installation (which one are you using?). Also, did you do a full wipe before flashing this new version?
[Galaxy Note 10.1 Android Development] iofthestorm:
Well, I generally don't do data wipes because I flash different builds way too often for that, and I am using the same gapps version. Hmm... But you're saying in your case the problem only occurs on headphones, not speakers?
[Galaxy Note 10.1 Android Development] dbolivar:
Exactly, only on headphones. I did some more testing: full wipe, flash version 20131215, flash version 20131225 without wiping, flash Gapps, flash SuperSu. No go.

To reproduce the issue exactly, do the following: open Google Play Music; play some music; pause it; wait about 10 seconds; IMPORTANT: switch to the home screen or another app; go back to Google Play Music, and resume playing.

I noticed that if you pause / play while Play Music is on the foreground, the problem doesn't happen, only when Play Music (or whatever other thing that is playing sound) goes to the background, you pause / stop, wait a while and try to resume playing.

---------- Post added at 08:13 PM ---------- Previous post was at 07:48 PM ----------

If it helps, analyzing logcat, I found that when the sound is output correctly to the headphones, I see this message:

D/audio_hw_primary( 1833): select_output_device: AUDIO_DEVICE_OUT_WIRED_HEADPHONE

However, when I reproduce the scenario to break it, on resuming playback, I don't see this message.
[Galaxy Note 10.1 Android Development] ©h®is:
thank you

just tell me if you need another log.. or testings..

restored my backup a while, but i can flash tomorrow again
[Galaxy Note 10.1 Android Development] *d1000:
No changes made in DSP Manager but as previously mentioned as far as I can recall every custom ROM has this issue for my 8010. Please let me know if I can assist in anyway.
[Galaxy Note 10.1 Android Development] xsoullz:
I have test with n8000 model with the last update [omni-4.4.2-20131225-n8000-HOMEMADE.zip] and i have 2 problems

1. No sound, all sound function not work no calling sound, touch sound, and music.

2. Problem with screen, when the tablet turn off the screen and i push the power button to wake it up the screen turning from dark to white all the screen with no ui, is that problem with my tablet or somebody has the same problem with me.
[Galaxy Note 10.1 Android Development] marco9333:
Hi,

I've already downloaded part of your sources and all of the cm10.2(more than 20 gb :eek:), maybe I can help with the n8000 after the holidays.

I was already looking at the sound config because mic headset wasn't working (I've fixed it in app but not in callings). I think the config in tiny_hw in n80xx-common is from s4, you can find information about FM radio audio routing and so on(????). Maybe something is wrong there.
[Galaxy Note 10.1 Android Development] dvux:
Is the flickering problem solved now?

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Galaxy Note 10.1 Android Development] dbodom:
I'm running the 120913 release on my n8013 and have the white screen problem also. Sometimes a few cycles of the power button brings my screen back but sometimes, I have to reboot. I've seen this on the 1204 version also so it appears that whatever this bug is, its still in the 1225 release.

I'll be installing the 1225 today to check it out.
[Galaxy Note 10.1 Android Development] iofthestorm:
White screen and flickering problems are still present. Haven't been able to figure out where it's coming from :(. For me it happens randomly and hasn't been happening recently though so it's hard to debug.
[Galaxy Note 10.1 Android Development] tsukaza:
Successfully dirty flash over the previous 4.4.2.1 ROM and so far so good, thanks.

Since I use regular speakers and BT headset, I have not experienced any sound issue.
[Galaxy Note 10.1 Android Development] tabtxk:
I tried to reproduce that on my 8010, but sound is working without problems for me. I just tried apollo, youtube and the total commander built-in player. I paused for a few seconds up to a few hours (sleep), switched to homescreen, ran different apps while pausing, no problems.

I'm using very core gapps and at the moment just the aosp launcher which is working since second or third build :) ... and did a full wipe.

First time I tried apollo i had the white screen bug. when turning the screen back on, it went from bright with structure to full white. had to reboot with power button, after that it was gone. I kind of suspect (not based on knowledge) it had something to do with apollo setting the albumcover as lockscreen-background. Never had the white screen before or after. one time (3-4 weeks ago?) i had the flickering starting in the corners then filling the whole display right after flashing, which was persistent in recovery and only went away after restoring some backups...that also happened just one time.
[Galaxy Note 10.1 Android Development] jaxxes:
I apologize in advance if this issue has been addressed, but I don't recall it in any of the thread.

I just installed the 122513 version last night, coming from hyperdrive 7, Samsung 4.1.2 ROM. Had to upgrade my recovery, now using Philz (1130 update I believe). Clean wiped for a new ROM. Anyway, installed fine and what little I've tested works really well. Awesome job!

The issue I'm having is that my data partition does not seem to be mounting correctly. I can see everything is there under Philz and the system registers the correct amount of free space under system --> storage, but the 5 GB is unaccounted for. Browsing either through system storage or through es file explorer I only see a set of empty directories from what looks like a newly created data partition. Either way, I can't get at my old data and not quite sure where to go from here. Any advice would be appreciated.

In the meantime, awesome job and thank you so much for your hard work!

Edit: Ack! Just saw someone else with the same mount point issue a few posts back! Where do I fix that?
[Galaxy Note 10.1 Android Development] mrcrassic:
I've been using this ROM for the last few weeks and it has been incredibly smooth! Thanks for bring KitKat to our N8013s!
[Galaxy Note 10.1 Android Development] dbodom:
Just installed the 1225 release on my n8013. Did a dirty flash using Philz recovery BUT did wipe Dalvik since I'm using ART and wanted it to precompile my apps again. After the initial 10 minute boot for pre-compilation, everything looks good. Sound works fine on the n8013. I suspect I will still have the white out issue sometimes, but it hasn't happened yet.

I love the speed of this ROM and the bragging rights of using 4.4.2.

Update: Still notice the flickering on certain apps. We need to figure this screen issue out, if possible.
[Galaxy Note 10.1 Android Development] dimqs153:
Once it happen to me when I first flashed cm rom on my note, just check to one of hidden folder ( .old folder if im correct ). I use es file explorer to see hidden folder, jist enable it first
[Galaxy Note 10.1 Android Development] jaxxes:
Thanks! Seems like a dumb fix I should have been able to find over Google. Took me way too long to find out the mount points were in the init.smdk4x12.rc file in the root directory rather than in the system/vold.fstab. Even then, their set to the correct directories (data/media) rather than the ones that are coming up as the sdcard (data/media/0). Tried just moving the contents over to the 0 directory but doesn't want to do that, even with root access in es file explorer. Also tried setting selinux to permissive in case that was interfering, but no go. Still something with the permissions? I'm pretty lousy figuring those out, admittedly.

Otherwise, saw the screen flickering/burning issue mentioned by so many others as well. Went away disabling auto brightness? Or maybe I just have the brightness set so low it's less of an issue? Just thought I would mention. And thanks again!
[Galaxy Note 10.1 Android Development] iofthestorm:
I'm actually going to be away for a few days, and I don't have my tablet with me, but one thing I've wanted to try is reverting to the older Mali (GPU) drivers. The issue is that since we share a kernel with the other smdk4x12 devices (i9300, Note 2, etc) I don't know if this is something that could be a permanent fix but I am still curious to see if the older drivers fix the screen issues. If I get some free time I might try and revert back to the old drivers and put out a test build for you guys.

Thus far there seems to be no reliable way to make it go away when it happens, so I wouldn't bother wiping data or cache or restoring backups or whatever, just power down for a while and it should go away on its own.

I do wonder if it has something to do with auto brightness or content adaptive backlight but at the least I think I've had it happen with a fixed brightness. Hopefully over time we can figure out what conditions trigger the bug by just gathering experiences, but for now I haven't been able to find anything that appears promising in the logs.
[Galaxy Note 10.1 Android Development] golcheck:
I got exactly the same problem with sound. Nothing at all. When I try to play a song I got "unfortunately dsp manager has stopped"

Also, I keep Settings app in dock. Each time I do a reboot this app disappears from dock. All other apps stay there...weird
[Galaxy Note 10.1 Android Development] planetf1:
Loving the ROM generally. Very smooth

I too though cannot get any sound from play music, iPlayer, YouTube, deck etc.. I get DSP manager has stopped too. Even straight after boot. Occurs with both dalvik and art.

Great work tho!

I'm installing on a n8010 which due to an hiccup months ago thinks its a n8000....
[Galaxy Note 10.1 Android Development] planetf1:
Ah I also now have seen the whiteout issue
[Galaxy Note 10.1 Android Development] dbodom:
Here's something to try to stop the flickering screen. Go into Dev Tools, Developers Options and check Disable HW Overlays. I found this out reading through a few OmniROM forums. See if it helps.

I need to test it a little while longer but it seems to be helping my screen flicker issue. No idea if it helps with the white screen problem.
[Galaxy Note 10.1 Android Development] Kidromulous:
white screen

Forgive me if this is something that has been discussed at length but I'm new to the device. I love this ROM but I'm having an issue where on wake I get a white screen. Sometimes I have to reboot the device to get it to wake at all. I don't have the flickering issue during normal use that some are reporting. Other than that it's a great ROM.
[Galaxy Note 10.1 Android Development] dbodom:
The white screen issue is affecting some of us. It happens to me also. The OP is working on it. A pain, for sure, but not a show stopper for me.
[Galaxy Note 10.1 Android Development] Kidromulous:
Certainly not a show stopper this ROM is fantastic thanks for the reply,
[Galaxy Note 10.1 Android Development] iofthestorm:
In my experience disabling hw overlays did not help with white screen/persistence or flickering, but I still basically have no idea what causes it so it's hard to say.

I think if you install the proper recovery for your tablet it should recognize itself as the right model? Or you could try installing PhilZ N8013 recovery and see if you can install the N8013 version and see if that has the issue as well. I think some people here reported that they were able to do this. I'd be really interested in seeing if you can install the N8013 ROM because then it might uncover whether there's an actual hardware difference.

Ugh, I wish I'd brought my tablet with me on this trip, now I'm sitting around bored lol.
[Galaxy Note 10.1 Android Development] jaxxes:
Just a quick update that was eventually able to copy old data out of data/media into data/media/0 and resolve the problem. Perhaps earlier copy issues were just the ROM settling? Either way working great! Absolutely love it! Can say I don't have the sound issues mentioned by others. Thanks again and looking forward to seeing where this goes!
[Galaxy Note 10.1 Android Development] miten_sheth:
Music does not work at all and no sound too.. On the latest one
[Galaxy Note 10.1 Android Development] TrOjAnUK:
? Really... I have the 8013 flashed on my 8010 and everything is working as it should...

TrOjAn
[Galaxy Note 10.1 Android Development] planetf1:
Interesting.

Months ago I somehow installed a n8000 recovery onto my n8010... And since then just used n8000 ROMs. Apart from reporting mmo signal I noticed no issues. Yesterday I tried to install philz n8010 recovery but due to a bad download link went with the n8000 instead.

I just went to replace my n8000 omnirom but of course it failed due to model number, so next plan when at pc in an hour or so is to try philz 8013 recovery then omnirom to see if there are differences

I am really liking 4.4 on the tablet....
[Galaxy Note 10.1 Android Development] planetf1:
OK. I used the N8013 ROM on my N8010, instead of the N8000 rom I previously tried (flashed philz n8013 recovery first)

SOUND IS WORKING!!!!

BRILLIANT!
[Galaxy Note 10.1 Android Development] planetf1:
Any suggestions on hiding root with this rom?

I did consider trying the xposed framework, but this is incompatible with ART which I'm playing with :)

Hide my root / hide su binary didn't seem to work - presumably as whilst the rom is pre-rooted, su isn't shipped - in fact as an aside would you recommend superuser or supersu

Ultimately it would be great if I could get "sky go tablet" working but this app is somewhat sneaky in in its root detection so I'm not too hopeful!
[Galaxy Note 10.1 Android Development] iofthestorm:
LOL well if just changing the ROM fixed audio on your tablet then I must have derped somewhere for the N8000 build. I'll take another look at the differences, it must be something silly. Though since I only added stuff to the device tree to build Omni it shouldn't have changed anything hardware specific, but who knows. I might also just do a repo sync and rebuild, though I thought I did both builds at the same time with the same code it's possible that I caught a bad patch for the N8000 and not N8013 builds or something.
[Galaxy Note 10.1 Android Development] planetf1:
I didn't clear data etc nor change any apps so definitely did seem just the ROM switch.

Loving it... Thx
[Galaxy Note 10.1 Android Development] iofthestorm:
Aha, found the sound derp, it's in the build.prop of all things.

If you N8000 folks want to fix it without waiting for a new build, just edit your /system/build.prop and change ro.product.device from "n8000" to "GT-N8000" (note the capitalization, and don't use quotes).

Edit: new build uploaded for N8000, the only change is fixing the build.prop to fix audio - if you're already on it, you can just do the above change if you don't want to download a full ROM.

omni-4.4.2-20131227-n8000-HOMEMADE.zip
[Galaxy Note 10.1 Android Development] ©h®is:
downloading.. :)
[Galaxy Note 10.1 Android Development] sudisk:
Nice one!

If you have time and want to try, could you cherry pick the merges for 9300 about exfat?
[Galaxy Note 10.1 Android Development] ©h®is:
Hmm

Unfortunately not be able to play a sound..

Didn't restore anything

Youtube closes

Also my media on the device..

?

Also device sounds..

(if i change ringtone..)

You need a log?

Mom

My fault..

Wait..

Ok

Downloaded version above and it shows me in settings 1225 omniversion (that the point i was confused..)

Still no sound..

Gesendet von meinem Nexus 4 mit Tapatalk
[Galaxy Note 10.1 Android Development] riggs170:
Thank you so much OP, KitKat for Christmas on my Note 10.1. Let me know if you need help with anything other than testing. I would love to be a part of this; even though it would be more of a learning experience for me. I am only about 2 hours in running on my 8013, no bugs yet to speak of great work.
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh, wait, what? Can you check your build.prop for the values in that post and see what they say? I might have needed to do a clean build which I didn't do :/ should have actually checked the file before uploading. Won't have access to my computer until later tonight so I can't re-upload until then. Just try changing the build.prop and rebooting, that should fix it.
[Galaxy Note 10.1 Android Development] ©h®is:
sorry, bro

just restored backup

have to prepare everything for my son arriving tomorrow..

try it asap..

thx for your work!
[Galaxy Note 10.1 Android Development] iofthestorm:
Ah shoot, it turned out the file I changed didn't get picked up as a change in the build system so the build was exactly the same. I removed the 12/27 build, and then because I'm an idiot and XDA's download manager doesn't ask for confirmation when deleting files I also accidentally deleted the n8013 12/25 build, sorry about that. It's not really a big deal because very little changed in that build for n8013 anyway. For n8000 users please do the build.prop mod for now until I can get at a computer and upload a fresh build. Sorry again for the mix up.
[Galaxy Note 10.1 Android Development] electrikjesus:
I was able to run the 12/25 n8013 build for almost the whole day, but then the ghosting started and got worse and worse to the point where I would get the nasty flickering or the white screen with every reboot. Turning the screen off and on only accelerated the effect to all white too... letting it sit for 30 minutes still had no change, it would come back within minutes. Changing the max screen brightness did prolong the effect, but did not fix the issue. I will be installing this as a dual-boot, this way I could always reboot into a stock kernel and let the flickering stop by itself eventually.

Wish me luck :)
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh hey, that's pretty neat, I'd be very interested to hear your experiences with that. Especially if it fixes your flickering instantly when you switch or if it persists into the stock ROM.
[Galaxy Note 10.1 Android Development] electrikjesus:
So far, the ghosting is still there once I switch over to stock, but it eventually fades off completly, and it doesnt come back as of yet. I will switch back over in a couple hours and see if it comes back and how fast if so.
[Galaxy Note 10.1 Android Development] TheMorpheus:
Nice... Swith to KitKat ASAP!!

Sent from my GT_N8000

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

Are you able to see the ExtSdcard??
[Galaxy Note 10.1 Android Development] sudisk:
I see the extsd from the recovery. Not from the ROM but it should come as soon as the i9300 kernel updates are merged into the main tree.

Another good news [MENTION=3125261]iofthestorm[/MENTION]: I reinstalled the test build and changed all the "n8000" entries in the build.prop file to "GT-N8000". The sound seems to work fine. I could hear GMail notifications and start/stop/resume playback in YouTube without issue. I also tried turning off/on the screen before resuming playback and the sound was still there.

I will remain for the remainder of the evening for more testing. I also did not have any more white screen since the change.

If anyone has an idea of test that I could easily perform, let me know.
[Galaxy Note 10.1 Android Development] planetf1:
Ok something weird just happened.

On the N8013 20131225 build I heard a buzz from my tablet (facebook) so hit the power button to unlock the screen

it was a werd few white stripes, with the background gradually getting brighter, starting to form a matrix -- the classic whiteout issue

I tried pressing power a few times, and this just toggled between blank and whiteout

I then just for fun pressed VOL- and power at same time, the screen returned onto the proper lock screen - no whiteout, all normal

Now this may just have been random but I wanted to mention it....
[Galaxy Note 10.1 Android Development] xxcrashxx:
This works out awesomely on my n8013. Thank you for the port. One issue I have is with the recovery. I have a 64gb microsd card fat32 formatted, but for some reason in CWM 6.0.4.4, it won't access the SD card. only says error when mounting sdcard1. I have also tried Philz recovery, same issue as well. any ideas on what I could try to get it to work??
[Galaxy Note 10.1 Android Development] iofthestorm:
Alright, sorry for the double derp, here's a fresh N8000 build with the proper build.prop changes. Also includes a little kernel patch that was merged recently; it doesn't seem to be relevant to the whiteout issue but you never know.

omni-4.4.2-20131227-n8000-HOMEMADE.zip
[Galaxy Note 10.1 Android Development] dbodom:
I posted earlier that checking Disable HW Overlays could help with flickering but after further research in some other forums they recommend checking both Disable HW Overlays AND Force GPU Rendering. I just set mine and will see if that helps.
[Galaxy Note 10.1 Android Development] TheMorpheus:
Same here, 32 Gb fat32 not recognized! I hope we'll find a solution soon, I don't have much space left in the internal memory :(

Sent from my GT-I9505
[Galaxy Note 10.1 Android Development] jobrv610:
I'm trying to set up a restricted user. Every time I set it up it freezes but if I get past that point I can't get to the home screen. I can pull down the setting menu but that is as far as I can get. Any suggestions?
[Galaxy Note 10.1 Android Development] iofthestorm:
Here's another build for N8013, just to make things even.

omni-4.4.2-20131227-n8013-HOMEMADE.zip

Regarding restricted profiles, I haven't tried that yet, but if you could get a log for that it would help in figuring out what's wrong. Is it a Kitkat feature? I noticed that [MENTION=3031478]humberos[/MENTION] did a device tree for Kitkat yesterday and he added a bunch of SELinux related files that I have not done, so maybe it has something to do with that.
[Galaxy Note 10.1 Android Development] DesignGrits:
Is dirty flash OK from the 20131214 build?
[Galaxy Note 10.1 Android Development] sudisk:
It should, but I suggest that you backup, flash and report.
[Galaxy Note 10.1 Android Development] iofthestorm:
Dirty flashing is always OK unless specifically noted otherwise.
[Galaxy Note 10.1 Android Development] dbodom:
Just dirty flashed the n8013 1227 version and then, for the heck of it, reflashed SuperSU and the latest 1215 PA GAPPS. Using ART so wiped Dalvik cache to recompile. Everything looks fine and the tablet is working great.
[Galaxy Note 10.1 Android Development] Ba7rani123:
Multi-User was added in 4.2

Restricted users was added in Android 4.3

I think thats what he means
[Galaxy Note 10.1 Android Development] MJ-12:
What is up with the flash?

Some times it works fine, but some times it says i don't have flash installed? Its appears to be working now after update :eek:

*** Also the performance controls don't work, the sliders are set at zero and don't move (no doubt because the kernel is not overclockable (is that even a word?))

Still a great ROM :)

Cheers
[Galaxy Note 10.1 Android Development] xlamian:
Same here, I thought it was me :p
[Galaxy Note 10.1 Android Development] riggs170:
My 32 GB card is accessible through es file explorer but every time I copy a file to it, a weird file is created as well. Swipe doesn't seem to be working with the stock keyboard, I am using pa_gapps-modular-mini-4.4.2-20131215-signed.zip.
[Galaxy Note 10.1 Android Development] Kidromulous:
Can someone recommend a stockish rom that's really good for this device? I'm new to this particular tablet and the white screen thing is getting to be a major problem as time goes on. What's the best tweaked touch wiz rom?