yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] Jiggs82:
Woohoo thanks for bringing 4.4 for the note 10.1 downloading now and will report back :D

---------- Post added at 05:23 PM ---------- Previous post was at 04:35 PM ----------

Hey guys for some reason I'm having trouble flashing ROM using twrp 2.6.3.0 it keeps saying failed I'm red and I full wipe data dalvik and cache , anything I need or doing wrong? Thanks
[Galaxy Note 10.1 Android Development] :
Did you try using the recovery IMG posted in OP? Recovery needs to support selinux. Otherwise try cwm 6.0.4.4.
[Galaxy Note 10.1 Android Development] Jiggs82:
Yeah I got to flash it through cwm touch :)
[Galaxy Note 10.1 Android Development] theatomizer90:
I've been using this rom all day and it seems like it works just fine. But I will keep it on for the next few days and see if i get any bug bites. The only downside is the lack of features. Like in cm Roms but I would rather alpha and beta builds be slim and stable.
[Galaxy Note 10.1 Android Development] :
I know that with CM it takes a bit before all the features get merged back in after a new version of Android. I would guess omnirom is the same.

I agree though, this port is very stable. Can be used as a daily driver i.m.o.
[Galaxy Note 10.1 Android Development] theatomizer90:
Ouch! I got bit. Before I report it I want to see if someone else can reproduce or confirm it. Play music then turn off your screen or unlocking the screen causes the transformer inside your note to yell.

tubas..... tubas everywhere....
[Galaxy Note 10.1 Android Development] :
Lol I like your bug bite metaphor. I'll see if I can reproduce when I get home.
[Galaxy Note 10.1 Android Development] :
I can confirm this bug. Almost like the music app freezes for a second when the screen locks / unlocks

---------- Post added at 02:35 AM ---------- Previous post was at 02:15 AM ----------

Replicated using Google play music
[Galaxy Note 10.1 Android Development] iofthestorm:
Hah, nice catch! I can confirm that it happens to me too, go ahead and report it if you haven't already.
[Galaxy Note 10.1 Android Development] theatomizer90:
I just realized I have no clue how to report a bug.

tubas..... tubas everywhere....
[Galaxy Note 10.1 Android Development] theatomizer90:
Oh I got it. I just realized maybe there was something I couldn't see on tapatalk, so I went to the web and saw it.

tubas..... tubas everywhere....
[Galaxy Note 10.1 Android Development] RETIEF:
64gb card doesn't work

The rom seems nice but my 64gb card won't mount. It is a deal killer for me.
[Galaxy Note 10.1 Android Development] sudisk:
Reformat your card using FAT32. There is no support for exfat yet in omni.
[Galaxy Note 10.1 Android Development] theatomizer90:
For the music bug, If you disable lockscreen it works just fine. I installed a new lock screen, a 3rd party app.
[Galaxy Note 10.1 Android Development] iofthestorm:
Good news, they fixed it! New build is up, see changelog in http://xdaforums.com/showpost.php?p=48013232&postcount=3

Also, you all should go buy all of xplodwild's apps because he just got Multiwindow sort of working again on Kitkat! A lot of apps are crashing and the back button is just weird but you can at least try it out now! See https://plus.google.com/u/0/+IbrahimAwwal/posts/24wN1Jg23np for a screenshot.
[Galaxy Note 10.1 Android Development] sudisk:
[MENTION=3125261]iofthestorm[/MENTION]

Hi, I would like to build for N8000. Do you know what to put in the local manifest for the device packages?

Thanks
[Galaxy Note 10.1 Android Development] iofthestorm:
If you look in the OP, I have omni-4.4 compatible device trees for n80xx-common and n8013 on GitHub. You can use my n80xx-common (maybe fork it in case you need to make changes) and look at my commit history in android_device_samsung_n8013, and then fork android_device_samsung_n8000 from CM and basically follow what I did for n8013.

The last thing you'll need is blobs, you can try and find the "secret" blob repo by following Omni developers on GitHub. But you'll need to import the blobs for N80xx from the CM blob repo since the Omni one doesn't have them yet. One thing to note is that OmniROM switched to Mali r3p2 drivers from r3p1 I believe, so those corresponding blobs must be updated as well. Never mind, those blobs are shared so nothing needs to be done there, just make sure you clone Omni 's blob repo and not CM's. Sorry I have to be vague about blob stuff, I don't think anyone really understands the legal issues surrounding them (I certainly don't) so it's kind of a weird gray area. PM me for more explicit info if you get stuck, I think that should be okay (I'm about to go to sleep though).
[Galaxy Note 10.1 Android Development] jusliloleme:
Ho-kay! After going through a few hoops, I managed to screw up my tablet and had to go back to square 1 (stock). That may be due to running outside into the -20 degree air to try and get my car started, to no avial, and then running very, VERY quickly back inside to warm up. Anyway, I managed to get Philz latest installed, load 0104 (after doing a clean everything) and then did the System Update to 0106. However, during the flash to 0106, Little Android Dude went belly up (red ! coming out of his reclined body just like Alien!). Some text flashed by way too quickly for my tired, old eyes to see what it said then my tablet rebooted and lo-and-behold, there was 0106. I'm sure there's some log someplace that will contain the information that I couldn't read, but I'm not sure where to go snooping to find it.

At any rate, based on usage of 0106 for less than an hour, I'm not seeing any problems. So far. Of course if I do see any problems, based on the day I've been having, it will most probably be operator error :p

I think I'm just going to sit with 0106 for a bit unless a release comes along with some major updates.
[Galaxy Note 10.1 Android Development] planetf1:
Updated fine here with philz recovery on my n8010 which thinks its a n8013...
[Galaxy Note 10.1 Android Development] Kidromulous:
Hmm not sure I like this build in terms of performance lots of lag for me especially when I switch apps or hit the home key. Anyone else having that issue.
[Galaxy Note 10.1 Android Development] MJ-12:
+1
[Galaxy Note 10.1 Android Development] iofthestorm:
Were you using my TWRP from the OP? That's weird...

The reason gapps and su weren't restored seems to be because the flash failed right before, and the error message looks like the one you used to get on recoveries that don't support SELinux properly. Hmm... maybe I should just disable the update feature since it's not so reliable, and work on fixing up TWRP so that when we actually have nightlies they can be auto updated correctly.
[Galaxy Note 10.1 Android Development] iofthestorm:
Hmm, now that you mention it I'm seeing the same thing, both the home and multitasking buttons seem unresponsive for a second or two after you press them. :(
[Galaxy Note 10.1 Android Development] Kidromulous:
For me it's any transition and also when you press on the screen to bring up the keyboard. If it helps the build before this was smoother but before that it was a bit sluggish much like this one.
[Galaxy Note 10.1 Android Development] kylew1212:
I am experiencing a slight lag as well. Its not bad, and barely even noticeable (until mentioned I didn't notice).

Also, I've found a few other random issues as well.

1. When opening stock camera app, it defaults to front camera (no big deal) however when in try to rotate to the back camera, my tablet auto reboots.

2. Screenshots work if holding down the power button then selecting screenshot, but if you hold power + volume down for the quick screen shot the device freezes.

Oh and I'm using phillz recovery, and your update server worked going from 1/4 to 1/6. I checked for updates, they downloaded then I selected flash. My tablet rebooted into recovery, installed the update, and then rebooted again to normal as expected. There were absolutely no issues, it worked perfectly!
[Galaxy Note 10.1 Android Development] Nemury:
Just upgrade with not issue using CW
[Galaxy Note 10.1 Android Development] usopjidin:
Install fresh from Stock rom. I notice my baseband has been changed and I am unable to connect to broadband. However, 3G works fine.
[Galaxy Note 10.1 Android Development] planetf1:
Yes I think a little lag here too. The previous builds were positively snappy, this one is merely just fine

---------- Post added at 09:27 AM ---------- Previous post was at 09:02 AM ----------

I just went back to the 20130104 n8013 build and was immediately reminded how much snappier it was. Its a significant difference
[Galaxy Note 10.1 Android Development] planetf1:
I've also noticed my Google contacts are not up to date. Sync is running ok, and my other device is fine (s4 stock)... I think someone else mentioned this. Perhaps more a general omnirom issue that something port specific. Its not such a big deal on my tablet anyway
[Galaxy Note 10.1 Android Development] Kidromulous:
Ill just say stock touch wiz is way more responsive at this point. Flashed back up till I figure out whats the reason. Im still new to this device so I forgot how powerful the hardware actually is.
[Galaxy Note 10.1 Android Development] MJ-12:
My 8010 is great! (Shows as an 8013)

A bit hard on the battery though

Keep up the great work :)

MJ-12
[Galaxy Note 10.1 Android Development] Kresh0:
Hello!

Firstly I would like to thank developer for doing a great thing! Thumbs up for that one.

But I have found some bugs that annoys time to time:

-Loading wallpaper after using application, or sometimes whole homescreens take 5-6 sec to respond after quiting application,

-sometimes screen image shakes for a second (drastic change since last update in a good way only occurs about once in hour),

-refreshing in storage, it takes full 5min to calculate storage data or app itself (even if its only 2mb file),

-sometimes opening app makes screen make double loop before opening,

-battery drains a lot by just typing, surfing (usually with other rooms I got atleast 7 hours just typing, now bout 4 hours), i didnt calibrate my battery maybe differend kernel?

I am using N8000. Tested s-pen and it works flawless, but I am not keen on it anyways. Otherwise apps works perfect and all, great ROM!

Sorry if some bugs are already mentioned and sry for bad english.

Cheers
[Galaxy Note 10.1 Android Development] wadken1:
Couple of things you can check quickly for battery life. Default OMNI settings for screen brightness and CPU Governer. I usually find that the auto brightness levels are set around twice a high as they need to be, particularly at the normal room lux levels, burning a lot of extra juice. CPU Governer can often bet set to Performance - you'll generally find it's just as responsive on Pegasusq and will improve battery life. Also, I'm using the "Deadline" scheduler rather than "cfg" - can't really say if this saves any juice but it does work well - i'm not experiencing the lags that many are mentioning here.
[Galaxy Note 10.1 Android Development] Kresh0:
Hi.

Tnx for the respond. Under perfomance tab i switched to perfomance and deadline. Hope will solve some problems.

But now i found another thing, processor 2 is offline. All others are to 1400mhz. Is this normal?

Cheers
[Galaxy Note 10.1 Android Development] wadken1:
I hope it's "Pegasusq" you've selected rather than "Performance" but Yes that's normal behaviour. Apart from scaling the operating frequency up and down to suit the current cpu load the CPU governers also use Hot Plugging to switch individual cpu cores on or off to save even more juice. Most of the time you are typing and browsing the CPU isn't actually needing to do a lot and it can cope quite easily on just 1 or 2 cores.
[Galaxy Note 10.1 Android Development] MoonPie2000:
Question about OTA zip manual update...

Just loaded ROM and love it so far - Great Work! :good:

I have Philz recovery and as noted above it does not perform OTA udpate successfully. My question is... Are there any risks by doing the below process:

- After checking for and downloading OTA update but prior to pressing FLASH NOW I located the location of the downloaded zip file - /storage/emulated/legacy/OpenDelta - and moved to SD Card storage. I then booted into Philz recovery and flashed the OTA update zip file successfully.

Since I am not aware of exactly what happens when doing the OTA OpenRecovery script update I wanted to make sure I have not done anything to compromise my system integrity. Thanks for your reply. :fingers-crossed:
[Galaxy Note 10.1 Android Development] Kresh0:
One more thing, how can I setup norma HD wallpapers? Reason Im asking that is bcuzz whenever I set my background from 3rd party apps all my wallpapers are zoomed in making picture pretty much worthless unless its plain blackground you can't tell difference. If I use system background I get nice sharp picture, but 3rd party apps (zedge, HD wallpapers - ofcourse for tablets) makes pixels or if its text I get only one word of it...
[Galaxy Note 10.1 Android Development] jusliloleme:
I use Simple Image Wallpaper which automatically sizes any background to fit the screen. It will also handle different backgrounds for landscape/portrait.

It works for both my tablet and our phones.
[Galaxy Note 10.1 Android Development] dvux:
Is the Whitescreen/flickering problem solved?

Gesendet von meinem GT-N8013 mit Tapatalk
[Galaxy Note 10.1 Android Development] iofthestorm:
Yeah, in a couple ways. The 1/04 builds have the s3cfb (framebuffer/LCD) driver update reverted, which fixes the issue and seems to have no other ill effects.

omni-4.4.2-20140104-n8000-HOMEMADE.zip

omni-4.4.2-20140104-n8013-HOMEMADE.zip

The 1/06 builds include a proper update of the s3cfb drivers to the version in the Samsung i9300 update 12 kernel release. Basically, in omni's kernel the driver was updated for i9300 but it wasn't clear at the time that it would affect other devices as well, and files needed for other devices were not included in the update, so we had sort of a partially updated driver. We added in the files for n80xx and that seems to fix the issues. But for some reason this build seems laggy, so I'd recommend sticking to 1/04 for now until I get a chance to debug further. But if you just want to help test, it's here:

omni-4.4.2-20140106-n8013-HOMEMADE.zip

Once we figure out if there are actually issues with the s3cfb update and fix them, there's just one other thing to fix and then I think we'll be ready for nightlies. Probably gonna have to be my weekend project, as school has started up for me again.

Also, going forward, we've decided to rebrand the n8013 build as n801x and allow it to be installed on n8010 as well, since it works on both devices. So when official nightlies come we'll do that. I don't know if n8000 will have nightlies yet, I haven't talked about it yet - not sure if we'd need an official maintainer with the device (Espenfjo is with OmniROM, at least he hangs out in IRC, but I think he's busy these days so he might not want to be an official maintainer).
[Galaxy Note 10.1 Android Development] Nemury:
Has anyone looking into the issue of recording with no sound, it does not bother me at all but it is a bug
[Galaxy Note 10.1 Android Development] iofthestorm:
During video recording? I found a sort of fix, but instead of no sound it recorded really distorted sound, so it wasn't really that much of an improvement. Right now I'm focused on cleaning up the blockers for nightlies but please remind me again once we have official builds.

Also, can I get some more feedback/information on the multitasking/home lag, or any other lag you guys are experiencing? I definitely noticed it after it was pointed out on the build from the 6th, but then I went back to the build from the 4th and I experienced the same thing. It's weird because I feel like I should have noticed it if it was present on the build from the 4th.
[Galaxy Note 10.1 Android Development] roywheels:
A huge thank you to iofthestorm for all the hard work you've already put into this rom. It's great to see omnirom on our note 10.1's! :good:

I installed the 06 version on my n8010 last night (installed through the iofthestorm TWRP) and, as you say, there's a bit of a pause here and there, but it seems very stable with no white screens or flickering issues as yet. I'm guessing the pauses are graphic driver related?

Whilst experimenting last night I installed the xposed framework and Gravitybox. My last everyday rom was CM10.2 and I love the pie control so it had to be tried out... It appears, in the limited time I've had to use it, to run without any problems. Expanded desktop and pie controls in a lovely omni 4.4 environment! :D

Is the expanded desktop/pie control likely to make it into Omni as a default option?
[Galaxy Note 10.1 Android Development] planetf1:
Its hard to describe the lag in the build of the 6th but it went away when i went back to the 4th.

Everything just seemed more sluggish.

Sorry i can't be more precise
[Galaxy Note 10.1 Android Development] wadken1:
Expanded Desktop is already available in Omni - it's call Immersive Mode and there's a quick Seetings tile for it. Works slightly differently in that while your apps are displayed full screen the status bar and nav bar are still available by dragging down from top or up from bottom. I like it a lot now.

Can't comment on PIE in Omni. No sign of it anywhere yet but maybe there'll be mention of in the main thread somewhere. I use LMT as it's the most flexible implementation I've yet found.

Cheers
[Galaxy Note 10.1 Android Development] roywheels:
Thanks for the tip! I didn't know about immersive mode- Just tried it out and it's a nice feature. No conflicts with the gravitybox pie either as far as I can tell.

It's probably not so great to use gravitybox with a custom rom but on this occasion, it works.
[Galaxy Note 10.1 Android Development] iofthestorm:
I'm just wondering if it's just a temporary post-flashing thing. I went back through the last 5 or 6 days worth of builds and didn't notice any improvement in the lag, which leads me to believe that it might just go away after the flash "stabilizes." And today I've been multitasking pretty heavily (I use my tablet exclusively for note taking in class, and often switch back between a PDF reader and my notetaking app) and noticed that the lag went away. But I also noticed yesterday and today that sometimes apps are missing from the recent tasks switcher, including one time where it was empty when I had opened 4 apps. So there might be some issue causing a delay in the population of the recent tasks, but I don't think it's specific to any driver versions. But I'm not sure. Either way, I think we'll just assume the patch is fine for now and if there is truly a performance regression we'll try to figure out why that is.
[Galaxy Note 10.1 Android Development] Kidromulous:
Weird. My note just must be finicky. Takes a full 3 or 4 seconds to get back home or multitask. I get better responsiveness on touch wiz. Each device is different I suppose.
[Galaxy Note 10.1 Android Development] iofthestorm:
Well, what I meant was that I did see that at first (full 3-4 seconds too), but it seems to have gone away now. But I think the culprit might have been the memory indicator on the recents view - something was just merged about fixing endless loops and it running when it wasn't supposed to. I'll do a test build in a few hours and see if it's better.
[Galaxy Note 10.1 Android Development] greekunit690:
A couple of questions...

1. Is there any way to bring the navigation buttons back to absolute left?

2. Can we bring the stock tablet mode back with the single notification page coming up from the bottom? Not too fond of how its split coming from the top.

Thanks a lot for an otherwise GREAT rom!!!
[Galaxy Note 10.1 Android Development] roywheels:
Fwiw, I've not seen anything like 3-4 seconds of lag on any function on the 06 build. It was a clean install and I made sure not to let Google reinstall every app I had on my CM10.2 build.

Isn't the speed of moving to the Home screen affected by the launcher you're using?
[Galaxy Note 10.1 Android Development] greekunit690:
I believe its actually if you have anything assigned to the home button as in double tap for recents and stuff like that
[Galaxy Note 10.1 Android Development] DutchmanIII:
Oops, now you mention it, it must have been the original version. sorry bout that!
[Galaxy Note 10.1 Android Development] iofthestorm:
On that note, could some of you guys test this recovery? Basically want to know if all the functionality works as desired, or if not what's broken.

http://dev.ibrahimawwal.net/omni/n8013/recovery.img

I've bumped the version to 2.6.3.1 to distinguish it from the last official release which doesn't support Kitkat, and I've also fixed the touchcscreen glitchiness.
[Galaxy Note 10.1 Android Development] israel_andrade:
Question about Recovery File

Will this be a "Dirty" type recovery or will it wipe out my tablet and be a clean load? I've never done a Recovery before, This is an IMG file, please advise on the recovery steps

Israel (Noob)
[Galaxy Note 10.1 Android Development] darksabre_x:
Flashing a recovery does not generally wipe your entire tablet. The recovery is on a separate partition.
[Galaxy Note 10.1 Android Development] Jamin13:
Is there an issue with the IR? Multiple TV remote control apps have seemed to have incorrect output except for the power button output.
[Galaxy Note 10.1 Android Development] iofthestorm:
Most likely they just have the wrong mapping for your TV set? I haven't used it much but it works fine when I do use it, I can set volume and change channels as well. Though technically my TV is TCL and that's not listed in most apps, but I think RCA works for me usually. Do you use root apps or ones that support the Kitkat API (i.e. don't need root)?
[Galaxy Note 10.1 Android Development] israel_andrade:
Thanks, I figured it out. It is to Flash TWRP onto the partition as opposed to Philz which I just replaced . Took me a minute to realize that I needed to make the img file into a tar, then to md5 checksum. But I got it!!!! Now I have another issue, maybe you can shine some light on it...

My apps are not recognizing that the tablet is rooted. i.e. Titanium Backup says it is not rooted (it looks to run the su command in /system/xbin)

I am a little stumped on this one.

Thanks,

Israel
[Galaxy Note 10.1 Android Development] darksabre_x:
That's an easy one. The rom is not rooted by default.

There's a SuperSu zip on the first page you can grab and flash in recovery. Once you flash it, go to the play store and grab the SuperSu app.

And you're good to go.
[Galaxy Note 10.1 Android Development] Jamin13:
I tried using Peel and another one designed for Samsung devices from the Play Store. My TV is an older 720p Magnavox (didn't think they even made HD sets). I went ahead and bought Smart IR Remote to test if it would work and every command works fine. I think I'm going to stick with it.
[Galaxy Note 10.1 Android Development] iofthestorm:
Haha, you don't even need to do all that, you can just use an app like Flashify or Recovery Tools to flash it. Or the desktop program Heimdall, it works great too (invaluable if you're going to be doing dev work on Samsung devices really).

You'll need to flash SuperSU as someone mentioned.
[Galaxy Note 10.1 Android Development] wadken1:
I've installed and run a nand backup. GUI is working well. Backup seemed to work fine but haven't proved it with a restore yet. Will try flashing at next update.
[Galaxy Note 10.1 Android Development] Kresh0:
I have a question. Why cant i shoot videos? I mean nothing happens when i click red button. Camera wporls, but poor quality. Anyone had this issue?

Edit1: my bad i fixed it by going to 720p recording. But images are still poor quality. Even on 5m i see more pixels than on my old mobiles.
[Galaxy Note 10.1 Android Development] roywheels:
It works well. File manager and backup fine although I haven't tried a restore yet.

Thanks for fixing the touch glitch. That drove me crazy in previous twrp releases.