yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] iofthestorm:
Known Issues

See bug reports at http://xdaforums.com/devdb/project/?id=1828#bugReporter

Experimental stuff

Multiwindow, to me, is the one of the most exciting features of OmniROM, but it is a work in progress and not completed yet. I will be doing builds with MultiWindow, but currently it does not function well yet - no bug reports on this please, but feel free to discuss it here.

Building instructions

For n801x, the repos are now on omnirom so you can just repo sync the omnirom tree and then brunch n801x. You'll need to cherry pick kernel fixes though.

For n8000, here's my local_manifests.xml

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/n8013" name="ibrahima/android_device_samsung_n8013" remote="github" revision="android-4.4" />
<project path="device/samsung/n8000" name="ibrahima/android_device_samsung_n8000" remote="github" revision="android-4.4" />
<project path="device/samsung/n80xx-common" name="ibrahima/android_device_samsung_n80xx-common" remote="github" revision="android-4.4" />
<project path="vendor/samsung" name="DonkeyCoyote/proprietary_vendor_samsung" remote="github" revision="android-4.4" />
<project name="codeworkx/omniscripts" path="buildscripts" remote="github" revision="android-4.4">
<copyfile dest="build.sh" src="build.sh" />
</project>
</manifest>
[Galaxy Note 10.1 Android Development] iofthestorm:
Changelog

1/6/14 (test, n8013 only): s3cfb drivers updated using i9300 update 12 code, also seems to fix screen issues but build seems laggy - not sure if related.

1/4/14: s3cfb commit reverted, fixes screen issues.

1/3/14: Quicksettings configuration and more tiles merged!

1/2/14: Threw in the towel and rolled back to Mali r3p1 drivers, screen glitches seem to be gone.

1/1/14: Updated libUMP.so, not sure if this has any effect.

12/27/13: Just a build for N8000 to fix audio.

12/25/13: Sorry for the lack of changelog updates, but not that much has changed recently. There are a host of new options in the interface settings, and that's the main difference. Camcorder audio sort of works. First N8000 build.

12/03/13: The big change is that xplodwild is a genius and he got Multiwindow sort of working again on Kitkat. It still crashes a lot of apps but you can try it out at least. Just please don't report any bugs about it to him (can talk about them here if you want).

Some other neat stuff:

Performance Control (in settings) also got a major UI revamp, see https://gerrit.omnirom.org/3067 - Great work Alexander Martinz!

There also appear to be some camera improvements for smdk4412 devices ( https://gerrit.omnirom.org/3052 ) - dunno how much this changes really, since tablet cameras universally suck :P

The "transformer yelling" during unlock while playing music seems to have been fixed! https://gerrit.omnirom.org/#/c/3014/

Option to hide ADB debugging notification: https://gerrit.omnirom.org/2933

11/29/13: First build
[Galaxy Note 10.1 Android Development] iofthestorm:
So this is really weird to have the first bug report be yourself, but has anyone experienced something like this? All of a sudden I'm getting image persistence in the corners of my screen (eg. clock shows up in recovery) as well as fading around the edges (I was like woah, Google Launcher fades the edges now too? Wait a minute...). I've had an issue where my LCD cable was loose before and it resulted in weird artifacts until I opened up my tablet and reinserted the cable, but I'm wondering if this is caused by the same thing or if it's something I've done wrong with the ROM. It even shows up in recovery and at boot time. And now my screen is flickering like crazy (in everything, ROM or recovery). I've been running this build for about a day though so if it's more than just a hardware issue on my tablet it probably won't show up instantly. I'm 90% sure it's because of my loose cable thing but just as a fair warning to anyone else...

https://www.dropbox.com/sc/vw8o98coistu63w/jlQOpGrlcY
[Galaxy Note 10.1 Android Development] chappatti:
Any progress? Is this safe enough to try??:)
[Galaxy Note 10.1 Android Development] iofthestorm:
Hah dude, I just posted that 5 minutes ago... anyway, I have a project to work on for school and finals to study for so I unfortunately cannot spend much more time than I already have on this for a few weeks (I really already spent too much time today setting up this thread and stuff). I really don't think this is an issue of the ROM but rather just my tablet because I've had a history of weird screen issues (I really should have RMAed it when it started happening but i started to depend on it heavily for school/research work). I personally think it should be safe to flash, no different from any other ROM since it uses more or less the same device code/blobs, but I don't really know since it's kind of coincidental that this happened to me today. I'd appreciate it if people would try it out and report back if they see this happen. FWIW the persistence/burn in went away but my screen was still flickering after I powered it down for a while, so I'm just going to shut it down for tonight and see what it's like tomorrow.
[Galaxy Note 10.1 Android Development] theatomizer90:
Can we get some pics or a video? My eyes must behold this rom!
[Galaxy Note 10.1 Android Development] iofthestorm:
I've been trying to upload screenshots to the screenshots page but for some reason XDA keeps eating them. I'm trying to use all the features of DevDB rather than put everything in the OP so that it's more organized[1]

I'll try again later, but for now there's just a screenshot of the settings app which shows the glorious Android 4.4 label. I don't know why it's not showing the other files I uploaded.

Just FYI, my screen persistence/burn in and flickering issue went away. One thing that I forgot is that OmniROM is using newer Mali (GPU) drivers than CM10 was (and I think CM11 as well, since most of the experienced Exynos guys jumped ship to Omni) for Exynos 4412 devices. So there's a small chance that that's related, but most likely it's just the screen issues that my specific unit has had since a few months after I got it.

[1] On that note, I'd really appreciate it if you guys could use the bug reports feature when reporting bugs, it seems much more organized than having bug reports scattered through a thread. We can keep the thread for general discussion and perhaps developer talk, and the bug tracker will make it easier for people to find bugs at a glance.

Oh, derp! XDA limits PNG files to a maximum of 256KB, which is too small for any screenshots except for the settings screen which is mostly black and white. Here's a temporary solution I suppose, I'll just stick them on my Dropbox for now: https://www.dropbox.com/sh/2qkn7aj9g8l1y3l/zf8uH4lb8O

There's not a whole lot new here yet to be honest, Omni is mostly just getting started and some of the innovations have been more phone oriented. But you can see the cool Kitkat features such as transparent status and navbars, as well as the immersive mode/swipe down to show notification bar feature (which is supported in MX Player, pretty neat). And the launcher pictured is the Google Experience Launcher so you get your Google Now on the leftmost homescreen which is neat. Though I prefer Action Launcher Pro anyway so it doesn't really matter to me.
[Galaxy Note 10.1 Android Development] dvijetrecine:
that screen "issues" you are talking about... yeah, i have that too. locked tablet, and on unlock, whole screen goes white. restarted it and everything is fine. for now.

only bug i found is only half visible clock in expanded notification bar. a little annoying.
[Galaxy Note 10.1 Android Development] kstephens98:
Awesome! Thanks for bringing 4.4 to 8013!
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh, did the screen issue happen after flashing the ROM or is that something that happened on your tablet before too?

Yeah, the clock thing is really weird and annoying, not sure why it happens. I think there aren't that many tablet users of Omni so some stuff may just be broken on some tablet layouts. I'll look into it in a few days.
[Galaxy Note 10.1 Android Development] dvijetrecine:
yup, after flashing rom (which is awesome by the way, i'm looking forward for your new updates)... but, for now after that one reboot i haven't experienced any screen issues

oh, and for clock... it dissapeared completely and now i have an empty space which is better because that half clock was useless. so yeah, if you implement tablet mode it will be perfect for me
[Galaxy Note 10.1 Android Development] theatomizer90:
Is the recovery that you have on this thread just the latest TWRP? also an app that works well flashing the recovery (after an hour of trying to flash the recovery img is recovery tools. here is the link, it will save alot of time.

https://play.google.com/store/apps/details?id=de.mkrtchyan.recoverytools&hl=en
[Galaxy Note 10.1 Android Development] :
Looks like I'm able to flash using cwm 6.0.4.4. :) I used flashify to update my cwm.

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

Edit:

Here is a link to the version of cwm that I used: http://d-h.st/ljE

Flash this recovery with Flashify (for root version): https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=en

Great work [MENTION=3125261]iofthestorm[/MENTION] !

---------- Post added at 06:34 PM ---------- Previous post was at 05:58 PM ----------

Interesting. I was having issues playing Netflix--I had sound but no video. This xposed module for cm10.1 fixed it for me.

I have no idea why it works. I just remembered having to do that for cm10.1, so I tried it.

http://xdaforums.com/showthread.php?t=2101525
[Galaxy Note 10.1 Android Development] iofthestorm:
Hmm, that's kind of worrying. Well, your issue is different from mine so maybe it's not a big deal but if these issues persist I may have to pull my builds for a while until someone with more knowledge like Entropy512 can look at my work. I don't want to cause problems if there is even a small chance of it.
[Galaxy Note 10.1 Android Development] iofthestorm:
Yes, it's just the latest TWRP built from source. When I started working on this at least the one for our device was not up to date, I haven't checked to see if they've posted a newer one. I imagine since Dees_Troy is an Omni developer eventually we might get an official update. I'm guessing it's just hard for him since he's managing so many devices to keep track of them all.

As I mentioned in the OP, this recovery might not work completely, so if you have issues going back to a different ROM you might need to flash a different one using Odin.
[Galaxy Note 10.1 Android Development] theatomizer90:
For Netflix I just flashed the zip that was done rather than the xposed. It works just fine now.
[Galaxy Note 10.1 Android Development] :
I have had zero issues so far. I flashed the standard version if the rom and pa mini gapps using cwm 6.0.4.4. Ive got no screen issues... All apps are running fine. All of my video apps are working after doing that xposed module.

No issues to report atm

---------- Post added at 07:39 PM ---------- Previous post was at 07:34 PM ----------

Could you link to the zip?? Thanks in advance
[Galaxy Note 10.1 Android Development] theatomizer90:
http://xdaforums.com/showthread.php?p=44620661

This is to the specific post. Just flash his zip and it should work. That's what I did and no adverse effects.... Yet... :P

tubas..... tubas everywhere....
[Galaxy Note 10.1 Android Development] dvijetrecine:
damn, and i just moved to another rom because online videos didn't worked. well, back to flashing then
[Galaxy Note 10.1 Android Development] phearus:
You are correct. That is almost about as OT as you could get. May I suggest you look elsewhere, perhaps the N8000 CM thread for assistance on this matter.

There are no longer any Note 10.1 CM maintainers - so expect things to get worse, not better, with that project.

Simple fix - don't use the latest nightlies - they are unstable by definition.

Back on topic:

[MENTION=3125261]iofthestorm[/MENTION] - are your recoveries build directly from TWRP github source, or a fork taken from some time afew weeks ago?

I ask as the official N8000 builds (or at least the distributed builds for this device) had something weird going on with them; the build.prop in the recovery was not for the N8000, so flashes would always fail at the device check before the flashing process. Do you build remedy this? I guess this question is also targeted at the other N8000 testers, too.

Thanks.
[Galaxy Note 10.1 Android Development] iofthestorm:
My recoveries are built from the omnirom repo: https://github.com/omnirom/android_bootable_recovery . I think TWRP is sort of "merging" with OmniROM as Dees_troy has been committing to this repo through gerrit, so this is basically directly from TWRP (the TeamWin repository doesn't even seem to be as up to date).

However, the device specific configuration is partly from me and partly from the smdk4412-common repository; I'm pretty sure I've done something wrong because people have pointed out that backups don't work properly. Personally I don't actually use those backups, I prefer to just have Titanium Backups of all my apps/data and just flash a new ROM and restore my apps that way - recovery backups take too long to make :P. Some parts I did take from the TeamWin repositories but as you've said I'm not really sure if even they had a proper configuration for the Note 10.1 devices, since there have always been glitches with TWRP.

So in the end, I don't really know if my recovery works at all for any purposes besides flashing OmniROM. But that's all I use it for, so it works for me. At some point I probably want to poke Dees_troy or bigbiff about getting it fixed up and releasing a new official version but it's not really urgent to me.

On another note, [MENTION=1466338]TheMorpheus[/MENTION] said he was able to boot my N8000 ROM but it was very laggy, so that's some good news. Hopefully we can work something out (hopefully it's simple) and upload something here soon. He also mentioned that my TWRP was basically useless for anything besides flashing the ROM.

Oh yeah, and for anyone who wants to play along at home, here's my local_manifests.xml so you too can build OmniROM for n8013 or n8000. Especially n8000 owners who know how to build ROMs, it would be useful to have more of you testing so we can get the bugs fixed and release something here! (If you knew how to build ROMs it should have been clear what to put in this file anyway, but just putting it out there for anyone who wasn't sure).

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/n8013" name="ibrahima/android_device_samsung_n8013" remote="github" revision="android-4.4" />
<project path="device/samsung/n8000" name="ibrahima/android_device_samsung_n8000" remote="github" revision="android-4.4" />
<project path="device/samsung/n80xx-common" name="ibrahima/android_device_samsung_n80xx-common" remote="github" revision="android-4.4" />
<project path="packages/apps/SamsungServiceMode" name="CyanogenMod/android_packages_apps_SamsungServiceMode" remote="github" revision="cm-10.2" />

<project path="vendor/samsung" name="ibrahima/proprietary_vendor_samsung" remote="github" revision="android-4.4" />
</manifest>

You'll also need to cherry pick these two changesets from gerrit: https://gerrit.omnirom.org/#/c/3011/ and https://gerrit.omnirom.org/#/c/3012/ .
[Galaxy Note 10.1 Android Development] MJ-12:
Yes I guessed that.

I was just wondering has anyone tried another kernel with overclocking?

BTW OP keep up the great work. I was happy with my note and the costume rom I was running but this is a brand new tablet now, smooth, new features, quick, great battery charging and very slow drainage while using.

You have brought my 8010 right bang up to date...

Cheers :)

MJ-12
[Galaxy Note 10.1 Android Development] sudisk:
Well I finally managed to install the N8000 version.

I updated my Philz recovery to the latest version and the installation went smoothly.

The rom seems to work fine, phone works and I did not have any fc of any kind.

The only thing that bothered me, because I forgot to anticipate it, is the change of mount point for the SD card, which is not at the root of internal storage anymore, but in /emulated/0.

I could't access anything in my internal storage, so my tests were a bit limited. However this rom seems quite ready for diffusion to a larger audience, provided that you add some information in OP for users coming from a Samsung ROM.

FYI using latest Philz allowed to easy switch back and forth between Omni 4.4 and Sammy 4.1. No exclusivity for kitkat or jellybean.

Great work!
[Galaxy Note 10.1 Android Development] TheMorpheus:
Did you installed this: philz_touch_6.00.8-n8000.zip
[Galaxy Note 10.1 Android Development] sudisk:
Yes, that one.
[Galaxy Note 10.1 Android Development] iofthestorm:
Ah, that's pretty neat, I will start recommending people use that recovery then rather than my TWRP (though I do want to fix up TWRP for this device, better for users to have a working recovery).

Also, cool news, the Omni guys are on a Christmas merging spree and they asked me about merging my stuff for n8013, so hopefully soon we'll have official nightlies! The only drawback is that they won't have Multiwindow until it's actually "finished" so I may continue putting out builds with that if people want it - though I'd rather focus on fixing bugs than putting out builds, so I'll probably upload builds at most once a week (which is about as often as I've been doing it anyway).
[Galaxy Note 10.1 Android Development] iofthestorm:
I'm fairly certain that there won't be any other kernels that work with this ROM, because this ROM's kernel uses the Mali r3p2 drivers and associated blobs (part of the system image) whereas CM uses r3p1, so probably all custom kernels are using r3p1 and will basically fail to show any graphics.

I'm also pretty sure that the lack of overclocking is some sort of bug in the configuration for the n8013 kernel, because performance controls are built into OmniROM and so it should be supported out of the box. I might look into it at some point but it's a low priority for me, because IMO overclocking can only cause problems and is rarely actually worth it.
[Galaxy Note 10.1 Android Development] iofthestorm:
Alright, here's a pair of new builds - thanks to the brave N8000 testers, we've confirmed that my N8000 build works okay! There might be some audio bugs and potentially other bugs but it seems like overall it's usable. Download the correct version for your device!

omni-4.4.2-20131225-n8013-HOMEMADE.zip

omni-4.4.2-20131225-n8000-HOMEMADE.zip

For new users/N8000 users, I now recommend using Philz touch recovery rather than mine, because he actually knows what he's doing with regards to recoveries ;). I do intend to finish fixing up my TWRP configuration though but until then it's better to use PhilZ, he seems like a swell guy and his recoveries are up to date for Kitkat support. I actually know now what's wrong with my TWRP but haven't figured out how to fix it yet.

There haven't been many feature changes in Omni really recently, but I tried to fix camcorder audio - now it records, but something is funky and it sounds doubled and weird so it's probably still not usable unless you're going for some sort of dubstep effect :P
[Galaxy Note 10.1 Android Development] MJ-12:
Hi, thank you for your detailed answer. I have to say I am well pleased with your rom regardless of lack of over clocking, it just would have been a bonus that I would have been very keen to implement to make this 4.4.2 even sweeter :)

I was starting to get really bad battery life from my previous rom (abnormally fast drainage and very very slow charging) and had tried lots of things to remedy this all to no avail. Now thanks to you I have a new tablet with great battery life... So, again a big thank you.

Merry Christmas

MJ-12
[Galaxy Note 10.1 Android Development] ©h®is:
rom is running super smooth on my n8000 :)

thx for your great work!

merry Christmas

unfortunately there is no sound when i want to play music, movies, etc.. :(

anyone else?

log: https://db.tt/ea5l4oQP
[Galaxy Note 10.1 Android Development] al5911:
Really want to try this on my N8000 but this stop me :(
[Galaxy Note 10.1 Android Development] tsukaza:
Just saw the 2013-12-25 n8013 ROM, dling now, thanks for the gift.

Successfully dirty flash over the previous 4.4.2.1 ROM and so far so good, thanks.
[Galaxy Note 10.1 Android Development] chmuts:
Thank you for bringing 4.4 to the N8000 thanks for your all hard work and the testers.
[Galaxy Note 10.1 Android Development] iofthestorm:
Yeah, TheMorpheus did notice that as well. Just wondering, do you have headphones in, and if not, can you try playing audio with headphones in and see if it works? And get a logcat of that too either way, just curious what it looks like.

It's weird because N8013 didn't have that problem but I wonder if because the N8000 has a 3G radio something somewhere is making it think it has a headset as well, since there is stuff in your log about a headset, and when it tries to play to the nonexistent headset it dies. I'll look into it some more, the good thing is that there aren't too many places the N8000 and N8013 code are different, but of course the bad thing is that I can't test it myself.
[Galaxy Note 10.1 Android Development] dbolivar:
First, thanks a lot [MENTION=3125261]iofthestorm[/MENTION] for all the hard work! The ROM is super smooth, and it's nice to have the latest Android version for our tablet.

I just tested the Dec. 25th version, and confirmed the following issues:

1) Video recording now works with audio, but the audio quality is bad. It is like a wrong sampling rate or codec. However now a problem I noticed on the previous version is solved: the device was rebooting after pressing the "back" button from the Gallery, when called from the camera (e.g. reviewing a photo just taken, on the Gallery, then pressing "back" to return to the camera), and now it's OK.

2) No sound: some people reported this, so I investigated the scenarios a little deeper.

2.1) The sound works normally right after boot. However, if I play a song, YouTube or whatever, stop, wait a few seconds, and play again, there's no sound.

2.2) The issue seems to only happen on the headphone, as the play / stop / play scenario works with the speakers. And if I unplug and replug the headphone, it works again.

2.3) I tried several audio mods: Viper4Android, Noozxoide and Alsa Mixer, but the issue continues, so it's something low level. Only unplugging/replugging the headphone, or rebooting, to make it work again.

2.4) I also tried PowerAmp, which has a direct volume control, but it didn't help.

Hope it helps your efforts to perfect this ROM. Thanks again!

P.S.: I own a N8010, compatible with the N8013.
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh interesting, so you've experienced this sound problem on N8010 as well? That's weird, I can't reproduce it on my N8013; I plugged headphones in, played music, paused, played again, it still worked. Tried Google Play Music, the stock Music player (Apollo), and Youtube.

Have you (or anyone else experiencing this issue) changed anything in DSP Manager, or any other sound related options? Has anyone else noticed this issue on N8010/N8013? Now I'm really perplexed.
[Galaxy Note 10.1 Android Development] TheMorpheus:
I tried with the headphones but still doesn't play music.

YouTube doesn't work either, so this 2 issues make the rom NOT a daily driver... I hope you can figure out soon... It is time to switch to 4.4 ?

Thanks for your work, always available for testing!

Marry Christmas!

Sent from my GT_N8000